[jira] [Updated] (KAFKA-4942) Kafka Connect: Offset committing times out before expected

[ https://issues.apache.org/jira/browse/KAFKA-4942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephane Maarek updated KAFKA-4942: --- Affects Version/s: 0.10.2.0 Priority: Major (was: Critical)

[jira] [Updated] (KAFKA-4942) Kafka Connect: Offset committing times out before expected

[ https://issues.apache.org/jira/browse/KAFKA-4942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephane Maarek updated KAFKA-4942: --- Description: On Kafka 0.10.2.0 I run a connector that deals with a lot of data, in a kafka

[jira] [Updated] (KAFKA-4942) Kafka Connect: Offset committing times out before expected

[ https://issues.apache.org/jira/browse/KAFKA-4942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephane Maarek updated KAFKA-4942: --- Description: On Kafka 0.10.2.0 I run a connector that deals with a lot of data, in a kafka

[jira] [Created] (KAFKA-4942) Kafka Connect: Offset committing times out before expected

Stephane Maarek created KAFKA-4942: -- Summary: Kafka Connect: Offset committing times out before expected Key: KAFKA-4942 URL: https://issues.apache.org/jira/browse/KAFKA-4942 Project: Kafka

Re: [DISCUSS] KIP-120: Cleanup Kafka Streams builder API

I don't feel strongly on this, so I'm happy with whatever everyone else wants. Michael, I'm not arguing that people don't need to understand topologies, I just think it is like rocks db, you need to understand it when debugging/operating but not in the initial coding since the metaphor we're

Re: [VOTE] KIP-111 Kafka should preserve the Principal generated by the PrincipalBuilder while processing the request received on socket channel, on the broker.

Hi Jun, Please find the replies inline. One reason to have KafkaPrincipal in ACL is that we can extend it to support group in the future. Have you thought about how to support that in your new proposal? ---> This is a feature of PrincipalBuilder and Authorizer, which are pluggable. The type of

[jira] [Created] (KAFKA-4941) Better definition/introduction to the term brokers

Yih Feng Low created KAFKA-4941: --- Summary: Better definition/introduction to the term brokers Key: KAFKA-4941 URL: https://issues.apache.org/jira/browse/KAFKA-4941 Project: Kafka Issue Type:

Offset data fetch in Kafka

Team , Can you help me with hot to use offset in bin/kafka-console-consumer.sh Instead of --from-beginning Like 01/02/2017 to 02/03/2017

[jira] [Updated] (KAFKA-4940) Cluster partially working if broker blocked with IO

[ https://issues.apache.org/jira/browse/KAFKA-4940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Victor Garcia updated KAFKA-4940: - Description: A cluster can partially work if there is an IO issue that blocks the broker process

[jira] [Created] (KAFKA-4940) Cluster partially working if broker blocked with IO

Victor Garcia created KAFKA-4940: Summary: Cluster partially working if broker blocked with IO Key: KAFKA-4940 URL: https://issues.apache.org/jira/browse/KAFKA-4940 Project: Kafka Issue

[jira] [Commented] (KAFKA-2729) Cached zkVersion not equal to that in zookeeper, broker not recovering.

[ https://issues.apache.org/jira/browse/KAFKA-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15937468#comment-15937468 ] Stephane Maarek commented on KAFKA-2729: If I may add, this is a pretty bad issue, but it got

[jira] [Updated] (KAFKA-4939) Kafka does not log NoRouteToHostException in ERROR log level

[ https://issues.apache.org/jira/browse/KAFKA-4939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] radha updated KAFKA-4939: - Description: If you have many brokers in your bootstrap.servers list and some cannot be reached by a specific

[jira] [Updated] (KAFKA-4939) Kafka does not log NoRouteToHostException in ERROR log level

[ https://issues.apache.org/jira/browse/KAFKA-4939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] radha updated KAFKA-4939: - Description: If you have many brokers in your bootstrap.servers list and some cannot be reached by a specific

[jira] [Updated] (KAFKA-4939) Kafka does not log NoRouteToHostException in ERROR log level

[ https://issues.apache.org/jira/browse/KAFKA-4939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] radha updated KAFKA-4939: - Description: If you have many brokers and some cannot be reached by a specific Kafka client for whatever reason,

[jira] [Created] (KAFKA-4939) Kafka does not log NoRouteToHostException in ERROR log level

radha created KAFKA-4939: Summary: Kafka does not log NoRouteToHostException in ERROR log level Key: KAFKA-4939 URL: https://issues.apache.org/jira/browse/KAFKA-4939 Project: Kafka Issue Type: Bug

Jenkins build is back to normal : kafka-0.10.2-jdk7 #110

See

[jira] [Issue Comment Deleted] (KAFKA-4392) Failed to lock the state directory due to an unexpected exception

[ https://issues.apache.org/jira/browse/KAFKA-4392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elias Levy updated KAFKA-4392: -- Comment: was deleted (was: I am still seeing this error in 0.10.2.0 during rebalances. Reopen or

[jira] [Commented] (KAFKA-4392) Failed to lock the state directory due to an unexpected exception

[ https://issues.apache.org/jira/browse/KAFKA-4392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15937388#comment-15937388 ] Elias Levy commented on KAFKA-4392: --- I am still seeing this error in 0.10.2.0 during rebalances. Reopen

[jira] [Commented] (KAFKA-4392) Failed to lock the state directory due to an unexpected exception

[ https://issues.apache.org/jira/browse/KAFKA-4392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15937389#comment-15937389 ] Elias Levy commented on KAFKA-4392: --- I am still seeing this error in 0.10.2.0 during rebalances. Reopen

Re: [DISCUSS] KIP-135 : Send of null key to a compacted topic should throw non-retriable error back to user

Mayuresh, The Compatibility/Migration section says to upgrade the clients first, before the brokers. Are you talking about implementation or deployment? Do you mean to implement the client changes before the broker changes? That would imply that it would take 2 Kafka releases to implement this

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

See

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

See Changes: [wangguoz] MINOR: Improvements on Streams log4j -- [...truncated 19.54 KB...] kafka.log.LogValidatorTest > testCreateTimeUpConversion PASSED

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

See Changes: [cshapi] KAFKA-4929: Transformation Key/Value type references should be to class -- [...truncated 860.24 KB...]

[DISCUSS] KIP-135 : Send of null key to a compacted topic should throw non-retriable error back to user

Hi All, We have created KIP-135 to propose that Kafka should return a non-retriable error when the producer produces a message with null key to a log compacted topic. Please find the KIP wiki in the link :

[jira] [Created] (KAFKA-4938) Creating a connector with missing name parameter throws a NullPointerException

Sönke Liebau created KAFKA-4938: --- Summary: Creating a connector with missing name parameter throws a NullPointerException Key: KAFKA-4938 URL: https://issues.apache.org/jira/browse/KAFKA-4938 Project:

[jira] [Commented] (KAFKA-4930) Connect Rest API allows creating connectors with an empty name

[ https://issues.apache.org/jira/browse/KAFKA-4930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15937220#comment-15937220 ] Sönke Liebau commented on KAFKA-4930: - I've created a potential fix for this issue and pushed to

[GitHub] kafka pull request #2702: MINOR: Improvements on log4j

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2702 --- 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] [Created] (KAFKA-4937) Batch resetting offsets in Streams' StoreChangelogReader

Guozhang Wang created KAFKA-4937: Summary: Batch resetting offsets in Streams' StoreChangelogReader Key: KAFKA-4937 URL: https://issues.apache.org/jira/browse/KAFKA-4937 Project: Kafka Issue

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

See Changes: [wangguoz] MINOR: MyProcessor doc example should implement, not extend `Processor` -- [...truncated 862.25 KB...]

[jira] [Commented] (KAFKA-4929) Transformation Key/Value type references should be to class name(), not canonicalName()

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

[GitHub] kafka pull request #2720: KAFKA-4929: Transformation Key/Value type referenc...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2720 --- 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-4929) Transformation Key/Value type references should be to class name(), not canonicalName()

[ https://issues.apache.org/jira/browse/KAFKA-4929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-4929: Resolution: Fixed Fix Version/s: 0.11.0.0 Status: Resolved (was: Patch Available)

Build failed in Jenkins: kafka-0.10.2-jdk7 #109

See Changes: [wangguoz] MINOR: MyProcessor doc example should implement, not extend `Processor` -- [...truncated 618.30 KB...]

[GitHub] kafka pull request #2724: MINOR: log state store restore offsets

Github user dguy closed the pull request at: https://github.com/apache/kafka/pull/2724 --- 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: [VOTE] KIP-123: Allow per stream/table timestamp extractor

Jeyhun, Could you update the status of this KIP since it has been some time since the last vote? I'm +1 besides the minor comments mentioned above. Guozhang On Mon, Mar 6, 2017 at 3:14 PM, Jeyhun Karimov wrote: > Sorry I was late. I will update javadocs in related

[jira] [Resolved] (KAFKA-4732) Unstable test: KStreamKTableJoinIntegrationTest.shouldCountClicksPerRegion[1]

[ https://issues.apache.org/jira/browse/KAFKA-4732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-4732. -- Resolution: Fixed As part of https://issues.apache.org/jira/browse/KAFKA-4859. > Unstable

[jira] [Assigned] (KAFKA-4732) Unstable test: KStreamKTableJoinIntegrationTest.shouldCountClicksPerRegion[1]

[ https://issues.apache.org/jira/browse/KAFKA-4732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax reassigned KAFKA-4732: -- Assignee: Guozhang Wang (was: Matthias J. Sax) > Unstable test:

Re: [DISCUSS] KIP 130: Expose states of active tasks to KafkaStreams public API

Thanks for the updated KIP, and sorry for the late replies! I think a little bit more about KIP-130, and I feel that if we are going to deprecate the `toString` function (it is not explicitly said in the KIP, so I'm not sure if you plan to still keep the `KafkaStreams#toString` as is or are going

[jira] [Commented] (KAFKA-4912) Add check for topic name length

[ https://issues.apache.org/jira/browse/KAFKA-4912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15936975#comment-15936975 ] Matthias J. Sax commented on KAFKA-4912: I am actually not 100% sure -- I guess, it depends how

[GitHub] kafka pull request #2723: MINOR: MyProcessor doc example should implement, n...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2723 --- 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] [Created] (KAFKA-4936) Allow dynamic routing of output records

Matthias J. Sax created KAFKA-4936: -- Summary: Allow dynamic routing of output records Key: KAFKA-4936 URL: https://issues.apache.org/jira/browse/KAFKA-4936 Project: Kafka Issue Type:

[jira] [Commented] (KAFKA-4919) Document that stores must not be closed when Processors are closed

[ https://issues.apache.org/jira/browse/KAFKA-4919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15936891#comment-15936891 ] Guozhang Wang commented on KAFKA-4919: -- [~elevy] There is a PR open for this ticket but not yet

Re: [DISCUSS] KIP-120: Cleanup Kafka Streams builder API

Regarding the naming of `StreamsTopologyBuilder` v.s. `StreamsBuilder` that are going to be used in DSL, I agree both has their arguments: 1. On one side, people using the DSL layer probably do not need to be aware (or rather, "learn about") of the "topology" concept, although this concept is a

Re: [DISCUSS] KIP-126 - Allow KafkaProducer to batch based on uncompressed size

Never mind about my second comment. I misunderstood the semantics of producer's batch.size. On Wed, Mar 22, 2017 at 10:20 AM, Dong Lin wrote: > Hey Becket, > > In addition to the batch-split-rate, should we also add batch-split-ratio > sensor to gauge the probability that

[jira] [Updated] (KAFKA-4935) Disable record level crc checks on the consumer with the KIP-98 message format

[ https://issues.apache.org/jira/browse/KAFKA-4935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-4935: Issue Type: Improvement (was: Bug) > Disable record level crc checks on the consumer with the

[jira] [Commented] (KAFKA-4159) Allow overriding producer & consumer properties at the connector level

[ https://issues.apache.org/jira/browse/KAFKA-4159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15936835#comment-15936835 ] Ewen Cheslack-Postava commented on KAFKA-4159: -- [~sjdurfey] Allowing configs like this is a

[jira] [Created] (KAFKA-4935) Disable record level crc checks on the consumer with the KIP-98 message format

Apurva Mehta created KAFKA-4935: --- Summary: Disable record level crc checks on the consumer with the KIP-98 message format Key: KAFKA-4935 URL: https://issues.apache.org/jira/browse/KAFKA-4935 Project:

[jira] [Created] (KAFKA-4934) Add streams test with RocksDb failures

Eno Thereska created KAFKA-4934: --- Summary: Add streams test with RocksDb failures Key: KAFKA-4934 URL: https://issues.apache.org/jira/browse/KAFKA-4934 Project: Kafka Issue Type: Bug

Re: [VOTE] KIP-117: Add a public AdminClient API for Kafka admin operations

On Fri, Mar 17, 2017, at 10:50, Jun Rao wrote: > Hi, Colin, > > Thanks for the KIP. Looks good overall. A few comments below. > > 1. Sometimes we return > CompletableFuture> > and some other times we return > Map > , which doesn't

Re: [DISCUSS] KIP-126 - Allow KafkaProducer to batch based on uncompressed size

Hey Becket, In addition to the batch-split-rate, should we also add batch-split-ratio sensor to gauge the probability that we have to split batch? Also, in the case that the batch size configured for the producer is smaller than the max message size configured for the broker, why can't we just

[jira] [Updated] (KAFKA-4919) Document that stores must not be closed when Processors are closed

[ https://issues.apache.org/jira/browse/KAFKA-4919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elias Levy updated KAFKA-4919: -- Summary: Document that stores must not be closed when Processors are closed (was: Streams job fails

[jira] [Commented] (KAFKA-4930) Connect Rest API allows creating connectors with an empty name

[ https://issues.apache.org/jira/browse/KAFKA-4930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15936720#comment-15936720 ] Nacho Munoz commented on KAFKA-4930: Actually, ignore my comment. I have just realised that validation

[jira] [Commented] (KAFKA-4919) Streams job fails with InvalidStateStoreException: Store is currently closed

[ https://issues.apache.org/jira/browse/KAFKA-4919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15936714#comment-15936714 ] Elias Levy commented on KAFKA-4919: --- Thanks for the information. It is something that should probably

[jira] [Commented] (KAFKA-4930) Connect Rest API allows creating connectors with an empty name

[ https://issues.apache.org/jira/browse/KAFKA-4930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15936679#comment-15936679 ] Nacho Munoz commented on KAFKA-4930: [~gwenshap] is there any reason why there's no validation when

Re: [VOTE] KIP-82 Add Record Headers

+1 On Tue, Mar 21, 2017 at 5:01 PM, Jason Gustafson wrote: > Thanks for the KIP! +1 (binding) from me. Just one nit: can we change > `Headers.header(key)` to be `Headers.lastHeader(key)`? It's not a > deal-breaker, but I think it's better to let the name reflect the actual >

Re: [DISCUSS] KIP-129: Kafka Streams Exactly-Once Semantics

This is a completely new feature which is controlled by a config. It would be a regression if you upgraded streams and saw a different behavior. That would not happen in this case. This is similar to how we are introducing idempotent producer in core kafka with a config to turn it on. There is no

Re: [DISCUSS] KIP-120: Cleanup Kafka Streams builder API

Forwarding to kafka-user. -- Forwarded message -- From: Michael Noll Date: Wed, Mar 22, 2017 at 8:48 AM Subject: Re: [DISCUSS] KIP-120: Cleanup Kafka Streams builder API To: dev@kafka.apache.org Matthias, > @Michael: > > You seemed to agree with Jay

[jira] [Commented] (KAFKA-4892) kafka 0.8.2.1 getOffsetsBefore API returning correct offset given timestamp in unix epoch format

[ https://issues.apache.org/jira/browse/KAFKA-4892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15936553#comment-15936553 ] Colin P. McCabe commented on KAFKA-4892: Can you be a little bit more descriptive about what the

[jira] [Created] (KAFKA-4933) Allow specifying keystore and truststore from byte array

Devon Meunier created KAFKA-4933: Summary: Allow specifying keystore and truststore from byte array Key: KAFKA-4933 URL: https://issues.apache.org/jira/browse/KAFKA-4933 Project: Kafka Issue

Re: Kafka design query

Hi Amit, In your example, computer A would be running the Kafka producer (which is a software library) and computer B would be running the Kafka broker (which is a long running-program, or daemon). Hope that helps. best, Colin On Fri, Mar 10, 2017, at 01:27, amit tomar wrote: > Hi Experts, >

[jira] [Updated] (KAFKA-4932) Add UUID Serde

[ https://issues.apache.org/jira/browse/KAFKA-4932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Klukas updated KAFKA-4932: --- Description: I propose adding serializers and deserializers for the java.util.UUID class. I have

[jira] [Updated] (KAFKA-4932) Add UUID Serde

[ https://issues.apache.org/jira/browse/KAFKA-4932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Klukas updated KAFKA-4932: --- Summary: Add UUID Serde (was: Add UUID Serdes) > Add UUID Serde > -- > >

[jira] [Created] (KAFKA-4932) Add UUID Serdes

Jeff Klukas created KAFKA-4932: -- Summary: Add UUID Serdes Key: KAFKA-4932 URL: https://issues.apache.org/jira/browse/KAFKA-4932 Project: Kafka Issue Type: Improvement Components:

[jira] [Resolved] (KAFKA-4918) Continuous fetch requests for offset storage topic in kafka connect

[ https://issues.apache.org/jira/browse/KAFKA-4918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira resolved KAFKA-4918. - Resolution: Not A Problem > Continuous fetch requests for offset storage topic in kafka connect >

[jira] [Assigned] (KAFKA-4918) Continuous fetch requests for offset storage topic in kafka connect

[ https://issues.apache.org/jira/browse/KAFKA-4918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira reassigned KAFKA-4918: --- Assignee: Gwen Shapira > Continuous fetch requests for offset storage topic in kafka connect

Re: [DISCUSS] KIP-129: Kafka Streams Exactly-Once Semantics

Separate reply because I'm switching topics (no pun intended). :-) One impact of the Streams EOS design is how we handle failures in Streams. In the EOS design we have effectively three main failure categories, as far as I understand: 1. Transient failures (which we now e.g. handle with infinite

Re: [DISCUSS] KIP-129: Kafka Streams Exactly-Once Semantics

I second Eno's concern regarding the impact of Streams EOS on state stores. > We do a full recovery today and the EOS proposal will not make this any worse. Yes, today we do a full state store recovery under certain failures. However, I think the point (or perhaps: open question) is that, with

[jira] [Commented] (KAFKA-4930) Connect Rest API allows creating connectors with an empty name

[ https://issues.apache.org/jira/browse/KAFKA-4930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15936374#comment-15936374 ] Gwen Shapira commented on KAFKA-4930: - Good catch! If you fix this, we'll gladly take the PR. Let me

[GitHub] kafka pull request #2725: MINOR: add note to Processor javadoc about not clo...

GitHub user dguy opened a pull request: https://github.com/apache/kafka/pull/2725 MINOR: add note to Processor javadoc about not closing state stores You can merge this pull request into a Git repository by running: $ git pull https://github.com/dguy/kafka

[jira] [Commented] (KAFKA-4919) Streams job fails with InvalidStateStoreException: Store is currently closed

[ https://issues.apache.org/jira/browse/KAFKA-4919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15936328#comment-15936328 ] Damian Guy commented on KAFKA-4919: --- Hi [~elevy] Yes that would be the issue. Because we now re-use the

[GitHub] kafka pull request #2724: MINOR: log state store restore offsets

GitHub user dguy opened a pull request: https://github.com/apache/kafka/pull/2724 MINOR: log state store restore offsets Debug logging of the start and end offsets used during state store restoration You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (KAFKA-4931) stop script fails due 4096 ps output limit

Amit Jain created KAFKA-4931: Summary: stop script fails due 4096 ps output limit Key: KAFKA-4931 URL: https://issues.apache.org/jira/browse/KAFKA-4931 Project: Kafka Issue Type: Bug

[GitHub] kafka-site issue #51: Add missing semicolon in JAAS config

Github user stromnet commented on the issue: https://github.com/apache/kafka-site/pull/51 Also added a note regarding authorizer.class.name which by default is empty. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If

Re: [VOTE] KIP-122: Add Reset Consumer Group Offsets tooling

@Jason, thanks for your feedback! You're right, we are not considering the old consumer, since we rely on the KafkaConsumer#seek operations. I'm happy to update the KIP to make this explicit. About the second comment: I suppose that it would work, but I would like to include it to the test cases

[GitHub] kafka-site pull request #51: Add missing semicolon in JAAS config

GitHub user stromnet opened a pull request: https://github.com/apache/kafka-site/pull/51 Add missing semicolon in JAAS config For future googlers ref, this solves the following error: ``` [2017-03-22 11:19:59,516] FATAL Fatal error during KafkaServerStartable startup.

[GitHub] kafka pull request #2723: MyProcessor doc example should implement, not exte...

GitHub user miguno opened a pull request: https://github.com/apache/kafka/pull/2723 MyProcessor doc example should implement, not extend `Processor` You can merge this pull request into a Git repository by running: $ git pull https://github.com/miguno/kafka

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

See Changes: [me] MINOR: Pluggable verifiable clients -- [...truncated 1.68 MB...] org.apache.kafka.connect.runtime.distributed.WorkerCoordinatorTest >

[GitHub] kafka pull request #2722: KAFKA-4878: Improved Invalid Connect Config Error ...

GitHub user original-brownbear opened a pull request: https://github.com/apache/kafka/pull/2722 KAFKA-4878: Improved Invalid Connect Config Error Message Addresses for https://issues.apache.org/jira/browse/KAFKA-4878 * Adjusted the error message to explicitly state errors