Re: [VOTE] 0.10.0.1 RC2

+1 (non-binding) On Thu, Aug 4, 2016 at 6:54 AM, Ismael Juma wrote: > Hello Kafka users, developers and client-developers, > > This is the third candidate for the release of Apache Kafka 0.10.0.1. This > is a bug fix release and it includes fixes and improvements from 53 JIRAs

Re: Request: Please add me to contributor list.

Hello, Just trying to follow up on the request to add me to the contributor list. Please let me know if more information is required. Chetan Singh chetanjbsi...@gmail.com On Mon, Aug 1, 2016 at 7:11 AM, chetan singh wrote: > Hello, > > I am interested in contributing

[jira] [Resolved] (KAFKA-3518) Transient failure in ReplicationTest.test_replication_with_broker_failure with ConsumerTimeoutException

[ https://issues.apache.org/jira/browse/KAFKA-3518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-3518. Resolution: Cannot Reproduce Closing the jira since it's likely fixed by KAFKA-3670. > Transient failure

[jira] [Commented] (KAFKA-3518) Transient failure in ReplicationTest.test_replication_with_broker_failure with ConsumerTimeoutException

[ https://issues.apache.org/jira/browse/KAFKA-3518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15408738#comment-15408738 ] Ewen Cheslack-Postava commented on KAFKA-3518: -- [~junrao] If this case seems to be either

[jira] [Commented] (KAFKA-3518) Transient failure in ReplicationTest.test_replication_with_broker_failure with ConsumerTimeoutException

[ https://issues.apache.org/jira/browse/KAFKA-3518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15408726#comment-15408726 ] Jun Rao commented on KAFKA-3518: Took a look at the log. The following are my findings. >From report.txt,

[jira] [Created] (KAFKA-4021) system tests need to enable trace level logging for controller and state-change log

Jun Rao created KAFKA-4021: -- Summary: system tests need to enable trace level logging for controller and state-change log Key: KAFKA-4021 URL: https://issues.apache.org/jira/browse/KAFKA-4021 Project: Kafka

[jira] [Commented] (KAFKA-3665) Default ssl.endpoint.identification.algorithm should be https

[ https://issues.apache.org/jira/browse/KAFKA-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15408544#comment-15408544 ] Ryan P commented on KAFKA-3665: --- [~junrao] yes I do think that SNI is still relevant despite the presence of

[jira] [Created] (KAFKA-4019) LogCleaner should grow read/write buffer to max message size for the topic

Jun Rao created KAFKA-4019: -- Summary: LogCleaner should grow read/write buffer to max message size for the topic Key: KAFKA-4019 URL: https://issues.apache.org/jira/browse/KAFKA-4019 Project: Kafka

[jira] [Created] (KAFKA-4020) Kafka consumer stop taking messages from kafka server

Shawn He created KAFKA-4020: --- Summary: Kafka consumer stop taking messages from kafka server Key: KAFKA-4020 URL: https://issues.apache.org/jira/browse/KAFKA-4020 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-3989) Add JMH module for Benchmarks

[ https://issues.apache.org/jira/browse/KAFKA-3989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15408276#comment-15408276 ] Bill Bejeck commented on KAFKA-3989: Yes, the classpath entry is in the 'buildscript section. To me,

[DISCUSS] KIP-72 Allow Sizing Incoming Request Queue in Bytes

Hello, I'd like to initiate a discussion about https://cwiki.apache.org/confluence/display/KAFKA/KIP-72%3A+Allow+Sizing+Incoming+Request+Queue+in+Bytes The goal of the KIP is to allow configuring a bound on the capacity (as in bytes of memory used) of the incoming request queue, in addition to

Re: [GitHub] kafka pull request #1661: KAFKA-3987: Allow config of the hash algorithm use...

Hi Could you please tell me if this pull request can be merged and if so when can we expect this to happen? Thanks Luciano On Tue, Jul 26, 2016 at 9:01 AM, Luciano Afranllie wrote: > Hi > > Could somebody with commit permission review (and eventually merge) this >

[jira] [Commented] (KAFKA-3989) Add JMH module for Benchmarks

[ https://issues.apache.org/jira/browse/KAFKA-3989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15408067#comment-15408067 ] Ismael Juma commented on KAFKA-3989: Is the former in the `buildscript` section? If so, that seems

[jira] [Updated] (KAFKA-3894) LogCleaner thread crashes if not even one segment can fit in the offset map

[ https://issues.apache.org/jira/browse/KAFKA-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3894: --- Summary: LogCleaner thread crashes if not even one segment can fit in the offset map (was:

[jira] [Updated] (KAFKA-3989) Add JMH module for Benchmarks

[ https://issues.apache.org/jira/browse/KAFKA-3989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Bejeck updated KAFKA-3989: --- Fix Version/s: 0.10.1.0 > Add JMH module for Benchmarks > - > >

[jira] [Commented] (KAFKA-3894) LogCleaner thread crashes if not even one segment can fit in the map

[ https://issues.apache.org/jira/browse/KAFKA-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15408036#comment-15408036 ] Ismael Juma commented on KAFKA-3894: I updated the title to match the issue that is still present in

[jira] [Updated] (KAFKA-3894) LogCleaner thread crashes if not even one segment can fit in the map

[ https://issues.apache.org/jira/browse/KAFKA-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3894: --- Fix Version/s: 0.10.1.0 > LogCleaner thread crashes if not even one segment can fit in the map >

[jira] [Updated] (KAFKA-3894) LogCleaner thread crashes if not even one segment can fit in the map

[ https://issues.apache.org/jira/browse/KAFKA-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3894: --- Affects Version/s: 0.10.0.0 > LogCleaner thread crashes if not even one segment can fit in the map >

[jira] [Updated] (KAFKA-3894) LogCleaner thread crashes if not even one segment can fit in the map

[ https://issues.apache.org/jira/browse/KAFKA-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3894: --- Summary: LogCleaner thread crashes if not even one segment can fit in the map (was: LogCleaner

[jira] [Updated] (KAFKA-3894) LogCleaner thread crashes if the number of unique keys in a segment

[ https://issues.apache.org/jira/browse/KAFKA-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3894: --- Summary: LogCleaner thread crashes if the number of unique keys in a segment (was: Log Cleaner

[jira] [Commented] (KAFKA-4009) Data corruption or EIO leads to data loss

[ https://issues.apache.org/jira/browse/KAFKA-4009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15407990#comment-15407990 ] Jun Rao commented on KAFKA-4009: Thanks for the info. Then, N1 only discovered the issue during log

[jira] [Commented] (KAFKA-3665) Default ssl.endpoint.identification.algorithm should be https

[ https://issues.apache.org/jira/browse/KAFKA-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15407964#comment-15407964 ] Jun Rao commented on KAFKA-3665: [~Ryan P], is SNI really relevant here? According to Rajini, only the

[VOTE] 0.10.0.1 RC2

Hello Kafka users, developers and client-developers, This is the third candidate for the release of Apache Kafka 0.10.0.1. This is a bug fix release and it includes fixes and improvements from 53 JIRAs (including a few critical bugs). See the release notes for more details:

[jira] [Commented] (KAFKA-4017) Return more helpful responses when misconfigured connectors are submitted

[ https://issues.apache.org/jira/browse/KAFKA-4017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15407746#comment-15407746 ] Dustin Cote commented on KAFKA-4017: [~ewencp] yeah that's right. Super easy to reproduce as well,

[jira] [Commented] (KAFKA-3940) Log should check the return value of dir.mkdirs()

[ https://issues.apache.org/jira/browse/KAFKA-3940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15407632#comment-15407632 ] Jim Jagielski commented on KAFKA-3940: -- Could you send over the patch... either via an attachment or

[jira] [Resolved] (KAFKA-3875) Transient test failure: kafka.api.SslProducerSendTest.testSendNonCompressedMessageWithCreateTime

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

[GitHub] kafka pull request #1703: KAFKA-3875: Transient test failure: kafka.api.SslP...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1703 --- 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-3875) Transient test failure: kafka.api.SslProducerSendTest.testSendNonCompressedMessageWithCreateTime

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

[jira] [Commented] (KAFKA-1310) Zookeeper timeout causes deadlock in Controller

[ https://issues.apache.org/jira/browse/KAFKA-1310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15407483#comment-15407483 ] .D. commented on KAFKA-1310: Excuse me, appear this error is how to solve? What principle, each too see? >

[jira] [Commented] (KAFKA-3817) KTableRepartitionMap should handle null inputs

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

[GitHub] kafka pull request #1705: KAFKA-3817: KTableRepartitionMap publish old Chang...

GitHub user Kaiserchen opened a pull request: https://github.com/apache/kafka/pull/1705 KAFKA-3817: KTableRepartitionMap publish old Change first, for non-count aggregates I affirm that the contribution is my original work and that I license the work to the project under the

[jira] [Comment Edited] (KAFKA-2471) Replicas Order and Leader out of sync

[ https://issues.apache.org/jira/browse/KAFKA-2471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15407254#comment-15407254 ] yf edited comment on KAFKA-2471 at 8/4/16 6:15 AM: --- I meet the same problem in the same

[jira] [Comment Edited] (KAFKA-2471) Replicas Order and Leader out of sync

[ https://issues.apache.org/jira/browse/KAFKA-2471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15407254#comment-15407254 ] yf edited comment on KAFKA-2471 at 8/4/16 6:14 AM: --- I meet the same problem in the same

[jira] [Commented] (KAFKA-2471) Replicas Order and Leader out of sync

[ https://issues.apache.org/jira/browse/KAFKA-2471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15407254#comment-15407254 ] yf commented on KAFKA-2471: --- I meet the same problem. But my data in zk is: {"version":1,"partitions":[]} >