[SERVER-16015] benchRun no longer working after switching PRIMARY replicaset member to a new node Created: 07/Nov/14 Updated: 15/Nov/21 Resolved: 10/Apr/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Tools |
| Affects Version/s: | 2.6.3 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Nikolaos Vyzas | Assignee: | Ramon Fernandez Marina |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Description |
|
Running this command worked both via mongos & directly on the replicaset until the primary node was replaced with a newly built node. The new node is of higher spec than the previous i.e. Initially we had: Then added Replicaset-node4 and removed Replicaset-node1 Final config: After that benchRun started reporting: Error: invalid parameter: expected an object ()
|
| Comments |
| Comment by Ramon Fernandez Marina [ 20/Mar/15 ] | ||||||||||||||||||||||||||||||||||||
|
Hi vyzas, apologies for the long delay. I finally got around to test this scenario using sharding and, to the best of my understanding, with a configuration that's analogous to you. This is what I did:
I was not able to observer the error you describe. I also tried replacing the primary while benchRun was not running, but I got the same result. If this is still an issue for you, can you please send us the logs for the mongos router as well as for all the data-bearing nodes in your cluster? Thanks, | ||||||||||||||||||||||||||||||||||||
| Comment by Nikolaos Vyzas [ 09/Dec/14 ] | ||||||||||||||||||||||||||||||||||||
|
Please add 3x config servers and 1x mongos router to your configuration, then enable sharding and run the test via the "mongos" service rather than directly on the replicaset. | ||||||||||||||||||||||||||||||||||||
| Comment by Ramon Fernandez Marina [ 04/Dec/14 ] | ||||||||||||||||||||||||||||||||||||
|
vyzas, I'm not able to reproduce the "invalid parameter" error message. This is what I did:
If you're still seeing this issue, could you post more detailed instructions on your setup so we can try to match it as closely as possible? Thanks, | ||||||||||||||||||||||||||||||||||||
| Comment by Alvin Richards (Inactive) [ 10/Nov/14 ] | ||||||||||||||||||||||||||||||||||||
|
vyzas@pythian.com the "cap" flag is just used for internal audit and verification. | ||||||||||||||||||||||||||||||||||||
| Comment by Nikolaos Vyzas [ 10/Nov/14 ] | ||||||||||||||||||||||||||||||||||||
|
What is required for CAP verification? The cluster is running in a single shard configuration with: 3x config servers |