Fwd: [jira] [Commented] (KAFKA-1207) Launch Kafka from within Apache Mesos

I don't understand why the whole dev list needs to be notified of failed email deliveries. Is there a way to shut these off? -- Forwarded message -- From: postmas...@inn.ru (JIRA) Date: Tue, Jan 17, 2017 at 9:50 PM Subject: [jira] [Commented] (KAFKA-1207)

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

See

Re: [VOTE] KIP-107 Add purgeDataBefore() API in AdminClient

Hi Jun, Thank you. Please see my answers below. The KIP is updated to answer these questions (see here ). 1. Yes, in this KIP we wait for all replicas. This is the same as if producer sends a messge with

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

See

[jira] [Commented] (KAFKA-1207) Launch Kafka from within Apache Mesos

[ https://issues.apache.org/jira/browse/KAFKA-1207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15827464#comment-15827464 ] postmas...@inn.ru commented on KAFKA-1207: -- Delivery is delayed to these recipients or groups:

[jira] [Commented] (KAFKA-1207) Launch Kafka from within Apache Mesos

[ https://issues.apache.org/jira/browse/KAFKA-1207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15827454#comment-15827454 ] postmas...@inn.ru commented on KAFKA-1207: -- Delivery is delayed to these recipients or groups:

[jira] [Commented] (KAFKA-4617) gradle-generated core eclipse project has incorrect source folder structure

[ https://issues.apache.org/jira/browse/KAFKA-4617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15827453#comment-15827453 ] Dhwani Katagade commented on KAFKA-4617: [~ecomar] Thanks for the review and LGTM :-) >

Re: Is this a bug or just unintuitive behavior?

Agree on suggesting in the docs that generally the default offset should be reset to "none" after the mirrormaker is going. There is an edgecase where you want to keep offsets to earliest: When you've got a mirrormaker consumer subscribed to a regex pattern and have auto-topic creation enabled on

Re: [DISCUSS] KIP-98: Exactly Once Delivery and Transactional Messaging

> > 114.The section on Discussion on Pro-active Transaction Timeout: "If there > is no other instance with the same PID yet, or it has not started a > transaction, or it has not appended a message to some of the partitions, > then the zombie can continue appending messages to those partitions

[jira] [Resolved] (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:all-tabpanel ] Jason Gustafson resolved KAFKA-3502. Resolution: Fixed Fix Version/s: 0.10.2.0 Issue resolved by pull request 2381

[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=15827413#comment-15827413 ] ASF GitHub Bot commented on KAFKA-3502: --- Github user asfgit closed the pull request at:

[GitHub] kafka pull request #2381: KAFKA-3502: move RocksDB options construction to i...

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

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

See Changes: [wangguoz] MINOR: remove ZK from system tests -- [...truncated 8387 lines...] kafka.integration.SaslPlaintextTopicMetadataTest > testIsrAfterBrokerShutDownAndJoinsBack STARTED

Re: Is this a bug or just unintuitive behavior?

I agree that setting the default auto.offset.reset to earliest makes sense (This was actually a default choice Flume made for its Kafka channel to avoid missing the first messages). However I think, at a minimum, we should also document a recommendation to consider changing the value to none after

[jira] [Commented] (KAFKA-4635) Client Compatibility follow-up

[ https://issues.apache.org/jira/browse/KAFKA-4635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15827354#comment-15827354 ] Ismael Juma commented on KAFKA-4635: "Sorry for the dumb question, but I don't completely understand

Re: [VOTE] KIP-107 Add purgeDataBefore() API in AdminClient

Hi, Dong, Thanks for the KIP. Looks good overall. Just a few more comments. 1."Note that the way broker handles PurgeRequest is similar to how it handles ProduceRequest with ack = -1 and isr=all_replicas". It seems that the implementation is a bit different. In this KIP, we wait for all

[jira] [Commented] (KAFKA-4591) Create Topic Policy

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

[GitHub] kafka pull request #2388: KAFKA-4591: Create Topic Policy follow-up

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2388 --- 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-3738) Add load system tests for Streams

[ https://issues.apache.org/jira/browse/KAFKA-3738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3738: - Issue Type: Task (was: Bug) > Add load system tests for Streams >

[jira] [Updated] (KAFKA-3738) Add load system tests for Streams

[ https://issues.apache.org/jira/browse/KAFKA-3738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3738: - Description: Today in system tests we have mainly two types of tests: 1) correctness tests for

Re: [DISCUSS] KIP-81: Max in-flight fetches

i have (hopefully?) addressed Rajini's concern of muting all connections ahead of time on the KIP-72 PR. as for avoiding the pool for small allocations i think thats a great idea. I also think you could implement it as a composite pool :-) (composite redirects all requests under size X to the NONE

[jira] [Updated] (KAFKA-3738) Add load system tests for Streams

[ https://issues.apache.org/jira/browse/KAFKA-3738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3738: - Summary: Add load system tests for Streams (was: Add system test against memory leak in Kafka

Re: [DISCUSS] KIP-98: Exactly Once Delivery and Transactional Messaging

Hi Jun, Some answers in line. 109. Could you describe when Producer.send() will receive an Unrecognized MessageException? This exception will be thrown if the producer sends a sequence number which is greater than the sequence number expected by the broker (ie. more than 1 greater than the

[GitHub] kafka pull request #2391: MINOR: remove ZK from system tests

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

Re: Is this a bug or just unintuitive behavior?

[Moving discussion from users list to dev list] I agree with Ewen that it's more sensible for mirrormaker to default to replicating topics from the earliest offset available, rather than just replicating from the current offset onward. I filed a JIRA ticket

[jira] [Commented] (KAFKA-4668) Mirrormaker should default to auto.offset.reset=earliest

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

[GitHub] kafka pull request #2394: KAFKA-4668: Replicate from topics from earliest

GitHub user jeffwidman opened a pull request: https://github.com/apache/kafka/pull/2394 KAFKA-4668: Replicate from topics from earliest Mirrormaker currently inherits the default value for auto.offset.reset, which is latest (new consumer) / largest (old consumer). While for

[jira] [Created] (KAFKA-4668) Mirrormaker should default to auto.offset.reset=earliest

Jeff Widman created KAFKA-4668: -- Summary: Mirrormaker should default to auto.offset.reset=earliest Key: KAFKA-4668 URL: https://issues.apache.org/jira/browse/KAFKA-4668 Project: Kafka Issue

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

See Changes: [wangguoz] KAFKA-4588: Wait for topics to be created in [wangguoz] KAFKA-3452 Follow-up: Refactoring StateStore hierarchies -- [...truncated 19319 lines...]

[GitHub] kafka pull request #2393: MINOR: Use new-consumer config in MirrorMaker doc

GitHub user jeffwidman opened a pull request: https://github.com/apache/kafka/pull/2393 MINOR: Use new-consumer config in MirrorMaker doc Mirrormaker was updated to default to the new consumer in 3db752a565071c78e4b11eaafa739844fa785b04 Old consumer calls the param

[jira] [Commented] (KAFKA-1207) Launch Kafka from within Apache Mesos

[ https://issues.apache.org/jira/browse/KAFKA-1207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15827222#comment-15827222 ] postmas...@inn.ru commented on KAFKA-1207: -- Delivery is delayed to these recipients or groups:

[jira] [Commented] (KAFKA-1207) Launch Kafka from within Apache Mesos

[ https://issues.apache.org/jira/browse/KAFKA-1207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15827211#comment-15827211 ] postmas...@inn.ru commented on KAFKA-1207: -- Delivery is delayed to these recipients or groups:

[jira] [Commented] (KAFKA-4635) Client Compatibility follow-up

[ https://issues.apache.org/jira/browse/KAFKA-4635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15827196#comment-15827196 ] Colin P. McCabe commented on KAFKA-4635: bq. 1. OffsetAndTimestamp is a public class and the

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

See Changes: [wangguoz] KAFKA-3452 Follow-up: Refactoring StateStore hierarchies -- [...truncated 19274 lines...] org.apache.kafka.streams.integration.KStreamAggregationDedupIntegrationTest >

[GitHub] kafka pull request #2392: MINOR: refactor streams system test class hierachy

GitHub user mjsax opened a pull request: https://github.com/apache/kafka/pull/2392 MINOR: refactor streams system test class hierachy You can merge this pull request into a Git repository by running: $ git pull https://github.com/mjsax/kafka minor-system-test-rework

[GitHub] kafka pull request #2391: MINOR: remove ZK from system tests

GitHub user mjsax opened a pull request: https://github.com/apache/kafka/pull/2391 MINOR: remove ZK from system tests You can merge this pull request into a Git repository by running: $ git pull https://github.com/mjsax/kafka kafka-4060-zk-follow-up-system-tests

Re: [DISCUSS] KIP-98: Exactly Once Delivery and Transactional Messaging

Hello, Nacho and others had questions about the rationale behind the AppId and PID design. In particular, why do we propose to have a broker-based map of AppId to PID? Why can't we use the AppId directly? And if we need to use an internal PID, why don't we do a static hashing of AppId to PID on

[jira] [Commented] (KAFKA-4635) Client Compatibility follow-up

[ https://issues.apache.org/jira/browse/KAFKA-4635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15827119#comment-15827119 ] Ismael Juma commented on KAFKA-4635: Great about #5! For #4, how do we handle the disconnection? We

Re: Okay to remove the deprecated kafka-consumer-offset-checker.sh?

+1 I also got confused when looking for the right tool. On Tue, Jan 17, 2017 at 2:57 PM, Jeff Widman wrote: > Kafka 9 deprecated kafka-consumer-offset-checker.sh > (kafka.tools.ConsumerOffsetChecker) in favor of kafka-consumer-groups.sh > (kafka.admin.ConsumerGroupCommand). >

[jira] [Commented] (KAFKA-4635) Client Compatibility follow-up

[ https://issues.apache.org/jira/browse/KAFKA-4635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15827057#comment-15827057 ] Colin P. McCabe commented on KAFKA-4635: Thanks for filling in the notes. #5 is implemented by

[jira] [Updated] (KAFKA-4664) Update docs/protocol.html with KIP-97 information

[ https://issues.apache.org/jira/browse/KAFKA-4664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin P. McCabe updated KAFKA-4664: --- Status: Patch Available (was: In Progress) > Update docs/protocol.html with KIP-97

[jira] [Updated] (KAFKA-4548) Add CompatibilityTest to verify that individual features are supported or not by the broker we're connecting to

[ https://issues.apache.org/jira/browse/KAFKA-4548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin P. McCabe updated KAFKA-4548: --- Status: Patch Available (was: In Progress) > Add CompatibilityTest to verify that individual

[jira] [Commented] (KAFKA-4630) Implement RecordTooLargeException when communicating with pre-KIP-74 brokers

[ https://issues.apache.org/jira/browse/KAFKA-4630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15827034#comment-15827034 ] Colin P. McCabe commented on KAFKA-4630: https://github.com/apache/kafka/pull/2390 > Implement

[jira] [Work stopped] (KAFKA-4630) Implement RecordTooLargeException when communicating with pre-KIP-74 brokers

[ https://issues.apache.org/jira/browse/KAFKA-4630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-4630 stopped by Colin P. McCabe. -- > Implement RecordTooLargeException when communicating with pre-KIP-74

[jira] [Updated] (KAFKA-4630) Implement RecordTooLargeException when communicating with pre-KIP-74 brokers

[ https://issues.apache.org/jira/browse/KAFKA-4630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin P. McCabe updated KAFKA-4630: --- Status: Patch Available (was: Open) > Implement RecordTooLargeException when communicating

[jira] [Commented] (KAFKA-4630) Implement RecordTooLargeException when communicating with pre-KIP-74 brokers

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

[jira] [Work started] (KAFKA-4630) Implement RecordTooLargeException when communicating with pre-KIP-74 brokers

[ https://issues.apache.org/jira/browse/KAFKA-4630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-4630 started by Colin P. McCabe. -- > Implement RecordTooLargeException when communicating with pre-KIP-74

[GitHub] kafka pull request #2390: KAFKA-4630: Implement RecordTooLargeException when...

GitHub user cmccabe opened a pull request: https://github.com/apache/kafka/pull/2390 KAFKA-4630: Implement RecordTooLargeException when communicating with pre-KIP-74 brokers You can merge this pull request into a Git repository by running: $ git pull

[jira] [Commented] (KAFKA-3705) Support non-key joining in KTable

[ https://issues.apache.org/jira/browse/KAFKA-3705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15827015#comment-15827015 ] Paul Vaughan commented on KAFKA-3705: - Healthcare data is intrinsically relational, but the bulk of

Okay to remove the deprecated kafka-consumer-offset-checker.sh?

Kafka 9 deprecated kafka-consumer-offset-checker.sh (kafka.tools.ConsumerOffsetChecker) in favor of kafka-consumer-groups.sh (kafka.admin.ConsumerGroupCommand). Since this was deprecated in 9, and the full functionality of the old script appears to be available in the new script, can we

[jira] [Created] (KAFKA-4667) Connect (and Stream?) should create internal topics with availability or consistency properly set

Emanuele Cesena created KAFKA-4667: -- Summary: Connect (and Stream?) should create internal topics with availability or consistency properly set Key: KAFKA-4667 URL:

[GitHub] kafka pull request #2389: Kafka 4060 remove zk client dependency in kafka st...

GitHub user hjafarpour opened a pull request: https://github.com/apache/kafka/pull/2389 Kafka 4060 remove zk client dependency in kafka streams followup re-branched from trunk Re-branched the trunk and applied the changes to the new branch to simplify commit log. You can merge

Jenkins build is back to normal : kafka-0.10.2-jdk7 #5

See

[jira] [Commented] (KAFKA-3452) Support session windows

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

[GitHub] kafka pull request #2360: KAFKA-3452 Follow-up: Refactoring StateStore hiera...

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

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

See Changes: [wangguoz] KAFKA-4588: Wait for topics to be created in -- [...truncated 2010 lines...] kafka.log.OffsetIndexTest > truncate STARTED kafka.log.OffsetIndexTest > truncate PASSED

[jira] [Commented] (KAFKA-2729) Cached zkVersion not equal to that in zookeeper, broker not recovering.

[ https://issues.apache.org/jira/browse/KAFKA-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15826905#comment-15826905 ] Sinóros-Szabó Péter commented on KAFKA-2729: Same issue on 0.10.1.1. Do you need logs? I can

[jira] [Updated] (KAFKA-4624) Streams smoke tests fails when there is only 1 broker

[ https://issues.apache.org/jira/browse/KAFKA-4624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-4624: --- Assignee: Ewen Cheslack-Postava (was: Hojjat Jafarpour) > Streams smoke tests fails when

[jira] [Updated] (KAFKA-4625) Streams smoke tests fails when there is only 1 broker

[ https://issues.apache.org/jira/browse/KAFKA-4625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-4625: --- Assignee: Ewen Cheslack-Postava (was: Matthias J. Sax) > Streams smoke tests fails when

[jira] [Assigned] (KAFKA-4625) Streams smoke tests fails when there is only 1 broker

[ https://issues.apache.org/jira/browse/KAFKA-4625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax reassigned KAFKA-4625: -- Assignee: Matthias J. Sax (was: Ewen Cheslack-Postava) > Streams smoke tests fails

[jira] [Commented] (KAFKA-3513) Transient failure of OffsetValidationTest

[ https://issues.apache.org/jira/browse/KAFKA-3513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15826869#comment-15826869 ] Ewen Cheslack-Postava commented on KAFKA-3513: -- This continues to pop up occasionally:

[jira] [Commented] (KAFKA-1207) Launch Kafka from within Apache Mesos

[ https://issues.apache.org/jira/browse/KAFKA-1207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15826865#comment-15826865 ] postmas...@inn.ru commented on KAFKA-1207: -- Delivery is delayed to these recipients or groups:

[jira] [Assigned] (KAFKA-4625) Streams smoke tests fails when there is only 1 broker

[ https://issues.apache.org/jira/browse/KAFKA-4625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava reassigned KAFKA-4625: Assignee: Ewen Cheslack-Postava (was: Hojjat Jafarpour) > Streams smoke

[jira] [Commented] (KAFKA-1207) Launch Kafka from within Apache Mesos

[ https://issues.apache.org/jira/browse/KAFKA-1207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15826843#comment-15826843 ] postmas...@inn.ru commented on KAFKA-1207: -- Delivery is delayed to these recipients or groups:

[jira] [Commented] (KAFKA-4591) Create Topic Policy

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

[GitHub] kafka pull request #2388: KAFKA-4591: Create Topic Policy follow-up

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/2388 KAFKA-4591: Create Topic Policy follow-up 1. Added javadoc to public classes 2. Removed `s` from config name for consistency with interface name 3. The policy interface now implements

[jira] [Commented] (KAFKA-4617) gradle-generated core eclipse project has incorrect source folder structure

[ https://issues.apache.org/jira/browse/KAFKA-4617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15826797#comment-15826797 ] Edoardo Comar commented on KAFKA-4617: -- [~dhwanikatagade] thanks for the PR ! > gradle-generated

[jira] [Commented] (KAFKA-4635) Client Compatibility follow-up

[ https://issues.apache.org/jira/browse/KAFKA-4635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15826790#comment-15826790 ] Jason Gustafson commented on KAFKA-4635: [~ijuma] I think I'm convinced we should not do #6. The

[jira] [Updated] (KAFKA-4588) QueryableStateIntegrationTest.shouldNotMakeStoreAvailableUntilAllStoresAvailable is occasionally failing on jenkins

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

[jira] [Commented] (KAFKA-4588) QueryableStateIntegrationTest.shouldNotMakeStoreAvailableUntilAllStoresAvailable is occasionally failing on jenkins

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

[GitHub] kafka pull request #2371: KAFKA-4588: Wait for topics to be created in Query...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2371 --- 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-3896) Unstable test KStreamRepartitionJoinTest.shouldCorrectlyRepartitionOnJoinOperations

[ https://issues.apache.org/jira/browse/KAFKA-3896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15826752#comment-15826752 ] Guozhang Wang commented on KAFKA-3896: -- Another instance:

[jira] [Updated] (KAFKA-3896) Unstable test KStreamRepartitionJoinTest.shouldCorrectlyRepartitionOnJoinOperations

[ https://issues.apache.org/jira/browse/KAFKA-3896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3896: - Assignee: Guozhang Wang (was: Damian Guy) > Unstable test >

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

See Changes: [ismael] KAFKA-4580; Use sasl.jaas.config for some system tests [jason] MINOR: Some cleanups and additional testing for KIP-88 -- [...truncated 18962 lines...]

[jira] [Created] (KAFKA-4666) Failure test for Kafka configured for consistency vs availability

Emanuele Cesena created KAFKA-4666: -- Summary: Failure test for Kafka configured for consistency vs availability Key: KAFKA-4666 URL: https://issues.apache.org/jira/browse/KAFKA-4666 Project: Kafka

[jira] [Assigned] (KAFKA-4665) Inconsistent handling of non-existing topics in offset fetch handling

[ https://issues.apache.org/jira/browse/KAFKA-4665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vahid Hashemian reassigned KAFKA-4665: -- Assignee: Vahid Hashemian > Inconsistent handling of non-existing topics in offset

[jira] [Updated] (KAFKA-3177) Kafka consumer can hang when position() is called on a non-existing partition.

[ https://issues.apache.org/jira/browse/KAFKA-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-3177: --- Fix Version/s: (was: 0.10.2.0) 0.10.3.0 > Kafka consumer can hang when

[jira] [Commented] (KAFKA-3177) Kafka consumer can hang when position() is called on a non-existing partition.

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

[GitHub] kafka pull request #1157: KAFKA-3177: log warning when topic/partition doesn...

Github user hachikuji closed the pull request at: https://github.com/apache/kafka/pull/1157 --- 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-4665) Inconsistent handling of non-existing topics in offset fetch handling

Jason Gustafson created KAFKA-4665: -- Summary: Inconsistent handling of non-existing topics in offset fetch handling Key: KAFKA-4665 URL: https://issues.apache.org/jira/browse/KAFKA-4665 Project:

[jira] [Commented] (KAFKA-1194) The kafka broker cannot delete the old log files after the configured time

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

[GitHub] kafka pull request #2386: [WIP] Upgrade Kafka and apply windows fix

Github user silpamittapalli closed the pull request at: https://github.com/apache/kafka/pull/2386 --- 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] [Work started] (KAFKA-4664) Update docs/protocol.html with KIP-97 information

[ https://issues.apache.org/jira/browse/KAFKA-4664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-4664 started by Colin P. McCabe. -- > Update docs/protocol.html with KIP-97 information >

[jira] [Commented] (KAFKA-4664) Update docs/protocol.html with KIP-97 information

[ https://issues.apache.org/jira/browse/KAFKA-4664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15826636#comment-15826636 ] Colin P. McCabe commented on KAFKA-4664: https://github.com/apache/kafka/pull/2387 > Update

[jira] [Commented] (KAFKA-4664) Update docs/protocol.html with KIP-97 information

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

[GitHub] kafka pull request #2387: KAFKA-4664: Update docs/protocol.html with KIP-97 ...

GitHub user cmccabe opened a pull request: https://github.com/apache/kafka/pull/2387 KAFKA-4664: Update docs/protocol.html with KIP-97 information You can merge this pull request into a Git repository by running: $ git pull https://github.com/cmccabe/kafka KAFKA-4664

[jira] [Created] (KAFKA-4664) Update docs/protocol.html with KIP-97 information

Colin P. McCabe created KAFKA-4664: -- Summary: Update docs/protocol.html with KIP-97 information Key: KAFKA-4664 URL: https://issues.apache.org/jira/browse/KAFKA-4664 Project: Kafka Issue

[jira] [Resolved] (KAFKA-4456) Offsets of deleted topics are not removed from consumer groups

[ https://issues.apache.org/jira/browse/KAFKA-4456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-4456. Resolution: Duplicate This looks like a duplicate of KAFKA-2000, which has a patch

[jira] [Commented] (KAFKA-1194) The kafka broker cannot delete the old log files after the configured time

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

[GitHub] kafka pull request #2386: Upgrade Kafka and apply windows fix

GitHub user silpamittapalli opened a pull request: https://github.com/apache/kafka/pull/2386 Upgrade Kafka and apply windows fix Based on https://github.com/fluetm/kafka/tree/kafka-upgrade. 1. Cherry-picked windows fix for https://issues.apache.org/jira/browse/KAFKA-1194

[jira] [Resolved] (KAFKA-4580) Change one SASL system test to use new JAAS config property

[ https://issues.apache.org/jira/browse/KAFKA-4580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-4580. Resolution: Fixed Issue resolved by pull request 2323 [https://github.com/apache/kafka/pull/2323]

[jira] [Commented] (KAFKA-4580) Change one SASL system test to use new JAAS config property

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

[GitHub] kafka pull request #2323: KAFKA-4580: Use sasl.jaas.config for some system t...

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

[GitHub] kafka pull request #2383: MINOR: Some cleanups and additional testing for KI...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2383 --- 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-3838) Bump zkclient and Zookeeper versions

[ https://issues.apache.org/jira/browse/KAFKA-3838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15826573#comment-15826573 ] James Cheng commented on KAFKA-3838: This JIRA moves ZKClient from 0.7 to 0.9. Can ZKClient 0.7 be

Re: [VOTE] KIP-107 Add purgeDataBefore() API in AdminClient

+1. Thanks for the KIP. On Thu, Jan 12, 2017 at 10:33 AM, Joel Koshy wrote: > +1 > > (for the record, I favor the rejected alternative of not awaiting low > watermarks to go past the purge offset. I realize it offers a weaker > guarantee but it is still very useful, easier

Re: [VOTE] KIP-107: Add purgeDataBefore() API in AdminClient

Hey Jun, Do you have time to review the KIP again or vote for it? Hey Ewen, Can you also review the KIP again or vote for it? I have discussed with Radai and Becket regarding your concern. We still think putting it in Admin Client seems more intuitive because there is use-case where application

[jira] [Commented] (KAFKA-1207) Launch Kafka from within Apache Mesos

[ https://issues.apache.org/jira/browse/KAFKA-1207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15826415#comment-15826415 ] postmas...@inn.ru commented on KAFKA-1207: -- Delivery is delayed to these recipients or groups:

[jira] [Commented] (KAFKA-1207) Launch Kafka from within Apache Mesos

[ https://issues.apache.org/jira/browse/KAFKA-1207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15826416#comment-15826416 ] postmas...@inn.ru commented on KAFKA-1207: -- Delivery is delayed to these recipients or groups:

[jira] [Commented] (KAFKA-3705) Support non-key joining in KTable

[ https://issues.apache.org/jira/browse/KAFKA-3705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15826346#comment-15826346 ] Jan Filipiak commented on KAFKA-3705: - AFAICS the table will be also filled by a different thread, IMO

  1   2   >