[SERVER-23820] "Operation timed out" when enableSharding on large collection in Microsoft Azure Created: 20/Apr/16  Updated: 22/Apr/16  Resolved: 20/Apr/16

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

Type: Bug Priority: Major - P3
Reporter: Jörg Rech Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-23784 Don't use 30 second network timeout o... Closed
Operating System: ALL
Participants:

 Description   

We've set up a MongoDB 3.2.5 cluster on Microsoft Azure with 3 shards (each a replica sets with 3 servers) and a 3-server config set. We access the cluster via a router.

Filling and sharding smaller collections (~400 million documents) worked with sh.shardCollection(). However, after filling a new collection with ~1.8 billion documents we tried to shard this new collection but keep getting the following error:

{ "code" : 50, "ok" : 0, "errmsg" : "Operation timed out" }

Note: At first we also had timeouts with count() and chunk balancing. After decreasing the TCP keepalive on all servers in the cluster below 240 seconds (the Microsoft Azure timeout) - based on the info at https://docs.mongodb.org/manual/faq/diagnostics/#does-tcp-keepalive-time-affect-mongodb-deployments - counting and balancing worked again. However, sharding our big collection still does not work.

Might be connected to Issue SERVER-22392



 Comments   
Comment by Ramon Fernandez Marina [ 22/Apr/16 ]

joerg.rech, this is to let you know that a 3.2.6-rc0 release candidate has been released today. If you give it a try please let us know if it addresses your needs.

Thanks,
Ramón.

Comment by Daniel Pasette (Inactive) [ 20/Apr/16 ]

We're planning to publish a release candidate for 3.2.6 tomorrow or Friday. If no additional issues come up, the production release should be released at the end of next week.

Comment by Jörg Rech [ 20/Apr/16 ]

Cool, any hope that 3.2.6 will be released in the next week? If not I can try to reload the data into a collection already sharded (which will take some days).

Comment by Kelsey Schubert [ 20/Apr/16 ]

Hi joerg.rech,

Thank you for opening this ticket. I believe the issue you are describing is a duplicate of SERVER-23784. A fix for this behavior will be included MongoDB 3.2.6 when it is released.

Kind regards,
Thomas

Generated at Thu Feb 08 04:04:33 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.