-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: 4.2.20, 4.4.18
-
Component/s: Performance, Querying, WiredTiger
-
Labels:
-
Environment:java client driver on client side - 3.12.9
mongo version - 4.2.20 (for 2 data members)
mongo version - 4.4.18 (for 2 data members)
Storage Engine - WT
Storage Type - tmpfs
Replica-set : 7 members (4 non-arbiter and 3 arbiter , all voting members)
One of the member CMD as an example:
mongod --keyFile=/mongodb.key --enableMajorityReadConcern false --ipv6 --bind_ip_all --port 27021 --dbpath=/data/db/wt-27021 --replSet rs-shard-2 --quiet --slowms 500 --logpath /data/db/mongo-27021.log --setParameter diagnosticDataCollectionEnabled=true --logappend --oplogSize 3221 --logRotate reopen --wiredTigerCacheSizeGB 4.40java client driver on client side - 3.12.9 mongo version - 4.2.20 (for 2 data members) mongo version - 4.4.18 (for 2 data members) Storage Engine - WT Storage Type - tmpfs Replica-set : 7 members (4 non-arbiter and 3 arbiter , all voting members) One of the member CMD as an example: mongod --keyFile=/mongodb.key --enableMajorityReadConcern false --ipv6 --bind_ip_all --port 27021 --dbpath=/data/db/wt-27021 --replSet rs-shard-2 --quiet --slowms 500 --logpath /data/db/mongo-27021.log --setParameter diagnosticDataCollectionEnabled=true --logappend --oplogSize 3221 --logRotate reopen --wiredTigerCacheSizeGB 4.40
-
ALL
-
Scenario - We run tests with same load on 2 mongo versions(4.2.20,4.4.20).
We found high query response(in range of 3-4 seconds) and very high cpu(100%) on primary for 4.2.20 version but no issue was found on 4.4.18
- As per the suggestion in Server-67217, we also collected disk usage but we did not find any high disk read/write at the issue time.
- In Server-67217, we did same test between (4.2.20 and 4.0.27) and still issue was found on 4.2.20 primary members only.
- Kindly refer Server-67217 for more details about the issue.
Note: Please provide cloud link to upload respective logs.
- is related to
-
-
- Closed
-