tranquility-server realtime(not creating merged beam)

[jwydecn]

2018-08-22 16:53:00,950 [ClusteredBeam-ZkFuturePool-e24324d4-4cf8-4472-998e-b99cdfd423bb] INFO c.m.tranquility.beam.ClusteredBeam - Global latestCloseTime[2018-08-22T08:00:00.000Z] for identifier[druid:overlord/test] has moved past timestamp[2018-08-22T08:00:00.000Z], not creating merged beam
2018-08-22 16:53:00,962 [ClusteredBeam-ZkFuturePool-e24324d4-4cf8-4472-998e-b99cdfd423bb] INFO c.m.tranquility.beam.ClusteredBeam - Turns out we decided not to actually make beams for identifier[druid:overlord/test] timestamp[2018-08-22T08:00:00.000Z]. Returning None.

task of segment2018-08-22T08:00:00.000Z in overload has killed, how can i retry it or new other?

[srggrs]

yeah I have the same issue

[eksantrik]

Have you guys been able to resolve this issue? I am getting the same problem and can't figure out whats causing this. I am watching overlord and middleManager logs and not seeing anything happening as tranquility drop the new messages.

[gianm]

Usually it happens if tranquility fails to create tasks for some reason, or if all the tasks die for a particular segmentGranularity time chunk. It often resolves when the next time chunk begins. Fwiw, Druid's native Kafka ingestion does not have this problem, if you are interested in checking that out.

[eksantrik]

I found some indexing logs under middleManager server:
index_realtime_log.log

According to this, there is an error: "Unable to find a region via the region provider chain. Must provide an explicit region in the builder or setup environment to supply a region".

I am installing Druid v0.13. Do you think this is related?