[jira] [Assigned] (KAFKA-2360) The kafka-consumer-perf-test.sh script help information print useless parameters.

[ https://issues.apache.org/jira/browse/KAFKA-2360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxihx reassigned KAFKA-2360: - Assignee: huxihx (was: jin xing) > The kafka-consumer-perf-test.sh script help information print

[jira] [Updated] (KAFKA-5560) LogManager should be able to create new logs based on free disk space

[ https://issues.apache.org/jira/browse/KAFKA-5560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxihx updated KAFKA-5560: -- Labels: needs-kip (was: kips) > LogManager should be able to create new logs based on free disk space >

[jira] [Commented] (KAFKA-5459) Support kafka-console-producer.sh messages as whole file

[ https://issues.apache.org/jira/browse/KAFKA-5459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16110657#comment-16110657 ] huxihx commented on KAFKA-5459: --- [~tombentley] How do we specify the key if the entire file content is the

[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=16110630#comment-16110630 ] huxihx commented on KAFKA-5358: --- [~hachikuji] How is the status for this KIP? Is it approved? > Consumer

[jira] [Commented] (KAFKA-5641) Metadata request should always be allowed to send no regardless of value for max.in.flight.requests.per.connection

[ https://issues.apache.org/jira/browse/KAFKA-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16110568#comment-16110568 ] huxihx commented on KAFKA-5641: --- Closed this jira since this improvement does not have much positive impact

[jira] [Resolved] (KAFKA-5641) Metadata request should always be allowed to send no regardless of value for max.in.flight.requests.per.connection

[ https://issues.apache.org/jira/browse/KAFKA-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxihx resolved KAFKA-5641. --- Resolution: Not A Problem > Metadata request should always be allowed to send no regardless of value for >

[jira] [Comment Edited] (KAFKA-5690) kafka-acls command should be able to list per principal

[ https://issues.apache.org/jira/browse/KAFKA-5690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16110080#comment-16110080 ] huxihx edited comment on KAFKA-5690 at 8/2/17 3:38 AM: --- I am seeing this jira as an

[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=16108674#comment-16108674 ] huxihx commented on KAFKA-5547: --- [~hachikuji] A quick question please. Why does the check order matter? Why

[jira] [Commented] (KAFKA-5007) Kafka Replica Fetcher Thread- Resource Leak

[ https://issues.apache.org/jira/browse/KAFKA-5007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16102622#comment-16102622 ] huxihx commented on KAFKA-5007: --- [~joseph.alias...@gmail.com] what's the status for this jira? Have you

[jira] [Commented] (KAFKA-5641) Metadata request should always be allowed to send no regardless of value for max.in.flight.requests.per.connection

[ https://issues.apache.org/jira/browse/KAFKA-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16101249#comment-16101249 ] huxihx commented on KAFKA-5641: --- [~ijuma] "The broker only processes one request at a time, so even if you

[jira] [Updated] (KAFKA-5641) Metadata request should always be allowed to send no regardless of value for max.in.flight.requests.per.connection

[ https://issues.apache.org/jira/browse/KAFKA-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxihx updated KAFKA-5641: -- Component/s: network > Metadata request should always be allowed to send no regardless of value for >

[jira] [Commented] (KAFKA-5630) Consumer poll loop over the same record after a CorruptRecordException

[ https://issues.apache.org/jira/browse/KAFKA-5630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16098134#comment-16098134 ] huxihx commented on KAFKA-5630: --- Seems it's a duplicate of

[jira] [Commented] (KAFKA-5630) Consumer poll loop over the same record after a CorruptRecordException

[ https://issues.apache.org/jira/browse/KAFKA-5630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16098117#comment-16098117 ] huxihx commented on KAFKA-5630: --- Did you enable `preallocate` for the topic? > Consumer poll loop over the

[jira] [Commented] (KAFKA-5296) Unable to write to some partitions of newly created topic in 10.2

[ https://issues.apache.org/jira/browse/KAFKA-5296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16098063#comment-16098063 ] huxihx commented on KAFKA-5296: --- There is only one active controller in a cluster. How did you tell multiple

[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=16095916#comment-16095916 ] huxihx commented on KAFKA-5611: --- [~pskianis] In the log, seems that the consumer on Server 3 did not get any

[jira] [Resolved] (KAFKA-5582) Log compaction with preallocation enabled does not trim segments

[ https://issues.apache.org/jira/browse/KAFKA-5582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxihx resolved KAFKA-5582. --- Resolution: Duplicate > Log compaction with preallocation enabled does not trim segments >

[jira] [Commented] (KAFKA-5592) Connection with plain client to SSL-secured broker causes OOM

[ https://issues.apache.org/jira/browse/KAFKA-5592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16094430#comment-16094430 ] huxihx commented on KAFKA-5592: --- Is it a duplicate of

[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=16094108#comment-16094108 ] huxihx commented on KAFKA-5611: --- Is there anything wrong with the network between server 3 and kafka

[jira] [Updated] (KAFKA-5560) LogManager should be able to create new logs based on free disk space

[ https://issues.apache.org/jira/browse/KAFKA-5560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxihx updated KAFKA-5560: -- Description: Currently, log manager chooses a directory configured in `log.dirs` by calculating the number

[jira] [Commented] (KAFKA-5585) Failover in a replicated Cluster does not work

[ https://issues.apache.org/jira/browse/KAFKA-5585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16085403#comment-16085403 ] huxihx commented on KAFKA-5585: --- [~tubayer] producer complains it failed to connect to Node 2 whose port

[jira] [Assigned] (KAFKA-5431) LogCleaner stopped due to org.apache.kafka.common.errors.CorruptRecordException

[ https://issues.apache.org/jira/browse/KAFKA-5431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxihx reassigned KAFKA-5431: - Assignee: huxihx > LogCleaner stopped due to > org.apache.kafka.common.errors.CorruptRecordException >

[jira] [Comment Edited] (KAFKA-5431) LogCleaner stopped due to org.apache.kafka.common.errors.CorruptRecordException

[ https://issues.apache.org/jira/browse/KAFKA-5431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16085357#comment-16085357 ] huxihx edited comment on KAFKA-5431 at 7/13/17 8:41 AM: Seems this only happens

[jira] [Commented] (KAFKA-5582) Log compaction with preallocation enabled does not trim segments

[ https://issues.apache.org/jira/browse/KAFKA-5582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16085382#comment-16085382 ] huxihx commented on KAFKA-5582: --- Seems in LogCleaner, `cleanSegments` should not set length for the

[jira] [Commented] (KAFKA-5431) LogCleaner stopped due to org.apache.kafka.common.errors.CorruptRecordException

[ https://issues.apache.org/jira/browse/KAFKA-5431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16085357#comment-16085357 ] huxihx commented on KAFKA-5431: --- Seems this only happens when preallocate is enabled and topic is configured

[jira] [Commented] (KAFKA-5585) Failover in a replicated Cluster does not work

[ https://issues.apache.org/jira/browse/KAFKA-5585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16085122#comment-16085122 ] huxihx commented on KAFKA-5585: --- [~ba...@oio.de] Could you check if leaders for all partitions are

[jira] [Updated] (KAFKA-5560) LogManager should be able to create new logs based on free disk space

[ https://issues.apache.org/jira/browse/KAFKA-5560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxihx updated KAFKA-5560: -- Labels: kips (was: ) > LogManager should be able to create new logs based on free disk space >

[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=16077536#comment-16077536 ] huxihx commented on KAFKA-5467: --- Log cleaner does not clean the active log segment. How many log segments do

[jira] [Commented] (KAFKA-5560) LogManager should be able to create new logs based on free disk space

[ https://issues.apache.org/jira/browse/KAFKA-5560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16077506#comment-16077506 ] huxihx commented on KAFKA-5560: --- [~junrao] Do you see it as a reasonable requirement? > LogManager should

[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=16077505#comment-16077505 ] huxihx commented on KAFKA-5407: --- [~fvegaucr] Did you find any exceptions thrown when new consumer was used?

[jira] [Created] (KAFKA-5560) LogManager should be able to create new logs based on free disk space

huxihx created KAFKA-5560: - Summary: LogManager should be able to create new logs based on free disk space Key: KAFKA-5560 URL: https://issues.apache.org/jira/browse/KAFKA-5560 Project: Kafka Issue

[jira] [Assigned] (KAFKA-5508) Documentation for altering topics

[ https://issues.apache.org/jira/browse/KAFKA-5508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxihx reassigned KAFKA-5508: - Assignee: huxihx > Documentation for altering topics > - > >

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

[ https://issues.apache.org/jira/browse/KAFKA-5407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16058584#comment-16058584 ] huxihx edited comment on KAFKA-5407 at 6/22/17 1:47 AM: Did you see any other

[jira] [Commented] (KAFKA-5432) producer and consumer SocketTimeoutException

[ https://issues.apache.org/jira/browse/KAFKA-5432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16051287#comment-16051287 ] huxihx commented on KAFKA-5432: --- Is it possible that the network outage occurred during your

<    1   2   3   4