Skip to content
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

How to configure the topic for posting messages back to a Kafka queue if writing to storage fails #2

Open
sjmittal opened this issue Aug 4, 2017 · 2 comments
Labels

Comments

@sjmittal
Copy link

sjmittal commented Aug 4, 2017

I have not understood this part:
It includes a Storage Exception Handler plugin that will post messages back to a Kafka queue if writing to storage fails

The config specifies

KafkaRpcPlugin.groups = TsdbConsumer,TsdbRequeueConsumer
KafkaRpcPlugin.seh.topic.default = TSDB_Requeue

So does this mean that second group is created to post the failed messages back to the requeue topic?

Do I also need to specify this:
KafkaRpcPlugin.TsdbRequeueConsumer.topics = TSDB_Requeue

@manolama
Copy link
Member

Failed writes (to HBase or whatnot) will post back to the "TSDB_Requeue" topic in Kafka. We want a separate topic so that the values don't circulate in the main data feed.

Instead we write to another topic, then create another consumer group (usually with fewer threads) that are dedicated to consuming just those requeued messages. So you do need KafkaRpcPlugin.TsdbRequeueConsumer.topics = TSDB_Requeue along with other KafkaRpcPlugin.TsdbRequeueConsumer..... settings.

@sjmittal
Copy link
Author

Understood.
Also the writes of failed messages to re-queue topic would work only if at opentsdb level we set:
tsd.core.storage_exception_handler.enable=true (default is false)
and add
tsd.core.storage_exception_handler.plugin=net.opentsdb.tsd.KafkaStorageExceptionHandler

If these two are not set and even if we set the TsdbRequeueConsumer properties it will still not work. Correct?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants