[jira] [Commented] (KAFKA-5337) Partition assignment strategy that distributes lag evenly across consumers in each group

[ https://issues.apache.org/jira/browse/KAFKA-5337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16027266#comment-16027266 ] Grant Neale commented on KAFKA-5337: PR raised: https://github.com/apache/kafka/pull/3158 > Partition

[jira] [Commented] (KAFKA-5337) Partition assignment strategy that distributes lag evenly across consumers in each group

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

[GitHub] kafka pull request #3158: KAFKA-5337: LagBasedAssignor partition assignment ...

GitHub user grantneale opened a pull request: https://github.com/apache/kafka/pull/3158 KAFKA-5337: LagBasedAssignor partition assignment strategy Existing partition assignment strategies (RangeAssignor and RoundRobinAssignor) do not account for the current consumer group lag on

[jira] [Updated] (KAFKA-5319) Add a tool to make cluster replica and leader balance

[ https://issues.apache.org/jira/browse/KAFKA-5319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ma Tianchi updated KAFKA-5319: -- Attachment: (was: AlgorithmDescription.png) > Add a tool to make cluster replica and leader balance

[jira] [Commented] (KAFKA-5337) Partition assignment strategy that distributes lag evenly across consumers in each group

[ https://issues.apache.org/jira/browse/KAFKA-5337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16027211#comment-16027211 ] Grant Neale commented on KAFKA-5337: Currently working on this and intend to raise a PR soon.

[jira] [Updated] (KAFKA-5337) Partition assignment strategy that distributes lag evenly across consumers in each group

[ https://issues.apache.org/jira/browse/KAFKA-5337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Neale updated KAFKA-5337: --- Description: Existing partition assignment strategies (RangeAssignor and RoundRobinAssignor) do not

[jira] [Updated] (KAFKA-5337) Partition assignment strategy that distributes lag evenly across consumers in each group

[ https://issues.apache.org/jira/browse/KAFKA-5337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Neale updated KAFKA-5337: --- Description: Existing partition assignment strategies (Range Assignor and RoubdRobinAssignor) do not

[jira] [Created] (KAFKA-5337) Partition assignment strategy that distributes lag evenly across consumers in each group

Grant Neale created KAFKA-5337: -- Summary: Partition assignment strategy that distributes lag evenly across consumers in each group Key: KAFKA-5337 URL: https://issues.apache.org/jira/browse/KAFKA-5337

[jira] [Assigned] (KAFKA-5171) TC should not accept empty string transactional id

[ https://issues.apache.org/jira/browse/KAFKA-5171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Umesh Chaudhary reassigned KAFKA-5171: -- Assignee: Umesh Chaudhary > TC should not accept empty string transactional id >

[jira] [Commented] (KAFKA-5171) TC should not accept empty string transactional id

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

[GitHub] kafka pull request #2973: KAFKA-5171 : TC should not accept empty string tra...

Github user umesh9794 closed the pull request at: https://github.com/apache/kafka/pull/2973 --- 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-5332) When resize the index file, maybe caused the content disappear

[ https://issues.apache.org/jira/browse/KAFKA-5332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16027184#comment-16027184 ] xuzq commented on KAFKA-5332: - @ [~guozhang] Can you check this bug? Thank you. > When resize the index file,

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

See Changes: [wangguoz] KAFKA-4660; Improve test coverage KafkaStreams [wangguoz] KAFKA-5191: Autogenerate Consumer Fetcher metrics -- [...truncated 2.95 MB...]

Re: KIP-162: Enable topic deletion by default

Would it make sense to resolve KAFKA-4893 before enabling it by default, as fixing the ticket would likely involve changing the log directory structure? On Fri, May 26, 2017 at 3:24 PM, Guozhang Wang wrote: > I'd say just remove those two lines. > > On Fri, May 26, 2017 at

[jira] [Commented] (KAFKA-5328) consider switching json parser from scala to jackson

[ https://issues.apache.org/jira/browse/KAFKA-5328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16027086#comment-16027086 ] Onur Karaman commented on KAFKA-5328: - I copied the topic assignment znodes and partition state znodes

[jira] [Created] (KAFKA-5336) The required ACL permission for ListGroup is invalid

Vahid Hashemian created KAFKA-5336: -- Summary: The required ACL permission for ListGroup is invalid Key: KAFKA-5336 URL: https://issues.apache.org/jira/browse/KAFKA-5336 Project: Kafka Issue

[jira] [Commented] (KAFKA-5211) KafkaConsumer should not skip a corrupted record after throwing an exception.

[ https://issues.apache.org/jira/browse/KAFKA-5211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16026977#comment-16026977 ] Guozhang Wang commented on KAFKA-5211: -- For this specific issue, Streams should be independent of

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

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

[GitHub] kafka pull request #2993: KAFKA-5191: Autogenerate Consumer Fetcher metrics

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2993 --- 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-5191) Autogenerate Consumer Fetcher metrics

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

[jira] [Commented] (KAFKA-4660) Improve test coverage KafkaStreams

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

[GitHub] kafka pull request #3099: KAFKA-4660 : Improve test coverage KafkaStreams

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3099 --- 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-4660) Improve test coverage KafkaStreams

[ https://issues.apache.org/jira/browse/KAFKA-4660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-4660: - Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request

[jira] [Commented] (KAFKA-5333) Remove Broker ACL resource type

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

[GitHub] kafka pull request #3154: KAFKA-5333; Remove Broker ACL resource type

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3154 --- 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-5333) Remove Broker ACL resource type

[ https://issues.apache.org/jira/browse/KAFKA-5333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-5333: --- Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request 3154

Re: KIP-162: Enable topic deletion by default

I'd say just remove those two lines. On Fri, May 26, 2017 at 7:55 AM, Gwen Shapira wrote: > This was a discussion, not a vote (sorry for mangling the title), but > thanks for all the +1 anyway. > > Regarding Ismael's feedback: > The current server.properties includes the

[jira] [Updated] (KAFKA-5226) NullPointerException (NPE) in SourceNodeRecordDeserializer.deserialize

[ https://issues.apache.org/jira/browse/KAFKA-5226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Bejeck updated KAFKA-5226: --- Status: Patch Available (was: In Progress) > NullPointerException (NPE) in

[jira] [Commented] (KAFKA-5226) NullPointerException (NPE) in SourceNodeRecordDeserializer.deserialize

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

[GitHub] kafka pull request #3157: KAFKA-5226: Fixes issue where adding topics matchi...

GitHub user bbejeck opened a pull request: https://github.com/apache/kafka/pull/3157 KAFKA-5226: Fixes issue where adding topics matching a regex subscribed stream may not be detected by all followers until onJoinComplete returns. You can merge this pull request into a Git

Re: KIP-162: Enable topic deletion by default

> On May 26, 2017, at 1:10 PM, Vahid S Hashemian > wrote: > > Gwen, thanks for the KIP. > It looks good to me. > > Just a minor suggestion: It would be great if the command asks for a > confirmation (y/n) before deleting the topic (similar to how removing ACLs >

[jira] [Commented] (KAFKA-5031) Additional validation in validateMessagesAndAssignOffsets

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

[GitHub] kafka pull request #3156: KAFKA-5031: validate count of records for DefaultR...

GitHub user gosubpl opened a pull request: https://github.com/apache/kafka/pull/3156 KAFKA-5031: validate count of records for DefaultRecordBatch in validateMessagesAndAssignOffsets https://issues.apache.org/jira/browse/KAFKA-5031 Implements additional check for

[jira] [Commented] (KAFKA-5329) Replica list in the metadata cache on the broker may have different order from zookeeper

[ https://issues.apache.org/jira/browse/KAFKA-5329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16026753#comment-16026753 ] James Cheng commented on KAFKA-5329: I noticed this as well.

[GitHub] kafka-site pull request #56: Update commiter page to indicate that Gwen is a...

GitHub user wushujames opened a pull request: https://github.com/apache/kafka-site/pull/56 Update commiter page to indicate that Gwen is a PMC member. Would it be a conflict of interest for @gwenshap to approve this PR? :) You can merge this pull request into a Git repository by

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

See

[jira] [Commented] (KAFKA-3151) kafka-consumer-groups.sh fail with sasl enabled

[ https://issues.apache.org/jira/browse/KAFKA-3151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16026658#comment-16026658 ] Vahid Hashemian commented on KAFKA-3151: For this to work I had to also add the following line to

[jira] [Resolved] (KAFKA-5011) Replica fetchers may need to down-convert messages during a selective message format upgrade

[ https://issues.apache.org/jira/browse/KAFKA-5011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-5011. Resolution: Won't Fix According to Joel's comment, closing this for now. > Replica fetchers may need to

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

See Changes: [wangguoz] KAFKA-5309: Stores not queryable after one thread died -- [...truncated 904.93 KB...] kafka.log.BrokerCompressionTest >

[jira] [Commented] (KAFKA-5329) Replica list in the metadata cache on the broker may have different order from zookeeper

[ https://issues.apache.org/jira/browse/KAFKA-5329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16026532#comment-16026532 ] Jiangjie Qin commented on KAFKA-5329: - [~ijuma] The ControllerContext is fine. This ticket is not

[jira] [Created] (KAFKA-5335) Controller should batch updatePartitionReassignmentData() operation

Dong Lin created KAFKA-5335: --- Summary: Controller should batch updatePartitionReassignmentData() operation Key: KAFKA-5335 URL: https://issues.apache.org/jira/browse/KAFKA-5335 Project: Kafka

Re: KIP-162: Enable topic deletion by default

Gwen, thanks for the KIP. It looks good to me. Just a minor suggestion: It would be great if the command asks for a confirmation (y/n) before deleting the topic (similar to how removing ACLs works). Thanks. --Vahid From: Gwen Shapira To: "dev@kafka.apache.org"

[jira] [Commented] (KAFKA-5128) TransactionCoordinator - Check inter broker protocol and message format and raise errors if incompatible

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

[GitHub] kafka pull request #3103: KAFKA-5128: check inter broker in transactional me...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3103 --- 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-5128) TransactionCoordinator - Check inter broker protocol and message format and raise errors if incompatible

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

[jira] [Commented] (KAFKA-5309) Stores not queryable after one thread died

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

[GitHub] kafka pull request #3140: KAFKA-5309: Stores not queryable after one thread ...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3140 --- 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-5309) Stores not queryable after one thread died

[ https://issues.apache.org/jira/browse/KAFKA-5309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-5309: - Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request

[jira] [Commented] (KAFKA-5322) Resolve AddPartitions response error code inconsistency

[ https://issues.apache.org/jira/browse/KAFKA-5322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16026481#comment-16026481 ] Guozhang Wang commented on KAFKA-5322: -- [~hachikuji] I'd prefer option 2, to still have a

Re: [DISCUSS]: KIP-161: streams record processing exception handlers

In that case, though, every access to that key is doomed to failure as the database is corrupted. So i think it should probably die in a steaming heap at that point! On Fri, 26 May 2017 at 17:33 Eno Thereska wrote: > Hi Damian, > > I was thinking of cases when there is

Re: [DISCUSS]: KIP-161: streams record processing exception handlers

Hi Damian, I was thinking of cases when there is bit-rot on the storage itself and we get a malformed record that cannot be de-serialized. There is an interesting intersection here with CRCs in both Kafka (already there, they throw on deserialization) and potentially local storage (we don't

[jira] [Commented] (KAFKA-1561) Data Loss for Incremented Replica Factor and Leader Election

[ https://issues.apache.org/jira/browse/KAFKA-1561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16026453#comment-16026453 ] Jun Rao commented on KAFKA-1561: Hmm, interesting. From the description, when the LEOs on the leader are

Kafka Loss of messages

Hi, I am experiencing loss of messages while scaling brokers up and down in kafka cluster. I came across this jira issue(link ). Can you confirm if this is actually an issue in kafka or can the problem be solved by changing some configuration

Re: [DISCUSS]: KIP-161: streams record processing exception handlers

Eno, Under what circumstances would you get a deserialization exception from the state store? I can only think of the case where someone has provided a bad deserializer to a method that creates a state store. In which case it would be a user error and probably should just abort? Thanks, Damian

[jira] [Updated] (KAFKA-3514) Stream timestamp computation needs some further thoughts

[ https://issues.apache.org/jira/browse/KAFKA-3514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-3514: Fix Version/s: (was: 0.11.0.0) 0.11.1.0 > Stream timestamp computation needs

[jira] [Updated] (KAFKA-4641) Improve test coverage of StreamsThread

[ https://issues.apache.org/jira/browse/KAFKA-4641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-4641: Fix Version/s: (was: 0.11.0.0) 0.11.1.0 > Improve test coverage of

[jira] [Updated] (KAFKA-3779) Add the LRU cache for KTable.to() operator

[ https://issues.apache.org/jira/browse/KAFKA-3779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-3779: Fix Version/s: (was: 0.11.0.0) > Add the LRU cache for KTable.to() operator >

[jira] [Updated] (KAFKA-4640) Improve Streams unit test coverage

[ https://issues.apache.org/jira/browse/KAFKA-4640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-4640: Fix Version/s: (was: 0.11.0.0) 0.11.1.0 > Improve Streams unit test coverage

[jira] [Updated] (KAFKA-4653) Improve test coverage of RocksDBStore

[ https://issues.apache.org/jira/browse/KAFKA-4653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-4653: Fix Version/s: (was: 0.11.0.0) 0.11.1.0 > Improve test coverage of

[jira] [Updated] (KAFKA-4643) Improve test coverage of StreamsKafkaClient

[ https://issues.apache.org/jira/browse/KAFKA-4643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-4643: Fix Version/s: (was: 0.11.0.0) > Improve test coverage of StreamsKafkaClient >

[jira] [Updated] (KAFKA-4651) Improve test coverage of Stores

[ https://issues.apache.org/jira/browse/KAFKA-4651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-4651: Fix Version/s: (was: 0.11.0.0) 0.11.1.0 > Improve test coverage of Stores >

[jira] [Updated] (KAFKA-4650) Improve test coverage org.apache.kafka.streams.kstream.internals

[ https://issues.apache.org/jira/browse/KAFKA-4650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-4650: Fix Version/s: (was: 0.11.0.0) 0.11.1.0 > Improve test coverage

[jira] [Updated] (KAFKA-4655) Improve test coverage of CompositeReadOnlySessionStore

[ https://issues.apache.org/jira/browse/KAFKA-4655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-4655: Fix Version/s: (was: 0.11.0.0) 0.11.1.0 > Improve test coverage of

[jira] [Updated] (KAFKA-4658) Improve test coverage InMemoryKeyValueLoggedStore

[ https://issues.apache.org/jira/browse/KAFKA-4658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-4658: Fix Version/s: (was: 0.11.0.0) 0.11.1.0 > Improve test coverage

[jira] [Updated] (KAFKA-4659) Improve test coverage of CachingKeyValueStore

[ https://issues.apache.org/jira/browse/KAFKA-4659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-4659: Fix Version/s: (was: 0.11.0.0) 0.11.1.0 > Improve test coverage of

[jira] [Updated] (KAFKA-4656) Improve test coverage of CompositeReadOnlyKeyValueStore

[ https://issues.apache.org/jira/browse/KAFKA-4656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-4656: Fix Version/s: (was: 0.11.0.0) 0.11.1.0 > Improve test coverage of

[jira] [Updated] (KAFKA-4730) Streams does not have an in-memory windowed store

[ https://issues.apache.org/jira/browse/KAFKA-4730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-4730: Fix Version/s: (was: 0.11.0.0) 0.11.1.0 > Streams does not have an in-memory

[jira] [Updated] (KAFKA-5037) Infinite loop if all input topics are unknown at startup

[ https://issues.apache.org/jira/browse/KAFKA-5037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-5037: --- Fix Version/s: (was: 0.11.0.0) 0.11.1.0 > Infinite loop if all input

[jira] [Updated] (KAFKA-4661) Improve test coverage UsePreviousTimeOnInvalidTimestamp

[ https://issues.apache.org/jira/browse/KAFKA-4661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-4661: Fix Version/s: (was: 0.11.0.0) > Improve test coverage UsePreviousTimeOnInvalidTimestamp >

[jira] [Updated] (KAFKA-4696) Streams standby task assignment should be state-store aware

[ https://issues.apache.org/jira/browse/KAFKA-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-4696: Fix Version/s: (was: 0.11.0.0) 0.11.1.0 > Streams standby task assignment

[jira] [Updated] (KAFKA-4729) Stores for kstream-kstream join cannot be in-memory

[ https://issues.apache.org/jira/browse/KAFKA-4729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-4729: Fix Version/s: (was: 0.11.0.0) 0.11.1.0 > Stores for kstream-kstream join

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

[ https://issues.apache.org/jira/browse/KAFKA-5063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-5063: --- Fix Version/s: (was: 0.11.1.0) > Flaky >

[jira] [Updated] (KAFKA-4875) Kafka Streams: topic groups and builder.stream API

[ https://issues.apache.org/jira/browse/KAFKA-4875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-4875: Fix Version/s: (was: 0.11.0.0) 0.11.1.0 > Kafka Streams: topic groups and

[jira] [Resolved] (KAFKA-4838) Export buffer cache metrics in JMX

[ https://issues.apache.org/jira/browse/KAFKA-4838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska resolved KAFKA-4838. - Resolution: Won't Fix > Export buffer cache metrics in JMX > -- >

[jira] [Updated] (KAFKA-3856) Cleanup Kafka Streams builder API

[ https://issues.apache.org/jira/browse/KAFKA-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-3856: --- Fix Version/s: 0.11.1.0 > Cleanup Kafka Streams builder API >

[jira] [Updated] (KAFKA-4904) Performance of RocksDb with state record cache

[ https://issues.apache.org/jira/browse/KAFKA-4904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-4904: Fix Version/s: (was: 0.11.0.0) 0.11.1.0 > Performance of RocksDb with state

[jira] [Updated] (KAFKA-4934) Add streams test with RocksDb failures

[ https://issues.apache.org/jira/browse/KAFKA-4934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-4934: Fix Version/s: (was: 0.11.0.0) 0.11.1.0 > Add streams test with RocksDb

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

[ https://issues.apache.org/jira/browse/KAFKA-5063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-5063: --- Fix Version/s: (was: 0.11.0.0) 0.11.1.0 > Flaky >

[jira] [Commented] (KAFKA-5037) Infinite loop if all input topics are unknown at startup

[ https://issues.apache.org/jira/browse/KAFKA-5037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16026413#comment-16026413 ] Eno Thereska commented on KAFKA-5037: - [~mjsax] is this still for 0.11? > Infinite loop if all input

Re: KIP-162: Enable topic deletion by default

+1 On Fri, May 26, 2017 at 10:55 AM, Gwen Shapira wrote: > This was a discussion, not a vote (sorry for mangling the title), but > thanks for all the +1 anyway. > > Regarding Ismael's feedback: > The current server.properties includes the following: > # Switch to enable topic

[jira] [Commented] (KAFKA-5054) ChangeLoggingKeyValueByteStore delete and putIfAbsent should be synchronized

[ https://issues.apache.org/jira/browse/KAFKA-5054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16026411#comment-16026411 ] Eno Thereska commented on KAFKA-5054: - [~damianguy] is this still for 0.11? >

[jira] [Updated] (KAFKA-5301) Improve exception handling on consumer path

[ https://issues.apache.org/jira/browse/KAFKA-5301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-5301: Fix Version/s: (was: 0.11.0.0) 0.11.1.0 > Improve exception handling on

Re: [DISCUSS]: KIP-161: streams record processing exception handlers

See latest reply to Jan's note. I think I unnecessarily broadened the scope of this KIP to the point where it sounded like it handles all sorts of exceptions. The scope should be strictly limited to "poison pill" records for now. Will update KIP, Thanks Eno > On 26 May 2017, at 16:16,

Re: [DISCUSS]: KIP-161: streams record processing exception handlers

Hi Jan, You're right. I think I got carried away and broadened the scope of this KIP beyond it's original purpose. This handler will only be there for deserialization errors, i.e., "poison pills" and is not intended to be a catch-all handler for all sorts of other problems (e.g., NPE exception

Re: [DISCUSS]: KIP-161: streams record processing exception handlers

"bad" for this case would mean, that we got an `DeserializationException`. I am not sure if any other processing error should be covered? @Eno: this raises one one question. Might it be better to allow for two handlers instead of one? One for deserialization exception and one for all other

Re: KIP-162: Enable topic deletion by default

This was a discussion, not a vote (sorry for mangling the title), but thanks for all the +1 anyway. Regarding Ismael's feedback: The current server.properties includes the following: # Switch to enable topic deletion or not, default value is false #delete.topic.enable=true We can't leave it as

Re: [DISCUSS]: KIP-161: streams record processing exception handlers

> On May 26, 2017, at 5:13 AM, Eno Thereska wrote: > > >> >> >> With regard to `DeserializationException`, do you thing it might make >> sense to have a "dead letter queue" as a feature to provide out-of-the-box? > > We could provide a special topic where bad

Re: KIP-162: Enable topic deletion by default

+1 (non-binding) On Fri, May 26, 2017 at 3:38 PM, Damian Guy wrote: > +1 > Also agree with what Ismael said. > > On Fri, 26 May 2017 at 15:26 Ismael Juma wrote: > > > Thanks for the KIP, sounds good to me. One comment: not sure we need to > add > > the

Re: KIP-162: Enable topic deletion by default

+1 Also agree with what Ismael said. On Fri, 26 May 2017 at 15:26 Ismael Juma wrote: > Thanks for the KIP, sounds good to me. One comment: not sure we need to add > the config to server.properties. Do we expect people to change this > default? > > On Fri, May 26, 2017 at 3:03

[GitHub] kafka pull request #3155: Fix KAKFA-5334.

GitHub user twbecker opened a pull request: https://github.com/apache/kafka/pull/3155 Fix KAKFA-5334. Handle` rocksdb.config.setter` being set as a class name or class instance. You can merge this pull request into a Git repository by running: $ git pull

Re: [DISCUSS]: KIP-161: streams record processing exception handlers

About `LogAndThresholdExceptionHandler`: If the handler needs to keep track of number of failed messages, than it becomes stateful -- not sure if we should do that. But maybe we can introduce 2 metrics (might be an interesting metric to report to the user anyway) and allow programmatic access to

Re: KIP-162: Enable topic deletion by default

Thanks for the KIP, sounds good to me. One comment: not sure we need to add the config to server.properties. Do we expect people to change this default? On Fri, May 26, 2017 at 3:03 PM, Gwen Shapira wrote: > Hi Kafka developers, users and friends, > > I've added a KIP to

[jira] [Created] (KAFKA-5334) rocksdb.config.setter must be a class instance, not a class name

Tommy Becker created KAFKA-5334: --- Summary: rocksdb.config.setter must be a class instance, not a class name Key: KAFKA-5334 URL: https://issues.apache.org/jira/browse/KAFKA-5334 Project: Kafka

Re: KIP-162: Enable topic deletion by default

+1 El vie., 26 may. 2017 a las 16:14, Matthias J. Sax () escribió: > +1 > > On 5/26/17 7:03 AM, Gwen Shapira wrote: > > Hi Kafka developers, users and friends, > > > > I've added a KIP to improve our out-of-the-box usability a bit: > > KIP-162: Enable topic deletion by

Re: KIP-162: Enable topic deletion by default

+1 On 5/26/17 7:03 AM, Gwen Shapira wrote: > Hi Kafka developers, users and friends, > > I've added a KIP to improve our out-of-the-box usability a bit: > KIP-162: Enable topic deletion by default: > https://cwiki.apache.org/confluence/display/KAFKA/KIP-162+-+Enable+topic+deletion+by+default >

[jira] [Updated] (KAFKA-5226) NullPointerException (NPE) in SourceNodeRecordDeserializer.deserialize

[ https://issues.apache.org/jira/browse/KAFKA-5226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Bejeck updated KAFKA-5226: --- Fix Version/s: 0.11.0.0 > NullPointerException (NPE) in SourceNodeRecordDeserializer.deserialize >

KIP-162: Enable topic deletion by default

Hi Kafka developers, users and friends, I've added a KIP to improve our out-of-the-box usability a bit: KIP-162: Enable topic deletion by default: https://cwiki.apache.org/confluence/display/KAFKA/KIP-162+-+Enable+topic+deletion+by+default Pretty simple :) Discussion and feedback are welcome.

[jira] [Updated] (KAFKA-5219) Move transaction expiration logic and scheduling to the Transaction Manager

[ https://issues.apache.org/jira/browse/KAFKA-5219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5219: --- Fix Version/s: (was: 0.11.0.0) 0.11.1.0 > Move transaction expiration logic

[jira] [Updated] (KAFKA-5313) Improve exception handling on coordinator interactions

[ https://issues.apache.org/jira/browse/KAFKA-5313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-5313: Fix Version/s: (was: 0.11.0.0) 0.11.1.0 > Improve exception handling on

[jira] [Updated] (KAFKA-5302) Improve exception handling on streams client (communication with brokers)

[ https://issues.apache.org/jira/browse/KAFKA-5302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-5302: Fix Version/s: (was: 0.11.0.0) 0.11.1.0 > Improve exception handling on

  1   2   >