-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Response of /_up is Not valid Json on one Node #5009
Comments
Thank you for your report. Yeah that looks like a bug we should fix. |
looks simple. we use lists:ukeymerge but did not ensure the original list was in key order. probably change this to a map now, though. |
@rnewson good idea to use a map, I had actually started on a PR during the weekend but didn't add tests yet. I'll add some test and push it later to day for the review. |
as for why it also uses rotate_list at the start is a mystery to me given the later assumption that it is in key order. |
Gave it a try here #5025 We didn't have any tests for |
Description
We have a CouchDB Cluster with 3 nodes. If we query /_up we get good responses on node 2 and 3, but on node 1 we get invalid json.
{"status":"ok","seeds":{"[email protected]":{"timestamp":"2024-03-22T14:06:46.891827Z","last_replication_status":"error"},"[email protected]":{"timestamp":"2024-03-22T14:06:47.909114Z","last_replication_status":"ok","pending_updates":{"_nodes":0,"_dbs":0,"_users":0}},"[email protected]":{}}}
The Key
[email protected]
is duplicated in the output and because of that, json parsers error out.Steps to Reproduce
I don't know. I can reproduce this on our non prod cluster and can provide more logs or test things if needed.
Expected Behaviour
I expect the Json to be valid, just like the on below, returned by node3
{"status":"ok","seeds":{"node1.cust.local":{"timestamp":"2024-03-22T09:39:10.048682Z","last_replication_status":"ok","pending_updates":{"_nodes":0,"_dbs":0,"_users":0}},"[email protected]":{}}}
Your Environment
Three Nodes in one Cluster. The config of the affected node is down below. The config for all nodes are the same, except the node name and uuids and so on.
vm.args
local.ini
/_node/_local/_versions:
The text was updated successfully, but these errors were encountered: