Thanks Gian for the help RE: task heartbeating.
We are using Tranquility for real-time tasks.
When using hour segment granularity, we see the firehoseId re-used after 24 hours, which results in a new task sitting in pending even though we have slots for it. I believe this is because the availabilityGroup does not include date:
156 val availabilityGroup = DruidBeamMaker.generateBaseFirehoseId(
The availability group is then substituted into the firehosePattern with:
val firehoseId = “%s-%04d” format(availabilityGroup, replicant)
Should we include some portion of the date into the availabilityGroup to allow for tasks running longer than 24 hours?