[SERVER-19280] messy database names in mongos Created: 03/Jul/15 Updated: 09/Jan/16 Resolved: 09/Jan/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.0.3, 3.0.4 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | DaixiShi | Assignee: | Unassigned |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | ALL |
| Sprint: | Sharding B (10/30/15) |
| Participants: |
| Description |
|
I have a sharded cluster with 4 shards using MongoDB 3.0.3 and WiredTiger engine. |
| Comments |
| Comment by Ramon Fernandez Marina [ 09/Jan/16 ] |
|
tottishi05, we haven't heard back from you for some time so I'm going to close this ticket. If this is still an issue for you please let us know so we can reopen the ticket. Regards, |
| Comment by Sam Kleinman (Inactive) [ 11/Nov/15 ] |
|
Hello, Sorry for not getting back to you sooner. I think that there are a few things we can do to move this forward. First, we want to be absolutely sure that we can rule out an issue with your driver:
Secondly, and perhaps more importantly it's very possible that you've run into an issue that the change included in Could you consider running your application in a test environment using 3.2.0-rc2? Thanks for your time, and sorry again for the delay. Cheers, |
| Comment by DaixiShi [ 14/Jul/15 ] |
|
shard04 with correct namespace |
| Comment by DaixiShi [ 14/Jul/15 ] |
|
shard01 with messy collections |
| Comment by DaixiShi [ 14/Jul/15 ] |
|
Thanks for Kaloian Manassiev. |
| Comment by Kaloian Manassiev [ 13/Jul/15 ] |
|
Some notes on the progress of investigation: In MongoDB 3.0 every request, which needs to check for the existence of a particular namespace, whether it is read or write, would create a database entry. This was fixed in 3.2 as part of Since the databases with the messy names are only present on MongoS (i.e., the config metadata) but not on the shards themselves, this must either have been a read operation, or it was a write operation, which subsequently failed on MongoD. |
| Comment by DaixiShi [ 08/Jul/15 ] |
|
Hi, Kaloian Manassiev. |
| Comment by Kaloian Manassiev [ 07/Jul/15 ] |
|
Thank you for the information, tottishi05. Let me check around to see whether there are some known issues with the C# driver at this version. As of this time I am working on the hypothesis that the driver somehow sent a wrong BSON and the command value was interpreted as a database name instead of command, so it should not be related to the combination of 3.0.3 and 3.0.4 in any way. Did this issue happen over a recent time period and is there any possibility that you still have the mongos log files from around the time it happened? If you still have them, would you mind attaching them to the ticket - this may greatly help with debugging. Note that if you are uploading logs and they may contact any sensitive information, send me a private message and I will give you a secure SCP server. Thank you for your help. Best regards, |
| Comment by DaixiShi [ 07/Jul/15 ] |
|
Thanks for Kaloian Manassiev! So, do you think my problem is associated with my mongodb version of 3.0.3 and 3.0.4?? |
| Comment by Kaloian Manassiev [ 06/Jul/15 ] |
|
Hi Daixi, Thank you very much for reporting this issue. From a first look, it appears like the messed up database names include partial BSON binary data from a command (for example, the two that begin with MediaDissector). What driver are you using to connect to mongos? I am wondering whether the driver might be constructing an incorrect command namespace, which in turn was incorrectly interpreted by mongos as the name of the database instead of as a command action. Also, did this happen after an upgrade or clean 3.0 install and are all of your instances (both mongos and mongod) at 3.0? Thank you in advance. -Kal. |
| Comment by DaixiShi [ 03/Jul/15 ] |
|
I have two mongos process. |
| Comment by Ramon Fernandez Marina [ 03/Jul/15 ] |
|
tottishi05, do you observe the same behavior in all your mongos nodes? Can you please connect to all your mongos instances and run the same commands? |