[jira] [Resolved] (KAFKA-8161) Comma conflict when run script bin/kafka-configs.sh with config 'follower.replication.throttled.replicas'

[ https://issues.apache.org/jira/browse/KAFKA-8161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxihx resolved KAFKA-8161. --- Resolution: Not A Problem > Comma conflict when run script bin/kafka-configs.sh with config >

[jira] [Commented] (KAFKA-7965) Flaky Test ConsumerBounceTest#testRollingBrokerRestartsWithSmallerMaxGroupSizeConfigDisruptsBigGroup

[ https://issues.apache.org/jira/browse/KAFKA-7965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16812335#comment-16812335 ] huxihx commented on KAFKA-7965: --- Seems [PR 6328|[https://github.com/apache/kafka/pull/6238]] changed the

[jira] [Comment Edited] (KAFKA-7965) Flaky Test ConsumerBounceTest#testRollingBrokerRestartsWithSmallerMaxGroupSizeConfigDisruptsBigGroup

[ https://issues.apache.org/jira/browse/KAFKA-7965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16812335#comment-16812335 ] huxihx edited comment on KAFKA-7965 at 4/8/19 10:51 AM: Seems

[jira] [Commented] (KAFKA-7983) supporting replication.throttled.replicas in dynamic broker configuration

[ https://issues.apache.org/jira/browse/KAFKA-7983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16810715#comment-16810715 ] huxihx commented on KAFKA-7983: --- If specified at broker level, should them follow the format of

[jira] [Commented] (KAFKA-7983) supporting replication.throttled.replicas in dynamic broker configuration

[ https://issues.apache.org/jira/browse/KAFKA-7983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16809714#comment-16809714 ] huxihx commented on KAFKA-7983: --- [~junrao] Seems these two configs could be modified dynamically through

[jira] [Commented] (KAFKA-8161) Comma conflict when run script bin/kafka-configs.sh with config 'follower.replication.throttled.replicas'

[ https://issues.apache.org/jira/browse/KAFKA-8161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16809560#comment-16809560 ] huxihx commented on KAFKA-8161: --- [~haiping] For kv pairs, you should use brackets to enclose the value, for

[jira] [Commented] (KAFKA-8148) Kafka Group deletion

[ https://issues.apache.org/jira/browse/KAFKA-8148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16807383#comment-16807383 ] huxihx commented on KAFKA-8148: --- 2181 is more likely to be the ZooKeeper port. Did you mistakenly specify

[jira] [Commented] (KAFKA-7965) Flaky Test ConsumerBounceTest#testRollingBrokerRestartsWithSmallerMaxGroupSizeConfigDisruptsBigGroup

[ https://issues.apache.org/jira/browse/KAFKA-7965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16806349#comment-16806349 ] huxihx commented on KAFKA-7965: --- [~enether] Are you still working on this jira? If not, I think I could

[jira] [Commented] (KAFKA-7965) Flaky Test ConsumerBounceTest#testRollingBrokerRestartsWithSmallerMaxGroupSizeConfigDisruptsBigGroup

[ https://issues.apache.org/jira/browse/KAFKA-7965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16804533#comment-16804533 ] huxihx commented on KAFKA-7965: --- Part of the failure is caused by the fact that the rebalance did not

[jira] [Commented] (KAFKA-8100) If delete expired topic, kafka consumer will keep flushing unknown_topic warning in log

[ https://issues.apache.org/jira/browse/KAFKA-8100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16798801#comment-16798801 ] huxihx commented on KAFKA-8100: --- Well, actually the consumer does refresh metadata periodically. Only

[jira] [Commented] (KAFKA-8100) If delete expired topic, kafka consumer will keep flushing unknown_topic warning in log

[ https://issues.apache.org/jira/browse/KAFKA-8100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16798686#comment-16798686 ] huxihx commented on KAFKA-8100: --- Since `UNKNOWN_TOPIC_OR_PARTITION` is a retriable exception, it's hard to

[jira] [Assigned] (KAFKA-8125) Check for topic existence in CreateTopicsRequest prior to creating replica assignment

[ https://issues.apache.org/jira/browse/KAFKA-8125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxihx reassigned KAFKA-8125: - Assignee: huxihx > Check for topic existence in CreateTopicsRequest prior to creating replica >

[jira] [Assigned] (KAFKA-7962) StickyAssignor: throws NullPointerException during assignments if topic is deleted

[ https://issues.apache.org/jira/browse/KAFKA-7962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxihx reassigned KAFKA-7962: - Assignee: huxihx > StickyAssignor: throws NullPointerException during assignments if topic is >

[jira] [Comment Edited] (KAFKA-7951) Log Cleaner thread stop with "Varint is too long" error

[ https://issues.apache.org/jira/browse/KAFKA-7951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16773631#comment-16773631 ] huxihx edited comment on KAFKA-7951 at 2/21/19 3:26 AM: [~ninth.nails] Had you

[jira] [Commented] (KAFKA-7951) Log Cleaner thread stop with "Varint is too long" error

[ https://issues.apache.org/jira/browse/KAFKA-7951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16773631#comment-16773631 ] huxihx commented on KAFKA-7951: --- [~ninth.nails] Had you upgraded or downgraded the Kafka version before

[jira] [Commented] (KAFKA-7927) Read committed receives aborted events

[ https://issues.apache.org/jira/browse/KAFKA-7927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16772477#comment-16772477 ] huxihx commented on KAFKA-7927: --- [~gsomogyi] Currently, the old consumer had already been removed from the

[jira] [Comment Edited] (KAFKA-7927) Read committed receives aborted events

[ https://issues.apache.org/jira/browse/KAFKA-7927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16769021#comment-16769021 ] huxihx edited comment on KAFKA-7927 at 2/15/19 8:31 AM: [~gsomogyi] The console

[jira] [Commented] (KAFKA-7927) Read committed receives aborted events

[ https://issues.apache.org/jira/browse/KAFKA-7927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16769021#comment-16769021 ] huxihx commented on KAFKA-7927: --- [~gsomogyi] The console consumer you were using is the Scala consumer

[jira] [Commented] (KAFKA-7794) kafka.tools.GetOffsetShell does not return the offset in some cases

[ https://issues.apache.org/jira/browse/KAFKA-7794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16767814#comment-16767814 ] huxihx commented on KAFKA-7794: --- There are some inconsistencies here where GetOffsetShell wants to seek the

[jira] [Commented] (KAFKA-7879) Data directory size decreases every few minutes when producer is sending large amount of data

[ https://issues.apache.org/jira/browse/KAFKA-7879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16755585#comment-16755585 ] huxihx commented on KAFKA-7879: --- [~bansalp] What's your filesystem?  > Data directory size decreases every

[jira] [Commented] (KAFKA-7879) Data directory size decreases every few minutes when producer is sending large amount of data

[ https://issues.apache.org/jira/browse/KAFKA-7879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16754710#comment-16754710 ] huxihx commented on KAFKA-7879: ---  Are you using `du -s` instead of `du -b` to check the size? The latter

[jira] [Commented] (KAFKA-7848) Idempotence producer keep retry on OutOfOrderSequenceException

[ https://issues.apache.org/jira/browse/KAFKA-7848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16753661#comment-16753661 ] huxihx commented on KAFKA-7848: --- Could you check the server log for the original leader of partition #88?

[jira] [Commented] (KAFKA-7848) Idempotence producer keep retry on OutOfOrderSequenceException

[ https://issues.apache.org/jira/browse/KAFKA-7848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16749401#comment-16749401 ] huxihx commented on KAFKA-7848: --- Did you move the leader to a different broker and change it back soon? A

[jira] [Assigned] (KAFKA-7813) JmxTool throws NPE when --object-name is omitted

[ https://issues.apache.org/jira/browse/KAFKA-7813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxihx reassigned KAFKA-7813: - Assignee: huxihx > JmxTool throws NPE when --object-name is omitted >

[jira] [Commented] (KAFKA-7810) AdminClient not found flink consumer group

[ https://issues.apache.org/jira/browse/KAFKA-7810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739280#comment-16739280 ] huxihx commented on KAFKA-7810: --- Seems you are using kafka.admin.AdminClient which is already marked as

[jira] [Assigned] (KAFKA-7771) Group/Transaction coordinators should update assignment based on current partition count

[ https://issues.apache.org/jira/browse/KAFKA-7771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxihx reassigned KAFKA-7771: - Assignee: huxihx > Group/Transaction coordinators should update assignment based on current >

[jira] [Created] (KAFKA-7801) TopicCommand should not be able to alter transaction topic partition count

huxihx created KAFKA-7801: - Summary: TopicCommand should not be able to alter transaction topic partition count Key: KAFKA-7801 URL: https://issues.apache.org/jira/browse/KAFKA-7801 Project: Kafka

[jira] [Created] (KAFKA-7779) Avoid unnecessary loop iteration in leastLoadedNode

huxihx created KAFKA-7779: - Summary: Avoid unnecessary loop iteration in leastLoadedNode Key: KAFKA-7779 URL: https://issues.apache.org/jira/browse/KAFKA-7779 Project: Kafka Issue Type: Improvement

[jira] [Commented] (KAFKA-7765) IdleExpiryManager should not passively close socket used by controller

[ https://issues.apache.org/jira/browse/KAFKA-7765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16729484#comment-16729484 ] huxihx commented on KAFKA-7765: --- [~rsivaram] Could you help look at this problem? > IdleExpiryManager

[jira] [Assigned] (KAFKA-7763) KafkaProducer with transactionId endless waits when network is disconnection for 10-20s

[ https://issues.apache.org/jira/browse/KAFKA-7763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxihx reassigned KAFKA-7763: - Assignee: huxihx > KafkaProducer with transactionId endless waits when network is disconnection > for

[jira] [Updated] (KAFKA-7765) IdleExpiryManager should not passively close socket used by controller

[ https://issues.apache.org/jira/browse/KAFKA-7765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxihx updated KAFKA-7765: -- Description: Currently, controller creates sockets for every living brokers without idle timeout. However,

[jira] [Commented] (KAFKA-7767) Console consumer should be able to print headers and partition/offsets

[ https://issues.apache.org/jira/browse/KAFKA-7767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16728564#comment-16728564 ] huxihx commented on KAFKA-7767: --- An alternative way is to implement MessageFormatter interface, making your

[jira] [Created] (KAFKA-7765) IdleExpiryManager should not passively close socket used by controller

huxihx created KAFKA-7765: - Summary: IdleExpiryManager should not passively close socket used by controller Key: KAFKA-7765 URL: https://issues.apache.org/jira/browse/KAFKA-7765 Project: Kafka

[jira] [Commented] (KAFKA-7690) Change disk allocation policy for multiple partitions on a broker when topic is created

[ https://issues.apache.org/jira/browse/KAFKA-7690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16723772#comment-16723772 ] huxihx commented on KAFKA-7690: --- [~yuhaiyang] As for the size-based strategy, it's difficult to estimate 

[jira] [Commented] (KAFKA-7732) Kafka broker lag metrics is more than 0, but no partitions are under replicated

[ https://issues.apache.org/jira/browse/KAFKA-7732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16723760#comment-16723760 ] huxihx commented on KAFKA-7732: --- The fix does not cover the metric you mentioned. > Kafka broker lag

[jira] [Commented] (KAFKA-7690) Change disk allocation policy for multiple partitions on a broker when topic is created

[ https://issues.apache.org/jira/browse/KAFKA-7690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16720867#comment-16720867 ] huxihx commented on KAFKA-7690: --- I did not understand the strategy you proposed here. Do you mean a

[jira] [Commented] (KAFKA-7732) Kafka broker lag metrics is more than 0, but no partitions are under replicated

[ https://issues.apache.org/jira/browse/KAFKA-7732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16720846#comment-16720846 ] huxihx commented on KAFKA-7732: --- It's already fixed in KAFKA-7704. > Kafka broker lag metrics is more than

[jira] [Assigned] (KAFKA-7704) kafka.server.ReplicaFetechManager.MaxLag.Replica metric is reported incorrectly

[ https://issues.apache.org/jira/browse/KAFKA-7704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxihx reassigned KAFKA-7704: - Assignee: huxihx > kafka.server.ReplicaFetechManager.MaxLag.Replica metric is reported > incorrectly >

[jira] [Updated] (KAFKA-7705) Update javadoc for the values of delivery.timeout.ms or linger.ms

[ https://issues.apache.org/jira/browse/KAFKA-7705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxihx updated KAFKA-7705: -- Summary: Update javadoc for the values of delivery.timeout.ms or linger.ms (was: Update javadoc for default

[jira] [Updated] (KAFKA-7705) Update javadoc for default value of delivery.timeout.ms

[ https://issues.apache.org/jira/browse/KAFKA-7705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxihx updated KAFKA-7705: -- Description: In

[jira] [Updated] (KAFKA-7705) Update javadoc for default value of delivery.timeout.ms

[ https://issues.apache.org/jira/browse/KAFKA-7705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxihx updated KAFKA-7705: -- Description: In

[jira] [Created] (KAFKA-7705) Update javadoc for default value of delivery.timeout.ms

huxihx created KAFKA-7705: - Summary: Update javadoc for default value of delivery.timeout.ms Key: KAFKA-7705 URL: https://issues.apache.org/jira/browse/KAFKA-7705 Project: Kafka Issue Type: Bug

[jira] [Assigned] (KAFKA-7687) Print batch level information in DumpLogSegments when deep iterating

[ https://issues.apache.org/jira/browse/KAFKA-7687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxihx reassigned KAFKA-7687: - Assignee: huxihx > Print batch level information in DumpLogSegments when deep iterating >

[jira] [Updated] (KAFKA-7665) Replace BaseConsumerRecord with ConsumerRecord in MM

[ https://issues.apache.org/jira/browse/KAFKA-7665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxihx updated KAFKA-7665: -- Labels: needs-kip (was: ) > Replace BaseConsumerRecord with ConsumerRecord in MM >

[jira] [Created] (KAFKA-7665) Replace BaseConsumerRecord with ConsumerRecord in MM

huxihx created KAFKA-7665: - Summary: Replace BaseConsumerRecord with ConsumerRecord in MM Key: KAFKA-7665 URL: https://issues.apache.org/jira/browse/KAFKA-7665 Project: Kafka Issue Type: Improvement

[jira] [Assigned] (KAFKA-7665) Replace BaseConsumerRecord with ConsumerRecord in MM

[ https://issues.apache.org/jira/browse/KAFKA-7665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxihx reassigned KAFKA-7665: - Assignee: huxihx > Replace BaseConsumerRecord with ConsumerRecord in MM >

[jira] [Commented] (KAFKA-7656) ReplicaManager fetch fails on leader due to long/integer overflow

[ https://issues.apache.org/jira/browse/KAFKA-7656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16692934#comment-16692934 ] huxihx commented on KAFKA-7656: --- Seems pull request  [#5332|https://github.com/apache/kafka/pull/5332] 

[jira] [Commented] (KAFKA-7587) Support for Protocol Buffers Message Format in kafka-console-consumer script

[ https://issues.apache.org/jira/browse/KAFKA-7587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16684789#comment-16684789 ] huxihx commented on KAFKA-7587: --- Did you try ConsoleConsumer with `--property  value.deserializer=`?  >

[jira] [Assigned] (KAFKA-7557) optimize LogManager.truncateFullyAndStartAt()

[ https://issues.apache.org/jira/browse/KAFKA-7557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxihx reassigned KAFKA-7557: - Assignee: huxihx > optimize LogManager.truncateFullyAndStartAt() >

[jira] [Commented] (KAFKA-7479) Call to "producer.initTransaction" hangs when using IP for "bootstrap.servers"

[ https://issues.apache.org/jira/browse/KAFKA-7479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16649996#comment-16649996 ] huxihx commented on KAFKA-7479: --- Seems it was already fixed by KAFKA-6446 > Call to

[jira] [Assigned] (KAFKA-7412) Bug prone response from producer.send(ProducerRecord, Callback) if Kafka broker is not running

[ https://issues.apache.org/jira/browse/KAFKA-7412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxihx reassigned KAFKA-7412: - Assignee: huxihx > Bug prone response from producer.send(ProducerRecord, Callback) if Kafka > broker

[jira] [Commented] (KAFKA-7442) forceUnmap mmap on linux when index resize

[ https://issues.apache.org/jira/browse/KAFKA-7442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16641305#comment-16641305 ] huxihx commented on KAFKA-7442: --- [~zhaiyuyong] Agreed. There is no reason to do the unmapping only for

[jira] [Commented] (KAFKA-7442) forceUnmap mmap on linux when index resize

[ https://issues.apache.org/jira/browse/KAFKA-7442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16632760#comment-16632760 ] huxihx commented on KAFKA-7442: --- Seems it's a duplicate of KAFKA-4614 > forceUnmap mmap on linux when

[jira] [Commented] (KAFKA-7451) Missing JMX metrics

[ https://issues.apache.org/jira/browse/KAFKA-7451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16631556#comment-16631556 ] huxihx commented on KAFKA-7451: --- Check out

[jira] [Assigned] (KAFKA-7409) Validate topic configs prior to topic creation

[ https://issues.apache.org/jira/browse/KAFKA-7409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxihx reassigned KAFKA-7409: - Assignee: huxihx > Validate topic configs prior to topic creation >

[jira] [Commented] (KAFKA-7337) Enhance Producer Performance tool to generate keys

[ https://issues.apache.org/jira/browse/KAFKA-7337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593210#comment-16593210 ] huxihx commented on KAFKA-7337: --- This might need a KIP. > Enhance Producer Performance tool to generate

[jira] [Commented] (KAFKA-7304) memory leakage in org.apache.kafka.common.network.Selector

[ https://issues.apache.org/jira/browse/KAFKA-7304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16583748#comment-16583748 ] huxihx commented on KAFKA-7304: --- [~yuzhih...@gmail.com] The channel was closed in `doClose`. > memory

[jira] [Assigned] (KAFKA-7299) batch LeaderAndIsr requests during auto preferred leader election

[ https://issues.apache.org/jira/browse/KAFKA-7299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxihx reassigned KAFKA-7299: - Assignee: huxihx > batch LeaderAndIsr requests during auto preferred leader election >

[jira] [Commented] (KAFKA-7291) kafka-console-consumer.sh waits on inexistent topic

[ https://issues.apache.org/jira/browse/KAFKA-7291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16581803#comment-16581803 ] huxihx commented on KAFKA-7291: --- With the latest build, ConsoleConsumer complains `Error while fetching

[jira] [Commented] (KAFKA-7279) partitionsFor implicitly creates topic for the existent topic

[ https://issues.apache.org/jira/browse/KAFKA-7279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16580729#comment-16580729 ] huxihx commented on KAFKA-7279: --- [~hachikuji] is it as designed? > partitionsFor implicitly creates topic

[jira] [Created] (KAFKA-7279) partitionsFor implicitly creates topic for the existent topic

huxihx created KAFKA-7279: - Summary: partitionsFor implicitly creates topic for the existent topic Key: KAFKA-7279 URL: https://issues.apache.org/jira/browse/KAFKA-7279 Project: Kafka Issue Type:

[jira] [Assigned] (KAFKA-7211) MM should handle timeouts in commitSync

[ https://issues.apache.org/jira/browse/KAFKA-7211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxihx reassigned KAFKA-7211: - Assignee: huxihx > MM should handle timeouts in commitSync > --- >

[jira] [Commented] (KAFKA-7232) Allow kafka-topics.sh to take brokerid as parameter to show partitions associated with it

[ https://issues.apache.org/jira/browse/KAFKA-7232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16574571#comment-16574571 ] huxihx commented on KAFKA-7232: --- This needs a KIP, right? > Allow kafka-topics.sh to take brokerid as

[jira] [Commented] (KAFKA-7262) Ability to support heterogeneous storage in Kafka

[ https://issues.apache.org/jira/browse/KAFKA-7262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16574467#comment-16574467 ] huxihx commented on KAFKA-7262: --- [~fangbin] That might deserve a new KIP that have `TopicCommand` support

[jira] [Commented] (KAFKA-7241) Reassignment partitiona to non existent broker

[ https://issues.apache.org/jira/browse/KAFKA-7241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16574331#comment-16574331 ] huxihx commented on KAFKA-7241: --- Did you try to run with `--verify` before doing reassigning. This should

[jira] [Commented] (KAFKA-7262) Ability to support heterogeneous storage in Kafka

[ https://issues.apache.org/jira/browse/KAFKA-7262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16574235#comment-16574235 ] huxihx commented on KAFKA-7262: --- As of Kafka 1.1, you could move key topic partition data to SSD-mounted

[jira] [Comment Edited] (KAFKA-7141) kafka-consumer-group doesn't describe existing group

[ https://issues.apache.org/jira/browse/KAFKA-7141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16539619#comment-16539619 ] huxihx edited comment on KAFKA-7141 at 7/11/18 6:24 AM: [~wushujames] Agreed.

[jira] [Comment Edited] (KAFKA-7141) kafka-consumer-group doesn't describe existing group

[ https://issues.apache.org/jira/browse/KAFKA-7141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16539619#comment-16539619 ] huxihx edited comment on KAFKA-7141 at 7/11/18 6:23 AM: [~wushujames] Agreed.

[jira] [Commented] (KAFKA-7141) kafka-consumer-group doesn't describe existing group

[ https://issues.apache.org/jira/browse/KAFKA-7141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16539619#comment-16539619 ] huxihx commented on KAFKA-7141: --- [~wushujames] Agreed. This makes no sense that whether committing offsets

[jira] [Reopened] (KAFKA-7141) kafka-consumer-group doesn't describe existing group

[ https://issues.apache.org/jira/browse/KAFKA-7141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxihx reopened KAFKA-7141: --- Assignee: huxihx > kafka-consumer-group doesn't describe existing group >

[jira] [Commented] (KAFKA-7078) Kafka 1.0.1 Broker version crashes when deleting log

[ https://issues.apache.org/jira/browse/KAFKA-7078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16536498#comment-16536498 ] huxihx commented on KAFKA-7078: --- [~zxj1009] Did you change the cleanup policy for topic

[jira] [Commented] (KAFKA-7078) Kafka 1.0.1 Broker version crashes when deleting log

[ https://issues.apache.org/jira/browse/KAFKA-7078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16518797#comment-16518797 ] huxihx commented on KAFKA-7078: --- [~zxj1009] Does

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

[ https://issues.apache.org/jira/browse/KAFKA-6952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16499984#comment-16499984 ] huxihx commented on KAFKA-6952: --- Could you offer the value of config `log.message.format.version` for your

[jira] [Commented] (KAFKA-6982) java.lang.ArithmeticException: / by zero

[ https://issues.apache.org/jira/browse/KAFKA-6982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16498824#comment-16498824 ] huxihx commented on KAFKA-6982: --- Did you resize the processor thread pool? >

[jira] [Assigned] (KAFKA-6973) setting invalid timestamp causes Kafka broker restart to fail

[ https://issues.apache.org/jira/browse/KAFKA-6973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxihx reassigned KAFKA-6973: - Assignee: huxihx (was: Manikumar) > setting invalid timestamp causes Kafka broker restart to fail >

[jira] [Comment Edited] (KAFKA-6898) org.apache.kafka.common.errors.TimeoutException

[ https://issues.apache.org/jira/browse/KAFKA-6898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16490189#comment-16490189 ] huxihx edited comment on KAFKA-6898 at 5/25/18 3:58 AM: Could you check if the

[jira] [Commented] (KAFKA-6842) initTransactions hangs when trying to connect to non-existing broker

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

[jira] [Assigned] (KAFKA-6814) Bad exception message for GroupIdNotFoundException/GroupNotEmptyException

[ https://issues.apache.org/jira/browse/KAFKA-6814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxihx reassigned KAFKA-6814: - Assignee: huxihx > Bad exception message for GroupIdNotFoundException/GroupNotEmptyException >

[jira] [Created] (KAFKA-6814) Bad exception message for GroupIdNotFoundException/GroupNotEmptyException

huxihx created KAFKA-6814: - Summary: Bad exception message for GroupIdNotFoundException/GroupNotEmptyException Key: KAFKA-6814 URL: https://issues.apache.org/jira/browse/KAFKA-6814 Project: Kafka

[jira] [Assigned] (KAFKA-6791) Add a CoordinatorNodeProvider in KafkaAdminClient

[ https://issues.apache.org/jira/browse/KAFKA-6791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxihx reassigned KAFKA-6791: - Assignee: huxihx > Add a CoordinatorNodeProvider in KafkaAdminClient >

[jira] [Commented] (KAFKA-6592) NullPointerException thrown when executing ConsoleCosumer with deserializer set to `WindowedDeserializer`

[ https://issues.apache.org/jira/browse/KAFKA-6592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16445120#comment-16445120 ] huxihx commented on KAFKA-6592: --- [~guozhang] Can this Jira issue be closed safely? > NullPointerException

[jira] [Commented] (KAFKA-6777) Wrong reaction on Out Of Memory situation

[ https://issues.apache.org/jira/browse/KAFKA-6777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16436445#comment-16436445 ] huxihx commented on KAFKA-6777: --- A possible way is to diagnose the GC logs to see why it spent so much CPU

[jira] [Commented] (KAFKA-2526) Console Producer / Consumer's serde config is not working

[ https://issues.apache.org/jira/browse/KAFKA-2526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16429606#comment-16429606 ] huxihx commented on KAFKA-2526: --- [~mgharat] Do you still work on this jira? > Console Producer / Consumer's

[jira] [Updated] (KAFKA-6731) waitOnState waits for the wrong state instead of the target one

[ https://issues.apache.org/jira/browse/KAFKA-6731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxihx updated KAFKA-6731: -- Description: In KafkaStreams.waitOnState, the code waits the state to be set to NOT_RUNNING instead of the

[jira] [Assigned] (KAFKA-6731) waitOnState waits for the wrong state instead of the target one

[ https://issues.apache.org/jira/browse/KAFKA-6731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxihx reassigned KAFKA-6731: - Assignee: huxihx > waitOnState waits for the wrong state instead of the target one >

[jira] [Created] (KAFKA-6731) waitOnState waits for the wrong state instead of the target one

huxihx created KAFKA-6731: - Summary: waitOnState waits for the wrong state instead of the target one Key: KAFKA-6731 URL: https://issues.apache.org/jira/browse/KAFKA-6731 Project: Kafka Issue Type:

[jira] [Commented] (KAFKA-6592) NullPointerException thrown when executing ConsoleCosumer with deserializer set to `WindowedDeserializer`

[ https://issues.apache.org/jira/browse/KAFKA-6592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420029#comment-16420029 ] huxihx commented on KAFKA-6592: --- [~guozhang]

[jira] [Assigned] (KAFKA-6716) discardChannel should be released in MockSelector#completeSend

[ https://issues.apache.org/jira/browse/KAFKA-6716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxihx reassigned KAFKA-6716: - Assignee: huxihx > discardChannel should be released in MockSelector#completeSend >

[jira] [Commented] (KAFKA-6689) Kafka not release .deleted file.

[ https://issues.apache.org/jira/browse/KAFKA-6689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16407938#comment-16407938 ] huxihx commented on KAFKA-6689: --- [~Ueng] I believe this issue actually results from the same root cause with

[jira] [Commented] (KAFKA-6666) OffsetOutOfRangeException: Replica Thread Stopped Resulting in Underreplicated Partitions

[ https://issues.apache.org/jira/browse/KAFKA-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16401411#comment-16401411 ] huxihx commented on KAFKA-: --- The exception is caused by the fact that high watermark was set to -1 which

[jira] [Assigned] (KAFKA-6663) Expression for GlobalKTable is not correct

[ https://issues.apache.org/jira/browse/KAFKA-6663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxihx reassigned KAFKA-6663: - Assignee: huxihx > Expression for GlobalKTable is not correct >

[jira] [Commented] (KAFKA-6666) OffsetOutOfRangeException: Replica Thread Stopped Resulting in Underreplicated Partitions

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

[jira] [Created] (KAFKA-6663) Expression for GlobalKTable is not correct

huxihx created KAFKA-6663: - Summary: Expression for GlobalKTable is not correct Key: KAFKA-6663 URL: https://issues.apache.org/jira/browse/KAFKA-6663 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-6651) SchemaBuilder should not allow Arrays or Maps to be created by type()

[ https://issues.apache.org/jira/browse/KAFKA-6651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16397962#comment-16397962 ] huxihx commented on KAFKA-6651: --- Instead of throwing exceptions, we could possibly add a couple of `setters`

[jira] [Assigned] (KAFKA-6637) if set topic config segment.ms=0 Kafka broker won't be able to start

[ https://issues.apache.org/jira/browse/KAFKA-6637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxihx reassigned KAFKA-6637: - Assignee: huxihx > if set topic config segment.ms=0 Kafka broker won't be able to start >

[jira] [Commented] (KAFKA-6627) Console producer default config values override explicitly provided properties

[ https://issues.apache.org/jira/browse/KAFKA-6627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16392272#comment-16392272 ] huxihx commented on KAFKA-6627: --- Seems this is similar to what's reported in

[jira] [Commented] (KAFKA-6507) NPE in KafkaStatusBackingStore

[ https://issues.apache.org/jira/browse/KAFKA-6507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16387435#comment-16387435 ] huxihx commented on KAFKA-6507: --- [~itaycohai] Did you run into this problem when using the same versions for

[jira] [Commented] (KAFKA-6610) initial high watermark -1, used for truncation, cause "Cannot truncate to a negative offset"

[ https://issues.apache.org/jira/browse/KAFKA-6610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16387110#comment-16387110 ] huxihx commented on KAFKA-6610: --- Could you turn on the trace and find if there are any traces like 'Reading

[jira] [Resolved] (KAFKA-6592) NullPointerException thrown when executing ConsoleCosumer with deserializer set to `WindowedDeserializer`

[ https://issues.apache.org/jira/browse/KAFKA-6592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxihx resolved KAFKA-6592. --- Resolution: Duplicate Seems it's a duplicate of

[jira] [Commented] (KAFKA-6595) Kafka connect commit offset incorrectly.

[ https://issues.apache.org/jira/browse/KAFKA-6595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16383062#comment-16383062 ] huxihx commented on KAFKA-6595: --- Could we simply cancel the flush if we find another thread has already

<    1   2   3   4   >