flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From zjureel <...@git.apache.org>
Subject [GitHub] flink issue #3901: [FLINK-6288] fix FlinkKafkaProducer's custom Partitioner ...
Date Mon, 15 May 2017 10:08:13 GMT
Github user zjureel commented on the issue:

    https://github.com/apache/flink/pull/3901
  
    @tzulitai I created the new PR here for issue 6288. As discussed in [https://github.com/apache/flink/pull/3766](url),
there are two ways to control timeout of fetching kafka meta
    
    1. Depend on the timeout mechanism of kafka. When fetching partition meta from kafka,
some timeout configurations should be setted.
    2. Using `Future` to get the partiton meta of kafka, and user can set the timeout with
configuration.
    
    In the new api, meta of kafka may be feched before data is sended, and some exceptions
such as network or disk problem may still block data send even that user set the request timeout
of kafka. So in the PR, I use Future to control the timeout of fetching kafka meta.
    
    The problem may not be so complicated, and we can use the timeout mechanism of kafka directly.
What do you think of it? Thanks.
    



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message