You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Glenn Sontheimer (JIRA)" <ji...@apache.org> on 2015/06/10 20:15:00 UTC

[jira] [Created] (KAFKA-2261) Provide a configurable timeout for NetworkClient.send

Glenn Sontheimer created KAFKA-2261:
---------------------------------------

             Summary: Provide a configurable timeout for NetworkClient.send
                 Key: KAFKA-2261
                 URL: https://issues.apache.org/jira/browse/KAFKA-2261
             Project: Kafka
          Issue Type: New Feature
          Components: clients
    Affects Versions: 0.8.2.0
            Reporter: Glenn Sontheimer


Currently once a message has been submitted asynchronously (only option for 0.8.2) there is a possibility that the message could remain in the submission state and never initiate the callback.  There are have been several iterations of the code (in previous versions) to help address this issue.  However these changes handle specific scenarios known as of each point in time, e.g. successful sends and node disconnects.  Additional failure scenarios may exist and/or be introduced in future iterations of the code base.  A fail safe mechanism seems appropriate in this situation while work continues to cover known and discovered scenarios.  

Adding a configuration to allow the client application to specify a timeout for the message send provides the following advantages:
1.  The client application will be guaranteed that a callback will be performed for every message.
2.  The interaction with the Kafka Queue can be better tuned to the application's needs.  In some cases a shorter timeout will be necessary to ensure data does not become too stale.

 







--
This message was sent by Atlassian JIRA
(v6.3.4#6332)