[KAFKA-1863] Exception categories / hierarchy in clients

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.9.0.0
• Assignee: Guozhang Wang
• Reporter: Guozhang Wang
• Created: 14/Jan/15 19:07
• Updated: 17/May/16 14:15
• Resolved: 13/Mar/15 22:18

Description

In the new clients package we introduces a new set of exceptions, but its hierarchy is not very clear as of today:

RuntimeException -> KafkaException -> BufferExhastedException
                                                           -> ConfigException
                                                           -> SerializationException
                                                           -> QuotaViolationException
                                                           -> SchemaException

                                                           -> ApiException

ApiException -> InvalidTopicException
                     -> OffsetMetadataTooLarge (probabaly need to be renamed)
                     -> RecordBatchTooLargeException
                     -> RecordTooLargeException
                     -> UnknownServerException

                     -> RetriableException

RetriableException -> CorruptRecordException
                               -> InvalidMetadataException
                               -> NotEnoughtReplicasAfterAppendException
                               -> NotEnoughReplicasException
                               -> OffsetOutOfRangeException
                               -> TimeoutException
                               -> UnknownTopicOrPartitionException

KafkaProducer.send() may throw KafkaExceptions that are not ApiExceptions; other exceptions will be set in the returned future metadata.

We need better to

1. Re-examine the hierarchy. For example, for producers only exceptions that are thrown directly from the caller thread before it is appended to the batch buffer should be ApiExceptions; some exceptions could be renamed / merged.

2. Clearly document the exception category / hierarchy as part of the release.

Chris Riccomini may have some more feedbacks for this issue from Samza's usage experience. Jay Kreps

Issue Links

• is related to: KAFKA-1865 Add a flush() call to the new producer API
• relates to: SAMZA-227 Upgrade KafkaSystemProducer to new API