[jira] [Commented] (KAFKA-5638) Inconsistency in consumer group related ACLs

[ https://issues.apache.org/jira/browse/KAFKA-5638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16113013#comment-16113013 ] Jason Gustafson commented on KAFKA-5638: Yes, compatibility is what I had in mind. I think my

[jira] [Commented] (KAFKA-5358) Consumer perf tool should count rebalance time separately

[ https://issues.apache.org/jira/browse/KAFKA-5358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16113750#comment-16113750 ] Jason Gustafson commented on KAFKA-5358: [~huxi_2b] It seems like the discussion thread on the dev

[jira] [Commented] (KAFKA-5407) Mirrormaker dont start after upgrade

[ https://issues.apache.org/jira/browse/KAFKA-5407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16113733#comment-16113733 ] Jason Gustafson commented on KAFKA-5407: [~fvegaucr] Can you attach the broker logs from that time

[jira] [Commented] (KAFKA-5467) setting offset retention minutes to a lower value is not reflecting

[ https://issues.apache.org/jira/browse/KAFKA-5467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16113745#comment-16113745 ] Jason Gustafson commented on KAFKA-5467: [~divyapaulraj92] Can you clarify the steps that you took

[jira] [Resolved] (KAFKA-5731) Connect WorkerSinkTask out of order offset commit can lead to inconsistent state

[ https://issues.apache.org/jira/browse/KAFKA-5731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-5731. Resolution: Fixed Fix Version/s: (was: 1.0.0) Issue resolved by pull request

[jira] [Commented] (KAFKA-5724) AbstractPartitionAssignor does not take into consideration that partition number may start from non-zero

[ https://issues.apache.org/jira/browse/KAFKA-5724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16123563#comment-16123563 ] Jason Gustafson commented on KAFKA-5724: [~allenxwang] I fear this is not the only place we make

[jira] [Created] (KAFKA-5729) Consumer should verify offset commits are from assigned partitions

Jason Gustafson created KAFKA-5729: -- Summary: Consumer should verify offset commits are from assigned partitions Key: KAFKA-5729 URL: https://issues.apache.org/jira/browse/KAFKA-5729 Project: Kafka

[jira] [Commented] (KAFKA-4682) Committed offsets should not be deleted if a consumer is still active

[ https://issues.apache.org/jira/browse/KAFKA-4682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16122580#comment-16122580 ] Jason Gustafson commented on KAFKA-4682: Sorry for the late response. There seem to be a few open

[jira] [Commented] (KAFKA-5595) Illegal state in SocketServer; attempt to send with another send in progress

[ https://issues.apache.org/jira/browse/KAFKA-5595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16090205#comment-16090205 ] Jason Gustafson commented on KAFKA-5595: Ensuring connectionId uniqueness is a nice improvement,

[jira] [Created] (KAFKA-5580) Group rebalance delay only used with generation 0

Jason Gustafson created KAFKA-5580: -- Summary: Group rebalance delay only used with generation 0 Key: KAFKA-5580 URL: https://issues.apache.org/jira/browse/KAFKA-5580 Project: Kafka Issue

[jira] [Created] (KAFKA-5595) Illegal state in SocketServer; attempt to send with another send in progress

Jason Gustafson created KAFKA-5595: -- Summary: Illegal state in SocketServer; attempt to send with another send in progress Key: KAFKA-5595 URL: https://issues.apache.org/jira/browse/KAFKA-5595

[jira] [Commented] (KAFKA-5595) Illegal state in SocketServer; attempt to send with another send in progress

[ https://issues.apache.org/jira/browse/KAFKA-5595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16087745#comment-16087745 ] Jason Gustafson commented on KAFKA-5595: cc [~rsivaram] In case you have any ideas. > Illegal

[jira] [Commented] (KAFKA-5634) Replica fetcher thread crashes due to OffsetOutOfRangeException

[ https://issues.apache.org/jira/browse/KAFKA-5634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16100252#comment-16100252 ] Jason Gustafson commented on KAFKA-5634: I've been looking at this a bit more. I think the only

[jira] [Commented] (KAFKA-5634) Replica fetcher thread crashes due to OffsetOutOfRangeException

[ https://issues.apache.org/jira/browse/KAFKA-5634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16100381#comment-16100381 ] Jason Gustafson commented on KAFKA-5634: I can confirm that this bug occurs when a fetch response

[jira] [Commented] (KAFKA-5611) One or more consumers in a consumer-group stop consuming after rebalancing

[ https://issues.apache.org/jira/browse/KAFKA-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16098973#comment-16098973 ] Jason Gustafson commented on KAFKA-5611: [~pskianis] You'd have to get pretty unlikely with the

[jira] [Assigned] (KAFKA-5611) One or more consumers in a consumer-group stop consuming after rebalancing

[ https://issues.apache.org/jira/browse/KAFKA-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson reassigned KAFKA-5611: -- Assignee: Jason Gustafson > One or more consumers in a consumer-group stop consuming

[jira] [Created] (KAFKA-5634) Replica fetcher thread crashes due to OffsetOutOfRangeException

Jason Gustafson created KAFKA-5634: -- Summary: Replica fetcher thread crashes due to OffsetOutOfRangeException Key: KAFKA-5634 URL: https://issues.apache.org/jira/browse/KAFKA-5634 Project: Kafka

[jira] [Resolved] (KAFKA-5634) Replica fetcher thread crashes due to OffsetOutOfRangeException

[ https://issues.apache.org/jira/browse/KAFKA-5634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-5634. Resolution: Fixed Issue resolved by pull request 3575

[jira] [Created] (KAFKA-5664) Disable auto offset commit in ConsoleConsumer if no group is provided

Jason Gustafson created KAFKA-5664: -- Summary: Disable auto offset commit in ConsoleConsumer if no group is provided Key: KAFKA-5664 URL: https://issues.apache.org/jira/browse/KAFKA-5664 Project:

[jira] [Commented] (KAFKA-5608) System test failure due to timeout starting Jmx tool

[ https://issues.apache.org/jira/browse/KAFKA-5608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16092497#comment-16092497 ] Jason Gustafson commented on KAFKA-5608: [~ewencp] I think there is a race condition when starting

[jira] [Commented] (KAFKA-5586) Handle client disconnects during JoinGroup

[ https://issues.apache.org/jira/browse/KAFKA-5586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16093969#comment-16093969 ] Jason Gustafson commented on KAFKA-5586: For a bit more background, this problem came up in the

[jira] [Created] (KAFKA-5586) Handle client disconnects during JoinGroup

Jason Gustafson created KAFKA-5586: -- Summary: Handle client disconnects during JoinGroup Key: KAFKA-5586 URL: https://issues.apache.org/jira/browse/KAFKA-5586 Project: Kafka Issue Type: Bug

[jira] [Updated] (KAFKA-5624) Unsafe use of expired sensors

[ https://issues.apache.org/jira/browse/KAFKA-5624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-5624: --- Description: Seems a couple unhandled cases following sensor expiration: 1. Static sensors

[jira] [Commented] (KAFKA-5611) One or more consumers in a consumer-group stop consuming after rebalancing

[ https://issues.apache.org/jira/browse/KAFKA-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16094176#comment-16094176 ] Jason Gustafson commented on KAFKA-5611: [~pskianis] Thanks for the report. If at all possible,

[jira] [Created] (KAFKA-5624) Unsafe use of expired sensors

Jason Gustafson created KAFKA-5624: -- Summary: Unsafe use of expired sensors Key: KAFKA-5624 URL: https://issues.apache.org/jira/browse/KAFKA-5624 Project: Kafka Issue Type: Bug

[jira] [Created] (KAFKA-5534) KafkaConsumer offsetsForTimes should include partitions in result even if no offset could be found

Jason Gustafson created KAFKA-5534: -- Summary: KafkaConsumer offsetsForTimes should include partitions in result even if no offset could be found Key: KAFKA-5534 URL:

[jira] [Commented] (KAFKA-5526) ConsumerGroupCommand no longer shows output for consumer groups which have not committed offsets

[ https://issues.apache.org/jira/browse/KAFKA-5526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16067286#comment-16067286 ] Jason Gustafson commented on KAFKA-5526: [~vahid] That's a good question. I was discussing this

[jira] [Commented] (KAFKA-5547) Return topic authorization failed if no topic describe access

[ https://issues.apache.org/jira/browse/KAFKA-5547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16070487#comment-16070487 ] Jason Gustafson commented on KAFKA-5547: cc [~ijuma] Any reason this wouldn't work? > Return

[jira] [Created] (KAFKA-5547) Return topic authorization failed if no topic describe access

Jason Gustafson created KAFKA-5547: -- Summary: Return topic authorization failed if no topic describe access Key: KAFKA-5547 URL: https://issues.apache.org/jira/browse/KAFKA-5547 Project: Kafka

[jira] [Commented] (KAFKA-5526) ConsumerGroupCommand no longer shows output for consumer groups which have not committed offsets

[ https://issues.apache.org/jira/browse/KAFKA-5526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16065430#comment-16065430 ] Jason Gustafson commented on KAFKA-5526: [~vahid] Yeah, that's what I was thinking, a --members

[jira] [Commented] (KAFKA-5526) ConsumerGroupCommand no longer shows output for consumer groups which have not committed offsets

[ https://issues.apache.org/jira/browse/KAFKA-5526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16066866#comment-16066866 ] Jason Gustafson commented on KAFKA-5526: I suppose what I'm suggesting is that we not try to

[jira] [Commented] (KAFKA-5705) Kafka Server start failed and reports "unsafe memory access operation"

[ https://issues.apache.org/jira/browse/KAFKA-5705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16115065#comment-16115065 ] Jason Gustafson commented on KAFKA-5705: Seems a dup of KAFKA-5628? Please resolve if so. > Kafka

[jira] [Commented] (KAFKA-1944) Rename LogCleaner and related classes to LogCompactor

[ https://issues.apache.org/jira/browse/KAFKA-1944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16105845#comment-16105845 ] Jason Gustafson commented on KAFKA-1944: The name LogCleaner is somewhat entrenched. If this is

[jira] [Updated] (KAFKA-5666) Need feedback to user if consumption fails due to offsets.topic.replication.factor=3

[ https://issues.apache.org/jira/browse/KAFKA-5666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-5666: --- Labels: newbie usability (was: newbie) > Need feedback to user if consumption fails due to

[jira] [Commented] (KAFKA-5621) The producer should retry expired batches when retries are enabled

[ https://issues.apache.org/jira/browse/KAFKA-5621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16108095#comment-16108095 ] Jason Gustafson commented on KAFKA-5621: Interesting discussion. Apurva's suggestion on a

[jira] [Commented] (KAFKA-5638) Inconsistency in consumer group related ACLs

[ https://issues.apache.org/jira/browse/KAFKA-5638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16108007#comment-16108007 ] Jason Gustafson commented on KAFKA-5638: [~vahid] Interesting point. Maybe we could just extend

[jira] [Commented] (KAFKA-5705) Kafka Server start failed and reports "unsafe memory access operation"

[ https://issues.apache.org/jira/browse/KAFKA-5705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16118658#comment-16118658 ] Jason Gustafson commented on KAFKA-5705: [~waleedfateem] Seems you are right: the traces are a

[jira] [Reopened] (KAFKA-5705) Kafka Server start failed and reports "unsafe memory access operation"

[ https://issues.apache.org/jira/browse/KAFKA-5705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson reopened KAFKA-5705: > Kafka Server start failed and reports "unsafe memory access operation" >

[jira] [Resolved] (KAFKA-5629) Console Consumer overrides auto.offset.reset property when provided on the command line without warning about it.

[ https://issues.apache.org/jira/browse/KAFKA-5629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-5629. Resolution: Fixed Fix Version/s: 1.0.0 Issue resolved by pull request 3566

[jira] [Commented] (KAFKA-5611) One or more consumers in a consumer-group stop consuming after rebalancing

[ https://issues.apache.org/jira/browse/KAFKA-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16100986#comment-16100986 ] Jason Gustafson commented on KAFKA-5611: bq. Is the above a valid scenario? Does that mean that we

[jira] [Commented] (KAFKA-5546) Temporary loss of availability data when the leader is disconnected

[ https://issues.apache.org/jira/browse/KAFKA-5546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114569#comment-16114569 ] Jason Gustafson commented on KAFKA-5546: If you bring the interface down, do open connections get

[jira] [Commented] (KAFKA-5617) Update to the list of third-party clients

[ https://issues.apache.org/jira/browse/KAFKA-5617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114621#comment-16114621 ] Jason Gustafson commented on KAFKA-5617: [~dasch] I've granted you access to edit the wiki here:

[jira] [Commented] (KAFKA-5430) new consumers getting data for revoked partitions

[ https://issues.apache.org/jira/browse/KAFKA-5430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16116776#comment-16116776 ] Jason Gustafson commented on KAFKA-5430: [~liorchaga] Thanks for the report. I think this problem

[jira] [Commented] (KAFKA-5503) Idempotent producer ignores shutdown while fetching ProducerId

[ https://issues.apache.org/jira/browse/KAFKA-5503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16116804#comment-16116804 ] Jason Gustafson commented on KAFKA-5503: [~evis] Apologies for the late response. The issue is

[jira] [Resolved] (KAFKA-5705) Kafka Server start failed and reports "unsafe memory access operation"

[ https://issues.apache.org/jira/browse/KAFKA-5705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-5705. Resolution: Duplicate Marking this as a duplicate of KAFKA-5628 since the exception trace

[jira] [Commented] (KAFKA-5212) Consumer ListOffsets request can starve group heartbeats

[ https://issues.apache.org/jira/browse/KAFKA-5212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16116953#comment-16116953 ] Jason Gustafson commented on KAFKA-5212: [~evis] The fetcher and the heartbeat share the same

[jira] [Updated] (KAFKA-5747) Broker crashes on startup when trying to parse empty snapshot files

[ https://issues.apache.org/jira/browse/KAFKA-5747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-5747: --- Fix Version/s: 0.11.0.1 > Broker crashes on startup when trying to parse empty snapshot files

[jira] [Resolved] (KAFKA-5730) Consumer should ensure consistent ordering between sync and async offset commits

[ https://issues.apache.org/jira/browse/KAFKA-5730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-5730. Resolution: Fixed Issue resolved by pull request 3666

[jira] [Commented] (KAFKA-5747) Broker crashes on startup when trying to parse empty snapshot files

[ https://issues.apache.org/jira/browse/KAFKA-5747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16131252#comment-16131252 ] Jason Gustafson commented on KAFKA-5747: Changed the affected version to 0.11.0.0 only since this

[jira] [Updated] (KAFKA-5747) Broker crashes on startup when trying to parse empty snapshot files

[ https://issues.apache.org/jira/browse/KAFKA-5747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-5747: --- Affects Version/s: (was: 0.10.1.0) > Broker crashes on startup when trying to parse empty

[jira] [Assigned] (KAFKA-5747) Broker crashes on startup when trying to parse empty snapshot files

[ https://issues.apache.org/jira/browse/KAFKA-5747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson reassigned KAFKA-5747: -- Assignee: Jason Gustafson > Broker crashes on startup when trying to parse empty

[jira] [Created] (KAFKA-5478) TransactionsTest.testFencingOnAddPartitions Timeout

Jason Gustafson created KAFKA-5478: -- Summary: TransactionsTest.testFencingOnAddPartitions Timeout Key: KAFKA-5478 URL: https://issues.apache.org/jira/browse/KAFKA-5478 Project: Kafka Issue

[jira] [Created] (KAFKA-5492) LogRecoveryTest.testHWCheckpointWithFailuresSingleLogSegment transient failure

Jason Gustafson created KAFKA-5492: -- Summary: LogRecoveryTest.testHWCheckpointWithFailuresSingleLogSegment transient failure Key: KAFKA-5492 URL: https://issues.apache.org/jira/browse/KAFKA-5492

[jira] [Created] (KAFKA-5503) Idempotent producer ignores shutdown while fetching ProducerId

Jason Gustafson created KAFKA-5503: -- Summary: Idempotent producer ignores shutdown while fetching ProducerId Key: KAFKA-5503 URL: https://issues.apache.org/jira/browse/KAFKA-5503 Project: Kafka

[jira] [Created] (KAFKA-5522) ListOffset should take LSO into account when searching by timestamp

Jason Gustafson created KAFKA-5522: -- Summary: ListOffset should take LSO into account when searching by timestamp Key: KAFKA-5522 URL: https://issues.apache.org/jira/browse/KAFKA-5522 Project: Kafka

[jira] [Assigned] (KAFKA-5465) FetchResponse v0 does not return any messages when max_bytes smaller than v2 message set

[ https://issues.apache.org/jira/browse/KAFKA-5465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson reassigned KAFKA-5465: -- Assignee: Jason Gustafson > FetchResponse v0 does not return any messages when

[jira] [Updated] (KAFKA-5465) FetchResponse v0 does not return any messages when max_bytes smaller than v2 message set

[ https://issues.apache.org/jira/browse/KAFKA-5465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-5465: --- Fix Version/s: 0.11.0.0 > FetchResponse v0 does not return any messages when max_bytes

[jira] [Resolved] (KAFKA-5959) NPE in NetworkClient

[ https://issues.apache.org/jira/browse/KAFKA-5959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-5959. Resolution: Fixed Issue resolved by pull request 3947

[jira] [Updated] (KAFKA-5960) Producer uses unsupported ProduceRequest version against older brokers

[ https://issues.apache.org/jira/browse/KAFKA-5960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-5960: --- Fix Version/s: 1.0.0 > Producer uses unsupported ProduceRequest version against older brokers

[jira] [Created] (KAFKA-5957) Producer IllegalStateException due to second deallocate after aborting a batch

Jason Gustafson created KAFKA-5957: -- Summary: Producer IllegalStateException due to second deallocate after aborting a batch Key: KAFKA-5957 URL: https://issues.apache.org/jira/browse/KAFKA-5957

[jira] [Updated] (KAFKA-5957) Producer IllegalStateException due to second deallocate after aborting a batch

[ https://issues.apache.org/jira/browse/KAFKA-5957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-5957: --- Component/s: producer > Producer IllegalStateException due to second deallocate after

[jira] [Resolved] (KAFKA-5358) Consumer perf tool should count rebalance time separately

[ https://issues.apache.org/jira/browse/KAFKA-5358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-5358. Resolution: Fixed Fix Version/s: 1.0.0 Issue resolved by pull request 3188

[jira] [Created] (KAFKA-5905) Remove PrincipalBuilder and DefaultPrincipalBuilder

Jason Gustafson created KAFKA-5905: -- Summary: Remove PrincipalBuilder and DefaultPrincipalBuilder Key: KAFKA-5905 URL: https://issues.apache.org/jira/browse/KAFKA-5905 Project: Kafka Issue

[jira] [Reopened] (KAFKA-5792) Transient failure in KafkaAdminClientTest.testHandleTimeout

[ https://issues.apache.org/jira/browse/KAFKA-5792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson reopened KAFKA-5792: Still seeing this:

[jira] [Created] (KAFKA-5960) Producer uses unsupported ProduceRequest version against older brokers

Jason Gustafson created KAFKA-5960: -- Summary: Producer uses unsupported ProduceRequest version against older brokers Key: KAFKA-5960 URL: https://issues.apache.org/jira/browse/KAFKA-5960 Project:

[jira] [Updated] (KAFKA-5959) NPE in NetworkClient

[ https://issues.apache.org/jira/browse/KAFKA-5959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-5959: --- Fix Version/s: 1.0.0 > NPE in NetworkClient > > > Key:

[jira] [Resolved] (KAFKA-5547) Return topic authorization failed if no topic describe access

[ https://issues.apache.org/jira/browse/KAFKA-5547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-5547. Resolution: Fixed Fix Version/s: (was: 1.1.0) 1.0.0 Issue

[jira] [Created] (KAFKA-5841) Open old index files with read-only permission

Jason Gustafson created KAFKA-5841: -- Summary: Open old index files with read-only permission Key: KAFKA-5841 URL: https://issues.apache.org/jira/browse/KAFKA-5841 Project: Kafka Issue Type:

[jira] [Resolved] (KAFKA-5756) Synchronization issue on flush

[ https://issues.apache.org/jira/browse/KAFKA-5756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-5756. Resolution: Fixed Fix Version/s: 0.11.0.1 1.0.0 Issue resolved by

[jira] [Resolved] (KAFKA-6005) Reject JoinGroup request from first member with empty protocol type/protocol list

[ https://issues.apache.org/jira/browse/KAFKA-6005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6005. Resolution: Fixed Issue resolved by pull request 3957

[jira] [Resolved] (KAFKA-5342) Distinguish abortable failures in transactional producer

[ https://issues.apache.org/jira/browse/KAFKA-5342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-5342. Resolution: Fixed Fix Version/s: 1.0.0 Issue resolved by pull request 3716

[jira] [Created] (KAFKA-5783) Implement KafkaPrincipalBuilder interface with support for SASL (KIP-189)

Jason Gustafson created KAFKA-5783: -- Summary: Implement KafkaPrincipalBuilder interface with support for SASL (KIP-189) Key: KAFKA-5783 URL: https://issues.apache.org/jira/browse/KAFKA-5783 Project:

[jira] [Resolved] (KAFKA-5747) Broker crashes on startup when trying to parse empty snapshot files

[ https://issues.apache.org/jira/browse/KAFKA-5747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-5747. Resolution: Fixed Issue resolved by pull request 3688

[jira] [Assigned] (KAFKA-5822) Consistent logging of topic partitions

[ https://issues.apache.org/jira/browse/KAFKA-5822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson reassigned KAFKA-5822: -- Assignee: Jason Gustafson > Consistent logging of topic partitions >

[jira] [Resolved] (KAFKA-5768) Upgrade ducktape version to 0.7.1, and use new kill_java_processes

[ https://issues.apache.org/jira/browse/KAFKA-5768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-5768. Resolution: Fixed Fix Version/s: 1.0.0 Issue resolved by pull request 3721

[jira] [Commented] (KAFKA-5016) Consumer hang in poll method while rebalancing is in progress

[ https://issues.apache.org/jira/browse/KAFKA-5016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16149533#comment-16149533 ] Jason Gustafson commented on KAFKA-5016: [~gdstewar] Let me explain the intended behavior: 1.

[jira] [Resolved] (KAFKA-5806) Fix transient unit test failure in trogdor coordinator shutdown

[ https://issues.apache.org/jira/browse/KAFKA-5806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-5806. Resolution: Fixed Fix Version/s: 1.0.0 Issue resolved by pull request 3755

[jira] [Created] (KAFKA-6030) Integer overflow in log cleaner cleanable ratio computation

Jason Gustafson created KAFKA-6030: -- Summary: Integer overflow in log cleaner cleanable ratio computation Key: KAFKA-6030 URL: https://issues.apache.org/jira/browse/KAFKA-6030 Project: Kafka

[jira] [Resolved] (KAFKA-6030) Integer overflow in log cleaner cleanable ratio computation

[ https://issues.apache.org/jira/browse/KAFKA-6030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6030. Resolution: Fixed Issue resolved by pull request 4043

[jira] [Commented] (KAFKA-6014) new consumer mirror maker halts after committing offsets to a deleted topic

[ https://issues.apache.org/jira/browse/KAFKA-6014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16211760#comment-16211760 ] Jason Gustafson commented on KAFKA-6014: Yeah, I agree with [~gilles.degols]. I'm not sure

[jira] [Assigned] (KAFKA-6014) new consumer mirror maker halts after committing offsets to a deleted topic

[ https://issues.apache.org/jira/browse/KAFKA-6014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson reassigned KAFKA-6014: -- Assignee: Jason Gustafson > new consumer mirror maker halts after committing offsets

[jira] [Created] (KAFKA-6275) Extend consumer offset reset tool to support deletion

Jason Gustafson created KAFKA-6275: -- Summary: Extend consumer offset reset tool to support deletion Key: KAFKA-6275 URL: https://issues.apache.org/jira/browse/KAFKA-6275 Project: Kafka

[jira] [Commented] (KAFKA-6275) Extend consumer offset reset tool to support deletion

[ https://issues.apache.org/jira/browse/KAFKA-6275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16267288#comment-16267288 ] Jason Gustafson commented on KAFKA-6275: [~vahid] Sure, makes sense to get in KIP-175 first (I'll

[jira] [Commented] (KAFKA-6278) Allow multiple concurrent transactions on a single producer

[ https://issues.apache.org/jira/browse/KAFKA-6278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16269597#comment-16269597 ] Jason Gustafson commented on KAFKA-6278: Thanks for the report. This was an unfortunate tradeoff

[jira] [Created] (KAFKA-6263) Expose metric for group metadata loading duration

Jason Gustafson created KAFKA-6263: -- Summary: Expose metric for group metadata loading duration Key: KAFKA-6263 URL: https://issues.apache.org/jira/browse/KAFKA-6263 Project: Kafka Issue

[jira] [Assigned] (KAFKA-6260) AbstractCoordinator not clearly handles NULL Exception

[ https://issues.apache.org/jira/browse/KAFKA-6260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson reassigned KAFKA-6260: -- Assignee: Jason Gustafson > AbstractCoordinator not clearly handles NULL Exception >

[jira] [Commented] (KAFKA-6260) AbstractCoordinator not clearly handles NULL Exception

[ https://issues.apache.org/jira/browse/KAFKA-6260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16271352#comment-16271352 ] Jason Gustafson commented on KAFKA-6260: [~guozhang] The collection mentioned above was only

[jira] [Commented] (KAFKA-6260) AbstractCoordinator not clearly handles NULL Exception

[ https://issues.apache.org/jira/browse/KAFKA-6260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16271400#comment-16271400 ] Jason Gustafson commented on KAFKA-6260: [~habdank] If possible, can you test with the patch

[jira] [Commented] (KAFKA-4669) KafkaProducer.flush hangs when NetworkClient.handleCompletedReceives throws exception

[ https://issues.apache.org/jira/browse/KAFKA-4669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16271827#comment-16271827 ] Jason Gustafson commented on KAFKA-4669: Reopened since there are two reported cases on 0.11.0.1.

[jira] [Commented] (KAFKA-4669) KafkaProducer.flush hangs when NetworkClient.handleCompletedReceives throws exception

[ https://issues.apache.org/jira/browse/KAFKA-4669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16271902#comment-16271902 ] Jason Gustafson commented on KAFKA-4669: [~aartigupta] The consumer logs would probably be more

[jira] [Reopened] (KAFKA-4669) KafkaProducer.flush hangs when NetworkClient.handleCompletedReceives throws exception

[ https://issues.apache.org/jira/browse/KAFKA-4669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson reopened KAFKA-4669: > KafkaProducer.flush hangs when NetworkClient.handleCompletedReceives throws > exception >

[jira] [Updated] (KAFKA-5936) KafkaProducer should not wrap InterruptedException in close() with KafkaException

[ https://issues.apache.org/jira/browse/KAFKA-5936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-5936: --- Fix Version/s: (was: 1.0.1) 1.1.0 > KafkaProducer should not wrap

[jira] [Commented] (KAFKA-4669) KafkaProducer.flush hangs when NetworkClient.handleCompletedReceives throws exception

[ https://issues.apache.org/jira/browse/KAFKA-4669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16271832#comment-16271832 ] Jason Gustafson commented on KAFKA-4669: [~nickt] [~aartigupta] Do either of you have client logs?

[jira] [Commented] (KAFKA-4669) KafkaProducer.flush hangs when NetworkClient.handleCompletedReceives throws exception

[ https://issues.apache.org/jira/browse/KAFKA-4669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16273501#comment-16273501 ] Jason Gustafson commented on KAFKA-4669: Rajini is right that this is probably caused by some

[jira] [Commented] (KAFKA-6282) exactly_once semantics breaks demo application

[ https://issues.apache.org/jira/browse/KAFKA-6282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16273527#comment-16273527 ] Jason Gustafson commented on KAFKA-6282: [~bigmcmark] [~mjsax] Would either of you be willing to

[jira] [Created] (KAFKA-6289) NetworkClient should not return internal failed api version responses from poll

Jason Gustafson created KAFKA-6289: -- Summary: NetworkClient should not return internal failed api version responses from poll Key: KAFKA-6289 URL: https://issues.apache.org/jira/browse/KAFKA-6289

[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=16267904#comment-16267904 ] Jason Gustafson commented on KAFKA-6264: [~becket_qin] Good catch. For users who hit this, one

[jira] [Created] (KAFKA-6276) AdminClient may leave some futures hanging after shutdown

Jason Gustafson created KAFKA-6276: -- Summary: AdminClient may leave some futures hanging after shutdown Key: KAFKA-6276 URL: https://issues.apache.org/jira/browse/KAFKA-6276 Project: Kafka

[jira] [Updated] (KAFKA-6271) FileInputStream.skip function can return 0 when the file is corrupted, causing an infinite loop

[ https://issues.apache.org/jira/browse/KAFKA-6271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-6271: --- Component/s: KafkaConnect > FileInputStream.skip function can return 0 when the file is

[jira] [Commented] (KAFKA-6260) AbstractCoordinator not clearly handles NULL Exception

[ https://issues.apache.org/jira/browse/KAFKA-6260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16271269#comment-16271269 ] Jason Gustafson commented on KAFKA-6260: I think I may have spotted a possible cause.

  1   2   3   4   5   6   7   8   9   10   >