keith-turner opened a new issue #992: Notifications never processed while running stress test URL: https://github.com/apache/fluo/issues/992 I ran the stress test against 1.2.0-SNAPSHOT on a single node with two workers. Two notifications were never processed. I did heap dump of the two worker processed and found one of them had two notifications in its NotificationProcessor.NotificationTracker.queuedWork set. However nothing in the process was working on these. There presences in the set prevent them from being added to the queue of notifications to process. Below are scans of the notifications. ``` ubuntu@cperf:~/git/stresso$ fluo scan -a stresso --raw -r 08:bq9d:08:000000001e7d3a3d 08:bq9d:08:000000001e7d3a3d count:wait [] 569030-TX_DONE 08:bq9d:08:000000001e7d3a3d count:wait [] 569030-WRITE 564254 PRIMARY 08:bq9d:08:000000001e7d3a3d count:wait [] 564254-DATA 1 08:bq9d:08:000000001e7d3a3d ntfy:count:wait [] 569030-INSERT ubuntu@cperf:~/git/stresso$ fluo scan -a stresso --raw -r 07:1do1:08:0000000036255e00 07:1do1:08:0000000036255e00 count:wait [] 569173-WRITE 562241 07:1do1:08:0000000036255e00 count:wait [] 562241-DATA 1 07:1do1:08:0000000036255e00 ntfy:count:wait [] 569173-INSERT ``` While looking into this I noticed that NotificationTracker.requeue() is not synchronized. Not sure if that has anything to do with this, but it seems like it should be synced. Killing the workers and restarting allowed the test to succeed.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
