[SERVER-10229] Please improve the error message in movePrimary() Created: 16/Jul/13  Updated: 06/Dec/22  Resolved: 11/Jun/21

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Minor - P4
Reporter: Angshuman Bagchi (Inactive) Assignee: [DO NOT USE] Backlog - Sharding EMEA
Resolution: Done Votes: 1
Labels: Sharding-EMEA, neweng, pm-1051-legacy-tickets, sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Assigned Teams:
Sharding EMEA
Sprint: Sharding 10 (02/19/16)
Participants:

 Description   

A user tried to drain a shard and was moving a database which was primary on that shard. The move was unsuccessful as the nagios plugin they were using created a database in each shard with the same name and db.printShardingStatus() was incorrectly claiming that the shard to be drained was the only shard. When they tried to run movePrimary() this was the error message"

"errmsg" : "clone failed"

Can this error message be improved so that it provides a better indication as to what the error might be?



 Comments   
Comment by Tommaso Tocci [ 11/Jun/21 ]

The message now contains meaningful information with the actual error.

Comment by Remon van Vliet [ 13/Aug/13 ]

Same problem here. Note that you do see the full error in your logs.

Generated at Thu Feb 08 03:22:37 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.