-
Type:
Bug
-
Resolution: Duplicate
-
Priority:
Critical - P2
-
None
-
Affects Version/s: 2.0.4
-
Component/s: Performance, Tools
-
None
-
Environment:CentOS 6.2 x86_64 - Runnig on VMWare ESX
-
ALL
-
None
-
None
-
None
-
None
-
None
-
None
-
None
I have observed and been able to duplicate mongorestore running very slowely when restoring data to a sharded cluster while using auth. I setup a simple test cluster for the below examples:
Before Auth: (fast, about 10MB/sec)
Restore to mongos:
[root@testserver scratch]# /opt/point2/mongodb/bin/mongorestore --host
mongotest --port 27017 -d testdb properties.bson
connected to: mongotest:27017
Mon Apr 30 15:52:12 properties.bson
Mon Apr 30 15:52:12 going into namespace [testdb.properties]
9168618/20325604307 0%
21463896/20325604307 0%
33556308/20325604307 0%
45867960/20325604307 0%
After Auth: (slow, about 3MB/sec)
Restore to mongos:
[root@testserver scratch]# /opt/point2/mongodb/bin/mongorestore --host
mongotest --port 27017 -d testdb -u user -p password properties.bson
connected to: mongotest:27017
Tue May 1 08:37:05 properties.bson
Tue May 1 08:37:05 going into namespace [testdb.properties]
2656954/20325604307 0%
7127948/20325604307 0%
10420282/20325604307 0%
15139072/20325604307 0%
Restore to replica set primary with auth: (fast, about 10MB/sec)
[root@testserver scratch]# /opt/point2/mongodb/bin/mongorestore --host
mongotest --port 27018 -d testdb -u user -p password properties.bson
connected to: mongotest:27018
Tue May 1 08:39:32 properties.bson
Tue May 1 08:39:32 going into namespace [testdb.properties]
9899255/20325604307 0%
23405742/20325604307 0%
36914260/20325604307 0%
50356611/20325604307 0%
This was a simple test setup that only contained 1 shard and 2 replica set members, the disparity in speed difference seems to be larger with a larger cluster. In our prod cluster mongorestore runs closer to 1MB/sec with auth against a mongos instance and 50MB/sec run directly against the primary server in one shard.
- duplicates
-
-
- Closed
-