[jira] [Commented] (KAFKA-2061) Offer a --version flag to print the kafka version

[ https://issues.apache.org/jira/browse/KAFKA-2061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16490367#comment-16490367 ] ASF GitHub Bot commented on KAFKA-2061: --- hachikuji closed pull request #639: KAFKA-2

[jira] [Resolved] (KAFKA-2061) Offer a --version flag to print the kafka version

[ https://issues.apache.org/jira/browse/KAFKA-2061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-2061. Resolution: Fixed Fix Version/s: 2.0.0 > Offer a --version flag to print the kafka ve

[jira] [Created] (KAFKA-6947) Mirrormaker Closing producer due to send failure

Andrew Holford created KAFKA-6947: - Summary: Mirrormaker Closing producer due to send failure Key: KAFKA-6947 URL: https://issues.apache.org/jira/browse/KAFKA-6947 Project: Kafka Issue Type:

[jira] [Updated] (KAFKA-6947) Mirrormaker Closing producer due to send failure

[ https://issues.apache.org/jira/browse/KAFKA-6947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Holford updated KAFKA-6947: -- Description: Hi On occasion our mirrormakers fail with the below error [2018-05-25 05:10:3

[jira] [Commented] (KAFKA-6933) Broker reports Corrupted index warnings apparently infinitely

[ https://issues.apache.org/jira/browse/KAFKA-6933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16490405#comment-16490405 ] Franco Bonazza commented on KAFKA-6933: --- I upgraded the broker to 1.1.0 and it recov

[jira] [Created] (KAFKA-6948) Avoid overflow in timestamp comparison

Giovanni Liva created KAFKA-6948: Summary: Avoid overflow in timestamp comparison Key: KAFKA-6948 URL: https://issues.apache.org/jira/browse/KAFKA-6948 Project: Kafka Issue Type: Improvement

[jira] [Commented] (KAFKA-6948) Avoid overflow in timestamp comparison

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

[jira] [Updated] (KAFKA-6947) Mirrormaker Closing producer due to send failure

[ https://issues.apache.org/jira/browse/KAFKA-6947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Holford updated KAFKA-6947: -- Description: Hi On occasion our mirrormakers fail with the below error [2018-05-25 05:10:3

[jira] [Commented] (KAFKA-6841) Add support for wildcard suffixed ACLs

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

[jira] [Commented] (KAFKA-6668) Broker crashes on restart ,got a CorruptRecordException: Record size is smaller than minimum record overhead(14)

[ https://issues.apache.org/jira/browse/KAFKA-6668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16490502#comment-16490502 ] evan einst commented on KAFKA-6668: --- Same error when our kafka server restart.   We upd

[jira] [Commented] (KAFKA-6900) Add thenCompose to KafkaFuture

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

[jira] [Commented] (KAFKA-6943) Have option to shutdown KS cleanly if any task crashes, or if all tasks crash

[ https://issues.apache.org/jira/browse/KAFKA-6943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16490638#comment-16490638 ] Antony Stubbs commented on KAFKA-6943: -- Sorry, should have said thread, not task. For

[jira] [Comment Edited] (KAFKA-6943) Have option to shutdown KS cleanly if any task crashes, or if all tasks crash

[ https://issues.apache.org/jira/browse/KAFKA-6943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16490638#comment-16490638 ] Antony Stubbs edited comment on KAFKA-6943 at 5/25/18 12:23 PM:

[jira] [Updated] (KAFKA-6943) Have option to shutdown KS cleanly if any threads crashes, or if all threads crash

[ https://issues.apache.org/jira/browse/KAFKA-6943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antony Stubbs updated KAFKA-6943: - Summary: Have option to shutdown KS cleanly if any threads crashes, or if all threads crash (was:

[jira] [Updated] (KAFKA-6943) Have option to shutdown KS cleanly if any threads crashes, or if all threads crash

[ https://issues.apache.org/jira/browse/KAFKA-6943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antony Stubbs updated KAFKA-6943: - Description: ATM users have to implement this themselves. Might be nice to have an option to conf

[jira] [Updated] (KAFKA-6942) Connect connectors api doesn't show versions of connectors

[ https://issues.apache.org/jira/browse/KAFKA-6942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-6942: - Labels: needs-kip (was: ) > Connect connectors api doesn't show versions of connectors >

[jira] [Commented] (KAFKA-6907) Not able to delete topic

[ https://issues.apache.org/jira/browse/KAFKA-6907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16490801#comment-16490801 ] praveen commented on KAFKA-6907: I was able to resolve this issue. Changed the advertised

[jira] [Resolved] (KAFKA-6907) Not able to delete topic

[ https://issues.apache.org/jira/browse/KAFKA-6907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] praveen resolved KAFKA-6907. Resolution: Fixed > Not able to delete topic > > > Key: KAFKA-6907

[jira] [Created] (KAFKA-6949) NoSuchElementException in ReplicaManager

Jason Gustafson created KAFKA-6949: -- Summary: NoSuchElementException in ReplicaManager Key: KAFKA-6949 URL: https://issues.apache.org/jira/browse/KAFKA-6949 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-6949) NoSuchElementException in ReplicaManager

[ https://issues.apache.org/jira/browse/KAFKA-6949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16490869#comment-16490869 ] Jason Gustafson commented on KAFKA-6949: [~lindong] If you have time, can you take

[jira] [Assigned] (KAFKA-6949) NoSuchElementException in ReplicaManager

[ https://issues.apache.org/jira/browse/KAFKA-6949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin reassigned KAFKA-6949: --- Assignee: Dong Lin > NoSuchElementException in ReplicaManager > -

[jira] [Commented] (KAFKA-6949) NoSuchElementException in ReplicaManager

[ https://issues.apache.org/jira/browse/KAFKA-6949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16491053#comment-16491053 ] Dong Lin commented on KAFKA-6949: - [~hachikuji] Certainly. I will look into this. > NoSuc

[jira] [Resolved] (KAFKA-6921) Remove old Scala producer and all related code, tests, and tools

[ https://issues.apache.org/jira/browse/KAFKA-6921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-6921. -- Resolution: Fixed > Remove old Scala producer and all related code, tests, and tools > -

[jira] [Resolved] (KAFKA-3649) Add capability to query broker process for configuration properties

[ https://issues.apache.org/jira/browse/KAFKA-3649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-3649. -- Resolution: Fixed Requested features are added in  KIP-133: Describe and Alter Configs Admin APIs and K

[jira] [Commented] (KAFKA-6811) Tasks should have access to connector and task metadata

[ https://issues.apache.org/jira/browse/KAFKA-6811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16491129#comment-16491129 ] Sandeep Tamhankar commented on KAFKA-6811: -- I'd suggest taking this one step furt

[jira] [Updated] (KAFKA-6950) Add mechanism to delay response to failed client authentication

[ https://issues.apache.org/jira/browse/KAFKA-6950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhruvil Shah updated KAFKA-6950: Issue Type: Improvement (was: Bug) > Add mechanism to delay response to failed client authenticatio

[jira] [Created] (KAFKA-6950) Add mechanism to delay response to failed client authentication

Dhruvil Shah created KAFKA-6950: --- Summary: Add mechanism to delay response to failed client authentication Key: KAFKA-6950 URL: https://issues.apache.org/jira/browse/KAFKA-6950 Project: Kafka

[jira] [Commented] (KAFKA-6616) kafka-merge-pr.py should use GitHub's REST API to merge

[ https://issues.apache.org/jira/browse/KAFKA-6616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16491215#comment-16491215 ] Ismael Juma commented on KAFKA-6616: [~vpopov89], sure! > kafka-merge-pr.py should us

[jira] [Assigned] (KAFKA-6616) kafka-merge-pr.py should use GitHub's REST API to merge

[ https://issues.apache.org/jira/browse/KAFKA-6616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Popov reassigned KAFKA-6616: --- Assignee: Viktor Popov > kafka-merge-pr.py should use GitHub's REST API to merge > --

[jira] [Created] (KAFKA-6951) Implement offset expiration semantics for unsubscribed topics

Vahid Hashemian created KAFKA-6951: -- Summary: Implement offset expiration semantics for unsubscribed topics Key: KAFKA-6951 URL: https://issues.apache.org/jira/browse/KAFKA-6951 Project: Kafka

[jira] [Commented] (KAFKA-6937) In-sync replica delayed during fetch if replica throttle is exceeded

[ https://issues.apache.org/jira/browse/KAFKA-6937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16491364#comment-16491364 ] Kevin Lafferty commented on KAFKA-6937: --- I was able to test this patch today, and it

[jira] [Commented] (KAFKA-6937) In-sync replica delayed during fetch if replica throttle is exceeded

[ https://issues.apache.org/jira/browse/KAFKA-6937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16491376#comment-16491376 ] Jun Rao commented on KAFKA-6937: [~klafferty], thanks for testing this out. Yes, the reaso

[jira] [Commented] (KAFKA-6937) In-sync replica delayed during fetch if replica throttle is exceeded

[ https://issues.apache.org/jira/browse/KAFKA-6937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16491384#comment-16491384 ] ASF GitHub Bot commented on KAFKA-6937: --- junrao closed pull request #5074: KAFKA-693

[jira] [Commented] (KAFKA-6930) Update KafkaZkClient debug log

[ https://issues.apache.org/jira/browse/KAFKA-6930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16491394#comment-16491394 ] ASF GitHub Bot commented on KAFKA-6930: --- ijuma closed pull request #5061: [KAFKA-693

[jira] [Resolved] (KAFKA-6937) In-sync replica delayed during fetch if replica throttle is exceeded

[ https://issues.apache.org/jira/browse/KAFKA-6937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-6937. Resolution: Fixed Fix Version/s: 1.1.1 1.0.2 2.0.0 Merged the P

[jira] [Resolved] (KAFKA-6930) Update KafkaZkClient debug log

[ https://issues.apache.org/jira/browse/KAFKA-6930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6930. Resolution: Fixed > Update KafkaZkClient debug log > -- > >

[jira] [Updated] (KAFKA-6930) Update KafkaZkClient debug log

[ https://issues.apache.org/jira/browse/KAFKA-6930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-6930: --- Fix Version/s: 1.1.1 2.0.0 > Update KafkaZkClient debug log > -

[jira] [Updated] (KAFKA-6949) alterReplicaLogDirs() should grab partition lock when accessing log of the future replica

[ https://issues.apache.org/jira/browse/KAFKA-6949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-6949: Summary: alterReplicaLogDirs() should grab partition lock when accessing log of the future replica (was: No

[jira] [Commented] (KAFKA-6950) Add mechanism to delay response to failed client authentication

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

[jira] [Commented] (KAFKA-6949) alterReplicaLogDirs() should grab partition lock when accessing log of the future replica

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

[jira] [Commented] (KAFKA-2951) Additional authorization test cases

[ https://issues.apache.org/jira/browse/KAFKA-2951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16491544#comment-16491544 ] ASF GitHub Bot commented on KAFKA-2951: --- hachikuji closed pull request #5054: KAFKA-

[jira] [Resolved] (KAFKA-2951) Additional authorization test cases

[ https://issues.apache.org/jira/browse/KAFKA-2951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-2951. Resolution: Fixed Fix Version/s: 2.0.0 > Additional authorization test cases > --