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

2016-12-27 Thread Apache Jenkins Server
See

[jira] [Created] (KAFKA-4571) Consumer fails to retrieve messages if started before producer

2016-12-27 Thread Sergiu Hlihor (JIRA)
Sergiu Hlihor created KAFKA-4571: Summary: Consumer fails to retrieve messages if started before producer Key: KAFKA-4571 URL: https://issues.apache.org/jira/browse/KAFKA-4571 Project: Kafka

[jira] [Resolved] (KAFKA-4092) retention.bytes should not be allowed to be less than segment.bytes

2016-12-27 Thread Ewen Cheslack-Postava (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-4092. -- Resolution: Fixed Reviewer: Ewen Cheslack-Postava Fix Version/s:

[jira] [Commented] (KAFKA-4092) retention.bytes should not be allowed to be less than segment.bytes

2016-12-27 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15781163#comment-15781163 ] ASF GitHub Bot commented on KAFKA-4092: --- Github user asfgit closed the pull request at:

[GitHub] kafka pull request #1796: KAFKA-4092: retention.bytes should not be allowed ...

2016-12-27 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1796 --- 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-3601) fail fast when newer client connecting to older server

2016-12-27 Thread Chris Pennello (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15780762#comment-15780762 ] Chris Pennello commented on KAFKA-3601: --- KAFKA-3600 is closed via

Re: custom offsets in ProduceRequest

2016-12-27 Thread radai
IIUC if you replicate from a single source cluster to a single target cluster, the topic has the same number of partitions on both, and no one writes directly to the target cluster (so master --> slave) the offsets would be preserved. but in the general case - how would you handle the case where

[jira] [Commented] (KAFKA-4477) Node reduces its ISR to itself, and doesn't recover. Other nodes do not take leadership, cluster remains sick until node is restarted.

2016-12-27 Thread Niles Hiray (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15780738#comment-15780738 ] Niles Hiray commented on KAFKA-4477: We are facing this issue on our systems too. Does 0.10.1.1

[jira] [Commented] (KAFKA-2260) Allow specifying expected offset on produce

2016-12-27 Thread Bill Warshaw (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-2260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15780697#comment-15780697 ] Bill Warshaw commented on KAFKA-2260: - [~ijuma] it seems like we would be able to satisfy this use

Experiencing trouble with KafkaCSVMetricsReporter

2016-12-27 Thread Dongjin Lee
In short: the resulting csv files from the brokers are filled with 0 only, although the broker cluster is running correctly. Hello. I am trying some benchmarks with KAFKA-4514[^1]. However, My KafkaCSVMetricsReporter is not working properly. I would like to ask if someone on this mailing list

[jira] [Created] (KAFKA-4570) How to transfer extended fields in producing or consuming requests.

2016-12-27 Thread zander (JIRA)
zander created KAFKA-4570: - Summary: How to transfer extended fields in producing or consuming requests. Key: KAFKA-4570 URL: https://issues.apache.org/jira/browse/KAFKA-4570 Project: Kafka Issue

[jira] [Commented] (KAFKA-4180) Shared authentication with multiple active Kafka producers/consumers

2016-12-27 Thread Edoardo Comar (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15780212#comment-15780212 ] Edoardo Comar commented on KAFKA-4180: -- Now that https://issues.apache.org/jira/browse/KAFKA-4259 has

[jira] [Commented] (KAFKA-4180) Shared authentication with multiple active Kafka producers/consumers

2016-12-27 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15780202#comment-15780202 ] ASF GitHub Bot commented on KAFKA-4180: --- GitHub user edoardocomar opened a pull request:

[GitHub] kafka pull request #2293: KAFKA-4180 : Authentication with multiple actives ...

2016-12-27 Thread edoardocomar
GitHub user edoardocomar opened a pull request: https://github.com/apache/kafka/pull/2293 KAFKA-4180 : Authentication with multiple actives Kafka producers/consumers Changed caching in LoginManager to allow one LoginManager per client JAAS configuration. Added test

[jira] [Commented] (KAFKA-4180) Shared authentication with multiple active Kafka producers/consumers

2016-12-27 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15780150#comment-15780150 ] ASF GitHub Bot commented on KAFKA-4180: --- Github user edoardocomar closed the pull request at:

[GitHub] kafka pull request #1989: Kafka 4180 - Shared authentification with multiple...

2016-12-27 Thread edoardocomar
Github user edoardocomar closed the pull request at: https://github.com/apache/kafka/pull/1989 --- 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

[GitHub] kafka pull request #2292: MINOR: Update rocksDB dependency to 4.13.5

2016-12-27 Thread jozi-k
GitHub user jozi-k opened a pull request: https://github.com/apache/kafka/pull/2292 MINOR: Update rocksDB dependency to 4.13.5 You can merge this pull request into a Git repository by running: $ git pull https://github.com/jozi-k/kafka update-rocksdb-4.13.5 Alternatively you