[jira] [Updated] (KAFKA-6076) Using new producer api of transaction twice failed when server run on Windows OS

2017-10-17 Thread Orwen Xiang (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Orwen Xiang updated KAFKA-6076: --- Description: Can't invoke twice (begin,commit transaction) on same Kafka Producer instance when it

[jira] [Updated] (KAFKA-6076) Using new producer api of transaction twice failed when server run on Windows OS

2017-10-17 Thread Orwen Xiang (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Orwen Xiang updated KAFKA-6076: --- Environment: OS: Windows 10 64bit Kafka:

[jira] [Updated] (KAFKA-6076) Using new producer api of transaction twice failed when server run on Windows OS

2017-10-17 Thread Orwen Xiang (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Orwen Xiang updated KAFKA-6076: --- Description: Can't invoke twice (begin,commit transaction) on same Kafka Producer instance when it

[jira] [Updated] (KAFKA-6076) Using new producer api of transaction twice failed when server run on Windows OS

2017-10-17 Thread Orwen Xiang (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Orwen Xiang updated KAFKA-6076: --- Description: Can't invoke twice (begin,commit transaction) on same Kafka Producer instance when it

[jira] [Created] (KAFKA-6076) Using new producer api of transaction twice failed when server run on Windows OS

2017-10-17 Thread Orwen Xiang (JIRA)
Orwen Xiang created KAFKA-6076: -- Summary: Using new producer api of transaction twice failed when server run on Windows OS Key: KAFKA-6076 URL: https://issues.apache.org/jira/browse/KAFKA-6076 Project:

[jira] [Commented] (KAFKA-5829) Speedup broker startup after unclean shutdown by reducing unnecessary snapshot files deletion

2017-10-17 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16208715#comment-16208715 ] ASF GitHub Bot commented on KAFKA-5829: --- Github user lindong28 closed the pull request at:

[jira] [Created] (KAFKA-6075) Kafka cannot recover after an unclean shutdown on Windows

2017-10-17 Thread Vahid Hashemian (JIRA)
Vahid Hashemian created KAFKA-6075: -- Summary: Kafka cannot recover after an unclean shutdown on Windows Key: KAFKA-6075 URL: https://issues.apache.org/jira/browse/KAFKA-6075 Project: Kafka

[jira] [Updated] (KAFKA-5647) Use async ZookeeperClient for Admin operations

2017-10-17 Thread Jun Rao (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-5647: --- Description: This includes ConfigCommand, ZkSecurityMigrator, ExportZkOffsets, ImportZkOffsets,

[jira] [Updated] (KAFKA-5646) Use async ZookeeperClient for DynamicConfigManager

2017-10-17 Thread Jun Rao (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-5646: --- Affects Version/s: 1.1.0 Fix Version/s: 1.1.0 Description: We want to replace the usage of

[jira] [Created] (KAFKA-6074) Use ZookeeperClient in ReplicaManager and Partition

2017-10-17 Thread Jun Rao (JIRA)
Jun Rao created KAFKA-6074: -- Summary: Use ZookeeperClient in ReplicaManager and Partition Key: KAFKA-6074 URL: https://issues.apache.org/jira/browse/KAFKA-6074 Project: Kafka Issue Type: Sub-task

[jira] [Created] (KAFKA-6073) Use ZookeeperClient in KafkaApis

2017-10-17 Thread Jun Rao (JIRA)
Jun Rao created KAFKA-6073: -- Summary: Use ZookeeperClient in KafkaApis Key: KAFKA-6073 URL: https://issues.apache.org/jira/browse/KAFKA-6073 Project: Kafka Issue Type: Sub-task

[jira] [Updated] (KAFKA-6072) Use ZookeeperClient in GroupCoordinator and TransactionCoordinator

2017-10-17 Thread Jun Rao (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-6072: --- Summary: Use ZookeeperClient in GroupCoordinator and TransactionCoordinator (was: Use ZookeeperClient in

[jira] [Created] (KAFKA-6071) Use ZookeeperClient in LogManager

2017-10-17 Thread Jun Rao (JIRA)
Jun Rao created KAFKA-6071: -- Summary: Use ZookeeperClient in LogManager Key: KAFKA-6071 URL: https://issues.apache.org/jira/browse/KAFKA-6071 Project: Kafka Issue Type: Sub-task

[jira] [Commented] (KAFKA-6070) ducker-ak: add ipaddress and enum34 dependencies to docker image

2017-10-17 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16208476#comment-16208476 ] ASF GitHub Bot commented on KAFKA-6070: --- GitHub user cmccabe opened a pull request:

[jira] [Commented] (KAFKA-6070) ducker-ak: add ipaddress and enum34 dependencies to docker image

2017-10-17 Thread Colin P. McCabe (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16208473#comment-16208473 ] Colin P. McCabe commented on KAFKA-6070: Fixes this issue: {code} Traceback (most recent call

[jira] [Created] (KAFKA-6070) ducker-ak: add ipaddress and enum34 dependencies to docker image

2017-10-17 Thread Colin P. McCabe (JIRA)
Colin P. McCabe created KAFKA-6070: -- Summary: ducker-ak: add ipaddress and enum34 dependencies to docker image Key: KAFKA-6070 URL: https://issues.apache.org/jira/browse/KAFKA-6070 Project: Kafka

[jira] [Commented] (KAFKA-6066) Use of SimpleDateFormat in RocksDBWindowStore may not be Threadsafe

2017-10-17 Thread Guozhang Wang (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16207871#comment-16207871 ] Guozhang Wang commented on KAFKA-6066: -- [~sriksun] which version of Kafka are you using? We have

[jira] [Commented] (KAFKA-5163) Support replicas movement between log directories (KIP-113)

2017-10-17 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16207849#comment-16207849 ] ASF GitHub Bot commented on KAFKA-5163: --- Github user asfgit closed the pull request at:

[jira] [Commented] (KAFKA-6069) Streams metrics tagged incorrectly

2017-10-17 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16207677#comment-16207677 ] ASF GitHub Bot commented on KAFKA-6069: --- GitHub user twbecker opened a pull request:

[jira] [Created] (KAFKA-6069) Streams metrics tagged incorrectly

2017-10-17 Thread Tommy Becker (JIRA)
Tommy Becker created KAFKA-6069: --- Summary: Streams metrics tagged incorrectly Key: KAFKA-6069 URL: https://issues.apache.org/jira/browse/KAFKA-6069 Project: Kafka Issue Type: Bug

[jira] [Resolved] (KAFKA-4504) Details of retention.bytes property at Topic level are not clear on how they impact partition size

2017-10-17 Thread Manikumar (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-4504. -- Resolution: Fixed Assignee: Manikumar Fix Version/s: 1.0.0 > Details of retention.bytes

[jira] [Commented] (KAFKA-4504) Details of retention.bytes property at Topic level are not clear on how they impact partition size

2017-10-17 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16207259#comment-16207259 ] ASF GitHub Bot commented on KAFKA-4504: --- Github user asfgit closed the pull request at:

[jira] [Updated] (KAFKA-6068) kafka-topic.sh alter replication-factor raise broker failure

2017-10-17 Thread haiyangyu (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] haiyangyu updated KAFKA-6068: - Attachment: example.png > kafka-topic.sh alter replication-factor raise broker failure >

[jira] [Commented] (KAFKA-6068) kafka-topic.sh alter replication-factor raise broker failure

2017-10-17 Thread haiyangyu (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16207246#comment-16207246 ] haiyangyu commented on KAFKA-6068: -- it looks like as the photo [^example.png] > kafka-topic.sh alter

[jira] [Updated] (KAFKA-6068) kafka-topic.sh alter replication-factor raise broker failure

2017-10-17 Thread haiyangyu (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] haiyangyu updated KAFKA-6068: - Description: 1) When I alter my topic replication-factor from 2 to 3, it only update zk topic data,

[jira] [Updated] (KAFKA-6068) kafka-topic.sh alter replication-factor raise broker failure

2017-10-17 Thread haiyangyu (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] haiyangyu updated KAFKA-6068: - Description: 1) When I alter my topic replication-factor from 2 to 3, it only update zk topic data,

[jira] [Updated] (KAFKA-6068) kafka-topic.sh alter replication-factor raise broker failure

2017-10-17 Thread haiyangyu (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] haiyangyu updated KAFKA-6068: - Description: 1) When I alter my topic replication-factor from 2 to 3, it only update zk topic data,

[jira] [Updated] (KAFKA-6068) kafka-topic.sh alter replication-factor raise broker failure

2017-10-17 Thread haiyangyu (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] haiyangyu updated KAFKA-6068: - Description: 1) When I alter my topic replication-factor from 2 to 3, it only update zk topic data,

[jira] [Commented] (KAFKA-6068) kafka-topic.sh alter replication-factor raise broker failure

2017-10-17 Thread huxihx (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16207236#comment-16207236 ] huxihx commented on KAFKA-6068: --- Don't you encounter `[replication-factor]" can't be used with

[jira] [Updated] (KAFKA-6068) kafka-topic.sh alter replication-factor raise broker failure

2017-10-17 Thread haiyangyu (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] haiyangyu updated KAFKA-6068: - Description: 1) When I alter my topic replication-factor from 2 to 3, it only update zk topic data,

[jira] [Updated] (KAFKA-6068) kafka-topic.sh alter replication-factor raise broker failure

2017-10-17 Thread haiyangyu (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] haiyangyu updated KAFKA-6068: - Description: 1) When I alter my topic replication-factor from 2 to 3, it only update zk topic data,

[jira] [Updated] (KAFKA-6068) kafka-topic.sh alter replication-factor raise broker failure

2017-10-17 Thread haiyangyu (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] haiyangyu updated KAFKA-6068: - Description: 1) When I alter my topic replication-factor from 2 to 3, it only update zk topic data,

[jira] [Updated] (KAFKA-6068) kafka-topic.sh alter replication-factor raise broker failure

2017-10-17 Thread haiyangyu (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] haiyangyu updated KAFKA-6068: - Description: 1) When I alter my topic replication-factor from 2 to 3, it only update zk topic data,

[jira] [Updated] (KAFKA-6068) kafka-topic.sh alter replication-factor raise broker failure

2017-10-17 Thread haiyangyu (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] haiyangyu updated KAFKA-6068: - Description: 1) When I alter my topic replication-factor from 2 to 3, it only update zk topic data,

[jira] [Updated] (KAFKA-6068) kafka-topic.sh alter replication-factor raise broker failure

2017-10-17 Thread haiyangyu (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] haiyangyu updated KAFKA-6068: - Issue Type: Bug (was: New Feature) > kafka-topic.sh alter replication-factor raise broker failure >

[jira] [Created] (KAFKA-6068) kafka-topic.sh alter replication-factor raise broker failure

2017-10-17 Thread haiyangyu (JIRA)
haiyangyu created KAFKA-6068: Summary: kafka-topic.sh alter replication-factor raise broker failure Key: KAFKA-6068 URL: https://issues.apache.org/jira/browse/KAFKA-6068 Project: Kafka Issue

[jira] [Issue Comment Deleted] (KAFKA-6067) how to process when all isr crashed

2017-10-17 Thread haiyangyu (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] haiyangyu updated KAFKA-6067: - Comment: was deleted (was: aaa) > how to process when all isr crashed >

[jira] [Commented] (KAFKA-6067) how to process when all isr crashed

2017-10-17 Thread haiyangyu (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16207102#comment-16207102 ] haiyangyu commented on KAFKA-6067: -- aaa > how to process when all isr crashed >

[jira] [Created] (KAFKA-6067) how to process when all isr crashed

2017-10-17 Thread haiyangyu (JIRA)
haiyangyu created KAFKA-6067: Summary: how to process when all isr crashed Key: KAFKA-6067 URL: https://issues.apache.org/jira/browse/KAFKA-6067 Project: Kafka Issue Type: New Feature