[jira] [Commented] (KAFKA-2608) Recommend kafka_2.11 for 0.9.0.0 on the website

[ https://issues.apache.org/jira/browse/KAFKA-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14948193#comment-14948193 ] Rajini Sivaram commented on KAFKA-2608: --- Should the default scala version in scala.gradle used in

[jira] [Commented] (KAFKA-2608) Recommend kafka_2.11 for 0.9.0.0 on the website

[ https://issues.apache.org/jira/browse/KAFKA-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14948209#comment-14948209 ] Ismael Juma commented on KAFKA-2608: I think that's less clear. There are pros and cons, but the

[jira] [Commented] (KAFKA-2608) Recommend kafka_2.11 for 0.9.0.0 on the website

[ https://issues.apache.org/jira/browse/KAFKA-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14948283#comment-14948283 ] Rajini Sivaram commented on KAFKA-2608: --- [~ijuma] No, I agree with your reasoning. We are currently

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

See

[jira] [Created] (KAFKA-2624) Truncate warn message logged after truncating partitions

Francois Visconte created KAFKA-2624: Summary: Truncate warn message logged after truncating partitions Key: KAFKA-2624 URL: https://issues.apache.org/jira/browse/KAFKA-2624 Project: Kafka

[jira] [Updated] (KAFKA-2614) No more clients can connect after `TooManyConnectionsException` threshold (max.connections.per.ip) is reached

[ https://issues.apache.org/jira/browse/KAFKA-2614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-2614: --- Reviewer: Jun Rao Status: Patch Available (was: In Progress) Ready for review [~junrao]. > No

[jira] [Updated] (KAFKA-2624) Truncate warn message logged after truncating partitions

[ https://issues.apache.org/jira/browse/KAFKA-2624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francois Visconte updated KAFKA-2624: - Priority: Trivial (was: Major) > Truncate warn message logged after truncating

[jira] [Commented] (KAFKA-2614) No more clients can connect after `TooManyConnectionsException` threshold (max.connections.per.ip) is reached

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

Re: [DISCUSS] KIP-36 - Rack aware replica assignment

I attended Tuesday's KIP hangout but this KIP was not discussed due to time constraint. However, after hearing discussion of KIP-35, I have the feeling that incompatibility (caused by new broker property) between brokers with different versions will be solved there. In addition, having stack in

[jira] [Commented] (KAFKA-2189) Snappy compression of message batches less efficient in 0.8.2.1

[ https://issues.apache.org/jira/browse/KAFKA-2189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14948989#comment-14948989 ] Andrew Olson commented on KAFKA-2189: - [~jbrosenb...@gmail.com] Yes your assumption is correct, this

[jira] [Commented] (KAFKA-2623) Kakfa broker not deleting logs after configured retention time properly

[ https://issues.apache.org/jira/browse/KAFKA-2623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14949007#comment-14949007 ] Jiangjie Qin commented on KAFKA-2623: - [~hzhang] Yes, this is a known issue and will be solve by

Kafka Mirror to consume data from beginning of topics

Hi there, I am trying to setup a Kafka Mirror mechanism, but it seems the consumer from the source Kafka cluster only reads from new incoming data to the topics, i.e. it does not read historically saved data in the topics. Is there a way to define the consumer of Kafka Mirror to read from the

Re: [DISCUSS] Email to dev list for GitHub PR comments

I too agree with others and think that option 1 is better. On Tue, Oct 6, 2015 at 11:00 PM, Dong Lin wrote: > I agree with Guozhang. > > On Tue, Oct 6, 2015 at 5:49 PM, Gwen Shapira wrote: > > > Agree with Guozhang. > > > > On Tue, Oct 6, 2015 at 3:22

Re: Kafka Mirror to consume data from beginning of topics

Yes, you can have your mirror maker reading from earliest offset by specifying "auto.offset.reset=smallest" in your consumer configuration file which is provided to mirror maker. On Thu, Oct 8, 2015 at 5:49 PM, Clelio De Souza wrote: > Hi there, > > I am trying to setup a

[jira] [Created] (KAFKA-2625) Unable to compile scala 2.10 with java 1.6

Arvind Viswanathan created KAFKA-2625: - Summary: Unable to compile scala 2.10 with java 1.6 Key: KAFKA-2625 URL: https://issues.apache.org/jira/browse/KAFKA-2625 Project: Kafka Issue

[jira] [Commented] (KAFKA-2625) Unable to compile scala 2.10 with java 1.6

[ https://issues.apache.org/jira/browse/KAFKA-2625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14949544#comment-14949544 ] Ismael Juma commented on KAFKA-2625: Kafka now requires Java 7, see KAFKA-2316. > Unable to compile

[jira] [Created] (KAFKA-2626) Null offsets in copycat causes exception in OffsetStorageWriter

Ewen Cheslack-Postava created KAFKA-2626: Summary: Null offsets in copycat causes exception in OffsetStorageWriter Key: KAFKA-2626 URL: https://issues.apache.org/jira/browse/KAFKA-2626

Re: Review Request 33049: Patch for KAFKA-2084

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/33049/#review101976 --- core/src/main/scala/kafka/server/ClientQuotaManager.scala (line

[GitHub] kafka pull request: MINOR: typing ProcessorDef

GitHub user ymatsuda opened a pull request: https://github.com/apache/kafka/pull/289 MINOR: typing ProcessorDef @guozhangwang This code change properly types ProcessorDef. This also makes KStream.process() typesafe. You can merge this pull request into a Git repository by

[jira] [Commented] (KAFKA-2459) Connection backoff/blackout period should start when a connection is disconnected, not when the connection attempt was initiated

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

[GitHub] kafka pull request: KAFKA-2459: connection backoff, timeouts and r...

GitHub user enothereska opened a pull request: https://github.com/apache/kafka/pull/290 KAFKA-2459: connection backoff, timeouts and retries This fix applies to three JIRAs, since they are all connected. KAFKA-2459Connection backoff/blackout period should start when a

Re: [VOTE] KIP-31 - Move to relative offsets in compressed message sets.

The updated upgrade path looks reasonable to me. Not all combinations of the configs are valid though. For example, we probably should disallow message.format.version=1 and intra.cluster.protocol = 0.9.0. Thanks, Jun On Tue, Oct 6, 2015 at 2:58 PM, Jiangjie Qin

[GitHub] kafka pull request: KAFKA-2621; nextOffsetMetadata should be chang...

Github user lindong28 closed the pull request at: https://github.com/apache/kafka/pull/286 --- 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-2621) nextOffsetMetadata should be changed after rolling a new log segment

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