Details
-
Bug
-
Resolution: Cannot Reproduce
-
Major
-
6.5.0
-
None
-
Untriaged
-
Unknown
Description
While investigating MB-31650, I noticed that we have a large volume of messages reporting getNumItemsForCursor_UNLOCKED being called for a null cursor :-
2018-10-15T04:28:48.185635Z WARNING (default) getNumItemsForCursor_UNLOCKED(): Cursor not found in the checkpoint manager on vb:655
|
2018-10-15T04:28:48.186274Z WARNING (default) getNumItemsForCursor_UNLOCKED(): Cursor not found in the checkpoint manager on vb:655
|
2018-10-15T04:28:48.187548Z WARNING (default) getNumItemsForCursor_UNLOCKED(): Cursor not found in the checkpoint manager on vb:655
|
2018-10-15T04:28:48.200844Z WARNING (default) getNumItemsForCursor_UNLOCKED(): Cursor not found in the checkpoint manager on vb:655
|
2018-10-15T04:28:48.202922Z WARNING (default) getNumItemsForCursor_UNLOCKED(): Cursor not found in the checkpoint manager on vb:655
|
2018-10-15T04:28:48.213579Z WARNING (default) getNumItemsForCursor_UNLOCKED(): Cursor not found in the checkpoint manager on vb:655
|
2018-10-15T04:28:48.216168Z WARNING (default) getNumItemsForCursor_UNLOCKED(): Cursor not found in the checkpoint manager on vb:655
|
2018-10-15T04:28:48.242530Z WARNING (default) getNumItemsForCursor_UNLOCKED(): Cursor not found in the checkpoint manager on vb:655
|
2018-10-15T04:28:48.244654Z WARNING (default) getNumItemsForCursor_UNLOCKED(): Cursor not found in the checkpoint manager on vb:655
|
...
|
While singular instances of this message are probably "expected" - possible when the front-end is say deleting a Cursor and the backend is just about to process messages for it - we don't expect to see multiple messages in sequence.
This might suggest some deeper issue with cursor management.