java - Chronicle queue writes moveToIndex log on each empty read -
chronicle queue writes movetoindex log on each call on excerpttailer.readdocument(message)
after rollcycle reaches. log comes when there no messages available in queue. expected behavior? make problem if appender got idle long time ?
i have case reader stops reading messages , return false appender still writes messages queue. i'm unable find out scenario. that's why doubted log.
log follows,
16:52:19.783 [chronicle reader] debug n.o.c.q.i.s.singlechroniclequeueexcerpts$storetailer - movetoindex: 17ec5f2 3 16:52:20.784 [chronicle reader] debug n.o.c.q.i.s.singlechroniclequeueexcerpts$storetailer - movetoindex: 17ec5f2 3 16:52:21.785 [chronicle reader] debug n.o.c.q.i.s.singlechroniclequeueexcerpts$storetailer - movetoindex: 17ec5f2 3 16:52:22.785 [chronicle reader] debug n.o.c.q.i.s.singlechroniclequeueexcerpts$storetailer - movetoindex: 17ec5f2 3 16:52:23.786 [chronicle reader] debug n.o.c.q.i.s.singlechroniclequeueexcerpts$storetailer - movetoindex: 17ec5f2 3 16:52:24.787 [chronicle reader] debug n.o.c.q.i.s.singlechroniclequeueexcerpts$storetailer - movetoindex: 17ec5f2 3 16:52:25.787 [chronicle reader] debug n.o.c.q.i.s.singlechroniclequeueexcerpts$storetailer - movetoindex: 17ec5f2 3 16:52:26.788 [chronicle reader] debug n.o.c.q.i.s.singlechroniclequeueexcerpts$storetailer - movetoindex: 17ec5f2 3
my chronicle-queue version: 4.5.27
Comments
Post a Comment