Tranquility Message Time policy again

Hey all!

So im using a custom timekeeper within my druid service to hack message time policy with tranquility. code looks like so:

.timekeeper(new CustomTimeKeeper(messageTime, appConfig.getTimekeeperTimezone()))

I am using kafka to consume events and tranquility does send these “older” events to the indexing service with no issue. however, when the task gets created by overlord it’s immediately completed/success’ed so none of the data actually get ingested.

How can i properly send older messages into the indexing service using tranquility?

I’ve attached overlord logs so you all can see what im talking about.


overlord-log.txt (12.9 KB)

Index service will throw the old messages too. You can check the index log to make sure.

在 2016年3月18日星期五 UTC+8上午5:13:20,Nicholas McKoy写道: