[
https://issues.apache.org/jira/browse/HADOOP-14623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16076154#comment-16076154
]
Hongyuan Li commented on HADOOP-14623:
--------------------------------------
i don't think so, setting it to 1 does not means that it will block.However, i
think that Ganglia knows the frquency of data lossed, but kafka does not. What
you have said under estimate kafka.Kafka has more power.Compared to complete
sync of setting acks to -1, setting acks to 1 is a better choice.
> KafkaSink#init should set acks to 1,not 0
> -----------------------------------------
>
> Key: HADOOP-14623
> URL: https://issues.apache.org/jira/browse/HADOOP-14623
> Project: Hadoop Common
> Issue Type: Bug
> Components: common, tools
> Affects Versions: 3.0.0-alpha3
> Reporter: Hongyuan Li
> Assignee: Hongyuan Li
> Attachments: HADOOP-14623-001.patch
>
>
> {{KafkaSink}}#{{init}} should set ack to *1* to make sure the message has
> been written to the broker at least.
> current code list below:
> {code}
>
> props.put("request.required.acks", "0");
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
