-
Notifications
You must be signed in to change notification settings - Fork 230
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tranquility-server realtime(not creating merged beam) #282
Comments
yeah I have the same issue |
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. |
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. |
I found some indexing logs under middleManager server: 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? |
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?
The text was updated successfully, but these errors were encountered: