[jira] [Work started] (KAFKA-5210) Application Reset Tool does not need to seek for internal topics

[ https://issues.apache.org/jira/browse/KAFKA-5210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-5210 started by Bharat Viswanadham. - > Application Reset Tool does not need to seek for internal topics >

[jira] [Assigned] (KAFKA-5210) Application Reset Tool does not need to seek for internal topics

[ https://issues.apache.org/jira/browse/KAFKA-5210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham reassigned KAFKA-5210: - Assignee: Bharat Viswanadham > Application Reset Tool does not need to seek for

[jira] [Commented] (KAFKA-5210) Application Reset Tool does not need to seek for internal topics

[ https://issues.apache.org/jira/browse/KAFKA-5210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16004085#comment-16004085 ] Bharat Viswanadham commented on KAFKA-5210: --- [~mjsax] I will contribute the changes for this

[jira] [Updated] (KAFKA-5210) Application Reset Tool does not need to seek for internal topics

[ https://issues.apache.org/jira/browse/KAFKA-5210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-5210: --- Labels: beginner newbie (was: ) > Application Reset Tool does not need to seek for internal

[jira] [Created] (KAFKA-5210) Application Reset Tool does not need to seek for internal topics

Matthias J. Sax created KAFKA-5210: -- Summary: Application Reset Tool does not need to seek for internal topics Key: KAFKA-5210 URL: https://issues.apache.org/jira/browse/KAFKA-5210 Project: Kafka

Re: [VOTE] KIP-146: Isolation of dependencies and classes in Kafka Connect (restarted voting thread)

+1 On Tue, May 9, 2017 at 9:43 PM, dan wrote: > +1 (non binding) > > thanks Konstantine :thumbsup: > > On Mon, May 8, 2017 at 3:24 PM, Guozhang Wang wrote: > > > +1 > > > > On Mon, May 8, 2017 at 1:36 PM, Stephane Maarek < > >

Re: [VOTE] KIP-146: Isolation of dependencies and classes in Kafka Connect (restarted voting thread)

+1 (non binding) thanks Konstantine :thumbsup: On Mon, May 8, 2017 at 3:24 PM, Guozhang Wang wrote: > +1 > > On Mon, May 8, 2017 at 1:36 PM, Stephane Maarek < > steph...@simplemachines.com.au> wrote: > > > +1 > > Thanks heaps I can’t wait! > > > > > > On 9/5/17, 4:48 am,

Re: [DISCUSS] KIP-155 Add range scan for windowed state stores

Thanks, the KIP sounds good to me. There is no implementation proposal in the JIRA / KIP yet, would you like you drive the implementation also? Guozhang On Tue, May 9, 2017 at 8:29 AM, Xavier Léauté wrote: > I updated the KIP to reflect Michal's comment. Unless there are

Re: [VOTE] KIP-156 Add option "dry run" to Streams application reset tool

+1 On Tue, May 9, 2017 at 3:41 PM BigData dev wrote: > Hi, Everyone, > > Since this is a relatively simple change, I would like to start the voting > process for KIP-156: Add option "dry run" to Streams application reset tool > >

Re: [DISCUSS] KIP-143: Controller Health Metrics

@Ismael, Jun After bringing up an earlier point twice now, it still doesn't feel like it's been commented on/addressed, so I'm going to give it one more shot: Assuming that ControllerState should reflect the current event being processed, the KIP is missing states. The controller currently has 14

Re: [VOTE] KIP-156 Add option "dry run" to Streams application reset tool

+1 On Tue, May 9, 2017 at 8:53 PM, Matthias J. Sax wrote: > +1 > > -Matthias > > On 5/9/17 2:58 PM, BigData dev wrote: > > Eno, > > Got info from the JIRA all tools and their parameters are public API. > > So, I have started voting for this KIP. > > > > Thanks, > > Bharat

Re: [VOTE] KIP-156 Add option "dry run" to Streams application reset tool

+1 -Matthias On 5/9/17 2:58 PM, BigData dev wrote: > Eno, > Got info from the JIRA all tools and their parameters are public API. > So, I have started voting for this KIP. > > Thanks, > Bharat > > On Tue, May 9, 2017 at 1:09 PM, Eno Thereska wrote: > >> +1 for me. I’m

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

See Changes: [wangguoz] KAFKA-4927: Fix KStreamsTestDriver to not throw NPE when KStream.to() [wangguoz] KAFKA-5063: Fix flaky o.a.k.streams.integration.ResetIntegrationTest

Re: [DISCUSS] KIP-143: Controller Health Metrics

Becket, Are you OK with extending the metrics via a subsequent KIP (assuming that what we're doing here doesn't prevent that)? The KIP freeze is tomorrow (although I will give it an extra day or two as many in the community have been attending the Kafka Summit this week), so we should avoid

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

See Changes: [jason] HOTFIX: Increase kafkatest startup wait time on ConnectDistributed -- [...truncated 1.67 MB...] kafka.integration.SaslPlaintextTopicMetadataTest >

Re: [DISCUSS] KIP-143: Controller Health Metrics

Hi, Becket, q10. The reason why there is not a timer metric for broker change event is that the controller currently always has a LeaderElectionRateAndTimeMs timer metric (in ControllerStats). q11. I agree that that it's useful to know the queue time in the controller event queue and suggested

Jenkins build is back to normal : kafka-trunk-jdk7 #2161

See

[jira] [Comment Edited] (KAFKA-5149) New producer hardcodes key and value serializers to ByteArray

[ https://issues.apache.org/jira/browse/KAFKA-5149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16003649#comment-16003649 ] Bharat Viswanadham edited comment on KAFKA-5149 at 5/9/17 10:12 PM:

[jira] [Resolved] (KAFKA-5149) New producer hardcodes key and value serializers to ByteArray

[ https://issues.apache.org/jira/browse/KAFKA-5149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham resolved KAFKA-5149. --- Resolution: Duplicate Closing this Jira as a duplicate of KAFKA-2526 > New producer

Re: [VOTE] KIP-156 Add option "dry run" to Streams application reset tool

Eno, Got info from the JIRA all tools and their parameters are public API. So, I have started voting for this KIP. Thanks, Bharat On Tue, May 9, 2017 at 1:09 PM, Eno Thereska wrote: > +1 for me. I’m not sure we even need a KIP for this but it’s better to be > safe I

Build failed in Jenkins: kafka-0.10.2-jdk7 #153

See Changes: [jason] HOTFIX: Increase kafkatest startup wait time on ConnectDistributed -- [...truncated 53.72 KB...] kafka.api.PlaintextConsumerTest >

[jira] [Resolved] (KAFKA-5208) Transient failure: kafka.api.SaslScramSslEndToEndAuthorizationTest.testNoConsumeWithDescribeAclViaSubscribe

[ https://issues.apache.org/jira/browse/KAFKA-5208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-5208. Resolution: Duplicate Duplicate of KAFKA-5173. > Transient failure: >

[jira] [Commented] (KAFKA-5063) Flaky ResetIntegrationTest.testReprocessingFromScratchAfterResetWithIntermediateUserTopic

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

Re: [VOTE] KIP-140: Add administrative RPCs for adding, deleting, and listing ACLs

On Tue, May 9, 2017, at 08:00, Ismael Juma wrote: > Hi Colin, > > I took another look and have a couple of comments: > > 1. DescribeAclsResponse only has an error code at the top level. In the > DescribeConfigs KIP, you suggested that we should have an error code at > the > batch level. Doesn't

[GitHub] kafka pull request #2931: KAFKA-5063: Flaky ResetIntegrationTest

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2931 --- 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-5063) Flaky ResetIntegrationTest.testReprocessingFromScratchAfterResetWithIntermediateUserTopic

[ https://issues.apache.org/jira/browse/KAFKA-5063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-5063: - Resolution: Fixed Fix Version/s: 0.11.0.0 Status: Resolved (was: Patch

[jira] [Created] (KAFKA-5209) Transient failure: kafka.server.MetadataRequestTest.testControllerId

Guozhang Wang created KAFKA-5209: Summary: Transient failure: kafka.server.MetadataRequestTest.testControllerId Key: KAFKA-5209 URL: https://issues.apache.org/jira/browse/KAFKA-5209 Project: Kafka

[jira] [Resolved] (KAFKA-4927) KStreamsTestDriver fails with NPE when KStream.to() sinks are used

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

[jira] [Commented] (KAFKA-4927) KStreamsTestDriver fails with NPE when KStream.to() sinks are used

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

[GitHub] kafka pull request #2716: KAFKA-4927 : KStreamsTestDriver fails with NPE whe...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2716 --- 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] [Created] (KAFKA-5208) Transient failure: kafka.api.SaslScramSslEndToEndAuthorizationTest.testNoConsumeWithDescribeAclViaSubscribe

Guozhang Wang created KAFKA-5208: Summary: Transient failure: kafka.api.SaslScramSslEndToEndAuthorizationTest.testNoConsumeWithDescribeAclViaSubscribe Key: KAFKA-5208 URL:

[GitHub] kafka pull request #3007: HOTFIX: Increase kafkatest startup wait time on Co...

Github user kkonstantine closed the pull request at: https://github.com/apache/kafka/pull/3007 --- 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

[GitHub] kafka pull request #3007: HOTFIX: Increase kafkatest startup wait time on Co...

GitHub user kkonstantine opened a pull request: https://github.com/apache/kafka/pull/3007 HOTFIX: Increase kafkatest startup wait time on ConnectDistributed service in 0.10.2 You can merge this pull request into a Git repository by running: $ git pull

[jira] [Resolved] (KAFKA-5207) Addition of a way to manually revoke individual partitions from a consumer

[ https://issues.apache.org/jira/browse/KAFKA-5207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Farmer resolved KAFKA-5207. Resolution: Fixed Heh, it was pointed out to me that assignment is an overwrite operation, not a

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

See Changes: [wangguoz] KAFKA-5126: Implement KIP-98 transactional methods in the MockProducer -- [...truncated 854.41 KB...]

[GitHub] kafka pull request #3006: HOTFIX: Increase kafkatest startup wait time on Co...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3006 --- 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] [Created] (KAFKA-5207) Addition of a way to manually revoke individual partitions from a consumer

Matt Farmer created KAFKA-5207: -- Summary: Addition of a way to manually revoke individual partitions from a consumer Key: KAFKA-5207 URL: https://issues.apache.org/jira/browse/KAFKA-5207 Project: Kafka

[GitHub] kafka pull request #3006: HOTFIX: Increase kafkatest startup wait time on Co...

GitHub user kkonstantine opened a pull request: https://github.com/apache/kafka/pull/3006 HOTFIX: Increase kafkatest startup wait time on ConnectDistributed service You can merge this pull request into a Git repository by running: $ git pull

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

See Changes: [wangguoz] KAFKA-4222: Adjust timeout in low resource environments -- [...truncated 2.47 MB...]

Re: [VOTE] KIP-156 Add option "dry run" to Streams application reset tool

+1 for me. I’m not sure we even need a KIP for this but it’s better to be safe I guess. Eno > On May 9, 2017, at 8:41 PM, BigData dev wrote: > > Hi, Everyone, > > Since this is a relatively simple change, I would like to start the voting > process for KIP-156: Add

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

See

[jira] [Commented] (KAFKA-4743) Add a tool to Reset Consumer Group Offsets

[ https://issues.apache.org/jira/browse/KAFKA-4743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16003394#comment-16003394 ] Jorge Quilcate commented on KAFKA-4743: --- Hi [~guozhang], I'm using the current operations from

[VOTE] KIP-156 Add option "dry run" to Streams application reset tool

Hi, Everyone, Since this is a relatively simple change, I would like to start the voting process for KIP-156: Add option "dry run" to Streams application reset tool https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=69410150 The vote will run for a minimum of 72 hours. Thanks,

[GitHub] kafka pull request #3005: Add option "dry run" to Streams application reset ...

GitHub user bharatviswa504 opened a pull request: https://github.com/apache/kafka/pull/3005 Add option "dry run" to Streams application reset tool Addressed the below review comment from #PR #2998 I am wondering if it would be better, to "embed" the dry-run into the

[jira] [Commented] (KAFKA-5166) Add option "dry run" to Streams application reset tool

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

[GitHub] kafka pull request #2998: KAFKA-5166: Add option dry run to Streams applicat...

Github user bharatviswa504 closed the pull request at: https://github.com/apache/kafka/pull/2998 --- 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

[jira] [Commented] (KAFKA-4982) Add listener tag to socket-server-metrics.connection-... metrics

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

[GitHub] kafka pull request #3004: KAFKA-4982: add protocol and listener tags to sock...

GitHub user edoardocomar opened a pull request: https://github.com/apache/kafka/pull/3004 KAFKA-4982: add protocol and listener tags to socket-server-metrics Added tags You can merge this pull request into a Git repository by running: $ git pull

Re: [VOTE] KIP-153 (separating replication traffic from BytesOutPerSec metric)

+1 (non-binding) On Tue, May 9, 2017 at 11:00 AM Dong Lin wrote: > +1 > > On Sun, May 7, 2017 at 7:40 PM, Jun Rao wrote: > > > Hi, Everyone, > > > > Since this is a relatively simple change, I would like to start the > voting > > process for KIP-153 :

[jira] [Commented] (KAFKA-5206) RocksDBSessionStore doesn't use default aggSerde.

[ https://issues.apache.org/jira/browse/KAFKA-5206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16003248#comment-16003248 ] Kyle Winkelman commented on KAFKA-5206: --- I have already made a PR but originally named it minor. I

[jira] [Created] (KAFKA-5206) RocksDBSessionStore doesn't use default aggSerde.

Kyle Winkelman created KAFKA-5206: - Summary: RocksDBSessionStore doesn't use default aggSerde. Key: KAFKA-5206 URL: https://issues.apache.org/jira/browse/KAFKA-5206 Project: Kafka Issue

[jira] [Commented] (KAFKA-5205) CachingSessionStore doesn't use the default keySerde.

[ https://issues.apache.org/jira/browse/KAFKA-5205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16003245#comment-16003245 ] Kyle Winkelman commented on KAFKA-5205: --- I have already made a PR but originally named it minor. I

[jira] [Created] (KAFKA-5205) CachingSessionStore doesn't use the default keySerde.

Kyle Winkelman created KAFKA-5205: - Summary: CachingSessionStore doesn't use the default keySerde. Key: KAFKA-5205 URL: https://issues.apache.org/jira/browse/KAFKA-5205 Project: Kafka Issue

Re: [VOTE] KIP-153 (separating replication traffic from BytesOutPerSec metric)

+1 On Sun, May 7, 2017 at 7:40 PM, Jun Rao wrote: > Hi, Everyone, > > Since this is a relatively simple change, I would like to start the voting > process for KIP-153 : Include only client traffic in BytesOutPerSec metric. > >

Re: [VOTE] KIP-153 (separating replication traffic from BytesOutPerSec metric)

+1 On Tue, May 9, 2017 at 3:06 AM, Rajini Sivaram wrote: > Hi Jun, Thank you for the KIP. > > +1 (binding) > > On Mon, May 8, 2017 at 6:23 PM, Guozhang Wang wrote: > > > +1 > > > > On Mon, May 8, 2017 at 2:25 PM, Joel Koshy

Re: [DISCUSS]: KIP-149: Enabling key access in ValueTransformer, ValueMapper, and ValueJoiner

If `ValueMapperWithKey` extends `ValueMapper` we don't need the new overlaod. And yes, we need to do one check -- but this happens when building the topology. At runtime (I mean after KafkaStream#start() we don't need any check as we will always use `ValueMapperWithKey`) -Matthias On 5/9/17

[jira] [Created] (KAFKA-5204) Connect needs to validate Connector type during instantiation

Konstantine Karantasis created KAFKA-5204: - Summary: Connect needs to validate Connector type during instantiation Key: KAFKA-5204 URL: https://issues.apache.org/jira/browse/KAFKA-5204

[jira] [Updated] (KAFKA-5126) Implement KIP-98 transactional methods in the MockProducer

[ https://issues.apache.org/jira/browse/KAFKA-5126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-5126: - Resolution: Fixed Fix Version/s: 0.11.0.0 Status: Resolved (was: Patch

[GitHub] kafka pull request #2951: KAFKA-5126: Implement KIP-98 transactional methods...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2951 --- 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-5126) Implement KIP-98 transactional methods in the MockProducer

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

[jira] [Updated] (KAFKA-5202) Handle topic deletion for ongoing transactions

[ https://issues.apache.org/jira/browse/KAFKA-5202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-5202: --- Description: If a topic is deleted, we should remove its partitions from ongoing

[jira] [Commented] (KAFKA-4222) Transient failure in QueryableStateIntegrationTest.queryOnRebalance

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

[GitHub] kafka pull request #2996: KAFKA-4222: Adjust timeout in low resource environ...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2996 --- 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-4222) Transient failure in QueryableStateIntegrationTest.queryOnRebalance

[ https://issues.apache.org/jira/browse/KAFKA-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-4222. -- Resolution: Fixed Issue resolved by pull request 2996

[jira] [Commented] (KAFKA-5201) Compacted topic could be misused to fill up a disk but deletion policy can't retain legitimate keys

[ https://issues.apache.org/jira/browse/KAFKA-5201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16002885#comment-16002885 ] Edoardo Comar commented on KAFKA-5201: -- Thanks [~mihbor] Sure there is no concept of legitimate vs

[jira] [Resolved] (KAFKA-5201) Compacted topic could be misused to fill up a disk but deletion policy can't retain legitimate keys

[ https://issues.apache.org/jira/browse/KAFKA-5201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edoardo Comar resolved KAFKA-5201. -- Resolution: Not A Problem > Compacted topic could be misused to fill up a disk but deletion

Re: [DISCUSS] KIP-155 Add range scan for windowed state stores

I updated the KIP to reflect Michal's comment. Unless there are any further comments, I will initiate a vote this evening. On Mon, May 8, 2017 at 11:01 AM Xavier Léauté wrote: > That sounds reasonable, Michal. Given the underlying implementation uses > the same segmented

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

Eno, is there anyone else that is an expert in the kafka streams realm that I should reach out to for input? I believe Damian Guy is still planning on reviewing this more in depth so I will wait for his inputs before continuing. On May 9, 2017 7:30 AM, "Eno Thereska"

Re: [VOTE] KIP-140: Add administrative RPCs for adding, deleting, and listing ACLs

Hi Colin, I took another look and have a couple of comments: 1. DescribeAclsResponse only has an error code at the top level. In the DescribeConfigs KIP, you suggested that we should have an error code at the batch level. Doesn't that apply here too? 2. CreateAclsResponse don't include the

[jira] [Commented] (KAFKA-3103) Transient Failure in kafka.integration.PlaintextTopicMetadataTest.testIsrAfterBrokerShutDownAndJoinsBack

[ https://issues.apache.org/jira/browse/KAFKA-3103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16002790#comment-16002790 ] Ivan A. Melnikov commented on KAFKA-3103: - Looks like it's still happening

[jira] [Commented] (KAFKA-4273) Streams DSL - Add TTL / retention period support for intermediate topics and state stores

[ https://issues.apache.org/jira/browse/KAFKA-4273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16002747#comment-16002747 ] Vinoth Rajasekar commented on KAFKA-4273: - we have a use case where we need to do a distinct count

[jira] [Commented] (KAFKA-5194) KIP-153 : Include only client traffic in BytesOutPerSec metric

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

[GitHub] kafka pull request #3003: KAFKA-5194: KIP-153: Include only client traffic i...

GitHub user mimaison opened a pull request: https://github.com/apache/kafka/pull/3003 KAFKA-5194: KIP-153: Include only client traffic in BytesOutPerSec me… …tric Also added 2 new metrics to account for incoming/outgoing traffic due to internal replication -

GlobalKTable not checkpointing offsets but reusing store

I'm experimenting with a streams application that does a KStream- GlobalKTable join, and I'm seeing some unexpected behavior when re- running the application. First, it does not appear that the offsets in the topic backing the GlobalKTable are being checkpointed to a file as I expected. This

[jira] [Commented] (KAFKA-5203) Percentilles are calculated incorrectly

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

[GitHub] kafka pull request #3002: KAFKA-5203: Metrics: fix resetting of histogram sa...

GitHub user iv-m opened a pull request: https://github.com/apache/kafka/pull/3002 KAFKA-5203: Metrics: fix resetting of histogram sample Without the histogram cleanup, the percentiles are calculated incorrectly after purging of one or more samples: event counts go out of

[jira] [Commented] (KAFKA-5203) Percentilles are calculated incorrectly

[ https://issues.apache.org/jira/browse/KAFKA-5203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16002583#comment-16002583 ] Ivan A. Melnikov commented on KAFKA-5203: - I actually have a fix for this issue. I'll create a

[jira] [Created] (KAFKA-5203) Percentilles are calculated incorrectly

Ivan A. Melnikov created KAFKA-5203: --- Summary: Percentilles are calculated incorrectly Key: KAFKA-5203 URL: https://issues.apache.org/jira/browse/KAFKA-5203 Project: Kafka Issue Type: Bug

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

Thanks Kyle, good arguments. Eno > On May 7, 2017, at 5:06 PM, Kyle Winkelman wrote: > > *- minor: could you add an exact example (similar to what Jay’s example is, > or like your Spark/Pig pointers had) to make this super concrete?* > I have added a more concrete

[jira] [Commented] (KAFKA-3502) Build is killed during kafka streams tests due to `pure virtual method called` error

[ https://issues.apache.org/jira/browse/KAFKA-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16002510#comment-16002510 ] Eno Thereska commented on KAFKA-3502: - This issue happens more in environments with restricted

[jira] [Commented] (KAFKA-5154) Kafka Streams throws NPE during rebalance

[ https://issues.apache.org/jira/browse/KAFKA-5154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16002457#comment-16002457 ] Lukas Gemela commented on KAFKA-5154: - today we reproduced the issue on two of our nodes, hope it

Re: [DISCUSS]: KIP-149: Enabling key access in ValueTransformer, ValueMapper, and ValueJoiner

One correction: and in runtime (inside processor) we still have to check it is ValueMapper > or ValueMapperWithKey before wrapping it into the rich function. this will be in compile time in API level. Cheers, Jeyhun On Tue, May 9, 2017 at 11:55 AM Jeyhun Karimov

Re: [VOTE] KIP-136: Add Listener name and Security Protocol name to SelectorMetrics tags

Hi Edo, Thank you for the KIP. +1 (binding) On Fri, May 5, 2017 at 9:05 PM, Gwen Shapira wrote: > +1 > > On Fri, May 5, 2017 at 1:26 PM, Edoardo Comar wrote: > > > Hi, > > I'd like to start the vote on this simple KIP : > >

Re: [VOTE] KIP-153 (separating replication traffic from BytesOutPerSec metric)

Hi Jun, Thank you for the KIP. +1 (binding) On Mon, May 8, 2017 at 6:23 PM, Guozhang Wang wrote: > +1 > > On Mon, May 8, 2017 at 2:25 PM, Joel Koshy wrote: > > > +1 > > > > On Mon, May 8, 2017 at 8:30 AM, Roger Hoover > >

Re: [DISCUSS]: KIP-149: Enabling key access in ValueTransformer, ValueMapper, and ValueJoiner

Hi, Thanks for feedback. Then we need to overload method KStream mapValues(ValueMapper mapper); with KStream mapValues(ValueMapperWithKey mapper); and in runtime (inside processor) we still have to check it is ValueMapper or ValueMapperWithKey before wrapping it into the rich

Re: [DISCUSS]: KIP-149: Enabling key access in ValueTransformer, ValueMapper, and ValueJoiner

+1 :) On 08/05/17 23:52, Matthias J. Sax wrote: Hi, I was reading the updated KIP and I am wondering, if we should do the design a little different. Instead of distinguishing between a RichFunction and non-RichFunction at runtime level, we would use RichFunctions all the time. Thus, on the

[jira] [Commented] (KAFKA-5201) Compacted topic could be misused to fill up a disk but deletion policy can't retain legitimate keys

[ https://issues.apache.org/jira/browse/KAFKA-5201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16002311#comment-16002311 ] Michal Borowiecki commented on KAFKA-5201: -- Hi Edoardo, >From the broker's perspective there is

[jira] [Commented] (KAFKA-5070) org.apache.kafka.streams.errors.LockException: task [0_18] Failed to lock the state directory: /opt/rocksdb/pulse10/0_18

[ https://issues.apache.org/jira/browse/KAFKA-5070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16002228#comment-16002228 ] Matthias J. Sax commented on KAFKA-5070: Digging a little further, it seems the first severe error

Re: [VOTE] KIP-133: List and Alter Configs Admin APIs (second attempt)

+1 (non-binding) James > On May 8, 2017, at 12:01 AM, Ismael Juma wrote: > > [Seems like the original message ended up in the discuss thread in GMail, > so trying again] > > Hi everyone, > > I believe I addressed the comments in the discussion thread and given the >

[jira] [Updated] (KAFKA-5191) Autogenerate Consumer Fetcher metrics

[ https://issues.apache.org/jira/browse/KAFKA-5191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Cheng updated KAFKA-5191: --- Attachment: generated_fetcher_docs_with_alternate_css.png See file

[jira] [Commented] (KAFKA-5070) org.apache.kafka.streams.errors.LockException: task [0_18] Failed to lock the state directory: /opt/rocksdb/pulse10/0_18

[ https://issues.apache.org/jira/browse/KAFKA-5070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16002190#comment-16002190 ] Matthias J. Sax commented on KAFKA-5070: [~dnagarajan], [~shoyebpathan] I did have a look into the

[jira] [Comment Edited] (KAFKA-5191) Autogenerate Consumer Fetcher metrics

[ https://issues.apache.org/jira/browse/KAFKA-5191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16002183#comment-16002183 ] James Cheng edited comment on KAFKA-5191 at 5/9/17 7:05 AM: See file

[jira] [Updated] (KAFKA-5191) Autogenerate Consumer Fetcher metrics

[ https://issues.apache.org/jira/browse/KAFKA-5191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Cheng updated KAFKA-5191: --- Attachment: generated_fetcher_docs_with_css.png Here is what the table looks like with the kafka-site

答复: Kafka 0.9.0.1 Direct Memory OOM

Could you set -XX:MaxDirectMemorySize to a larger value and retry? 发件人: JsonTu 发送时间: 2017年5月9日 14:38 收件人: us...@kafka.apache.org; dev@kafka.apache.org; wangg...@gmail.com; becket@gmail.com 主题: Kafka 0.9.0.1 Direct Memory OOM Hi All, We

[jira] [Created] (KAFKA-5202) Handle topic deletion for ongoing transactions

Jason Gustafson created KAFKA-5202: -- Summary: Handle topic deletion for ongoing transactions Key: KAFKA-5202 URL: https://issues.apache.org/jira/browse/KAFKA-5202 Project: Kafka Issue Type:

Kafka 0.9.0.1 Direct Memory OOM

Hi All, We have a cluster with 6 nodes. we have meet a direct buffer memory OOM in our prod enviroment. Default config of Kafka’s JVM is used in our cluster. some error is like below, java.lang.OutOfMemoryError: Direct buffer memory at java.nio.Bits.reserveMemory(Bits.java:658)

[jira] [Commented] (KAFKA-5167) streams task gets stuck after re-balance due to LockException

[ https://issues.apache.org/jira/browse/KAFKA-5167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16002152#comment-16002152 ] Matthias J. Sax commented on KAFKA-5167: [~Narendra Kumar] Sorry. Did miss you last reply (did not

[jira] [Commented] (KAFKA-5167) streams task gets stuck after re-balance due to LockException

[ https://issues.apache.org/jira/browse/KAFKA-5167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16002128#comment-16002128 ] Matthias J. Sax commented on KAFKA-5167: It seems that this issues does not affect current

[jira] [Updated] (KAFKA-5167) streams task gets stuck after re-balance due to LockException

[ https://issues.apache.org/jira/browse/KAFKA-5167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-5167: --- Affects Version/s: 0.10.2.1 Status: Patch Available (was: In Progress) >

[jira] [Comment Edited] (KAFKA-5200) Deleting topic when one broker is down will prevent topic to be re-creatable

[ https://issues.apache.org/jira/browse/KAFKA-5200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16002107#comment-16002107 ] huxi edited comment on KAFKA-5200 at 5/9/17 6:15 AM: - Could add a parameter for

  1   2   >