-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: 1.8.2, 1.9.1
-
Component/s: Replication, Sharding
-
None
-
Environment:Ubuntu 10.10 x86_64
-
ALL
To test the mongoDb sharding capabilities we have continuously inserted data into a single shard consisting of one replica set (1 Master, 1 Secondary and 1 Arbiter). Almost every time a chunk is splitted (as indicated by the mongod log file of the master) a MongeException "norepl" occurs. We are using the mongo java driver 2.6.2 but could also reproduce the problem with the php driver.
This only happens when we use the WriteConcern "ReplicasSafe".
To reproduce the problem a java maven project is attached to this issue. Here are the necessary steps to run the application:
- Read the README.txt to see the necessary test setup.
- Adapt the "config.properties" to use the correct mongos uri and writeconcern.
- Start the Inserter (located in src\main\java\com\seitenbau\testing\mongo\runner) main method and watch the console output.
- duplicates
-
SERVER-5243 mongos will route getLastError command to the config server when last insert triggered a split
- Closed