[jira] [Created] (KAFKA-6082) consider fencing zookeeper updates with controller epoch zkVersion

2017-10-18 Thread Onur Karaman (JIRA)
Onur Karaman created KAFKA-6082: --- Summary: consider fencing zookeeper updates with controller epoch zkVersion Key: KAFKA-6082 URL: https://issues.apache.org/jira/browse/KAFKA-6082 Project: Kafka

[jira] [Created] (KAFKA-6081) response error code checking

2017-10-18 Thread Onur Karaman (JIRA)
Onur Karaman created KAFKA-6081: --- Summary: response error code checking Key: KAFKA-6081 URL: https://issues.apache.org/jira/browse/KAFKA-6081 Project: Kafka Issue Type: Sub-task

[jira] [Resolved] (KAFKA-5083) always leave the last surviving member of the ISR in ZK

2017-10-18 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Onur Karaman resolved KAFKA-5083. - Resolution: Fixed This has been fixed in KAFKA-5642. > always leave the last surviving member of

[jira] [Created] (KAFKA-6065) Add zookeeper metrics to ZookeeperClient as in KIP-188

2017-10-16 Thread Onur Karaman (JIRA)
Onur Karaman created KAFKA-6065: --- Summary: Add zookeeper metrics to ZookeeperClient as in KIP-188 Key: KAFKA-6065 URL: https://issues.apache.org/jira/browse/KAFKA-6065 Project: Kafka Issue

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

2017-10-04 Thread Onur Karaman (JIRA)
Onur Karaman created KAFKA-6014: --- Summary: new consumer mirror maker halts after committing offsets to a deleted topic Key: KAFKA-6014 URL: https://issues.apache.org/jira/browse/KAFKA-6014 Project:

[jira] [Created] (KAFKA-5894) add the notion of max inflight requests to async ZookeeperClient

2017-09-14 Thread Onur Karaman (JIRA)
Onur Karaman created KAFKA-5894: --- Summary: add the notion of max inflight requests to async ZookeeperClient Key: KAFKA-5894 URL: https://issues.apache.org/jira/browse/KAFKA-5894 Project: Kafka

[jira] [Resolved] (KAFKA-4747) add metrics for KafkaConsumer.poll

2017-09-11 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Onur Karaman resolved KAFKA-4747. - Resolution: Won't Fix [~junrao] pointed out that the distinction between tim-in-poll and

[jira] [Resolved] (KAFKA-5703) allow debug-level logging for RequestChannel's request logger

2017-08-04 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Onur Karaman resolved KAFKA-5703. - Resolution: Fixed Woops. Looks like [~ijuma] already fixed this 3 days ago:

[jira] [Created] (KAFKA-5703) allow debug-level logging for RequestChannel's request logger

2017-08-04 Thread Onur Karaman (JIRA)
Onur Karaman created KAFKA-5703: --- Summary: allow debug-level logging for RequestChannel's request logger Key: KAFKA-5703 URL: https://issues.apache.org/jira/browse/KAFKA-5703 Project: Kafka

[jira] [Resolved] (KAFKA-5501) introduce async ZookeeperClient

2017-07-26 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Onur Karaman resolved KAFKA-5501. - Resolution: Fixed > introduce async ZookeeperClient > --- > >

[jira] [Created] (KAFKA-5642) use async ZookeeperClient everywhere

2017-07-26 Thread Onur Karaman (JIRA)
Onur Karaman created KAFKA-5642: --- Summary: use async ZookeeperClient everywhere Key: KAFKA-5642 URL: https://issues.apache.org/jira/browse/KAFKA-5642 Project: Kafka Issue Type: Sub-task

[jira] [Created] (KAFKA-5502) read current brokers from zookeeper upon processing broker change

2017-06-22 Thread Onur Karaman (JIRA)
Onur Karaman created KAFKA-5502: --- Summary: read current brokers from zookeeper upon processing broker change Key: KAFKA-5502 URL: https://issues.apache.org/jira/browse/KAFKA-5502 Project: Kafka

[jira] [Created] (KAFKA-5501) use async zookeeper apis everywhere

2017-06-22 Thread Onur Karaman (JIRA)
Onur Karaman created KAFKA-5501: --- Summary: use async zookeeper apis everywhere Key: KAFKA-5501 URL: https://issues.apache.org/jira/browse/KAFKA-5501 Project: Kafka Issue Type: Sub-task

[jira] [Commented] (KAFKA-4595) Controller send thread can't stop when broker change listener event trigger for dead brokers

2017-06-02 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16035465#comment-16035465 ] Onur Karaman commented on KAFKA-4595: - [~ijuma] Yeah I think KAFKA-5028 solved this issue. >

[jira] [Commented] (KAFKA-1595) Remove deprecated and slower scala JSON parser from kafka.consumer.TopicCount

2017-06-02 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-1595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16035365#comment-16035365 ] Onur Karaman commented on KAFKA-1595: - Sounds good. > Remove deprecated and slower scala JSON parser

[jira] [Comment Edited] (KAFKA-1595) Remove deprecated and slower scala JSON parser from kafka.consumer.TopicCount

2017-05-31 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-1595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16032276#comment-16032276 ] Onur Karaman edited comment on KAFKA-1595 at 6/1/17 12:50 AM: -- I think

[jira] [Commented] (KAFKA-1595) Remove deprecated and slower scala JSON parser from kafka.consumer.TopicCount

2017-05-31 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-1595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16032276#comment-16032276 ] Onur Karaman commented on KAFKA-1595: - I think [~ijuma]'s PR (https://github.com/apache/kafka/pull/83)

[jira] [Commented] (KAFKA-5328) consider switching json parser from scala to jackson

2017-05-26 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16027086#comment-16027086 ] Onur Karaman commented on KAFKA-5328: - I copied the topic assignment znodes and partition state znodes

[jira] [Created] (KAFKA-5328) consider switching json parser from scala to jackson

2017-05-25 Thread Onur Karaman (JIRA)
Onur Karaman created KAFKA-5328: --- Summary: consider switching json parser from scala to jackson Key: KAFKA-5328 URL: https://issues.apache.org/jira/browse/KAFKA-5328 Project: Kafka Issue Type:

[jira] [Updated] (KAFKA-5323) AdminUtils.createTopic should check topic existence upfront

2017-05-25 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Onur Karaman updated KAFKA-5323: Status: Patch Available (was: Open) > AdminUtils.createTopic should check topic existence upfront

[jira] [Commented] (KAFKA-5323) AdminUtils.createTopic should check topic existence upfront

2017-05-24 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16024223#comment-16024223 ] Onur Karaman commented on KAFKA-5323: - This can have a larger impact than one might initially suspect.

[jira] [Created] (KAFKA-5323) AdminUtils.createTopic should check topic existence upfront

2017-05-24 Thread Onur Karaman (JIRA)
Onur Karaman created KAFKA-5323: --- Summary: AdminUtils.createTopic should check topic existence upfront Key: KAFKA-5323 URL: https://issues.apache.org/jira/browse/KAFKA-5323 Project: Kafka

[jira] [Updated] (KAFKA-5310) reset ControllerContext during resignation

2017-05-23 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Onur Karaman updated KAFKA-5310: Status: Patch Available (was: Open) > reset ControllerContext during resignation >

[jira] [Updated] (KAFKA-5310) reset ControllerContext during resignation

2017-05-23 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Onur Karaman updated KAFKA-5310: Description: This ticket is all about ControllerContext initialization and teardown. The key

[jira] [Created] (KAFKA-5310) reset ControllerContext during resignation

2017-05-23 Thread Onur Karaman (JIRA)
Onur Karaman created KAFKA-5310: --- Summary: reset ControllerContext during resignation Key: KAFKA-5310 URL: https://issues.apache.org/jira/browse/KAFKA-5310 Project: Kafka Issue Type: Sub-task

[jira] [Commented] (KAFKA-4896) Offset loading can use more threads

2017-05-22 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16020447#comment-16020447 ] Onur Karaman commented on KAFKA-4896: - handleGroupImmigration only gets called from handling a

[jira] [Updated] (KAFKA-5258) move all partition and replica state transition rules into their states

2017-05-17 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Onur Karaman updated KAFKA-5258: Description: Today the PartitionStateMachine and ReplicaStateMachine defines and asserts the valid

[jira] [Updated] (KAFKA-5258) move all partition and replica state transition rules into their states

2017-05-17 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Onur Karaman updated KAFKA-5258: Description: Today the PartitionStateMachine and ReplicaStateMachine defines and asserts the valid

[jira] [Updated] (KAFKA-5258) move all partition and replica state transition rules into their states

2017-05-17 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Onur Karaman updated KAFKA-5258: Summary: move all partition and replica state transition rules into their states (was: move all

[jira] [Commented] (KAFKA-5261) Performance improvement of SimpleAclAuthorizer

2017-05-17 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16013665#comment-16013665 ] Onur Karaman commented on KAFKA-5261: - Would one alternative be to just make a CachedAclAuthorizer

[jira] [Updated] (KAFKA-5258) move all partition and replica state transition rules into a map

2017-05-16 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Onur Karaman updated KAFKA-5258: Status: Patch Available (was: In Progress) > move all partition and replica state transition rules

[jira] [Work started] (KAFKA-5258) move all partition and replica state transition rules into a map

2017-05-16 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-5258 started by Onur Karaman. --- > move all partition and replica state transition rules into a map >

[jira] [Created] (KAFKA-5258) move all partition and replica state transition rules into a map

2017-05-16 Thread Onur Karaman (JIRA)
Onur Karaman created KAFKA-5258: --- Summary: move all partition and replica state transition rules into a map Key: KAFKA-5258 URL: https://issues.apache.org/jira/browse/KAFKA-5258 Project: Kafka

[jira] [Comment Edited] (KAFKA-5175) Transient failure: ControllerIntegrationTest.testPreferredReplicaLeaderElection

2017-05-16 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16011851#comment-16011851 ] Onur Karaman edited comment on KAFKA-5175 at 5/16/17 7:01 AM: -- Cool. I can

[jira] [Commented] (KAFKA-5175) Transient failure: ControllerIntegrationTest.testPreferredReplicaLeaderElection

2017-05-16 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16011851#comment-16011851 ] Onur Karaman commented on KAFKA-5175: - Cool. I can steadily reproduce this by inserting a long sleep

[jira] [Commented] (KAFKA-5175) Transient failure: ControllerIntegrationTest.testPreferredReplicaLeaderElection

2017-05-15 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16011500#comment-16011500 ] Onur Karaman commented on KAFKA-5175: - Thanks [~ijuma]. I've been staring at this and couldn't figure

[jira] [Commented] (KAFKA-3356) Remove ConsumerOffsetChecker, deprecated in 0.9, in 0.11

2017-05-15 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16010823#comment-16010823 ] Onur Karaman commented on KAFKA-3356: - I agree with [~jeffwidman]. > Remove ConsumerOffsetChecker,

[jira] [Updated] (KAFKA-5180) Transient failure: ControllerIntegrationTest.testControllerMoveIncrementsControllerEpoch

2017-05-12 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Onur Karaman updated KAFKA-5180: Status: Patch Available (was: In Progress) > Transient failure: >

[jira] [Work started] (KAFKA-5180) Transient failure: ControllerIntegrationTest.testControllerMoveIncrementsControllerEpoch

2017-05-12 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-5180 started by Onur Karaman. --- > Transient failure: >

[jira] [Resolved] (KAFKA-5120) Several controller metrics block if controller lock is held by another thread

2017-05-11 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Onur Karaman resolved KAFKA-5120. - Resolution: Fixed KAFKA-5028 has been checked in so this should no longer be an issue. > Several

[jira] [Resolved] (KAFKA-3107) Error when trying to shut down auto balancing scheduler of controller

2017-05-11 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Onur Karaman resolved KAFKA-3107. - Resolution: Fixed This problem should no longer exist after KAFKA-5028. > Error when trying to

[jira] [Updated] (KAFKA-5197) add a tool analyzing zookeeper client performance across its various apis

2017-05-08 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Onur Karaman updated KAFKA-5197: Status: Patch Available (was: In Progress) > add a tool analyzing zookeeper client performance

[jira] [Work started] (KAFKA-5197) add a tool analyzing zookeeper client performance across its various apis

2017-05-08 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-5197 started by Onur Karaman. --- > add a tool analyzing zookeeper client performance across its various apis >

[jira] [Created] (KAFKA-5197) add a tool analyzing zookeeper client performance across its various apis

2017-05-08 Thread Onur Karaman (JIRA)
Onur Karaman created KAFKA-5197: --- Summary: add a tool analyzing zookeeper client performance across its various apis Key: KAFKA-5197 URL: https://issues.apache.org/jira/browse/KAFKA-5197 Project: Kafka

[jira] [Commented] (KAFKA-5099) Replica Deletion Regression from KIP-101

2017-05-07 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16000261#comment-16000261 ] Onur Karaman commented on KAFKA-5099: - By the way, I reran the file descriptor experiment against both

[jira] [Commented] (KAFKA-5099) Replica Deletion Regression from KIP-101

2017-05-05 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15999200#comment-15999200 ] Onur Karaman commented on KAFKA-5099: - Hi [~junrao]. Thanks for figuring it out. I gave your solution

[jira] [Assigned] (KAFKA-5180) Transient failure: ControllerIntegrationTest.testControllerMoveIncrementsControllerEpoch

2017-05-05 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Onur Karaman reassigned KAFKA-5180: --- Assignee: Onur Karaman > Transient failure: >

[jira] [Assigned] (KAFKA-5175) Transient failure: ControllerIntegrationTest.testPreferredReplicaLeaderElection

2017-05-04 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Onur Karaman reassigned KAFKA-5175: --- Assignee: Onur Karaman > Transient failure: >

[jira] [Updated] (KAFKA-5107) remove preferred replica election state from ControllerContext

2017-04-27 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Onur Karaman updated KAFKA-5107: Status: Patch Available (was: In Progress) > remove preferred replica election state from

[jira] [Work started] (KAFKA-5107) remove preferred replica election state from ControllerContext

2017-04-27 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-5107 started by Onur Karaman. --- > remove preferred replica election state from ControllerContext >

[jira] [Commented] (KAFKA-5028) convert kafka controller to a single-threaded event queue model

2017-04-27 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15987101#comment-15987101 ] Onur Karaman commented on KAFKA-5028: - Shortly after check-in, I noticed a bug: the patch has

[jira] [Commented] (KAFKA-5120) Several controller metrics block if controller lock is held by another thread

2017-04-24 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15982118#comment-15982118 ] Onur Karaman commented on KAFKA-5120: - This will be fixed in KAFKA-5028. It chooses the latter

[jira] [Updated] (KAFKA-5107) remove preferred replica election state from ControllerContext

2017-04-21 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Onur Karaman updated KAFKA-5107: Summary: remove preferred replica election state from ControllerContext (was: investigate removing

[jira] [Created] (KAFKA-5107) investigate removing preferred replica leader election state from ControllerContext

2017-04-21 Thread Onur Karaman (JIRA)
Onur Karaman created KAFKA-5107: --- Summary: investigate removing preferred replica leader election state from ControllerContext Key: KAFKA-5107 URL: https://issues.apache.org/jira/browse/KAFKA-5107

[jira] [Commented] (KAFKA-5099) Replica Deletion Regression from KIP-101

2017-04-20 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15977902#comment-15977902 ] Onur Karaman commented on KAFKA-5099: - My initial guess is that the new epoch checkpoint file isn't

[jira] [Created] (KAFKA-5099) Replica Deletion Regression from KIP-101

2017-04-20 Thread Onur Karaman (JIRA)
Onur Karaman created KAFKA-5099: --- Summary: Replica Deletion Regression from KIP-101 Key: KAFKA-5099 URL: https://issues.apache.org/jira/browse/KAFKA-5099 Project: Kafka Issue Type: Bug

[jira] [Created] (KAFKA-5083) always leave the last surviving member of the ISR in ZK

2017-04-18 Thread Onur Karaman (JIRA)
Onur Karaman created KAFKA-5083: --- Summary: always leave the last surviving member of the ISR in ZK Key: KAFKA-5083 URL: https://issues.apache.org/jira/browse/KAFKA-5083 Project: Kafka Issue

[jira] [Updated] (KAFKA-5069) add controller integration tests

2017-04-14 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Onur Karaman updated KAFKA-5069: Status: Patch Available (was: In Progress) > add controller integration tests >

[jira] [Updated] (KAFKA-5028) convert kafka controller to a single-threaded event queue model

2017-04-14 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Onur Karaman updated KAFKA-5028: Status: Patch Available (was: In Progress) > convert kafka controller to a single-threaded event

[jira] [Work started] (KAFKA-5069) add controller integration tests

2017-04-13 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-5069 started by Onur Karaman. --- > add controller integration tests > > >

[jira] [Created] (KAFKA-5069) add controller integration tests

2017-04-13 Thread Onur Karaman (JIRA)
Onur Karaman created KAFKA-5069: --- Summary: add controller integration tests Key: KAFKA-5069 URL: https://issues.apache.org/jira/browse/KAFKA-5069 Project: Kafka Issue Type: Sub-task

[jira] [Work started] (KAFKA-5028) convert kafka controller to a single-threaded event queue model

2017-04-05 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-5028 started by Onur Karaman. --- > convert kafka controller to a single-threaded event queue model >

[jira] [Updated] (KAFKA-5028) convert kafka controller to a single-threaded event queue model

2017-04-05 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Onur Karaman updated KAFKA-5028: Summary: convert kafka controller to a single-threaded event queue model (was: Convert Kafka

[jira] [Created] (KAFKA-5028) Convert Kafka Controller to a single-threaded event queue model

2017-04-05 Thread Onur Karaman (JIRA)
Onur Karaman created KAFKA-5028: --- Summary: Convert Kafka Controller to a single-threaded event queue model Key: KAFKA-5028 URL: https://issues.apache.org/jira/browse/KAFKA-5028 Project: Kafka

[jira] [Created] (KAFKA-5027) Kafka Controller Redesign

2017-04-05 Thread Onur Karaman (JIRA)
Onur Karaman created KAFKA-5027: --- Summary: Kafka Controller Redesign Key: KAFKA-5027 URL: https://issues.apache.org/jira/browse/KAFKA-5027 Project: Kafka Issue Type: Improvement

[jira] [Updated] (KAFKA-4959) remove controller concurrent access to non-threadsafe NetworkClient, Selector, and SSLEngine

2017-03-27 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Onur Karaman updated KAFKA-4959: Status: Patch Available (was: In Progress) > remove controller concurrent access to non-threadsafe

[jira] [Work started] (KAFKA-4959) remove controller concurrent access to non-threadsafe NetworkClient, Selector, and SSLEngine

2017-03-27 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-4959 started by Onur Karaman. --- > remove controller concurrent access to non-threadsafe NetworkClient, >

[jira] [Created] (KAFKA-4959) remove controller concurrent access to non-threadsafe NetworkClient, Selector, and SSLEngine

2017-03-27 Thread Onur Karaman (JIRA)
Onur Karaman created KAFKA-4959: --- Summary: remove controller concurrent access to non-threadsafe NetworkClient, Selector, and SSLEngine Key: KAFKA-4959 URL: https://issues.apache.org/jira/browse/KAFKA-4959

[jira] [Commented] (KAFKA-4900) Brokers stuck in controller re-election loop after failing to register metrics

2017-03-27 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15943568#comment-15943568 ] Onur Karaman commented on KAFKA-4900: - [~nickt] Do you think it makes sense for me to open a new

[jira] [Commented] (KAFKA-4900) Brokers stuck in controller re-election loop after failing to register metrics

2017-03-24 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15941296#comment-15941296 ] Onur Karaman commented on KAFKA-4900: - I haven't figured out some of the small details but I think I

[jira] [Commented] (KAFKA-4900) Brokers stuck in controller re-election loop after failing to register metrics

2017-03-16 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15929447#comment-15929447 ] Onur Karaman commented on KAFKA-4900: - Okay yeah with bad znode data, I could see how the controller

[jira] [Commented] (KAFKA-4893) async topic deletion conflicts with max topic length

2017-03-15 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15927298#comment-15927298 ] Onur Karaman commented on KAFKA-4893: - Also [~vahid] while I agree reducing the limit is by far the

[jira] [Commented] (KAFKA-4900) Brokers stuck in controller re-election loop after failing to register metrics

2017-03-15 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15927200#comment-15927200 ] Onur Karaman commented on KAFKA-4900: - I hadn't yet investigated why some of the fetchers hadn't

[jira] [Comment Edited] (KAFKA-4893) async topic deletion conflicts with max topic length

2017-03-15 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15927155#comment-15927155 ] Onur Karaman edited comment on KAFKA-4893 at 3/15/17 11:23 PM: --- [~ijuma] I

[jira] [Commented] (KAFKA-4893) async topic deletion conflicts with max topic length

2017-03-15 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15927155#comment-15927155 ] Onur Karaman commented on KAFKA-4893: - [~ijuma] I had thought about the additional fsync on the

[jira] [Comment Edited] (KAFKA-4900) Brokers stuck in controller re-election loop after failing to register metrics

2017-03-15 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15925611#comment-15925611 ] Onur Karaman edited comment on KAFKA-4900 at 3/15/17 6:44 AM: -- For reference,

[jira] [Commented] (KAFKA-4900) Brokers stuck in controller re-election loop after failing to register metrics

2017-03-15 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15925611#comment-15925611 ] Onur Karaman commented on KAFKA-4900: - For reference, I think the controller was changing every 3

[jira] [Commented] (KAFKA-4900) Brokers stuck in controller re-election loop after failing to register metrics

2017-03-14 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15925503#comment-15925503 ] Onur Karaman commented on KAFKA-4900: - We hit the same re-election loop issue from

[jira] [Commented] (KAFKA-4896) Offset loading can use more threads

2017-03-14 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15924764#comment-15924764 ] Onur Karaman commented on KAFKA-4896: - [~junrao] Naively bumping the number of scheduler threads might

[jira] [Commented] (KAFKA-4893) async topic deletion conflicts with max topic length

2017-03-14 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15923636#comment-15923636 ] Onur Karaman commented on KAFKA-4893: - Maybe the right move is to just add more layers to the log

[jira] [Created] (KAFKA-4893) async topic deletion conflicts with max topic length

2017-03-13 Thread Onur Karaman (JIRA)
Onur Karaman created KAFKA-4893: --- Summary: async topic deletion conflicts with max topic length Key: KAFKA-4893 URL: https://issues.apache.org/jira/browse/KAFKA-4893 Project: Kafka Issue Type:

[jira] [Created] (KAFKA-4891) kafka.request.logger TRACE regression

2017-03-13 Thread Onur Karaman (JIRA)
Onur Karaman created KAFKA-4891: --- Summary: kafka.request.logger TRACE regression Key: KAFKA-4891 URL: https://issues.apache.org/jira/browse/KAFKA-4891 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-1895) Investigate moving deserialization and decompression out of KafkaConsumer

2017-02-22 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-1895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15879561#comment-15879561 ] Onur Karaman commented on KAFKA-1895: - I think it's worth defining the relation between the two

[jira] [Commented] (KAFKA-4753) KafkaConsumer susceptible to FetchResponse starvation

2017-02-22 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15879558#comment-15879558 ] Onur Karaman commented on KAFKA-4753: - [~ijuma] I don't think mitigation is the way to go. The two

[jira] [Commented] (KAFKA-4757) Improve NetworkClient trace logging of request details

2017-02-17 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15872616#comment-15872616 ] Onur Karaman commented on KAFKA-4757: - Left some comments on the PR. Speaking of which, usually the

[jira] [Commented] (KAFKA-4757) NetworkClient should log request details at trace level when a request is cancelled because of disconnection

2017-02-17 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15872390#comment-15872390 ] Onur Karaman commented on KAFKA-4757: - Ah. Might've found it: Here's what ApiVersionsRequest schema

[jira] [Commented] (KAFKA-4757) NetworkClient should log request details at trace level when a request is cancelled because of disconnection

2017-02-17 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15872284#comment-15872284 ] Onur Karaman commented on KAFKA-4757: - [~cmccabe] I double checked and the 2nd logging issue still

[jira] [Commented] (KAFKA-4676) Kafka consumers gets stuck for some partitions

2017-02-17 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15872213#comment-15872213 ] Onur Karaman commented on KAFKA-4676: - This ticket never really found a root cause so it might not be

[jira] [Commented] (KAFKA-4676) Kafka consumers gets stuck for some partitions

2017-02-17 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15872199#comment-15872199 ] Onur Karaman commented on KAFKA-4676: - [~Narendra Kumar] if you're repeatedly seeing the request

[jira] [Commented] (KAFKA-4757) NetworkClient should log request details at trace level when a request is cancelled because of disconnection

2017-02-17 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15872194#comment-15872194 ] Onur Karaman commented on KAFKA-4757: - Thanks [~cmccabe]. Regarding the second issue, I'll need to

[jira] [Created] (KAFKA-4757) NetworkClient trace level logging regressions

2017-02-10 Thread Onur Karaman (JIRA)
Onur Karaman created KAFKA-4757: --- Summary: NetworkClient trace level logging regressions Key: KAFKA-4757 URL: https://issues.apache.org/jira/browse/KAFKA-4757 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-4753) KafkaConsumer susceptible to FetchResponse starvation

2017-02-09 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15860872#comment-15860872 ] Onur Karaman commented on KAFKA-4753: - It might mitigate users whose consumers participate in group

[jira] [Commented] (KAFKA-4753) KafkaConsumer susceptible to FetchResponse starvation

2017-02-09 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15860366#comment-15860366 ] Onur Karaman commented on KAFKA-4753: - One way to mitigate but not fully solve the starvation problem

[jira] [Created] (KAFKA-4753) KafkaConsumer susceptible to FetchResponse starvation

2017-02-09 Thread Onur Karaman (JIRA)
Onur Karaman created KAFKA-4753: --- Summary: KafkaConsumer susceptible to FetchResponse starvation Key: KAFKA-4753 URL: https://issues.apache.org/jira/browse/KAFKA-4753 Project: Kafka Issue

[jira] [Created] (KAFKA-4749) fix join-time-max and sync-time-max MeasurableStat type

2017-02-08 Thread Onur Karaman (JIRA)
Onur Karaman created KAFKA-4749: --- Summary: fix join-time-max and sync-time-max MeasurableStat type Key: KAFKA-4749 URL: https://issues.apache.org/jira/browse/KAFKA-4749 Project: Kafka Issue

[jira] [Created] (KAFKA-4747) add metrics for KafkaConsumer.poll

2017-02-08 Thread Onur Karaman (JIRA)
Onur Karaman created KAFKA-4747: --- Summary: add metrics for KafkaConsumer.poll Key: KAFKA-4747 URL: https://issues.apache.org/jira/browse/KAFKA-4747 Project: Kafka Issue Type: Improvement

[jira] [Assigned] (KAFKA-4513) Support migration of old consumers to new consumers without downtime

2017-02-06 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Onur Karaman reassigned KAFKA-4513: --- Assignee: Onur Karaman > Support migration of old consumers to new consumers without

[jira] [Commented] (KAFKA-4704) Group coordinator cache loading fails if groupId is used first for consumer groups and then for simple consumer

2017-01-26 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15840663#comment-15840663 ] Onur Karaman commented on KAFKA-4704: - It might be worth mentioning that I hit a similar scenario when

[jira] [Updated] (KAFKA-3959) __consumer_offsets wrong number of replicas at startup

2017-01-25 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Onur Karaman updated KAFKA-3959: Fix Version/s: (was: 0.10.3.0) 0.10.2.0 > __consumer_offsets wrong number of

[jira] [Commented] (KAFKA-4576) Log segments close to max size break on fetch

2017-01-03 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15794567#comment-15794567 ] Onur Karaman commented on KAFKA-4576: - I think you're right, [~huxi_2b]. It looks like we incorrectly

  1   2   3   4   >