Details
-
Bug
-
Resolution: Fixed
-
Major
-
3.0, 3.0.1, 3.0.2, 3.0.3, 3.1.0, 3.1.1, 3.1.2, 3.1.3, 3.1.4, 3.1.5, 4.0.0, 4.1.0, 4.1.1, 4.1.2, 4.5.0
Description
The call to c->cb.callback doesn't check the status of the cb object for !SUCCESS after the call.
The cb object is an instance of LoadStorageKVPairCallback which sets status to ENOMEM when warmup is done.
This is quite hard to reproduce (i.e. not yet reproduced) as you need a severe DGM (big vbuckets) so you don't stop warmup at the metadata loading phase, but continue to loading access logs and find that say the first shard fills memory. The other threads will keep calling back using batchWarmupCallback without stopping.
However reviewing the code reveals the issue.