Jun Rao created KAFKA-3045:
--
Summary: ZkNodeChangeNotificationListener shouldn't log
interrupted exception as error
Key: KAFKA-3045
URL: https://issues.apache.org/jira/browse/KAFKA-3045
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-3045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-3045:
---
Labels: security (was: )
> ZkNodeChangeNotificationListener shouldn't log interrupted exception as error
> --
Jun Rao created KAFKA-3048:
--
Summary: incorrect property name ssl.want.client.auth
Key: KAFKA-3048
URL: https://issues.apache.org/jira/browse/KAFKA-3048
Project: Kafka
Issue Type: Improvement
Jun Rao created KAFKA-3051:
--
Summary: security.protocol documentation is inaccurate
Key: KAFKA-3051
URL: https://issues.apache.org/jira/browse/KAFKA-3051
Project: Kafka
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/KAFKA-3045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-3045:
---
Fix Version/s: 0.9.0.1
> ZkNodeChangeNotificationListener shouldn't log interrupted exception as error
> -
[
https://issues.apache.org/jira/browse/KAFKA-3048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-3048:
---
Fix Version/s: 0.9.0.1
> incorrect property name ssl.want.client.auth
> -
Jun Rao created KAFKA-3052:
--
Summary: broker properties get logged twice if acl is enabled
Key: KAFKA-3052
URL: https://issues.apache.org/jira/browse/KAFKA-3052
Project: Kafka
Issue Type: Improvemen
[
https://issues.apache.org/jira/browse/KAFKA-2949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-2949.
Resolution: Fixed
Fix Version/s: 0.9.1.0
Issue resolved by pull request 631
[https://github.com/apach
Jun Rao created KAFKA-3058:
--
Summary: remove the usage of deprecated config properties
Key: KAFKA-3058
URL: https://issues.apache.org/jira/browse/KAFKA-3058
Project: Kafka
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/KAFKA-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-3051:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Issue resolved by pull request 724
[https:/
[
https://issues.apache.org/jira/browse/KAFKA-3048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-3048:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Issue resolved by pull request 724
[https:/
[
https://issues.apache.org/jira/browse/KAFKA-3010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-3010:
---
Resolution: Fixed
Fix Version/s: 0.9.0.1
Status: Resolved (was: Patch Available)
Issue reso
[
https://issues.apache.org/jira/browse/KAFKA-3045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-3045.
Resolution: Fixed
Issue resolved by pull request 731
[https://github.com/apache/kafka/pull/731]
> ZkNodeCha
[
https://issues.apache.org/jira/browse/KAFKA-3058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-3058:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Issue resolved by pull request 732
[https:/
Jun Rao created KAFKA-3068:
--
Summary: NetworkClient may connect to a different Kafka cluster
than originally configured
Key: KAFKA-3068
URL: https://issues.apache.org/jira/browse/KAFKA-3068
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-3068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15084470#comment-15084470
]
Jun Rao commented on KAFKA-3068:
[~enothereska], [~ijuma], [~guozhang], [~ewencp], [~hachi
[
https://issues.apache.org/jira/browse/KAFKA-3068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15084507#comment-15084507
]
Jun Rao commented on KAFKA-3068:
Yes, without this caching, in theory, this is still possi
[
https://issues.apache.org/jira/browse/KAFKA-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15086375#comment-15086375
]
Jun Rao commented on KAFKA-2937:
The situation that [~mgharat] described can indeed happen
[
https://issues.apache.org/jira/browse/KAFKA-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-2937:
---
Resolution: Fixed
Fix Version/s: 0.9.0.1
Status: Resolved (was: Patch Available)
Issue reso
[
https://issues.apache.org/jira/browse/KAFKA-2850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-2850.
Resolution: Fixed
Fix Version/s: 0.9.1.0
Issue resolved by pull request 546
[https://github.com/apach
[
https://issues.apache.org/jira/browse/KAFKA-2874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-2874.
Resolution: Fixed
Fix Version/s: 0.9.1.0
Issue resolved by pull request 573
[https://github.com/apach
[
https://issues.apache.org/jira/browse/KAFKA-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-2072:
---
Resolution: Fixed
Fix Version/s: 0.9.1.0
Status: Resolved (was: Patch Available)
Issue reso
[
https://issues.apache.org/jira/browse/KAFKA-3068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15086717#comment-15086717
]
Jun Rao commented on KAFKA-3068:
There are 2 possible ways of configuring bootstrap server
Jun Rao created KAFKA-3076:
--
Summary: BrokerChangeListener should log the brokers in order
Key: KAFKA-3076
URL: https://issues.apache.org/jira/browse/KAFKA-3076
Project: Kafka
Issue Type: Improvemen
Jun Rao created KAFKA-3083:
--
Summary: a soft failure in controller may leader a topic partition
in an inconsistent state
Key: KAFKA-3083
URL: https://issues.apache.org/jira/browse/KAFKA-3083
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-3083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-3083:
---
Description:
The following sequence can happen.
1. Broker A is the controller and is in the middle of process
[
https://issues.apache.org/jira/browse/KAFKA-3083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15089422#comment-15089422
]
Jun Rao commented on KAFKA-3083:
[~fpj] suggested that reason that this could happen is th
Jun Rao created KAFKA-3085:
--
Summary: BrokerChangeListener computes inconsistent live/dead
broker list
Key: KAFKA-3085
URL: https://issues.apache.org/jira/browse/KAFKA-3085
Project: Kafka
Issue Typ
Jun Rao created KAFKA-3086:
--
Summary: unused handle method in MirrorMakerMessageHandler
Key: KAFKA-3086
URL: https://issues.apache.org/jira/browse/KAFKA-3086
Project: Kafka
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/KAFKA-3085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15092923#comment-15092923
]
Jun Rao commented on KAFKA-3085:
[~dajac], sorry, I overlooked this when reviewing the pat
[
https://issues.apache.org/jira/browse/KAFKA-3083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15095495#comment-15095495
]
Jun Rao commented on KAFKA-3083:
This can potentially lead to more serious issues. For exa
[
https://issues.apache.org/jira/browse/KAFKA-2695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15098250#comment-15098250
]
Jun Rao commented on KAFKA-2695:
[~hachikuji], when using a compacted topic, we use a null
Jun Rao created KAFKA-3111:
--
Summary: java.lang.ArithmeticException: / by zero in
ConsumerPerformance
Key: KAFKA-3111
URL: https://issues.apache.org/jira/browse/KAFKA-3111
Project: Kafka
Issue Type
[
https://issues.apache.org/jira/browse/KAFKA-3083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15102589#comment-15102589
]
Jun Rao commented on KAFKA-3083:
[~fpj], thanks for the clarification. If broker A shrinks
[
https://issues.apache.org/jira/browse/KAFKA-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15102649#comment-15102649
]
Jun Rao commented on KAFKA-3111:
The log line when the exception happens won't be printed
[
https://issues.apache.org/jira/browse/KAFKA-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15102761#comment-15102761
]
Jun Rao commented on KAFKA-3111:
Interesting, this article
(http://voidexception.weebly.c
[
https://issues.apache.org/jira/browse/KAFKA-3083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15102804#comment-15102804
]
Jun Rao commented on KAFKA-3083:
[~mgharat], in general, the approach of checking if still
[
https://issues.apache.org/jira/browse/KAFKA-3083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15102903#comment-15102903
]
Jun Rao commented on KAFKA-3083:
That api doesn't exist in SessionExpirationListener. Even
[
https://issues.apache.org/jira/browse/KAFKA-3083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15103013#comment-15103013
]
Jun Rao commented on KAFKA-3083:
We will have a take closer look at the ZKClient implement
[
https://issues.apache.org/jira/browse/KAFKA-3085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-3085:
---
Resolution: Fixed
Fix Version/s: 0.9.1.0
Status: Resolved (was: Patch Available)
Issue reso
[
https://issues.apache.org/jira/browse/KAFKA-3083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15109838#comment-15109838
]
Jun Rao commented on KAFKA-3083:
[~mgharat], in step 4) ii), if the session expires, you w
Jun Rao created KAFKA-3143:
--
Summary: inconsistent state in ZK when all replicas are dead
Key: KAFKA-3143
URL: https://issues.apache.org/jira/browse/KAFKA-3143
Project: Kafka
Issue Type: Bug
[
https://issues.apache.org/jira/browse/KAFKA-3143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15114526#comment-15114526
]
Jun Rao commented on KAFKA-3143:
The fix is probably to transition all offline replicas to
[
https://issues.apache.org/jira/browse/KAFKA-3143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15114623#comment-15114623
]
Jun Rao commented on KAFKA-3143:
[~ijuma], yes, this seems to be similar to KAFKA-3096, bu
Jun Rao created KAFKA-3144:
--
Summary: report members with no assigned partitions in
ConsumerGroupCommand
Key: KAFKA-3144
URL: https://issues.apache.org/jira/browse/KAFKA-3144
Project: Kafka
Issue T
[
https://issues.apache.org/jira/browse/KAFKA-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15115594#comment-15115594
]
Jun Rao commented on KAFKA-3144:
Also, currently, when using the --new-consumer option, if
[
https://issues.apache.org/jira/browse/KAFKA-3068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15115702#comment-15115702
]
Jun Rao commented on KAFKA-3068:
[~ewencp], having a pluggable discovery service may be re
[
https://issues.apache.org/jira/browse/KAFKA-3076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-3076:
---
Resolution: Fixed
Fix Version/s: 0.9.1.0
Status: Resolved (was: Patch Available)
Issue reso
[
https://issues.apache.org/jira/browse/KAFKA-2676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-2676:
---
Labels: newbie (was: )
There are a few other classes like that. It would be good to have them all
fixed in t
[
https://issues.apache.org/jira/browse/KAFKA-3100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-3100:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Issue resolved by pull request 773
[https:/
Jun Rao created KAFKA-3152:
--
Summary: kafka-acl doesn't allow space in principal name
Key: KAFKA-3152
URL: https://issues.apache.org/jira/browse/KAFKA-3152
Project: Kafka
Issue Type: Bug
C
[
https://issues.apache.org/jira/browse/KAFKA-1791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15118078#comment-15118078
]
Jun Rao commented on KAFKA-1791:
Could you share the error and the stack trace in the log?
[
https://issues.apache.org/jira/browse/KAFKA-3088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-3088:
---
Assignee: (was: Jun Rao)
> 0.9.0.0 broker crash on receipt of produce request with empty client ID
> -
[
https://issues.apache.org/jira/browse/KAFKA-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15118362#comment-15118362
]
Jun Rao commented on KAFKA-3147:
I think the issue could be related to "abort.on.send.fail
[
https://issues.apache.org/jira/browse/KAFKA-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15120591#comment-15120591
]
Jun Rao commented on KAFKA-3147:
It also seems that in RecordAccumulator.abortBatches(), i
[
https://issues.apache.org/jira/browse/KAFKA-3152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-3152:
---
Resolution: Fixed
Fix Version/s: (was: 0.9.1.0)
Status: Resolved (was: Patch Available)
Jun Rao created KAFKA-3175:
--
Summary: topic not accessible after deletion even when
delete.topic.enable is disabled
Key: KAFKA-3175
URL: https://issues.apache.org/jira/browse/KAFKA-3175
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-3175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15124643#comment-15124643
]
Jun Rao commented on KAFKA-3175:
The issue is that during the controller failover, we call
[
https://issues.apache.org/jira/browse/KAFKA-3175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15124722#comment-15124722
]
Jun Rao commented on KAFKA-3175:
It's already doing that. The problem is that initialTopic
[
https://issues.apache.org/jira/browse/KAFKA-3175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15126407#comment-15126407
]
Jun Rao commented on KAFKA-3175:
Also, another thing is that if topic deletion is not enab
[
https://issues.apache.org/jira/browse/KAFKA-2936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15128448#comment-15128448
]
Jun Rao commented on KAFKA-2936:
[~becket_qin], is this still an issue? We fixed a similar
Jun Rao created KAFKA-3215:
--
Summary: controller may not be started when there are multiple ZK
session expirations
Key: KAFKA-3215
URL: https://issues.apache.org/jira/browse/KAFKA-3215
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-3145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-3145:
---
Assignee: (was: Jun Rao)
Description:
CPU spike to 100% when network connection is to error port.
I
[
https://issues.apache.org/jira/browse/KAFKA-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-3159:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Issue resolved by pull request 884
[https:/
[
https://issues.apache.org/jira/browse/KAFKA-3221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-3221:
---
Fix Version/s: (was: 0.9.0.1)
0.9.1.0
> kafka-acls.sh must verify if a user has suffici
[
https://issues.apache.org/jira/browse/KAFKA-3187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-3187:
---
Fix Version/s: (was: 0.9.0.1)
0.9.1.0
> Make kafka-acls.sh help messages more generic.
[
https://issues.apache.org/jira/browse/KAFKA-3190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-3190:
---
Fix Version/s: (was: 0.9.0.1)
0.9.1.0
> KafkaProducer should not invoke callback in sen
[
https://issues.apache.org/jira/browse/KAFKA-3186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-3186:
---
Fix Version/s: (was: 0.9.0.1)
0.9.1.0
> Kafka authorizer should be aware of principal t
[
https://issues.apache.org/jira/browse/KAFKA-3175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-3175:
---
Fix Version/s: (was: 0.9.0.1)
0.9.1.0
> topic not accessible after deletion even when d
[
https://issues.apache.org/jira/browse/KAFKA-3173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-3173:
---
Fix Version/s: (was: 0.9.0.1)
0.9.1.0
> Error while moving some partitions to OnlinePar
[
https://issues.apache.org/jira/browse/KAFKA-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-3147:
---
Fix Version/s: (was: 0.9.0.1)
0.9.1.0
> Memory records is not writable in MirrorMaker
>
[
https://issues.apache.org/jira/browse/KAFKA-3145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-3145:
---
Fix Version/s: (was: 0.9.0.1)
0.9.1.0
> CPU Usage Spike to 100% when network connection
[
https://issues.apache.org/jira/browse/KAFKA-3088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-3088:
---
Fix Version/s: (was: 0.9.0.1)
0.9.1.0
> 0.9.0.0 broker crash on receipt of produce requ
[
https://issues.apache.org/jira/browse/KAFKA-2930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-2930:
---
Fix Version/s: (was: 0.9.0.1)
0.9.1.0
> Update references to ZooKeeper in the docs
> --
[
https://issues.apache.org/jira/browse/KAFKA-1215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-1215:
---
Assignee: Allen Wang (was: Jun Rao)
> Rack-Aware replica assignment option
>
[
https://issues.apache.org/jira/browse/KAFKA-3025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-3025:
---
Resolution: Fixed
Fix Version/s: 0.9.1.0
Status: Resolved (was: Patch Available)
Issue reso
[
https://issues.apache.org/jira/browse/KAFKA-3025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15154642#comment-15154642
]
Jun Rao commented on KAFKA-3025:
[~becket_qin], thanks again for the patch. Currently, in
Jun Rao created KAFKA-3252:
--
Summary: compression type for a topic should be used during log
compaction
Key: KAFKA-3252
URL: https://issues.apache.org/jira/browse/KAFKA-3252
Project: Kafka
Issue T
[
https://issues.apache.org/jira/browse/KAFKA-2971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-2971:
---
Fix Version/s: (was: 0.8.2.2)
0.9.1.0
> KAFKA - Not obeying log4j settings, DailyRollin
[
https://issues.apache.org/jira/browse/KAFKA-3256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15156184#comment-15156184
]
Jun Rao commented on KAFKA-3256:
[~becket_qin], could you try the fix in ConsoleConsumer a
[
https://issues.apache.org/jira/browse/KAFKA-3256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-3256:
---
Resolution: Fixed
Fix Version/s: 0.9.1.0
Status: Resolved (was: Patch Available)
Issue reso
[
https://issues.apache.org/jira/browse/KAFKA-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-3259:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Issue resolved by pull request 943
[https:/
[
https://issues.apache.org/jira/browse/KAFKA-3253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-3253:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Issue resolved by pull request 943
[https:/
[
https://issues.apache.org/jira/browse/KAFKA-3025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15167485#comment-15167485
]
Jun Rao commented on KAFKA-3025:
[~becket_qin], another thing. Could you update
https://c
Jun Rao created KAFKA-3292:
--
Summary: ClientQuotaManager.getOrCreateQuotaSensors() may return a
null ClientSensors.throttleTimeSensor
Key: KAFKA-3292
URL: https://issues.apache.org/jira/browse/KAFKA-3292
Pro
[
https://issues.apache.org/jira/browse/KAFKA-3292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-3292:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Issue resolved by pull request 977
[https:/
Jun Rao created KAFKA-3301:
--
Summary: CommonClientConfigs.METRICS_SAMPLE_WINDOW_MS_DOC is
incorrect
Key: KAFKA-3301
URL: https://issues.apache.org/jira/browse/KAFKA-3301
Project: Kafka
Issue Type:
Jun Rao created KAFKA-3310:
--
Summary: fetch requests can trigger repeated NPE when quota is
enabled
Key: KAFKA-3310
URL: https://issues.apache.org/jira/browse/KAFKA-3310
Project: Kafka
Issue Type:
[
https://issues.apache.org/jira/browse/KAFKA-3310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15172950#comment-15172950
]
Jun Rao commented on KAFKA-3310:
[~aauradkar], do you think this is a problem?
> fetch re
[
https://issues.apache.org/jira/browse/KAFKA-3273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-3273:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Issue resolved by pull request 972
[https:/
[
https://issues.apache.org/jira/browse/KAFKA-3310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15173295#comment-15173295
]
Jun Rao commented on KAFKA-3310:
[~aauradkar], that depends. In this case, the NPE is trig
Jun Rao created KAFKA-3314:
--
Summary: Add CDDL license to LICENSE and NOTICE file
Key: KAFKA-3314
URL: https://issues.apache.org/jira/browse/KAFKA-3314
Project: Kafka
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/KAFKA-3196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-3196:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Issue resolved by pull request 951
[https:/
[
https://issues.apache.org/jira/browse/KAFKA-3314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-3314:
---
Status: Patch Available (was: Open)
> Add CDDL license to LICENSE and NOTICE file
> -
[
https://issues.apache.org/jira/browse/KAFKA-3310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-3310:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Issue resolved by pull request 989
[https:/
[
https://issues.apache.org/jira/browse/KAFKA-3343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-3343:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Issue resolved by pull request 1023
[https:
[
https://issues.apache.org/jira/browse/KAFKA-2232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14576488#comment-14576488
]
Jun Rao commented on KAFKA-2232:
[~apakulov], since the partitioner is always instantiated
[
https://issues.apache.org/jira/browse/KAFKA-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14577563#comment-14577563
]
Jun Rao commented on KAFKA-1367:
Yes, we need some kind of notion of zones for both the br
[
https://issues.apache.org/jira/browse/KAFKA-2225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14577571#comment-14577571
]
Jun Rao commented on KAFKA-2225:
A few notes on this.
1. We probably should only do this
[
https://issues.apache.org/jira/browse/KAFKA-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14577881#comment-14577881
]
Jun Rao commented on KAFKA-1690:
[~sriharsha], thanks for the latest patch. Haven't looked
801 - 900 of 3542 matches
Mail list logo
