[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=16047582#comment-16047582 ] Jian Lin commented on KAFKA-5432: - One thing I can be sure of is that the error occurred after kafka

[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=16047637#comment-16047637 ] huxihx edited comment on KAFKA-5431 at 6/13/17 9:25 AM: Could you run commands

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

[ https://issues.apache.org/jira/browse/KAFKA-5432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian Lin updated KAFKA-5432: Description: Hey all, I met a strange problem, hope someone can help me. The program ran normally for a

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

[ https://issues.apache.org/jira/browse/KAFKA-5432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxihx updated KAFKA-5432: -- Component/s: (was: KafkaConnect) > producer and consumer SocketTimeoutException >

[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=16047561#comment-16047561 ] huxihx commented on KAFKA-5007: --- [~junrao] is it possible that it 's caused by the code snippet below:

Re: [DISCUSS] KIP-163: Lower the Minimum Required ACL Permission of OffsetFetch

Hi Vahid, +1 wrt OffsetFetch. The "Additional Food for Thought" mentions Heartbeat as a non-mutating action. I don't think that's true as the GroupCoordinator updates the latestHeartbeat field for the member and adds a new object to the heartbeatPurgatory, see

[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=16047569#comment-16047569 ] huxihx commented on KAFKA-5432: --- Seems it is a duplicate of

[jira] [Commented] (KAFKA-5123) Refactor ZkUtils readData* methods

[ https://issues.apache.org/jira/browse/KAFKA-5123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16047649#comment-16047649 ] Balint Molnar commented on KAFKA-5123: -- [~ijuma] what do you think about this? > Refactor ZkUtils

Re: [DISCUSS] KIP-150 - Kafka-Streams Cogroup

First, I would prefer not calling it aggregate because there are already plenty of aggregate methods. Second, I dont think this would really work because after each aggregate you now have a unique KTable (someone may want a table with 4 streams and reuse those 4 in another table but with one more

[GitHub] kafka pull request #3314: KAFKA-5439: Verify that no unexpected threads are ...

GitHub user rajinisivaram opened a pull request: https://github.com/apache/kafka/pull/3314 KAFKA-5439: Verify that no unexpected threads are left behind in tests You can merge this pull request into a Git repository by running: $ git pull

[jira] [Commented] (KAFKA-5439) Add checks in integration tests to verify that threads have been shutdown

[ https://issues.apache.org/jira/browse/KAFKA-5439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16047555#comment-16047555 ] ASF GitHub Bot commented on KAFKA-5439: --- GitHub user rajinisivaram opened a pull request:

[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=16047637#comment-16047637 ] huxihx commented on KAFKA-5431: --- Could you run command below to see whether there exists a corrupt record

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

[ https://issues.apache.org/jira/browse/KAFKA-5432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian Lin updated KAFKA-5432: Environment: os:Red Hat 4.4.7-17 java: java version "1.8.0_131" Java(TM) SE Runtime Environment (build

[jira] [Commented] (KAFKA-5245) KStream builder should capture serdes

[ https://issues.apache.org/jira/browse/KAFKA-5245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16047608#comment-16047608 ] Michal Borowiecki commented on KAFKA-5245: -- Just wanted to say it's great to see there's a ticket

[jira] [Updated] (KAFKA-5327) Console Consumer should only poll for up to max messages

[ https://issues.apache.org/jira/browse/KAFKA-5327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5327: --- Fix Version/s: (was: 0.11.0.0) 0.11.0.1 > Console Consumer should only poll

[jira] [Updated] (KAFKA-5383) Additional Test Cases for ReplicaManager

[ https://issues.apache.org/jira/browse/KAFKA-5383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5383: --- Fix Version/s: (was: 0.11.0.0) 0.11.0.1 > Additional Test Cases for

[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=16047871#comment-16047871 ] Carsten Rietz commented on KAFKA-5431: -- Thanks for the fast reponse. We did some more digging today

[jira] [Commented] (KAFKA-5165) Kafka Logs Cleanup Not happening, Huge File Growth - Windows

[ https://issues.apache.org/jira/browse/KAFKA-5165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16047917#comment-16047917 ] Manikandan P commented on KAFKA-5165: - This issue is happening in 0.10.0.0 version also. > Kafka

[jira] [Commented] (KAFKA-5245) KStream builder should capture serdes

[ https://issues.apache.org/jira/browse/KAFKA-5245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16047933#comment-16047933 ] Evgeny Veretennikov commented on KAFKA-5245: Matthias, thanks for explanation! How can I

[jira] [Updated] (KAFKA-4868) Optimize RocksDb config for fast recovery/bulk load

[ https://issues.apache.org/jira/browse/KAFKA-4868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Bejeck updated KAFKA-4868: --- Issue Type: Sub-task (was: Improvement) Parent: KAFKA-5363 > Optimize RocksDb config for

[jira] [Commented] (KAFKA-5274) Review and improve AdminClient Javadoc for the first release (KIP-117)

[ https://issues.apache.org/jira/browse/KAFKA-5274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16047966#comment-16047966 ] ASF GitHub Bot commented on KAFKA-5274: --- GitHub user ijuma opened a pull request:

[jira] [Assigned] (KAFKA-5418) ZkUtils.getAllPartitions() may fail if a topic is marked for deletion

[ https://issues.apache.org/jira/browse/KAFKA-5418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-5418: -- Assignee: Mickael Maison (was: Edoardo Comar) > ZkUtils.getAllPartitions() may fail if a

[jira] [Commented] (KAFKA-5439) Add checks in integration tests to verify that threads have been shutdown

[ https://issues.apache.org/jira/browse/KAFKA-5439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16047835#comment-16047835 ] ASF GitHub Bot commented on KAFKA-5439: --- Github user asfgit closed the pull request at:

[GitHub] kafka pull request #3314: KAFKA-5439: Verify that no unexpected threads are ...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3314 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Resolved] (KAFKA-5439) Add checks in integration tests to verify that threads have been shutdown

[ https://issues.apache.org/jira/browse/KAFKA-5439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram resolved KAFKA-5439. --- Resolution: Fixed Fix Version/s: 0.11.1.0 Issue resolved by pull request 3314

[jira] [Resolved] (KAFKA-1019) kafka-preferred-replica-election.sh will fail without clear error message if /brokers/topics/[topic]/partitions does not exist

[ https://issues.apache.org/jira/browse/KAFKA-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-1019. Resolution: Duplicate The underlying reason could be the same as KAFKA-5418. Closing as a

[jira] [Commented] (KAFKA-5418) ZkUtils.getAllPartitions() may fail if a topic is marked for deletion

[ https://issues.apache.org/jira/browse/KAFKA-5418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16047807#comment-16047807 ] ASF GitHub Bot commented on KAFKA-5418: --- Github user asfgit closed the pull request at:

[GitHub] kafka pull request #3316: [WIP] KAFKA-5274: AdminClient Javadoc improvements

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/3316 [WIP] KAFKA-5274: AdminClient Javadoc improvements Also improve the Javadoc for ExtendedSerializer, ExtendedDeserializer and InterfaceStability. Publish Javadoc for common.annotation

[GitHub] kafka pull request #3315: MINOR: Generate deprecated warning for static defa...

GitHub user rajinisivaram opened a pull request: https://github.com/apache/kafka/pull/3315 MINOR: Generate deprecated warning for static default quota config The default client-id bandwidth quota config properties have been marked deprecated in the doc, but a warning may be useful

[GitHub] kafka pull request #3295: KAFKA-5418: ZkUtils.getAllPartitions() may fail if...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3295 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Resolved] (KAFKA-5418) ZkUtils.getAllPartitions() may fail if a topic is marked for deletion

[ https://issues.apache.org/jira/browse/KAFKA-5418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-5418. Resolution: Fixed Fix Version/s: 0.11.0.0 Issue resolved by pull request 3295

Build failed in Jenkins: kafka-trunk-jdk7 #2387

See Changes: [ismael] MINOR: Avoid calling interceptors.onSendError() with null TopicPartition -- [...truncated 2.56 MB...]

[jira] [Commented] (KAFKA-3476) -Xloggc is not recognised by IBM java

[ https://issues.apache.org/jira/browse/KAFKA-3476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16047894#comment-16047894 ] Miguel Tablado commented on KAFKA-3476: --- Hi there, With latest apache kafka 0.10.2.1, scala 2.12

Build failed in Jenkins: kafka-trunk-jdk8 #1695

See Changes: [ismael] MINOR: Avoid calling interceptors.onSendError() with null TopicPartition -- [...truncated 2.57 MB...]

[GitHub] kafka pull request #3280: MINOR: Avoid calling interceptors.onSendError() wi...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3280 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Work started] (KAFKA-5274) Review and improve AdminClient Javadoc for the first release (KIP-117)

[ https://issues.apache.org/jira/browse/KAFKA-5274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-5274 started by Ismael Juma. -- > Review and improve AdminClient Javadoc for the first release (KIP-117) >

Build failed in Jenkins: kafka-trunk-jdk7 #2388

See Changes: [ismael] KAFKA-5418; ZkUtils.getAllPartitions() may fail if a topic is marked for [rajinisivaram] KAFKA-5439; Verify that no unexpected threads are left behind in tests

[jira] [Commented] (KAFKA-5354) MirrorMaker not preserving headers

[ https://issues.apache.org/jira/browse/KAFKA-5354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048298#comment-16048298 ] ASF GitHub Bot commented on KAFKA-5354: --- GitHub user michaelandrepearce opened a pull request:

[jira] [Comment Edited] (KAFKA-5354) MirrorMaker not preserving headers

[ https://issues.apache.org/jira/browse/KAFKA-5354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048320#comment-16048320 ] Michael Andre Pearce edited comment on KAFKA-5354 at 6/13/17 7:58 PM: --

Re: [DISCUSS]: KIP-159: Introducing Rich functions to Streams

Thanks for the comment Matthias. After all the discussion (thanks to all participants), I think this (single method that passes in a RecordContext object) is the best alternative. Just a side note: I think KAFKA-3907 [1] can also be integrated into the KIP by adding related method inside

[jira] [Commented] (KAFKA-5354) MirrorMaker not preserving headers

[ https://issues.apache.org/jira/browse/KAFKA-5354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048320#comment-16048320 ] Michael Andre Pearce commented on KAFKA-5354: - [~junrao] yes it was a bug, I've created a test

[jira] [Comment Edited] (KAFKA-5354) MirrorMaker not preserving headers

[ https://issues.apache.org/jira/browse/KAFKA-5354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048320#comment-16048320 ] Michael Andre Pearce edited comment on KAFKA-5354 at 6/13/17 7:57 PM: --

[jira] [Updated] (KAFKA-5354) MirrorMaker not preserving headers

[ https://issues.apache.org/jira/browse/KAFKA-5354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5354: --- Priority: Blocker (was: Major) > MirrorMaker not preserving headers >

[jira] [Commented] (KAFKA-5413) Log cleaner fails due to large offset in segment file

[ https://issues.apache.org/jira/browse/KAFKA-5413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048394#comment-16048394 ] Nicholas Ngorok commented on KAFKA-5413: This happened again today on another cluster we had

[DISCUSS] KIP-167: Add interface for the state store restoration process

The KIP has been updated to incorporate support for users to receive notification of state store restore progress for either pre-existing or custom state stores. A PR has been submitted concurrently https://github.com/apache/kafka/pull/3325 Thanks, Bill

[jira] [Assigned] (KAFKA-5212) Consumer ListOffsets request can starve group heartbeats

[ https://issues.apache.org/jira/browse/KAFKA-5212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson reassigned KAFKA-5212: -- Assignee: (was: Jason Gustafson) > Consumer ListOffsets request can starve group

[jira] [Updated] (KAFKA-4585) Offset fetch and commit requests use the same permissions

[ https://issues.apache.org/jira/browse/KAFKA-4585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vahid Hashemian updated KAFKA-4585: --- Labels: kip (was: needs-kip) > Offset fetch and commit requests use the same permissions >

[jira] [Work started] (KAFKA-5370) Replace uses of old consumer with the new consumer

[ https://issues.apache.org/jira/browse/KAFKA-5370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-5370 started by Vahid Hashemian. -- > Replace uses of old consumer with the new consumer >

Re: [VOTE] KIP-117: Add a public AdminClient API for Kafka admin operations

Hi all, We're getting close to the final 0.11 release and we still haven't gotten the version retrieval API for AdminClient in, as described by KAFKA-5214. Let's put this off until the next release so that we have some time to let it soak before shipping. This will just mean that we will remove

Re: [DISCUSS] KIP-150 - Kafka-Streams Cogroup

+1 on deferring discussion on Serdes until API improvements are ironed out. On Tue, Jun 13, 2017 at 2:06 PM, Matthias J. Sax wrote: > Hi, > > I am just catching up on this thread. (1) as most people agree, we > should not add anything to KStreamBuilder (btw: we actually

Re: [DISCUSS] KIP-163: Lower the Minimum Required ACL Permission of OffsetFetch

Hi Michal, Thanks a lot for your feedback. Your statement about Heartbeat is fair and makes sense. I'll update the KIP accordingly. --Vahid From: Michal Borowiecki To: us...@kafka.apache.org, Vahid S Hashemian ,

[jira] [Work started] (KAFKA-5363) Add ability to batch restore and receive restoration stats.

[ https://issues.apache.org/jira/browse/KAFKA-5363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-5363 started by Bill Bejeck. -- > Add ability to batch restore and receive restoration stats. >

[jira] [Commented] (KAFKA-5363) Add ability to batch restore and receive restoration stats.

[ https://issues.apache.org/jira/browse/KAFKA-5363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048378#comment-16048378 ] ASF GitHub Bot commented on KAFKA-5363: --- GitHub user bbejeck opened a pull request:

[GitHub] kafka pull request #3325: KAFKA-5363 [WIP] : Initial cut at implementing bul...

GitHub user bbejeck opened a pull request: https://github.com/apache/kafka/pull/3325 KAFKA-5363 [WIP] : Initial cut at implementing bulk load for persistent stat… …e stores You can merge this pull request into a Git repository by running: $ git pull

[GitHub] kafka pull request #3322: KAFKA-5354: MirrorMaker not preserving headers

GitHub user michaelandrepearce opened a pull request: https://github.com/apache/kafka/pull/3322 KAFKA-5354: MirrorMaker not preserving headers Add test case to ensure fix and avoid regression Update mirror maker for new consumer to preserve headers You can merge this pull

[jira] [Work started] (KAFKA-4868) Optimize RocksDb config for fast recovery/bulk load

[ https://issues.apache.org/jira/browse/KAFKA-4868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-4868 started by Bill Bejeck. -- > Optimize RocksDb config for fast recovery/bulk load >

Re: [DISCUSS] KIP-132: Augment KStream.print to allow extra parameters in the printed string

As there was no response from Marc, and we got KIP-160 as duplicate, I am "closing" this KIP without a vote. If there are any objections please let me know. -Matthias On 6/7/17 5:24 PM, Matthias J. Sax wrote: > Hi, > > as it turns out, we got two KIPs for the same Jira. KIP-160 duplicates >

[GitHub] kafka pull request #3324: Temporarily remove the apiVersions API for 0.11

GitHub user cmccabe opened a pull request: https://github.com/apache/kafka/pull/3324 Temporarily remove the apiVersions API for 0.11 You can merge this pull request into a Git repository by running: $ git pull https://github.com/cmccabe/kafka removeApiVersions Alternatively

[jira] [Commented] (KAFKA-5413) Log cleaner fails due to large offset in segment file

[ https://issues.apache.org/jira/browse/KAFKA-5413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048429#comment-16048429 ] Jun Rao commented on KAFKA-5413: [~Kelvinrutt], yes, that seems to be the issue.

[jira] [Commented] (KAFKA-5354) MirrorMaker not preserving headers

[ https://issues.apache.org/jira/browse/KAFKA-5354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048318#comment-16048318 ] ASF GitHub Bot commented on KAFKA-5354: --- GitHub user michaelandrepearce opened a pull request:

[GitHub] kafka pull request #3323: KAFKA-5354: MirrorMaker not preserving headers

GitHub user michaelandrepearce opened a pull request: https://github.com/apache/kafka/pull/3323 KAFKA-5354: MirrorMaker not preserving headers Add test case to ensure fix and avoid regression Update mirror maker for new consumer to preserve headers You can merge this pull

[jira] [Updated] (KAFKA-5354) MirrorMaker not preserving headers

[ https://issues.apache.org/jira/browse/KAFKA-5354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5354: --- Fix Version/s: 0.11.0.0 > MirrorMaker not preserving headers > -- > >

[jira] [Updated] (KAFKA-5354) MirrorMaker not preserving headers

[ https://issues.apache.org/jira/browse/KAFKA-5354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5354: --- Status: Patch Available (was: Open) > MirrorMaker not preserving headers >

[GitHub] kafka pull request #3321: HOTFIX: Handle Connector version returning 'null' ...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3321 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Commented] (KAFKA-3455) Connect custom processors with the streams DSL

[ https://issues.apache.org/jira/browse/KAFKA-3455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048626#comment-16048626 ] Bobby Calderwood commented on KAFKA-3455: - Hi Michal Borowiecki, Sorry for the late reply. I am

Jenkins build is back to normal : kafka-trunk-jdk8 #1702

See

[jira] [Comment Edited] (KAFKA-5444) Producer.send() will hang 8+ hours

[ https://issues.apache.org/jira/browse/KAFKA-5444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048709#comment-16048709 ] Hongyuan Li edited comment on KAFKA-5444 at 6/14/17 4:57 AM: - [~huxi_2b] May

[jira] [Commented] (KAFKA-5444) Producer.send() will hang 8+ hours

[ https://issues.apache.org/jira/browse/KAFKA-5444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048709#comment-16048709 ] Hongyuan Li commented on KAFKA-5444: [~huxi_2b] May be not duplicate of KAFKA-3552, the log

[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=16048586#comment-16048586 ] Joseph Aliase commented on KAFKA-5007: -- [~huxi_2b] Please let me know the class this block belongs

[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=16048605#comment-16048605 ] huxihx commented on KAFKA-5007: --- [~joseph.alias...@gmail.com] org.apache.kafka.common.network.Selector >

[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=16048615#comment-16048615 ] huxihx commented on KAFKA-5432: --- I might not see rolling new log segment as an indicator of the cause. Is

Build failed in Jenkins: kafka-trunk-jdk8 #1701

See Changes: [jason] KAFKA-5438; Fix UnsupportedOperationException in WriteTxnMarkersRequest [me] MINOR: Add unit tests for PluginDesc in Connect. -- [...truncated 4.21

[jira] [Created] (KAFKA-5444) Producer.send() will hang 8 hours,

Hongyuan Li created KAFKA-5444: -- Summary: Producer.send() will hang 8 hours, Key: KAFKA-5444 URL: https://issues.apache.org/jira/browse/KAFKA-5444 Project: Kafka Issue Type: Bug

[jira] [Updated] (KAFKA-5444) Producer.send() will hang 8+ hours

[ https://issues.apache.org/jira/browse/KAFKA-5444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hongyuan Li updated KAFKA-5444: --- Summary: Producer.send() will hang 8+ hours (was: Producer.send() will hang 8 hours, ) >

[GitHub] kafka pull request #3331: KAFKA-5443: Consumer should use last offset from b...

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/3331 KAFKA-5443: Consumer should use last offset from batch to set next fetch offset You can merge this pull request into a Git repository by running: $ git pull

[jira] [Commented] (KAFKA-5443) Consumer should use last offset from batch to set next fetch offset

[ https://issues.apache.org/jira/browse/KAFKA-5443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048688#comment-16048688 ] ASF GitHub Bot commented on KAFKA-5443: --- GitHub user hachikuji opened a pull request:

[jira] [Updated] (KAFKA-5444) Producer.send() will hang 8+ hours

[ https://issues.apache.org/jira/browse/KAFKA-5444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hongyuan Li updated KAFKA-5444: --- Description: Frequent kafka old Producer open and close with cause the server hang with lots of

[GitHub] kafka pull request #3330: MINOR: Javadoc for ExtendedSerializer and Extended...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3330 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Commented] (KAFKA-5245) KStream builder should capture serdes

[ https://issues.apache.org/jira/browse/KAFKA-5245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048738#comment-16048738 ] Evgeny Veretennikov commented on KAFKA-5245: There are actually a lot of KStream methods, that

[jira] [Commented] (KAFKA-5444) Producer.send() will hang 8+ hours

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

[jira] [Comment Edited] (KAFKA-5444) Producer.send() will hang 8+ hours

[ https://issues.apache.org/jira/browse/KAFKA-5444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048709#comment-16048709 ] Hongyuan Li edited comment on KAFKA-5444 at 6/14/17 4:58 AM: - [~huxi_2b] May

[jira] [Comment Edited] (KAFKA-5348) kafka-consumer-groups.sh refuses to remove groups without ids

[ https://issues.apache.org/jira/browse/KAFKA-5348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048486#comment-16048486 ] Vahid Hashemian edited comment on KAFKA-5348 at 6/13/17 10:36 PM: --

[jira] [Work started] (KAFKA-5442) Streams producer `client.id` are not unique for EOS

[ https://issues.apache.org/jira/browse/KAFKA-5442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-5442 started by Matthias J. Sax. -- > Streams producer `client.id` are not unique for EOS >

[jira] [Updated] (KAFKA-5442) Streams producer `client.id` are not unique for EOS

[ https://issues.apache.org/jira/browse/KAFKA-5442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-5442: --- Status: Patch Available (was: In Progress) > Streams producer `client.id` are not unique for

[jira] [Commented] (KAFKA-5442) Streams producer `client.id` are not unique for EOS

[ https://issues.apache.org/jira/browse/KAFKA-5442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048509#comment-16048509 ] ASF GitHub Bot commented on KAFKA-5442: --- GitHub user mjsax opened a pull request:

[jira] [Resolved] (KAFKA-5317) Update KIP-98 to reflect changes during implementation.

[ https://issues.apache.org/jira/browse/KAFKA-5317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta resolved KAFKA-5317. - Resolution: Fixed > Update KIP-98 to reflect changes during implementation. >

[GitHub] kafka pull request #3326: MINOR: Add unit tests for PluginDesc in Connect.

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3326 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Updated] (KAFKA-5413) Log cleaner fails due to large offset in segment file

[ https://issues.apache.org/jira/browse/KAFKA-5413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5413: --- Fix Version/s: 0.11.0.1 > Log cleaner fails due to large offset in segment file >

[jira] [Updated] (KAFKA-5214) Re-add KafkaAdminClient#apiVersions

[ https://issues.apache.org/jira/browse/KAFKA-5214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5214: --- Summary: Re-add KafkaAdminClient#apiVersions (was: KafkaAdminClient#apiVersions should return a

[GitHub] kafka pull request #3324: Temporarily remove the apiVersions API for 0.11

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3324 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Updated] (KAFKA-5435) Produce state lost if no snapshot retained

[ https://issues.apache.org/jira/browse/KAFKA-5435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5435: --- Status: Patch Available (was: Open) > Produce state lost if no snapshot retained >

[jira] [Updated] (KAFKA-5214) Re-add KafkaAdminClient#apiVersions

[ https://issues.apache.org/jira/browse/KAFKA-5214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5214: --- Description: We removed KafkaAdminClient#apiVersions just before 0.11.0.0 to give us a bit more time

[GitHub] kafka pull request #3327: HOTFIX: Introduce max wait time for retry-and-back...

GitHub user mjsax opened a pull request: https://github.com/apache/kafka/pull/3327 HOTFIX: Introduce max wait time for retry-and-backoff while creating tasks You can merge this pull request into a Git repository by running: $ git pull https://github.com/mjsax/kafka

[GitHub] kafka pull request #3329: KAFKA-5442: Streams producer client.id are not uni...

GitHub user mjsax opened a pull request: https://github.com/apache/kafka/pull/3329 KAFKA-5442: Streams producer client.id are not unique for EOS You can merge this pull request into a Git repository by running: $ git pull https://github.com/mjsax/kafka

[jira] [Commented] (KAFKA-5317) Update KIP-98 to reflect changes during implementation.

[ https://issues.apache.org/jira/browse/KAFKA-5317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048515#comment-16048515 ] Apurva Mehta commented on KAFKA-5317: - I updated both the wiki and the google doc to reflect the

[jira] [Assigned] (KAFKA-5020) Update protocol documentation to mention message format v2

[ https://issues.apache.org/jira/browse/KAFKA-5020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta reassigned KAFKA-5020: --- Assignee: Apurva Mehta > Update protocol documentation to mention message format v2 >

[jira] [Commented] (KAFKA-764) Race Condition in Broker Registration after ZooKeeper disconnect

[ https://issues.apache.org/jira/browse/KAFKA-764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048552#comment-16048552 ] Robert P. Thille commented on KAFKA-764: I believe we saw this issue, or something very similar.

[jira] [Created] (KAFKA-5441) Fix transaction marker grouping by producerId in TC

Jason Gustafson created KAFKA-5441: -- Summary: Fix transaction marker grouping by producerId in TC Key: KAFKA-5441 URL: https://issues.apache.org/jira/browse/KAFKA-5441 Project: Kafka Issue

[GitHub] kafka pull request #3328: HOTFIX: log level should be ERROR for conflicting ...

GitHub user mjsax opened a pull request: https://github.com/apache/kafka/pull/3328 HOTFIX: log level should be ERROR for conflicting metric names You can merge this pull request into a Git repository by running: $ git pull https://github.com/mjsax/kafka hotfix-app-info-log

[jira] [Commented] (KAFKA-5438) UnsupportedOperationException in WriteTxnMarkers handler

[ https://issues.apache.org/jira/browse/KAFKA-5438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048514#comment-16048514 ] ASF GitHub Bot commented on KAFKA-5438: --- Github user asfgit closed the pull request at:

  1   2   >