[jira] [Commented] (KAFKA-4367) MirrorMaker shuts down gracefully without actually being stopped

[ https://issues.apache.org/jira/browse/KAFKA-4367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15634711#comment-15634711 ] huxi commented on KAFKA-4367: - Did you run it with nohup? > MirrorMaker shuts down gracefully

[jira] [Commented] (KAFKA-4373) Kafka Consumer API jumping offsets

[ https://issues.apache.org/jira/browse/KAFKA-4373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15634757#comment-15634757 ] huxi commented on KAFKA-4373: - Could you paste your client code and the stack trace? > Kafka

[jira] [Commented] (KAFKA-4386) Producer Metrics Explanation

[ https://issues.apache.org/jira/browse/KAFKA-4386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15646087#comment-15646087 ] huxi commented on KAFKA-4386: - In my understanding, these metrics are all request-level. Take

[jira] [Commented] (KAFKA-4389) kafka-server.stop.sh not work

[ https://issues.apache.org/jira/browse/KAFKA-4389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15646319#comment-15646319 ] huxi commented on KAFKA-4389: - Seems it is a duplicate of issue 4297. https://issues.apache.o

[jira] [Commented] (KAFKA-4391) On Windows, Kafka server stops with uncaught exception after coming back from sleep

[ https://issues.apache.org/jira/browse/KAFKA-4391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15649179#comment-15649179 ] huxi commented on KAFKA-4391: - It might because of the fact that network and disk will be deac

[jira] [Comment Edited] (KAFKA-4391) On Windows, Kafka server stops with uncaught exception after coming back from sleep

[ https://issues.apache.org/jira/browse/KAFKA-4391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15649179#comment-15649179 ] huxi edited comment on KAFKA-4391 at 11/8/16 11:31 PM: --- It might be

[jira] [Commented] (KAFKA-4396) Seeing offsets not resetting even when reset policy is configured explicitly

[ https://issues.apache.org/jira/browse/KAFKA-4396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15652596#comment-15652596 ] huxi commented on KAFKA-4396: - I notice that you set "enable.auto.commit" to false meaning you

[jira] [Created] (KAFKA-4398) offsetsForTimes returns false starting offset when timestamp of messages are not monotonically increasing

huxi created KAFKA-4398: --- Summary: offsetsForTimes returns false starting offset when timestamp of messages are not monotonically increasing Key: KAFKA-4398 URL: https://issues.apache.org/jira/browse/KAFKA-4398

[jira] [Commented] (KAFKA-4398) offsetsForTimes returns false starting offset when timestamp of messages are not monotonically increasing

[ https://issues.apache.org/jira/browse/KAFKA-4398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15657350#comment-15657350 ] huxi commented on KAFKA-4398: - [~becket_qin] Does it make any sense? > offsetsForTimes return

[jira] [Commented] (KAFKA-4398) offsetsForTimes returns false starting offset when timestamp of messages are not monotonically increasing

[ https://issues.apache.org/jira/browse/KAFKA-4398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15658690#comment-15658690 ] huxi commented on KAFKA-4398: - [~becket_qin] Based on the current design, you are definitely r

[jira] [Commented] (KAFKA-4398) offsetsForTimes returns false starting offset when timestamp of messages are not monotonically increasing

[ https://issues.apache.org/jira/browse/KAFKA-4398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15659333#comment-15659333 ] huxi commented on KAFKA-4398: - yes, what we really needs is to have the time index entry can b

[jira] [Resolved] (KAFKA-4398) offsetsForTimes returns false starting offset when timestamp of messages are not monotonically increasing

[ https://issues.apache.org/jira/browse/KAFKA-4398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxi resolved KAFKA-4398. - Resolution: Not A Bug > offsetsForTimes returns false starting offset when timestamp of messages are > not monoto

[jira] [Commented] (KAFKA-4391) On Windows, Kafka server stops with uncaught exception after coming back from sleep

[ https://issues.apache.org/jira/browse/KAFKA-4391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15669074#comment-15669074 ] huxi commented on KAFKA-4391: - If we focus on the renameTo issue, that's an infamous issue on

[jira] [Commented] (KAFKA-4414) Unexpected "Halting because log truncation is not allowed"

[ https://issues.apache.org/jira/browse/KAFKA-4414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15669513#comment-15669513 ] huxi commented on KAFKA-4414: - Could you reproduce the issue if setting a smaller value for "

[jira] [Commented] (KAFKA-4425) Topic created with CreateTopic command, does not list partitions in metadata

[ https://issues.apache.org/jira/browse/KAFKA-4425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15682220#comment-15682220 ] huxi commented on KAFKA-4425: - What timeout value do you specify in the TopicDetails? > Topic

[jira] [Assigned] (KAFKA-4428) Kafka does not exit when it receives "Address already in use" error during startup

[ https://issues.apache.org/jira/browse/KAFKA-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxi reassigned KAFKA-4428: --- Assignee: huxi > Kafka does not exit when it receives "Address already in use" error during > startup >

[jira] [Commented] (KAFKA-4428) Kafka does not exit when it receives "Address already in use" error during startup

[ https://issues.apache.org/jira/browse/KAFKA-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15685562#comment-15685562 ] huxi commented on KAFKA-4428: - During Acceptor initialization, if "Address already in use" err

[jira] [Comment Edited] (KAFKA-4428) Kafka does not exit when it receives "Address already in use" error during startup

[ https://issues.apache.org/jira/browse/KAFKA-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15685562#comment-15685562 ] huxi edited comment on KAFKA-4428 at 11/22/16 3:32 AM: --- During Accep

[jira] [Comment Edited] (KAFKA-4428) Kafka does not exit when it receives "Address already in use" error during startup

[ https://issues.apache.org/jira/browse/KAFKA-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15685562#comment-15685562 ] huxi edited comment on KAFKA-4428 at 11/22/16 3:39 AM: --- During Accep

[jira] [Commented] (KAFKA-4430) Broker logging "Topic and partition to exceptions: [topic,6] -> kafka.common.MessageSizeTooLargeException"

[ https://issues.apache.org/jira/browse/KAFKA-4430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15685848#comment-15685848 ] huxi commented on KAFKA-4430: - Check broker config 'message.max.bytes' for Aggregate Kafka clu

[jira] [Commented] (KAFKA-4430) Broker logging "Topic and partition to exceptions: [topic,6] -> kafka.common.MessageSizeTooLargeException"

[ https://issues.apache.org/jira/browse/KAFKA-4430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15685911#comment-15685911 ] huxi commented on KAFKA-4430: - Maybe you could confirm this: complete serialized size of the

[jira] [Commented] (KAFKA-4430) Broker logging "Topic and partition to exceptions: [topic,6] -> kafka.common.MessageSizeTooLargeException"

[ https://issues.apache.org/jira/browse/KAFKA-4430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15688610#comment-15688610 ] huxi commented on KAFKA-4430: - Seems no debug statements can be enabled, but you could fire up

[jira] [Commented] (KAFKA-4430) Broker logging "Topic and partition to exceptions: [topic,6] -> kafka.common.MessageSizeTooLargeException"

[ https://issues.apache.org/jira/browse/KAFKA-4430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15689102#comment-15689102 ] huxi commented on KAFKA-4430: - A message larger than batch.size but smaller than max.request.s

[jira] [Commented] (KAFKA-4430) Broker logging "Topic and partition to exceptions: [topic,6] -> kafka.common.MessageSizeTooLargeException"

[ https://issues.apache.org/jira/browse/KAFKA-4430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15692402#comment-15692402 ] huxi commented on KAFKA-4430: - Great find. And, why is the message compressed twice and how di

[jira] [Updated] (KAFKA-4434) KafkaProducer configuration is logged twice

[ https://issues.apache.org/jira/browse/KAFKA-4434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxi updated KAFKA-4434: Assignee: kevin.chen > KafkaProducer configuration is logged twice > --- > >

[jira] [Commented] (KAFKA-4434) KafkaProducer configuration is logged twice

[ https://issues.apache.org/jira/browse/KAFKA-4434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15720878#comment-15720878 ] huxi commented on KAFKA-4434: - already assigned to you. > KafkaProducer configuration is logg

[jira] [Commented] (KAFKA-4489) Kafka Consumer throws Java Heap Out of Space Error on failed SSL connections

[ https://issues.apache.org/jira/browse/KAFKA-4489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15723994#comment-15723994 ] huxi commented on KAFKA-4489: - Seems a thread pool holding multiple KafkaConsumer instances wa

[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&focusedCommentId=15724184#comment-15724184 ] huxi commented on KAFKA-2526: - For the new producer, serde config is hard coded as props.put

[jira] [Commented] (KAFKA-4505) Cannot get topic lag since kafka upgrade from 0.8.1.0 to 0.10.1.0

[ https://issues.apache.org/jira/browse/KAFKA-4505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15730958#comment-15730958 ] huxi commented on KAFKA-4505: - Is the group active? Check if znode '/consumers//owners' exists

[jira] [Commented] (KAFKA-4497) log cleaner breaks on timeindex

[ https://issues.apache.org/jira/browse/KAFKA-4497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15731588#comment-15731588 ] huxi commented on KAFKA-4497: - LogCleaner.cleanOrSleep only captures LogCleaningAbortedExcepti

[jira] [Commented] (KAFKA-4497) log cleaner breaks on timeindex

[ https://issues.apache.org/jira/browse/KAFKA-4497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15731654#comment-15731654 ] huxi commented on KAFKA-4497: - [~roschumann] Did you enable compression for topic 'xdc_listing

[jira] [Commented] (KAFKA-4505) Cannot get topic lag since kafka upgrade from 0.8.1.0 to 0.10.1.0

[ https://issues.apache.org/jira/browse/KAFKA-4505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15733965#comment-15733965 ] huxi commented on KAFKA-4505: - Do you use the new consumer or the zk consumer after the migrat

[jira] [Commented] (KAFKA-4497) log cleaner breaks on timeindex

[ https://issues.apache.org/jira/browse/KAFKA-4497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15734657#comment-15734657 ] huxi commented on KAFKA-4497: - A safe but naive solution is to reject this invalid index entry

[jira] [Commented] (KAFKA-4515) Async producer send not retrying on TimeoutException: Batch Expired

[ https://issues.apache.org/jira/browse/KAFKA-4515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15734702#comment-15734702 ] huxi commented on KAFKA-4515: - Did you see lots of "Got error produce response with correlatio

[jira] [Commented] (KAFKA-4530) cant stop kafka server

[ https://issues.apache.org/jira/browse/KAFKA-4530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15744578#comment-15744578 ] huxi commented on KAFKA-4530: - Is it a duplicate of [kafka-4297|https://issues.apache.org/jir

[jira] [Commented] (KAFKA-4505) Cannot get topic lag since kafka upgrade from 0.8.1.0 to 0.10.1.0

[ https://issues.apache.org/jira/browse/KAFKA-4505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15745241#comment-15745241 ] huxi commented on KAFKA-4505: - I am assuming you are still using the old consumer (using 'zook

[jira] [Commented] (KAFKA-4505) Cannot get topic lag since kafka upgrade from 0.8.1.0 to 0.10.1.0

[ https://issues.apache.org/jira/browse/KAFKA-4505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15746918#comment-15746918 ] huxi commented on KAFKA-4505: - I don't think it's a good solution. The path you created in Zoo

[jira] [Commented] (KAFKA-4015) Change cleanup.policy config to accept a list of valid policies

[ https://issues.apache.org/jira/browse/KAFKA-4015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15753796#comment-15753796 ] huxi commented on KAFKA-4015: - [~damianguy]I did not find any occurrence in the doc or sou

[jira] [Commented] (KAFKA-4560) Min / Max Partitions Fetch Records params

[ https://issues.apache.org/jira/browse/KAFKA-4560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15762931#comment-15762931 ] huxi commented on KAFKA-4560: - There is a consumer config named "max.poll.records" that contro

[jira] [Commented] (KAFKA-4560) Min / Max Partitions Fetch Records params

[ https://issues.apache.org/jira/browse/KAFKA-4560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15763027#comment-15763027 ] huxi commented on KAFKA-4560: - Not sure if I catch your meaning. You want a config controlling

[jira] [Commented] (KAFKA-4560) Min / Max Partitions Fetch Records params

[ https://issues.apache.org/jira/browse/KAFKA-4560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15769203#comment-15769203 ] huxi commented on KAFKA-4560: - Could you illustrate a real scenario when 'max.partitions.fetch

[jira] [Commented] (KAFKA-4573) Producer sporadic timeout

[ https://issues.apache.org/jira/browse/KAFKA-4573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15784692#comment-15784692 ] huxi commented on KAFKA-4573: - Is it possible it's caused by a transient network error? > Pr

[jira] [Commented] (KAFKA-4577) NPE in ControllerChannelManager.scala::addUpdateMetadataRequestForBrokers

[ https://issues.apache.org/jira/browse/KAFKA-4577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15790517#comment-15790517 ] huxi commented on KAFKA-4577: - Could you elaborate on the steps you ran into this problem? >

[jira] [Comment Edited] (KAFKA-4577) NPE in ControllerChannelManager.scala::addUpdateMetadataRequestForBrokers

[ https://issues.apache.org/jira/browse/KAFKA-4577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15790517#comment-15790517 ] huxi edited comment on KAFKA-4577 at 1/1/17 4:26 AM: - Could you elabor

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

[ https://issues.apache.org/jira/browse/KAFKA-4576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15794042#comment-15794042 ] huxi commented on KAFKA-4576: - Seems FileChannel.read does not fill up the 12-byte buffer alth

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

[ https://issues.apache.org/jira/browse/KAFKA-4576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15795040#comment-15795040 ] huxi commented on KAFKA-4576: - If we use a loop structure to collect all the 12 bytes, there i

[jira] [Assigned] (KAFKA-4434) KafkaProducer configuration is logged twice

[ https://issues.apache.org/jira/browse/KAFKA-4434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxi reassigned KAFKA-4434: --- Assignee: huxi (was: kevin.chen) > KafkaProducer configuration is logged twice > ---

[jira] [Resolved] (KAFKA-4308) Inconsistent parameters between console producer and consumer

[ https://issues.apache.org/jira/browse/KAFKA-4308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxi resolved KAFKA-4308. - Resolution: Duplicate > Inconsistent parameters between console producer and consumer > --

[jira] [Assigned] (KAFKA-3739) Add no-arg constructor for library provided serdes

[ https://issues.apache.org/jira/browse/KAFKA-3739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxi reassigned KAFKA-3739: --- Assignee: huxi > Add no-arg constructor for library provided serdes > ---

[jira] [Resolved] (KAFKA-4434) KafkaProducer configuration is logged twice

[ https://issues.apache.org/jira/browse/KAFKA-4434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxi resolved KAFKA-4434. - Resolution: Fixed Reviewer: Ismael Juma > KafkaProducer configuration is logged twice >

[jira] [Commented] (KAFKA-4811) ReplicaFetchThread may fail to create due to existing metric

[ https://issues.apache.org/jira/browse/KAFKA-4811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15887308#comment-15887308 ] huxi commented on KAFKA-4811: - [~junrao] what about the port change? Do we also need to consid

[jira] [Assigned] (KAFKA-4811) ReplicaFetchThread may fail to create due to existing metric

[ https://issues.apache.org/jira/browse/KAFKA-4811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxi reassigned KAFKA-4811: --- Assignee: huxi > ReplicaFetchThread may fail to create due to existing metric > -

[jira] [Commented] (KAFKA-4822) Kafka producer implementation without additional threads, similar to sync producer of 0.8.

[ https://issues.apache.org/jira/browse/KAFKA-4822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15889871#comment-15889871 ] huxi commented on KAFKA-4822: - For KafkaProducer, all writes are asynchronous by default. Snip

[jira] [Commented] (KAFKA-4834) Kafka cannot delete topic with ReplicaStateMachine went wrong

[ https://issues.apache.org/jira/browse/KAFKA-4834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15893619#comment-15893619 ] huxi commented on KAFKA-4834: - How did you delete the topic? Seems the partitions' state is st

[jira] [Commented] (KAFKA-4844) kafka is holding open file descriptors

[ https://issues.apache.org/jira/browse/KAFKA-4844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15896815#comment-15896815 ] huxi commented on KAFKA-4844: - What is your OS version? Seems it's a known behavior before NFS

[jira] [Commented] (KAFKA-4834) Kafka cannot delete topic with ReplicaStateMachine went wrong

[ https://issues.apache.org/jira/browse/KAFKA-4834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15898790#comment-15898790 ] huxi commented on KAFKA-4834: - Did you delete the zookeeper nodes manually before issuing this

[jira] [Assigned] (KAFKA-4866) Kafka console consumer property is ignored

[ https://issues.apache.org/jira/browse/KAFKA-4866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxi reassigned KAFKA-4866: --- Assignee: huxi > Kafka console consumer property is ignored > -- > >

[jira] [Commented] (KAFKA-4879) KafkaConsumer.position may hang forever when deleting a topic

[ https://issues.apache.org/jira/browse/KAFKA-4879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15904322#comment-15904322 ] huxi commented on KAFKA-4879: - Could have KafkaConsumer#updateFetchPositions, Fetcher#updateFe

[jira] [Commented] (KAFKA-4908) consumer.properties logging warnings

[ https://issues.apache.org/jira/browse/KAFKA-4908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15932099#comment-15932099 ] huxi commented on KAFKA-4908: - `zookeeper.connection.timeout.ms` and `zookeeper.connect` are

[jira] [Commented] (KAFKA-4949) Calling kaka-consumer-group.sh to get the consumer offset throws OOM with heap space error

[ https://issues.apache.org/jira/browse/KAFKA-4949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15942584#comment-15942584 ] huxi commented on KAFKA-4949: - Is is a duplicate of [kafka-4090|https://issues.apache.org/jir

[jira] [Comment Edited] (KAFKA-4949) Calling kaka-consumer-group.sh to get the consumer offset throws OOM with heap space error

[ https://issues.apache.org/jira/browse/KAFKA-4949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15942584#comment-15942584 ] huxi edited comment on KAFKA-4949 at 3/27/17 3:30 AM: -- Is it a duplic

[jira] [Commented] (KAFKA-4952) ZkUtils get topics by consumer group not correct

[ https://issues.apache.org/jira/browse/KAFKA-4952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15944500#comment-15944500 ] huxi commented on KAFKA-4952: - [~zxylvlp] All subscribed topics' names will be created as a ch

[jira] [Commented] (KAFKA-4987) Topic creation allows invalid config values on running brokers

[ https://issues.apache.org/jira/browse/KAFKA-4987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15950237#comment-15950237 ] huxi commented on KAFKA-4987: - Did you use a higher version of client talking to a lower versi

[jira] [Commented] (KAFKA-5048) kafka brokers hang when one of broker node killed in the cluster and remaining broker nodes are not consuming the data.

[ https://issues.apache.org/jira/browse/KAFKA-5048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15965622#comment-15965622 ] huxi commented on KAFKA-5048: - These warnings should be transient as long as you set the repli

[jira] [Commented] (KAFKA-5062) Kafka brokers can accept malformed requests which allocate gigabytes of memory

[ https://issues.apache.org/jira/browse/KAFKA-5062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15967026#comment-15967026 ] huxi commented on KAFKA-5062: - I am intrigued by how to reproduce the problem. > Kafka broker

[jira] [Commented] (KAFKA-5068) Optionally print out metrics after running the perf tests

[ https://issues.apache.org/jira/browse/KAFKA-5068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15968805#comment-15968805 ] huxi commented on KAFKA-5068: - Seems ProducerPerformance does print the final result for the t

[jira] [Assigned] (KAFKA-5068) Optionally print out metrics after running the perf tests

[ https://issues.apache.org/jira/browse/KAFKA-5068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxi reassigned KAFKA-5068: --- Assignee: huxi > Optionally print out metrics after running the perf tests >

[jira] [Commented] (KAFKA-5010) Log cleaner crashed with BufferOverflowException when writing to the writeBuffer

[ https://issues.apache.org/jira/browse/KAFKA-5010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15972081#comment-15972081 ] huxi commented on KAFKA-5010: - [~ijuma] Is it due to the fact that Kafka chooses 1024 as the m

[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&focusedCommentId=15972314#comment-15972314 ] huxi commented on KAFKA-5007: - Maybe a complete stack trace is helpful to diagnose what action

[jira] [Assigned] (KAFKA-5104) DumpLogSegments should not open index files with `rw`

[ https://issues.apache.org/jira/browse/KAFKA-5104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxi reassigned KAFKA-5104: --- Assignee: huxi > DumpLogSegments should not open index files with `rw` >

[jira] [Reopened] (KAFKA-4295) kafka-console-consumer.sh does not delete the temporary group in zookeeper

[ https://issues.apache.org/jira/browse/KAFKA-4295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxi reopened KAFKA-4295: - > kafka-console-consumer.sh does not delete the temporary group in zookeeper > ---

[jira] [Commented] (KAFKA-4592) Kafka Producer Metrics Invalid Value

[ https://issues.apache.org/jira/browse/KAFKA-4592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15801348#comment-15801348 ] huxi commented on KAFKA-4592: - Seems that o.a.k.common.metrics.stats.Max's default constructor

[jira] [Comment Edited] (KAFKA-4592) Kafka Producer Metrics Invalid Value

[ https://issues.apache.org/jira/browse/KAFKA-4592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15801348#comment-15801348 ] huxi edited comment on KAFKA-4592 at 1/5/17 1:31 PM: - Seems that o.a.k

[jira] [Assigned] (KAFKA-4592) Kafka Producer Metrics Invalid Value

[ https://issues.apache.org/jira/browse/KAFKA-4592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxi reassigned KAFKA-4592: --- Assignee: huxi > Kafka Producer Metrics Invalid Value > > >

[jira] [Comment Edited] (KAFKA-4592) Kafka Producer Metrics Invalid Value

[ https://issues.apache.org/jira/browse/KAFKA-4592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15801348#comment-15801348 ] huxi edited comment on KAFKA-4592 at 1/5/17 2:36 PM: - Seems that o.a.k

[jira] [Commented] (KAFKA-4599) KafkaConsumer encounters SchemaException when Kafka broker stopped

[ https://issues.apache.org/jira/browse/KAFKA-4599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15803315#comment-15803315 ] huxi commented on KAFKA-4599: - What kind of Storm-supplied kafka client do you use? storm-kafk

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

[ https://issues.apache.org/jira/browse/KAFKA-4595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15803804#comment-15803804 ] huxi commented on KAFKA-4595: - Yes, seems that the process might look like this: 1. At some po

[jira] [Commented] (KAFKA-4603) argument error,and command parsed error

[ https://issues.apache.org/jira/browse/KAFKA-4603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15803933#comment-15803933 ] huxi commented on KAFKA-4603: - [~auroraxlh] If you exactly type '--zookeeper.connect' the comm

[jira] [Commented] (KAFKA-4614) Long GC pause harming broker performance which is caused by mmap objects created for OffsetIndex

[ https://issues.apache.org/jira/browse/KAFKA-4614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15817849#comment-15817849 ] huxi commented on KAFKA-4614: - Great catch for the whole things. As for the unmap things, se

[jira] [Comment Edited] (KAFKA-4614) Long GC pause harming broker performance which is caused by mmap objects created for OffsetIndex

[ https://issues.apache.org/jira/browse/KAFKA-4614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15817849#comment-15817849 ] huxi edited comment on KAFKA-4614 at 1/11/17 10:00 AM: --- Great catch

[jira] [Commented] (KAFKA-4616) Message log is seen when kafka-producer-perf-test.sh is running and any broker restarted in middle in-between

[ https://issues.apache.org/jira/browse/KAFKA-4616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15817886#comment-15817886 ] huxi commented on KAFKA-4616: - Could you set acks = -1 and retry the producer to see if there

[jira] [Commented] (KAFKA-4616) Message log is seen when kafka-producer-perf-test.sh is running and any broker restarted in middle in-between

[ https://issues.apache.org/jira/browse/KAFKA-4616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15820267#comment-15820267 ] huxi commented on KAFKA-4616: - Appending acks option to the command as this: --producer-props

[jira] [Commented] (KAFKA-4616) Message loss is seen when kafka-producer-perf-test.sh is running and any broker restarted in middle

[ https://issues.apache.org/jira/browse/KAFKA-4616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15821473#comment-15821473 ] huxi commented on KAFKA-4616: - They are not missing, but are just not delivered to Kafka succe

[jira] [Commented] (KAFKA-4629) Per topic MBeans leak

[ https://issues.apache.org/jira/browse/KAFKA-4629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15823029#comment-15823029 ] huxi commented on KAFKA-4629: - I tried in my kafka0.10.0.1 single-broker test environment with

[jira] [Commented] (KAFKA-4629) Per topic MBeans leak

[ https://issues.apache.org/jira/browse/KAFKA-4629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15823329#comment-15823329 ] huxi commented on KAFKA-4629: - [~alberto.fo...@natwestmarkets.com] Yes, multiple brokers DOES

[jira] [Commented] (KAFKA-4577) NPE in ControllerChannelManager.scala::addUpdateMetadataRequestForBrokers

[ https://issues.apache.org/jira/browse/KAFKA-4577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15823347#comment-15823347 ] huxi commented on KAFKA-4577: - I suspect the TopicDeletionManager instance in KafkaController

[jira] [Commented] (KAFKA-4557) ConcurrentModificationException in KafkaProducer event loop

[ https://issues.apache.org/jira/browse/KAFKA-4557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15823399#comment-15823399 ] huxi commented on KAFKA-4557: - [~scf37] Did you create your own Sender instances in the produc

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

[ https://issues.apache.org/jira/browse/KAFKA-4595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15823594#comment-15823594 ] huxi commented on KAFKA-4595: - [~pengwei] I don't think it's doable since it would leave incon

[jira] [Comment Edited] (KAFKA-4629) Per topic MBeans leak

[ https://issues.apache.org/jira/browse/KAFKA-4629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15823329#comment-15823329 ] huxi edited comment on KAFKA-4629 at 1/16/17 9:36 AM: -- [~alberto.fo..

[jira] [Commented] (KAFKA-4629) Per topic MBeans leak

[ https://issues.apache.org/jira/browse/KAFKA-4629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15825545#comment-15825545 ] huxi commented on KAFKA-4629: - Thanks for [~alberto.fo...@natwestmarkets.com]'s response. Afte

[jira] [Comment Edited] (KAFKA-4629) Per topic MBeans leak

[ https://issues.apache.org/jira/browse/KAFKA-4629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15825545#comment-15825545 ] huxi edited comment on KAFKA-4629 at 1/17/17 6:41 AM: -- Thanks for [~a

[jira] [Comment Edited] (KAFKA-4629) Per topic MBeans leak

[ https://issues.apache.org/jira/browse/KAFKA-4629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15825545#comment-15825545 ] huxi edited comment on KAFKA-4629 at 1/17/17 6:48 AM: -- Thanks for [~a

[jira] [Commented] (KAFKA-4674) Frequent ISR shrinking and expanding and disconnects among brokers

[ https://issues.apache.org/jira/browse/KAFKA-4674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15829525#comment-15829525 ] huxi commented on KAFKA-4674: - Is it a duplicate of [KAFKA-3916|https://issues.apache.org/jir

[jira] [Updated] (KAFKA-4295) kafka-console-consumer.sh does not delete the temporary group in zookeeper

[ https://issues.apache.org/jira/browse/KAFKA-4295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxi updated KAFKA-4295: Reviewer: Ismael Juma > kafka-console-consumer.sh does not delete the temporary group in zookeeper > ---

[jira] [Updated] (KAFKA-4592) Kafka Producer Metrics Invalid Value

[ https://issues.apache.org/jira/browse/KAFKA-4592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxi updated KAFKA-4592: Reviewer: Ismael Juma > Kafka Producer Metrics Invalid Value > > >

[jira] [Commented] (KAFKA-4675) Subsequent CreateTopic command could be lost after a DeleteTopic command

[ https://issues.apache.org/jira/browse/KAFKA-4675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15831945#comment-15831945 ] huxi commented on KAFKA-4675: - Seems deleting '/brokers/topics/' comes fourth from the bottom

[jira] [Commented] (KAFKA-4680) min.insync.replicas can be set higher than replication factor

[ https://issues.apache.org/jira/browse/KAFKA-4680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15832729#comment-15832729 ] huxi commented on KAFKA-4680: - If sending records to a topic with a larger 'min.insync.replica

[jira] [Created] (KAFKA-4684) Kafka does not offer kafka-configs.bat on Windows box

huxi created KAFKA-4684: --- Summary: Kafka does not offer kafka-configs.bat on Windows box Key: KAFKA-4684 URL: https://issues.apache.org/jira/browse/KAFKA-4684 Project: Kafka Issue Type: Improvement

[jira] [Comment Edited] (KAFKA-4675) Subsequent CreateTopic command could be lost after a DeleteTopic command

[ https://issues.apache.org/jira/browse/KAFKA-4675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1586#comment-1586 ] huxi edited comment on KAFKA-4675 at 1/22/17 7:26 AM: -- Failed to repr

[jira] [Commented] (KAFKA-4675) Subsequent CreateTopic command could be lost after a DeleteTopic command

[ https://issues.apache.org/jira/browse/KAFKA-4675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1586#comment-1586 ] huxi commented on KAFKA-4675: - Failed to reproduce this issue with snippet below: {code} val

  1   2   >