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

See

[jira] [Updated] (KAFKA-4102) Is kafka mirror maker in 0.10.X don't support mirror kafka 0.8.X?

[ https://issues.apache.org/jira/browse/KAFKA-4102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yf updated KAFKA-4102: -- Description: I want this feature (https://cwiki.apache.org/confluence/display/KAFKA/KIP-3+-+Mirror+Maker+Enhancement)

[jira] [Updated] (KAFKA-4102) Is kafka mirror maker in 0.10.X don't support mirror kafka 0.8.X?

[ https://issues.apache.org/jira/browse/KAFKA-4102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yf updated KAFKA-4102: -- Description: I want this feature (https://cwiki.apache.org/confluence/display/KAFKA/KIP-3+-+Mirror+Maker+Enhancement)

[jira] [Created] (KAFKA-4102) Is kafka mirror maker in 0.10.X don't support mirror kafka 0.8.X?

yf created KAFKA-4102: - Summary: Is kafka mirror maker in 0.10.X don't support mirror kafka 0.8.X? Key: KAFKA-4102 URL: https://issues.apache.org/jira/browse/KAFKA-4102 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-4100) Connect Struct schemas built using SchemaBuilder with no fields cause NPE in Struct constructor

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

[GitHub] kafka pull request #1800: KAFKA-4100: ensure 'fields' and 'fieldsByName' are...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1800 --- 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] [Resolved] (KAFKA-4100) Connect Struct schemas built using SchemaBuilder with no fields cause NPE in Struct constructor

[ https://issues.apache.org/jira/browse/KAFKA-4100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-4100. -- Resolution: Fixed Issue resolved by pull request 1800

[jira] [Comment Edited] (KAFKA-4101) java.lang.IllegalStateException in org.apache.kafka.common.network.Selector.channelOrFail

[ https://issues.apache.org/jira/browse/KAFKA-4101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15447337#comment-15447337 ] Jason Gustafson edited comment on KAFKA-4101 at 8/29/16 11:03 PM: --

[jira] [Commented] (KAFKA-4101) java.lang.IllegalStateException in org.apache.kafka.common.network.Selector.channelOrFail

[ https://issues.apache.org/jira/browse/KAFKA-4101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15447337#comment-15447337 ] Jason Gustafson commented on KAFKA-4101: [~andrey-sra] I think this might be fixed by KAFKA-3341

[jira] [Work started] (KAFKA-4100) Connect Struct schemas built using SchemaBuilder with no fields cause NPE in Struct constructor

[ https://issues.apache.org/jira/browse/KAFKA-4100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-4100 started by Shikhar Bhushan. -- > Connect Struct schemas built using SchemaBuilder with no fields cause NPE

[jira] [Commented] (KAFKA-4099) Change the time based log rolling to base on the file create time instead of timestamp of the first message.

[ https://issues.apache.org/jira/browse/KAFKA-4099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15447253#comment-15447253 ] Jiangjie Qin commented on KAFKA-4099: - [~junrao] I am thinking about this solution. It seems still not

[jira] [Created] (KAFKA-4101) java.lang.IllegalStateException in org.apache.kafka.common.network.Selector.channelOrFail

Andrey Savov created KAFKA-4101: --- Summary: java.lang.IllegalStateException in org.apache.kafka.common.network.Selector.channelOrFail Key: KAFKA-4101 URL: https://issues.apache.org/jira/browse/KAFKA-4101

[jira] [Commented] (KAFKA-4100) Connect Struct schemas built using SchemaBuilder with no fields cause NPE in Struct constructor

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

[GitHub] kafka pull request #1800: KAFKA-4100: ensure 'fields' and 'fieldsByName' are...

GitHub user shikhar opened a pull request: https://github.com/apache/kafka/pull/1800 KAFKA-4100: ensure 'fields' and 'fieldsByName' are not null for Struct schemas You can merge this pull request into a Git repository by running: $ git pull https://github.com/shikhar/kafka

[jira] [Created] (KAFKA-4100) Connect Struct schemas built using SchemaBuilder with no fields cause NPE in Struct constructor

Shikhar Bhushan created KAFKA-4100: -- Summary: Connect Struct schemas built using SchemaBuilder with no fields cause NPE in Struct constructor Key: KAFKA-4100 URL: https://issues.apache.org/jira/browse/KAFKA-4100

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

See

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

See Changes: [me] KAFKA-4098: NetworkClient should not intercept user metdata requests on -- [...truncated 336 lines...] Download

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

GitHub user hjafarpour opened a pull request: https://github.com/apache/kafka/pull/1799 Kafka 4060 remove zk client dependency in kafka streams Removed Zookeeper client from the Kafka Streams. The internal topic manager now will use Kafka Client to create/delete internal topics.

[jira] [Commented] (KAFKA-4081) Consumer API consumer new interface commitSyn does not verify the validity of offset

[ https://issues.apache.org/jira/browse/KAFKA-4081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15447017#comment-15447017 ] Jason Gustafson commented on KAFKA-4081: I think it definitely makes sense to reject negative

[jira] [Created] (KAFKA-4099) Change the time based log rolling to base on the file create time instead of timestamp of the first message.

Jiangjie Qin created KAFKA-4099: --- Summary: Change the time based log rolling to base on the file create time instead of timestamp of the first message. Key: KAFKA-4099 URL:

[jira] [Resolved] (KAFKA-4098) NetworkClient should not intercept all metadata requests on disconnect

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

[jira] [Commented] (KAFKA-4098) NetworkClient should not intercept all metadata requests on disconnect

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

[GitHub] kafka pull request #1798: KAFKA-4098: NetworkClient should not intercept use...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1798 --- 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-4098) NetworkClient should not intercept all metadata requests on disconnect

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

[GitHub] kafka pull request #1798: KAFKA-4098: NetworkClient should not intercept use...

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/1798 KAFKA-4098: NetworkClient should not intercept user metdata requests on disconnect You can merge this pull request into a Git repository by running: $ git pull

Re: [DISCUSS] Remove beta label from the new Java consumer

+1 I talk to a lot of kafka users, and I would say > 75% of people doing new things are on the new consumer despite our warnings :-) -Jay On Thu, Aug 25, 2016 at 2:05 PM, Jason Gustafson wrote: > I'm +1 also. I feel a lot more confident about this with all of the system >

[jira] [Created] (KAFKA-4098) NetworkClient should not intercept all metadata requests on disconnect

Jason Gustafson created KAFKA-4098: -- Summary: NetworkClient should not intercept all metadata requests on disconnect Key: KAFKA-4098 URL: https://issues.apache.org/jira/browse/KAFKA-4098 Project:

[GitHub] kafka pull request #1787: KAFKA-3940 Log should check the return value of di...

GitHub user imandhan reopened a pull request: https://github.com/apache/kafka/pull/1787 KAFKA-3940 Log should check the return value of dir.mkdirs() You can merge this pull request into a Git repository by running: $ git pull https://github.com/imandhan/kafka KAFKA-3940

[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=15446621#comment-15446621 ] ASF GitHub Bot commented on KAFKA-3940: --- GitHub user imandhan reopened a pull request:

Re: Batch Expired

Hi, RequestTimeout is used for 2 cases : 1) Timing out the batches sitting in the accumulator. 2) Requests that are already sent over the wire and you have not yet heard from the server. In a case where there is a network partition, the client might not detect it, till the actual TCP timeout

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

[GitHub] kafka pull request #1787: KAFKA-3940 Log should check the return value of di...

Github user imandhan closed the pull request at: https://github.com/apache/kafka/pull/1787 --- 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-4062) Require --print-data-log if --offsets-decoder is enabled for DumpLogOffsets

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

[GitHub] kafka pull request #1797: KAFKA-4062: Require --print-data-log if --offsets-...

GitHub user cotedm opened a pull request: https://github.com/apache/kafka/pull/1797 KAFKA-4062: Require --print-data-log if --offsets-decoder is enabled for DumpLogOffsets set print-data-log option when offset-decoder is set. @hachikuji we had talked about this one before, does

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

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

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

GitHub user cotedm opened a pull request: https://github.com/apache/kafka/pull/1796 KAFKA-4092: retention.bytes should not be allowed to be less than segment.bytes adding a LogConfig value validator. @gwenshap or @junrao would you mind taking a look? You can merge this pull

Reg: DefaultParititioner in Kafka

Hi All, In DefaultPartitioner implementation, when key is null, we get the partition number by modulo of available partitions. Below is the code snippet. if (availablePartitions.size() > 0) { int part = Utils.toPositive(nextValue) % availablePartitions.size(); return

Re: [DISCUSS] KIP-78: Cluster Id

Ismael, What happens when the cluster.id changes from initial value. Ex, Users changed their zookeeper.root and now new cluster.id generated. Do you think it would be useful to store this in meta.properties along with broker.id. So that we only generate it once and store it in disk.

Re: [DISCUSS] Remove beta label from the new Java consumer

New consumer API haven't taken a wide adoption yet from my experience with users. We at Storm recently shipped the new consumer API spout and its probably good idea wait a one more minor release before removing the beta label. I am ok with either way. Thanks, Harsha On Thu, Aug 25, 2016 at 2:05

[jira] [Commented] (KAFKA-156) Messages should not be dropped when brokers are unavailable

[ https://issues.apache.org/jira/browse/KAFKA-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15446486#comment-15446486 ] Jason Gustafson commented on KAFKA-156: --- [~dpnchl] KAFKA-789 is already resolved as a duplicate of

[jira] [Updated] (KAFKA-3538) Abstract the creation/retrieval of Producer for stream sinks for unit testing

[ https://issues.apache.org/jira/browse/KAFKA-3538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-3538: Affects Version/s: (was: 0.10.1.0) 0.10.0.0 Issue Type:

[jira] [Commented] (KAFKA-4091) Unable to produce or consume on any topic

[ https://issues.apache.org/jira/browse/KAFKA-4091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15446460#comment-15446460 ] Jason Gustafson commented on KAFKA-4091: [~datawiz...@gmail.com] It seems possible that Kafka had

Re: [VOTE] KIP-77: Improve Kafka Streams Join Semantics

+1 (non-binding) > On 29 Aug 2016, at 12:22, Bill Bejeck wrote: > > +1 > > On Mon, Aug 29, 2016 at 5:50 AM, Matthias J. Sax > wrote: > >> I’d like to initiate the voting process for KIP-77: >> >>

RE: Batch Expired

Hi Krishna, Thank you for your response. Connections already made but if we increase the request timeout 5 times let's say request.timeout.ms= 5*6 , then the number of 'Batch Expired ' exception is less, so what is the recommended value for ' request.timeout.ms '. If we increase more, is

[jira] [Assigned] (KAFKA-4095) When a topic is deleted and then created with the same name, 'committed' offsets are not reset

[ https://issues.apache.org/jira/browse/KAFKA-4095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vahid Hashemian reassigned KAFKA-4095: -- Assignee: Vahid Hashemian > When a topic is deleted and then created with the same

[jira] [Commented] (KAFKA-4095) When a topic is deleted and then created with the same name, 'committed' offsets are not reset

[ https://issues.apache.org/jira/browse/KAFKA-4095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15446292#comment-15446292 ] Vahid Hashemian commented on KAFKA-4095: I can take a look at this. > When a topic is deleted and

[jira] [Updated] (KAFKA-4097) "Server not found in kerberos database" issue while starting a Kafka server in a secured mode

[ https://issues.apache.org/jira/browse/KAFKA-4097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-4097: - Component/s: (was: KafkaConnect) > "Server not found in kerberos database"

[jira] [Updated] (KAFKA-4097) "Server not found in kerberos database" issue while starting a Kafka server in a secured mode

[ https://issues.apache.org/jira/browse/KAFKA-4097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-4097: - Assignee: (was: Ewen Cheslack-Postava) > "Server not found in kerberos

[jira] [Commented] (KAFKA-3129) Console producer issue when request-required-acks=0

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

[jira] [Assigned] (KAFKA-3129) Console producer issue when request-required-acks=0

[ https://issues.apache.org/jira/browse/KAFKA-3129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dustin Cote reassigned KAFKA-3129: -- Assignee: Dustin Cote (was: Neha Narkhede) > Console producer issue when

[GitHub] kafka pull request #1795: KAFKA-3129: Console producer issue when request-re...

GitHub user cotedm opened a pull request: https://github.com/apache/kafka/pull/1795 KAFKA-3129: Console producer issue when request-required-acks=0 change console producer default acks to 1, update acks docs. Also added the -1 config to the acks docs since that question comes up

[jira] [Commented] (KAFKA-4097) "Server not found in kerberos database" issue while starting a Kafka server in a secured mode

[ https://issues.apache.org/jira/browse/KAFKA-4097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15445637#comment-15445637 ] syam prasad commented on KAFKA-4097: Sorry. I have missed adding this property in my last update under

[jira] [Commented] (KAFKA-4097) "Server not found in kerberos database" issue while starting a Kafka server in a secured mode

[ https://issues.apache.org/jira/browse/KAFKA-4097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15445644#comment-15445644 ] syam prasad commented on KAFKA-4097: By list_principals command in kadmin window, I was able to see

[jira] [Updated] (KAFKA-4097) "Server not found in kerberos database" issue while starting a Kafka server in a secured mode

[ https://issues.apache.org/jira/browse/KAFKA-4097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] syam prasad updated KAFKA-4097: --- Summary: "Server not found in kerberos database" issue while starting a Kafka server in a secured

[jira] [Commented] (KAFKA-4097) "Server not found in kerberos database" issue while starting Kafka broker in secured mode

[ https://issues.apache.org/jira/browse/KAFKA-4097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15445624#comment-15445624 ] syam prasad commented on KAFKA-4097: Hi, Zookeeper was started well in a secured mode (as I can see

[jira] [Updated] (KAFKA-4097) "Server not found in kerberos database" issue while starting Kafka broker in secured mode

[ https://issues.apache.org/jira/browse/KAFKA-4097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] syam prasad updated KAFKA-4097: --- Summary: "Server not found in kerberos database" issue while starting Kafka broker in secured mode

[jira] [Created] (KAFKA-4097) Server not found in kerberos database while starting Kafka broker in secured mode

syam prasad created KAFKA-4097: -- Summary: Server not found in kerberos database while starting Kafka broker in secured mode Key: KAFKA-4097 URL: https://issues.apache.org/jira/browse/KAFKA-4097 Project:

Re: [VOTE] KIP-77: Improve Kafka Streams Join Semantics

+1 On Mon, Aug 29, 2016 at 5:50 AM, Matthias J. Sax wrote: > I’d like to initiate the voting process for KIP-77: > > https://cwiki.apache.org/confluence/display/KAFKA/KIP- > 77%3A+Improve+Kafka+Streams+Join+Semantics > > -Matthias > > >

[VOTE] KIP-77: Improve Kafka Streams Join Semantics

I’d like to initiate the voting process for KIP-77: https://cwiki.apache.org/confluence/display/KAFKA/KIP-77%3A+Improve+Kafka+Streams+Join+Semantics -Matthias signature.asc Description: OpenPGP digital signature