You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Guozhang Wang (Jira)" <ji...@apache.org> on 2020/07/20 04:19:00 UTC
[jira] [Created] (KAFKA-10294) Consider whether some of
ProcessorStateException should be auto-handled by Streams
Guozhang Wang created KAFKA-10294:
-------------------------------------
Summary: Consider whether some of ProcessorStateException should be auto-handled by Streams
Key: KAFKA-10294
URL: https://issues.apache.org/jira/browse/KAFKA-10294
Project: Kafka
Issue Type: Improvement
Components: streams
Reporter: Guozhang Wang
Assignee: Bruno Cadonna
Currently, when there's an error e.g. initializing a state store (e.g. RocksDB.open throws an exception), or writing checkpoints throws IOException, it would cause a ProcessorStateException which is a sub-class of the more general StreamsException and it is considered a fatal error and would cause the streams to stop.
While the latter case is arguably a valid exception to throw to users to handle, for the first case, and some others, we can potentially let Streams to handle this case by, e.g., wiping out the whole store and then retry initializing the state store with bootstrapping position at offset 0, but this worth some discussion here: which type of state store management related exceptions should be handled automatically by Streams, and which others should still be thrown to users.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)