EOS queue size does noe consumed and result in 15 minutes delay when put tx and query it in mongo?

[csquan]

debug 2018-12-25T07:48:58.502 thread-0 fork_database.cpp:147 add ] queue size: 1873
info 2018-12-25T07:48:58.502 thread-0 producer_plugin.cpp:341 on_incoming_block ] Received block 220ce7a4f11e751e... #3474964 @ 2018-12-25T07:48:58.500 signed by bpingtai1111 [trxs: 0, lib: 3474918, conf: 0, latency: 2 ms],which code is
if( oldest->block_num < lib ) {
prune( oldest );
}
dlog("queue size: ${l}", ("l", my->index.get<by_block_num>().size())); in fork_database.cpp, it's effect is when I have wirte data to eos which connect mongo,I found data not exist in mongo until 15 minutes later,that confuse me a lot,can anyone have any idea?

[csquan]

this problem confuse me a lot.
when I update BP,I stop eos and update to new version,build and run,in this time,when it's turn for this BP pruduce block,it can not produce for stop.
so other BPs will wait for some seconds.
In this gap,block will cumulate.
when BP is update completed, cumulate blocks still there,it does not consumed.

[heifner]

It is possible you are seeing this: #6409 (comment)

[jgiszczak]

Filer unresponsive for 50 days. Closing.