[
https://issues.apache.org/jira/browse/BEAM-9420?focusedWorklogId=409451&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-409451
]
ASF GitHub Bot logged work on BEAM-9420:
----------------------------------------
Author: ASF GitHub Bot
Created on: 25/Mar/20 11:23
Start Date: 25/Mar/20 11:23
Worklog Time Spent: 10m
Work Description: aromanenko-dev commented on issue #11099: [BEAM-9420]
Configurable timeout for blocking kafka API call(s)
URL: https://github.com/apache/beam/pull/11099#issuecomment-603786407
Run Java PreCommit
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 409451)
Time Spent: 1h 40m (was: 1.5h)
> Configurable timeout for Kafka setupInitialOffset()
> ---------------------------------------------------
>
> Key: BEAM-9420
> URL: https://issues.apache.org/jira/browse/BEAM-9420
> Project: Beam
> Issue Type: Bug
> Components: io-java-kafka
> Affects Versions: 2.19.0
> Reporter: Jozef Vilcek
> Assignee: Jozef Vilcek
> Priority: Major
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> If bootstrap brokers does contain an unhealthy server, it can break the start
> of a whole Beam job. During the start, `KafkaUnboundedReader` is waiting for
> `setupInitialOffset()`. Wait timeout is either a double time of `request.
> timeout.ms` or some default constant. In both cases, it might not be enough
> time for kafka-client to initiate fallback and retry metadata discovery via
> another broker from given bootstrap list.
> The client should be able to specify timeout for `setupInitialOffset()`
> explicitly as a setting to KafkaIO read.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
