[SERVER-31759] Sync Issue on sharded cluster Created: 28/Oct/17 Updated: 07/Jan/18 Resolved: 08/Dec/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 3.4.10 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kalpesh Chheda [X] | Assignee: | Mark Agarunov |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | Sync | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Windows Server 2016 |
||
| Attachments: |
|
| Participants: |
| Description |
|
I am having 3 Servers 3 ReplicaSet and 3 Shards. I have manually deleted database and its recreated using server application. Now in 2 server if I access data it is in sync buy 1 server is working as is own not in sync. Please some one help me. Before deleting it was working fine. All the 3 server database were in sync. If I do rs.status() and sh.status() its output looks ok to me if some one can check this It will be appreciated.
|
| Comments |
| Comment by Mark Agarunov [ 08/Dec/17 ] |
|
Hello KalpeshChheda, We haven’t heard back from you for some time, so I’m going to mark this ticket as resolved. If this is still an issue for you, please provide additional information and we will reopen the ticket. Thanks, |
| Comment by Mark Agarunov [ 01/Dec/17 ] |
|
Hello KalpeshChheda, We still need additional information to diagnose the problem. If this is still an issue for you, would you please provide the complete log files from all affected mongod and mongos nodes? Thanks, |
| Comment by Mark Agarunov [ 06/Nov/17 ] |
|
Hello KalpeshChheda, Thank you for the update. The location of the log files should be specified in the configuration file for mongod and mongos. I've created a secure upload portal so that you can send us these files privately. Thanks, |
| Comment by Kalpesh Chheda [X] [ 02/Nov/17 ] |
|
Hi Mark, Currently I have cleared everything and recreated the cluster again which is working fine now. I have saw bugs related to my issue which are still open So I decided not to delete database from onwards and keep working. But setup is still in testing I can recreate the situation. If you want some other logs please tell me, so I can get before and after logs as well. Thanks, |
| Comment by Mark Agarunov [ 30/Oct/17 ] |
|
Hello KalpeshChheda, Thank you for the report. To get a better idea of what may be causing this behavior, could you please provide the complete log files from all affected mongod and mongos nodes? This should provide some insight into why this node is not properly replicating. Thanks, |