[jira] [Created] (KAFKA-6620) Documentation about "exactly_once" doesn't mention "transaction.state.log.min.isr"

Daniel Qian created KAFKA-6620: -- Summary: Documentation about "exactly_once" doesn't mention "transaction.state.log.min.isr" Key: KAFKA-6620 URL: https://issues.apache.org/jira/browse/KAFKA-6620 Project

[jira] [Commented] (KAFKA-5999) Offset Fetch Request

[ https://issues.apache.org/jira/browse/KAFKA-5999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16389387#comment-16389387 ] Zhao Weilong commented on KAFKA-5999: - Sorry for late reply On Wed, Mar 7, 2018 at 2:

[jira] [Commented] (KAFKA-5999) Offset Fetch Request

[ https://issues.apache.org/jira/browse/KAFKA-5999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16389402#comment-16389402 ] Zhao Weilong commented on KAFKA-5999: - Hi Vahid Hashemian, Ewen Cheslack-Postava: Sor

[jira] [Commented] (KAFKA-6195) DNS alias support for secured connections

[ https://issues.apache.org/jira/browse/KAFKA-6195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16389585#comment-16389585 ] Rajini Sivaram commented on KAFKA-6195: --- [~jonathanskrzypek] Sorry for the delay, I

[jira] [Commented] (KAFKA-6195) DNS alias support for secured connections

[ https://issues.apache.org/jira/browse/KAFKA-6195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16389736#comment-16389736 ] Jonathan Skrzypek commented on KAFKA-6195: -- Thanks for reviewing. Yes, that make

[jira] [Updated] (KAFKA-6614) kafka-streams to configure internal topics message.timestamp.type=CreateTime

[ https://issues.apache.org/jira/browse/KAFKA-6614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-6614: - Labels: newbie (was: ) > kafka-streams to configure internal topics message.timestamp.type=Create

[jira] [Commented] (KAFKA-6127) Streams should never block infinitely

[ https://issues.apache.org/jira/browse/KAFKA-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16390105#comment-16390105 ] Guozhang Wang commented on KAFKA-6127: -- We are poll() with a timeout, but yes, admitt

[jira] [Commented] (KAFKA-6127) Streams should never block infinitely

[ https://issues.apache.org/jira/browse/KAFKA-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16390108#comment-16390108 ] Matthias J. Sax commented on KAFKA-6127: It might be bad to block in poll() as wel

[jira] [Created] (KAFKA-6621) Update Streams docs with details for UncaughtExceptionHandler

Matthias J. Sax created KAFKA-6621: -- Summary: Update Streams docs with details for UncaughtExceptionHandler Key: KAFKA-6621 URL: https://issues.apache.org/jira/browse/KAFKA-6621 Project: Kafka

[jira] [Commented] (KAFKA-6399) Consider reducing "max.poll.interval.ms" default for Kafka Streams

[ https://issues.apache.org/jira/browse/KAFKA-6399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16390248#comment-16390248 ] Khaireddine Rezgui commented on KAFKA-6399: --- I agree with the value, 30 seconds

[jira] [Commented] (KAFKA-6400) Consider setting default cache size to zero in Kafka Streams

[ https://issues.apache.org/jira/browse/KAFKA-6400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16390270#comment-16390270 ] Khaireddine Rezgui commented on KAFKA-6400: --- I got sometimes the same experience

[jira] [Assigned] (KAFKA-6399) Consider reducing "max.poll.interval.ms" default for Kafka Streams

[ https://issues.apache.org/jira/browse/KAFKA-6399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Khaireddine Rezgui reassigned KAFKA-6399: - Assignee: Khaireddine Rezgui > Consider reducing "max.poll.interval.ms" default f

[jira] [Comment Edited] (KAFKA-6400) Consider setting default cache size to zero in Kafka Streams

[ https://issues.apache.org/jira/browse/KAFKA-6400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16390270#comment-16390270 ] Khaireddine Rezgui edited comment on KAFKA-6400 at 3/7/18 10:06 PM:

[jira] [Commented] (KAFKA-6530) Use actual first offset of messages when rolling log segment for magic v2

[ https://issues.apache.org/jira/browse/KAFKA-6530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16390468#comment-16390468 ] ASF GitHub Bot commented on KAFKA-6530: --- dhruvilshah3 opened a new pull request #466

[jira] [Created] (KAFKA-6622) GroupMetadataManager.loadGroupsAndOffsets decompresses record batch needlessly

radai rosenblatt created KAFKA-6622: --- Summary: GroupMetadataManager.loadGroupsAndOffsets decompresses record batch needlessly Key: KAFKA-6622 URL: https://issues.apache.org/jira/browse/KAFKA-6622 Pr

[jira] [Commented] (KAFKA-6622) GroupMetadataManager.loadGroupsAndOffsets decompresses record batch needlessly

[ https://issues.apache.org/jira/browse/KAFKA-6622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16390502#comment-16390502 ] radai rosenblatt commented on KAFKA-6622: - see PR - https://github.com/apache/kafk

[jira] [Commented] (KAFKA-5939) Add a dryrun option to release.py

[ https://issues.apache.org/jira/browse/KAFKA-5939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16390528#comment-16390528 ] Ewen Cheslack-Postava commented on KAFKA-5939: -- I think dry run is fine if we

[jira] [Commented] (KAFKA-6264) Log cleaner thread may die on legacy segment containing messages whose offsets are too large

[ https://issues.apache.org/jira/browse/KAFKA-6264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16390535#comment-16390535 ] Dhruvil Shah commented on KAFKA-6264: - [~becket_qin] would you mind if I picked this i

[jira] [Comment Edited] (KAFKA-6264) Log cleaner thread may die on legacy segment containing messages whose offsets are too large

[ https://issues.apache.org/jira/browse/KAFKA-6264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16390535#comment-16390535 ] Dhruvil Shah edited comment on KAFKA-6264 at 3/8/18 12:57 AM: --

[jira] [Created] (KAFKA-6623) Consider renaming inefficient RecordBatch operations

Jason Gustafson created KAFKA-6623: -- Summary: Consider renaming inefficient RecordBatch operations Key: KAFKA-6623 URL: https://issues.apache.org/jira/browse/KAFKA-6623 Project: Kafka Issue

[jira] [Updated] (KAFKA-6413) ReassignPartitionsCommand#parsePartitionReassignmentData() should give better error message when JSON is malformed

[ https://issues.apache.org/jira/browse/KAFKA-6413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated KAFKA-6413: -- Labels: json (was: ) > ReassignPartitionsCommand#parsePartitionReassignmentData() should give better > error m

[jira] [Created] (KAFKA-6624) log segment deletion could cause a disk to be marked offline incorrectly

Jun Rao created KAFKA-6624: -- Summary: log segment deletion could cause a disk to be marked offline incorrectly Key: KAFKA-6624 URL: https://issues.apache.org/jira/browse/KAFKA-6624 Project: Kafka I

[jira] [Commented] (KAFKA-6624) log segment deletion could cause a disk to be marked offline incorrectly

[ https://issues.apache.org/jira/browse/KAFKA-6624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16390572#comment-16390572 ] Jun Rao commented on KAFKA-6624: One way to fix this is to add a flag for a log segment to

[jira] [Updated] (KAFKA-6619) InstanceAlreadyExistsException while Tomcat starting up

[ https://issues.apache.org/jira/browse/KAFKA-6619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiezhi updated KAFKA-6619: -- Description:  I configured log4j to send application logs to kafka. There is no more producer, one only. So I c

[jira] [Commented] (KAFKA-6624) log segment deletion could cause a disk to be marked offline incorrectly

[ https://issues.apache.org/jira/browse/KAFKA-6624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16390727#comment-16390727 ] Jun Rao commented on KAFKA-6624: [~lindong], do you think this is an issue? Thanks. > log

[jira] [Commented] (KAFKA-6624) log segment deletion could cause a disk to be marked offline incorrectly

[ https://issues.apache.org/jira/browse/KAFKA-6624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16390748#comment-16390748 ] ASF GitHub Bot commented on KAFKA-6624: --- lindong28 opened a new pull request #4663:

[jira] [Commented] (KAFKA-6624) log segment deletion could cause a disk to be marked offline incorrectly

[ https://issues.apache.org/jira/browse/KAFKA-6624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16390753#comment-16390753 ] Dong Lin commented on KAFKA-6624: - [~junrao] It may be reasonable to grab the lock of the

[jira] [Updated] (KAFKA-6623) Consider renaming inefficient RecordBatch operations

[ https://issues.apache.org/jira/browse/KAFKA-6623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-6623: --- Description: Certain batch-level operations are only efficient with the new  message format ver

[jira] [Created] (KAFKA-6625) kafka offset reset when I upgrade kafka from 0.11.0 to 1.0.0 version

barry010 created KAFKA-6625: --- Summary: kafka offset reset when I upgrade kafka from 0.11.0 to 1.0.0 version Key: KAFKA-6625 URL: https://issues.apache.org/jira/browse/KAFKA-6625 Project: Kafka Iss

[jira] [Updated] (KAFKA-6625) kafka offset reset when I upgrade kafka from 0.11.0 to 1.0.0 version

[ https://issues.apache.org/jira/browse/KAFKA-6625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] barry010 updated KAFKA-6625: Description: when I upgrade kafka from 0.11.0 to 1.0.0 version，during I shut down the broker01 with kill si

[jira] [Updated] (KAFKA-6625) kafka offset reset when I upgrade kafka from 0.11.0 to 1.0.0 version

[ https://issues.apache.org/jira/browse/KAFKA-6625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] barry010 updated KAFKA-6625: Environment: flume 1.8 with Kafka client version : 0.9.0.1 Kafka version : 0.11.0 > kafka offset reset when

[jira] [Created] (KAFKA-6626) Performance bottleneck in Kafka Connect sendRecords

Maciej Bryński created KAFKA-6626: - Summary: Performance bottleneck in Kafka Connect sendRecords Key: KAFKA-6626 URL: https://issues.apache.org/jira/browse/KAFKA-6626 Project: Kafka Issue Typ

[jira] [Updated] (KAFKA-6626) Performance bottleneck in Kafka Connect sendRecords

[ https://issues.apache.org/jira/browse/KAFKA-6626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maciej Bryński updated KAFKA-6626: -- Description: Kafka Connect is using IdentityHashMap for storing records. [https://github.com/ap

[jira] [Commented] (KAFKA-1368) Upgrade log4j

[ https://issues.apache.org/jira/browse/KAFKA-1368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16390872#comment-16390872 ] Vladislav Pernin commented on KAFKA-1368: - Log4j upgrade was needed in 2014 to be