-
Type:
Bug
-
Resolution: Done
-
Priority:
Major - P3
-
Affects Version/s: 2.4.0, 2.4.1
-
Component/s: Sharding
-
None
-
Environment:Config Server 1:
CentOS release 6.2 (Final)
db version v2.2.2, pdfile version 4.5
2GB Ram
1.5G in data directory
Config Server 2:
CentOS release 6.3 (Final)
db version v2.2.0, pdfile version 4.5
1GB Ram
1.5G in data directory
Config Server 3:
Ubuntu 10.04 Lucid (32 bit machine)
db version v2.2.2, pdfile version 4.5
512MB RAM
593 MB in data directoryConfig Server 1: CentOS release 6.2 (Final) db version v2.2.2, pdfile version 4.5 2GB Ram 1.5G in data directory Config Server 2: CentOS release 6.3 (Final) db version v2.2.0, pdfile version 4.5 1GB Ram 1.5G in data directory Config Server 3: Ubuntu 10.04 Lucid (32 bit machine) db version v2.2.2, pdfile version 4.5 512MB RAM 593 MB in data directory
-
ALL
-
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
When trying to perform an upgrade on the config servers, we get a timeout issue.
[code]
ERROR: error upgrading config database to v4 :: caused by :: error upgrading config database from v3 to v4 :: caused by :: could not copy config.chunks to config.chunks-upgrade-514cfc77fc5d397af47be301 :: caused by :: could not copy data into new collection :: caused by :: 13127 getMore: cursor didn't exist on server, possible restart or timeout?
[/code]
Our database consists of 18312, and of those, 16790 belong to a single collection.
I have attempted to repeat the upgrade many times, and the issue continues to occur.