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

[ https://issues.apache.org/jira/browse/KAFKA-4576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4576: --- Fix Version/s: 0.10.2.0 > Log segments close to max size break on fetch >

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

[ https://issues.apache.org/jira/browse/KAFKA-4576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4576: --- Priority: Critical (was: Major) > Log segments close to max size break on fetch >

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

[ https://issues.apache.org/jira/browse/KAFKA-4576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4576: --- Assignee: huxi > Log segments close to max size break on fetch >

[jira] [Created] (KAFKA-4581) Fail gracefully if multiple login modules are specified in sasl.jaas.config

Rajini Sivaram created KAFKA-4581: - Summary: Fail gracefully if multiple login modules are specified in sasl.jaas.config Key: KAFKA-4581 URL: https://issues.apache.org/jira/browse/KAFKA-4581 Project:

[jira] [Updated] (KAFKA-4528) Failure in kafka.producer.ProducerTest.testAsyncSendCanCorrectlyFailWithTimeout

[ https://issues.apache.org/jira/browse/KAFKA-4528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4528: --- Fix Version/s: 0.10.2.0 > Failure in >

[jira] [Assigned] (KAFKA-4528) Failure in kafka.producer.ProducerTest.testAsyncSendCanCorrectlyFailWithTimeout

[ https://issues.apache.org/jira/browse/KAFKA-4528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-4528: -- Assignee: Ismael Juma > Failure in >

[jira] [Commented] (KAFKA-4528) Failure in kafka.producer.ProducerTest.testAsyncSendCanCorrectlyFailWithTimeout

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

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

@jun - good proposal. i was willing to concede that read-uncommitted was impossible under my proposal but if LSO/NSO is introduced is becomes possible. On Tue, Jan 3, 2017 at 7:50 AM, Jun Rao wrote: > Just to follow up on Radai's idea of pushing the buffering logic to the >

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

See Changes: [me] KAFKA-4261: Provide debug option in vagrant-up.sh -- [...truncated 17643 lines...] org.apache.kafka.streams.processor.internals.RecordCollectorTest > testSpecificPartition

[GitHub] kafka pull request #2304: kafka-4576: Log segments close to max size break o...

GitHub user amethystic opened a pull request: https://github.com/apache/kafka/pull/2304 kafka-4576: Log segments close to max size break on fetch JVM spec does not make a guarantee that the buffer will be filled up when invoking FileChannel.read, which is called in

Re: [DISCUSS] KIP-106 - Change Default unclean.leader.election.enabled from True to False

+1 On Tue, Jan 3, 2017 at 11:56 AM, Ian Wrigley wrote: > +1 from me too. When I talk to people in training classes, who are > typically much newer to Kafka, they tend to be surprised (and > scared/horrified) that the default is true. Much safer to set it to false > and let

Re: [VOTE] KIP-99: Add Global Tables to Kafka Streams

+1 On Tue, Jan 3, 2017 at 11:43 AM, Neha Narkhede wrote: > +1 (binding) > > On Tue, Jan 3, 2017 at 11:40 AM Ewen Cheslack-Postava > wrote: > > > +1 > > > > -Ewen > > > > On Tue, Jan 3, 2017 at 11:16 AM, Gwen Shapira wrote: > > > > > +1

[jira] [Commented] (KAFKA-4535) http://kafka.apache.org/quickstart Step 8 missing argument

[ https://issues.apache.org/jira/browse/KAFKA-4535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15796933#comment-15796933 ] Xin commented on KAFKA-4535: the version is 0.10.0.1,i typed the wrong version number >

[jira] [Updated] (KAFKA-4535) http://kafka.apache.org/quickstart Step 8 missing argument

[ https://issues.apache.org/jira/browse/KAFKA-4535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xin updated KAFKA-4535: --- Affects Version/s: (was: 0.10.1.0) 0.10.0.1 > http://kafka.apache.org/quickstart Step 8

[GitHub] kafka pull request #2271: MINOR: Improvements to Record related classes (par...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2271 --- 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-4584) Fail the 'kafka-configs' command if the config to be removed does not exist

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

[GitHub] kafka pull request #2305: MINOR: Replacing for with foreach loop in stream t...

GitHub user PKOfficial opened a pull request: https://github.com/apache/kafka/pull/2305 MINOR: Replacing for with foreach loop in stream test classes You can merge this pull request into a Git repository by running: $ git pull https://github.com/PKOfficial/kafka code-refactor

[GitHub] kafka pull request #2300: KAFKA-4584: Fail the 'kafka-configs' command if th...

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

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

See

[jira] [Commented] (KAFKA-4535) http://kafka.apache.org/quickstart Step 8 missing argument

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

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

Rajini Sivaram created KAFKA-4580: - Summary: Change one SASL system test to use new JAAS config property Key: KAFKA-4580 URL: https://issues.apache.org/jira/browse/KAFKA-4580 Project: Kafka

Re: [DISCUSS] KIP-99: Add Global Tables to Kafka Streams

Thanks Gouzhang - i'll remove the joins. I agree we need to refactor TopologyBuilder, but I think we'll need another KIP for that. Thanks, Damian On Fri, 30 Dec 2016 at 01:32 Guozhang Wang wrote: > 1/2: Sounds good, let's remove the joins within KGlobalTable for now. > >

[jira] [Created] (KAFKA-4579) Schema Registry client should have a proper caching mechanism for schema IDs

Justin Manchester created KAFKA-4579: Summary: Schema Registry client should have a proper caching mechanism for schema IDs Key: KAFKA-4579 URL: https://issues.apache.org/jira/browse/KAFKA-4579

[GitHub] kafka pull request #2298: KAFKA-4528: Fix failure in ProducerTest.testAsyncS...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/2298 KAFKA-4528: Fix failure in ProducerTest.testAsyncSendCanCorrectlyFailWithTimeout I was able to reproduce the failure in less than 10 runs before the change. With the change, the test passed 70

Re: kafka.log:type=LogFlushStats,name=LogFlushRateAndTimeMs Not Reported

I am running into the same. which version are you using? On Thu, Dec 1, 2016 at 11:55 PM, Madhuri Sasurkar wrote: > Hi All, > > I have set up my kafka cluster and enabled JMX. > I was going through all the mbeans that are exposed and I am not able to > find mbean

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

[ https://issues.apache.org/jira/browse/KAFKA-4576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15794567#comment-15794567 ] Onur Karaman commented on KAFKA-4576: - I think you're right, [~huxi_2b]. It looks like we incorrectly

[GitHub] kafka pull request #2072: Kafka-4351: Topic regex behavioral change with Mir...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2072 --- 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 #2297: MINOR: Code refactoring in scala classes.

GitHub user himani1 opened a pull request: https://github.com/apache/kafka/pull/2297 MINOR: Code refactoring in scala classes. You can merge this pull request into a Git repository by running: $ git pull https://github.com/himani1/kafka refactored_code Alternatively you can

[GitHub] kafka pull request #2297: MINOR: Code refactoring in scala classes.

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2297 --- 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-4480) kafka-configs will execute the removal of an invalid property and not report an error

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

[GitHub] kafka pull request #2218: KAFKA-4480: Report an error in 'kafka-configs' com...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2218 --- 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: [DISCUSS] KIP-48 Support for delegation tokens as an authentication mechanism

Thanks for the KIP. Request-level impersonation is going to make the client implementation more complicated. On the producer side, we batch messages per partition. Now, do we have to batch per partition, per user? The consumer client is designed to be single-threaded. So, I am not sure if

Re: [VOTE] KIP-48 Support for delegation tokens as an authentication mechanism

Hi, Mani Thanks for the proposal. Looks good at the high level. A few comments below. 101. DelegationTokenRequest/DelegationTokenResponse 101.1 I am wondering if renewer should be principalType + name to match what we have in kafka-acls tool? 101.2 Do we need to return owner in

[GitHub] kafka pull request #2083: KAFKA-4318 Migrate ProducerSendTest to the new con...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2083 --- 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-4318) Migrate ProducerSendTest to the new consumer

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

[jira] [Resolved] (KAFKA-4318) Migrate ProducerSendTest to the new consumer

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

[GitHub] kafka pull request #2281: KAFKA-4561: Ordering of operations in StreamThread...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2281 --- 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-4561) Ordering of operations in StreamThread.shutdownTasksAndState may void at-least-once guarantees

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

[jira] [Commented] (KAFKA-4113) Allow KTable bootstrap

[ https://issues.apache.org/jira/browse/KAFKA-4113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15795304#comment-15795304 ] Mitch Seymour commented on KAFKA-4113: -- I believe I am experiencing the same issue that [~gfodor]

[jira] [Commented] (KAFKA-4561) Ordering of operations in StreamThread.shutdownTasksAndState may void at-least-once guarantees

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

[jira] [Created] (KAFKA-4583) KafkaConsumerTest.consumerCloseTest transient failure

Ismael Juma created KAFKA-4583: -- Summary: KafkaConsumerTest.consumerCloseTest transient failure Key: KAFKA-4583 URL: https://issues.apache.org/jira/browse/KAFKA-4583 Project: Kafka Issue Type:

[jira] [Commented] (KAFKA-4569) Transient failure in org.apache.kafka.clients.consumer.KafkaConsumerTest.testWakeupWithFetchDataAvailable

[ https://issues.apache.org/jira/browse/KAFKA-4569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15795223#comment-15795223 ] Ismael Juma commented on KAFKA-4569: This started failing recently, so it would be good to understand

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

Just to follow up on Radai's idea of pushing the buffering logic to the broker. It may be possible to do this efficiently if we assume aborted transactions are rare. The following is a draft proposal. For each partition, the broker maintains the last stable offset (LSO) as described in the

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

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

[jira] [Commented] (KAFKA-4583) KafkaConsumerTest.testGracefulClose transient failure

[ https://issues.apache.org/jira/browse/KAFKA-4583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15795212#comment-15795212 ] Ismael Juma commented on KAFKA-4583: [~rsivaram], maybe you could take a look at this one? >

[jira] [Updated] (KAFKA-4583) KafkaConsumerTest.testGracefulClose transient failure

[ https://issues.apache.org/jira/browse/KAFKA-4583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4583: --- Summary: KafkaConsumerTest.testGracefulClose transient failure (was:

[jira] [Updated] (KAFKA-4528) Failure in kafka.producer.ProducerTest.testAsyncSendCanCorrectlyFailWithTimeout

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

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

See Changes: [ismael] MINOR: Scala code readability improvements -- [...truncated 17626 lines...] org.apache.kafka.streams.KafkaStreamsTest > shouldNotGetAllTasksWithStoreWhenNotRunning

[jira] [Created] (KAFKA-4582) KStream job fails in multi-thread mode

Manuel Romero created KAFKA-4582: Summary: KStream job fails in multi-thread mode Key: KAFKA-4582 URL: https://issues.apache.org/jira/browse/KAFKA-4582 Project: Kafka Issue Type: Bug

[jira] [Resolved] (KAFKA-2057) DelayedOperationTest.testRequestExpiry transient failure

[ https://issues.apache.org/jira/browse/KAFKA-2057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-2057. Resolution: Fixed https://github.com/apache/kafka/pull/1890 did eventually fix the new issue so

[jira] [Updated] (KAFKA-4569) Transient failure in org.apache.kafka.clients.consumer.KafkaConsumerTest.testWakeupWithFetchDataAvailable

[ https://issues.apache.org/jira/browse/KAFKA-4569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4569: --- Fix Version/s: 0.10.2.0 > Transient failure in >

[jira] [Commented] (KAFKA-4550) current trunk unstable

[ https://issues.apache.org/jira/browse/KAFKA-4550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15795221#comment-15795221 ] Ismael Juma commented on KAFKA-4550: I provided a patch for KAFKA-4528. I suggest closing this JIRA

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

[ https://issues.apache.org/jira/browse/KAFKA-4576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15795130#comment-15795130 ] Ismael Juma commented on KAFKA-4576: In theory, we should eventually reach the end of the file, read

[jira] [Reopened] (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 reopened KAFKA-4222: -- > Transient failure in QueryableStateIntegrationTest.queryOnRebalance >

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

[ https://issues.apache.org/jira/browse/KAFKA-4497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15795598#comment-15795598 ] Andrew Holford commented on KAFKA-4497: --- Hi, We have hit this issue in one of our test environments

[jira] [Commented] (KAFKA-4550) current trunk unstable

[ https://issues.apache.org/jira/browse/KAFKA-4550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15795573#comment-15795573 ] Guozhang Wang commented on KAFKA-4550: -- I'm re-opening

[jira] [Commented] (KAFKA-4528) Failure in kafka.producer.ProducerTest.testAsyncSendCanCorrectlyFailWithTimeout

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

[jira] [Updated] (KAFKA-4528) Failure in kafka.producer.ProducerTest.testAsyncSendCanCorrectlyFailWithTimeout

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

[GitHub] kafka pull request #2298: KAFKA-4528: Fix failure in ProducerTest.testAsyncS...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2298 --- 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-4466) Add support to ducktape to run only a part of all tests

[ https://issues.apache.org/jira/browse/KAFKA-4466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raghav Kumar Gautam updated KAFKA-4466: --- Assignee: Ewen Cheslack-Postava > Add support to ducktape to run only a part of all

[jira] [Resolved] (KAFKA-4466) Add support to ducktape to run only a part of all tests

[ https://issues.apache.org/jira/browse/KAFKA-4466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raghav Kumar Gautam resolved KAFKA-4466. Resolution: Fixed > Add support to ducktape to run only a part of all tests >

[jira] [Commented] (KAFKA-4466) Add support to ducktape to run only a part of all tests

[ https://issues.apache.org/jira/browse/KAFKA-4466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15795601#comment-15795601 ] Raghav Kumar Gautam commented on KAFKA-4466: Thanks [~ewencp] for adding the support to

[jira] [Commented] (KAFKA-2434) remove roundrobin identical topic constraint in consumer coordinator (old API)

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

[jira] [Resolved] (KAFKA-4582) KStream job fails in multi-thread mode

[ https://issues.apache.org/jira/browse/KAFKA-4582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-4582. Resolution: Duplicate > KStream job fails in multi-thread mode >

[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=15795576#comment-15795576 ] Guozhang Wang commented on KAFKA-4222: -- Re-opening this issue as we have seen it happen again with a

[jira] [Updated] (KAFKA-2434) remove roundrobin identical topic constraint in consumer coordinator (old API)

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

[jira] [Commented] (KAFKA-2394) Use RollingFileAppender by default in log4j.properties

[ https://issues.apache.org/jira/browse/KAFKA-2394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15795530#comment-15795530 ] Gérald Quintana commented on KAFKA-2394: It would be great to be able to mix time based and size

[GitHub] kafka pull request #145: KAFKA-2434: Remove identical topic subscription con...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/145 --- 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-4582) KStream job fails in multi-thread mode

[ https://issues.apache.org/jira/browse/KAFKA-4582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15795551#comment-15795551 ] Matthias J. Sax commented on KAFKA-4582: [~manudb9] Thanks for reporting! This should be fixed

Re: [VOTE] KIP-99: Add Global Tables to Kafka Streams

Thank Guozhang, i've updated the KIP based on the discussion. On Fri, 30 Dec 2016 at 01:33 Guozhang Wang wrote: > Besides my comments on the other DISCUSS email thread, I'm +1. > > > On Mon, Dec 12, 2016 at 9:32 AM, Bill Bejeck wrote: > > > +1 > > > > On

[VOTE] KIP-101: Alter Replication Protocol to use Leader Generation rather than High Watermark for Truncation

Hi All Happy New Year! Hopefully everyone has had an opportunity to review this KIP now, if they wished to, so I'd like to call a vote. As a reminder the KIP proposes a change to the replication protocol to remove the potential for replicas to diverge.

Re: [DISCUSS] KIP-66 Kafka Connect Transformers for messages

Makes sense Ewen, I edited the KIP to include this criteria. I'd like to start a voting thread soon unless anyone has additional points for discussion. On Fri, Dec 30, 2016 at 12:14 PM Ewen Cheslack-Postava wrote: On Thu, Dec 15, 2016 at 7:41 PM, Shikhar Bhushan

Re: [VOTE] KIP-99: Add Global Tables to Kafka Streams

+1 I'm glad this super-common use-case will become more performant now. On Mon, Dec 12, 2016 at 3:45 AM, Damian Guy wrote: > Hi all, > > I'd like to start the vote for KIP-99: > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=67633649 > > There is a PR for

Re: [DISCUSS] Dormant/Inactive KIPs

+1. This is a good idea as we have a lot of KIPs in flight. On Tue, Dec 13, 2016 at 3:53 AM Ismael Juma wrote: > Hi all, > > A while back Grant proposed moving inactive/dormant KIPs to a separate > table in the wiki. I think this is a good idea as it will make it easier > for

Re: [VOTE] KIP-99: Add Global Tables to Kafka Streams

+1 (binding) On Tue, Jan 3, 2017 at 11:40 AM Ewen Cheslack-Postava wrote: > +1 > > -Ewen > > On Tue, Jan 3, 2017 at 11:16 AM, Gwen Shapira wrote: > > > +1 > > > > I'm glad this super-common use-case will become more performant now. > > > > On Mon, Dec 12,

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

See Changes: [ismael] KAFKA-4318; Migrate ProducerSendTest to the new consumer -- [...truncated 32970 lines...] org.apache.kafka.streams.KafkaStreamsTest >

Re: [DISCUSS] KIP-106 - Change Default unclean.leader.election.enabled from True to False

Big +1. On Tue, Jan 3, 2017 at 11:22 AM Tom Crayford wrote: > +1. We've been running it in production for a long time and it's the right > default. > > On Tue, Jan 3, 2017 at 7:17 PM, Ismael Juma wrote: > > > Thanks for the KIP, +1 from me. > > > >

Build problems in Eclipse dev environment setup

Hi, I am trying to setup the eclipse dev environment on trunk. I have followed the instructions given here https://github.com/apache/kafka/blob/trunk/README.md https://cwiki.apache.org/confluence/display/KAFKA/Developer+Setup#DeveloperSetup-Eclipsesetup After I run ./gradlew eclipse in the

[DISCUSS] KIP-106 - Change Default unclean.leader.election.enabled from True to False

Hi All Please find the below KIP which proposes changing the setting unclean.leader.election.enabled from true to false. The motivation for this change is that it catches out new Kafka users who don’t realise the default favours availability over data loss. This would mean clusters wishing to

[jira] [Commented] (KAFKA-4404) Add knowledge of sign to numeric schema types

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

[jira] [Updated] (KAFKA-4584) Fail the 'kafka-configs' command if the config to be removed does not exist

[ https://issues.apache.org/jira/browse/KAFKA-4584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vahid Hashemian updated KAFKA-4584: --- Description: With [KAFKA-4480|https://issues.apache.org/jira/browse/KAFKA-4480], the

[jira] [Created] (KAFKA-4584) Fail the 'kafka-configs' command if the config to be removed does not exist

Vahid Hashemian created KAFKA-4584: -- Summary: Fail the 'kafka-configs' command if the config to be removed does not exist Key: KAFKA-4584 URL: https://issues.apache.org/jira/browse/KAFKA-4584

Re: [DISCUSS] KIP-106 - Change Default unclean.leader.election.enabled from True to False

I strongly support this. I've seen many users and customers accidentally lose data because they didn't know this configuration exists. I always support defaulting to "Not lose data" and let the users who prefer high availability do some extra research. This will need to be very well documented -

Re: [DISCUSS] KIP-104: Granular Sensors for Streams

Thanks for the proposed KIP. Overall LGTM. A few comments: 1. "at the granularity of each processor node, in the addition to the global rate" I think you also add one sensor at the granularity of tasks, "Skipped records sensor in StreamTask" right? 2. From PR 1446 it seems you have also added

Re: [DISCUSS] KIP-106 - Change Default unclean.leader.election.enabled from True to False

+1. We've been running it in production for a long time and it's the right default. On Tue, Jan 3, 2017 at 7:17 PM, Ismael Juma wrote: > Thanks for the KIP, +1 from me. > > Ismael > > On 3 Jan 2017 6:54 pm, "Ben Stopford" wrote: > > > Hi All > > > > Please

[jira] [Commented] (KAFKA-3209) Support single message transforms in Kafka Connect

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

Re: [VOTE] KIP-99: Add Global Tables to Kafka Streams

+1 -Ewen On Tue, Jan 3, 2017 at 11:16 AM, Gwen Shapira wrote: > +1 > > I'm glad this super-common use-case will become more performant now. > > On Mon, Dec 12, 2016 at 3:45 AM, Damian Guy wrote: > > Hi all, > > > > I'd like to start the vote for

Re: [DISCUSS] KIP-106 - Change Default unclean.leader.election.enabled from True to False

+1 On Tue, Jan 3, 2017 at 1:12 PM, Sriram Subramanian wrote: > +1 > > On Tue, Jan 3, 2017 at 11:56 AM, Ian Wrigley wrote: > > > +1 from me too. When I talk to people in training classes, who are > > typically much newer to Kafka, they tend to be surprised

Re: [DISCUSS] KIP 88: OffsetFetch Protocol Update

I also prefer option 1. Ismael On Fri, Dec 16, 2016 at 7:11 PM, Jason Gustafson wrote: > Thanks Vahid. To clarify the impact of this issue, since we have no way to > send an error code in the OffsetFetchResponse when requesting all offsets, > we cannot detect when the

[jira] [Resolved] (KAFKA-4258) Page not found http://kafka.apache.org/streams.html

[ https://issues.apache.org/jira/browse/KAFKA-4258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-4258. -- Resolution: Invalid Assignee: Ewen Cheslack-Postava [~adyachkov] Did that

[jira] [Updated] (KAFKA-3429) Remove Serdes needed for repartitioning in KTable stateful operations

[ https://issues.apache.org/jira/browse/KAFKA-3429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-3429: --- Assignee: (was: Matthias J. Sax) > Remove Serdes needed for repartitioning in KTable

[jira] [Created] (KAFKA-4586) Add purgeDataBefore() API in AdminClient

Dong Lin created KAFKA-4586: --- Summary: Add purgeDataBefore() API in AdminClient Key: KAFKA-4586 URL: https://issues.apache.org/jira/browse/KAFKA-4586 Project: Kafka Issue Type: New Feature

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

See Changes: [jason] KAFKA-4429; Consumer lag metric should be zero if FetchResponse is empty -- [...truncated 3886 lines...] kafka.log.LogTest > testReadWithTooSmallMaxLength STARTED

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

Dong, Looks like that's an internal link, https://cwiki.apache.org/confluence/display/KAFKA/KIP-107%3A+Add+purgeDataBefore%28%29+API+in+AdminClient is the right one. I have a question about one of the rejected alternatives: > Using committed offset instead of an extra API to trigger data purge

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

Ewen Cheslack-Postava created KAFKA-4585: Summary: Offset fetch and commit requests use the same permissions Key: KAFKA-4585 URL: https://issues.apache.org/jira/browse/KAFKA-4585 Project:

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

[ https://issues.apache.org/jira/browse/KAFKA-4585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15796353#comment-15796353 ] Vahid Hashemian commented on KAFKA-4585: [~ewencp] Sure, I'd be happy to take a look. Thanks! >

[jira] [Updated] (KAFKA-4171) Kafka-connect prints outs keystone and truststore password in log2

[ https://issues.apache.org/jira/browse/KAFKA-4171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-4171: - Fix Version/s: 0.10.2.0 > Kafka-connect prints outs keystone and truststore

[jira] [Assigned] (KAFKA-4572) Kafka connect for windows is missing

[ https://issues.apache.org/jira/browse/KAFKA-4572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vahid Hashemian reassigned KAFKA-4572: -- Assignee: Vahid Hashemian (was: Ewen Cheslack-Postava) > Kafka connect for windows is

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

[ https://issues.apache.org/jira/browse/KAFKA-4585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15796326#comment-15796326 ] Ewen Cheslack-Postava commented on KAFKA-4585: -- [~vahid] I noticed this issue when looking at

[jira] [Resolved] (KAFKA-4261) Provide debug option in vagrant-up.sh

[ https://issues.apache.org/jira/browse/KAFKA-4261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-4261. -- Resolution: Fixed Fix Version/s: (was: 0.11.0.0)

  1   2   >