[SERVER-17269] Fix concurrency and sharding tests in Rocks Created: 12/Feb/15  Updated: 25/Jan/17  Resolved: 13/Feb/15

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

Type: Bug Priority: Major - P3
Reporter: Igor Canadi Assignee: Benety Goh
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:

 Description   

Both of those tests started failing when we moved the data to a single column family. Both of them are failing because we report "wrong" storageSize(). When data is in a single column family it's a bit harder to report storageSize(), especially when bunch of bytes are in the write-ahead-log.

I'm fixing those tests by changing what we return in storageSize() to make tests happy. We could also make the changes to the tests.



 Comments   
Comment by Githook User [ 13/Feb/15 ]

Author:

{u'username': u'igorcanadi', u'name': u'Igor Canadi', u'email': u'icanadi@fb.com'}

Message: SERVER-17269 Fix concurrency and sharding tests in Rocks

Signed-off-by: Benety Goh <benety@mongodb.com>
Branch: master
https://github.com/mongodb/mongo/commit/c1b5595b5fdf93e0599bbdd4154f35bfa10fadd1

Comment by Igor Canadi [ 12/Feb/15 ]

Patch is here: https://github.com/mongodb-partners/mongo/tree/fixes

Generated at Thu Feb 08 03:43:51 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.