[GitHub] kafka pull request #4038: [KAFKA-4818][FOLLOW-UP] Include isolationLevel in ...

[jaceklaskowski]

GitHub user jaceklaskowski opened a pull request:

https://github.com/apache/kafka/pull/4038

[KAFKA-4818][FOLLOW-UP] Include isolationLevel in toString of FetchRequest

Include `isolationLevel` in `toString` of `FetchRequest`

This is a follow-up to https://issues.apache.org/jira/browse/KAFKA-4818.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/jaceklaskowski/kafka KAFKA-4818-isolationLevel

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/4038.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #4038


commit 12e6367952c93326b687d22771882d732fd41cf3
Author: Jacek Laskowski 
Date:   2017-10-07T14:48:19Z

[KAFKA-4818][FOLLOW-UP] Include isolationLevel in toString of FetchRequest




---

[GitHub] kafka-site issue #92: Redesign of Streams page - includes video & customer l...

[furyus]

Github user furyus commented on the issue:

https://github.com/apache/kafka-site/pull/92
  
Please @ mention me when this gets merged - thanks for your hard work!


---

[GitHub] kafka pull request #4039: MINOR: Bump the request timeout for the transactio...

[apurvam]

GitHub user apurvam opened a pull request:

https://github.com/apache/kafka/pull/4039

MINOR: Bump the request timeout for the transactional message copier

Multiple inflights means that when there are rolling bounces and other 
cluster instability, there is an
increased likelihood of having previously tried batch expire in th 
accumulator. This is a fatal error
for a transaction, causing the copier to exit. To work around this, we bump 
the request timeout. We can get rid of this when KIP-91 is merged.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/apurvam/kafka 
MINOR-bump-request-timeout-in-transactional-message-copier

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/4039.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #4039


commit 5ad017fd90b75b13b6683efaac17454d9cc5bb26
Author: Apurva Mehta 
Date:   2017-10-07T17:50:33Z

Bump the reuest timeout for the transactional message copier to fix the 
transient system test failures




---

[jira] [Created] (KAFKA-6021) run kafka-mirror-maker.sh in daemon mode

[Ronald van de Kuil (JIRA)]

Ronald van de Kuil created KAFKA-6021:
-

 Summary: run kafka-mirror-maker.sh in daemon mode
 Key: KAFKA-6021
 URL: https://issues.apache.org/jira/browse/KAFKA-6021
 Project: Kafka
  Issue Type: Improvement
Reporter: Ronald van de Kuil
Priority: Minor


I run kafka_2.11-0.11.0.0. 

It would be nice if the mirror maker could run in daemon mode like the broker 
and the zookeeper.

pi@pi5:/opt/kafka_2.11-0.11.0.0 $ bin/kafka-mirror-maker.sh -daemon 
--consumer.config config/DC1.properties --num.streams 1 --producer.config 
config/DC2.properties --whitelist=".*"
Java HotSpot(TM) Server VM warning: G1 GC is disabled in this release.
[2017-10-08 08:36:10,627] ERROR Exception when starting mirror maker. 
(kafka.tools.MirrorMaker$)
joptsimple.UnrecognizedOptionException: d is not a recognized option
 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (KAFKA-6022) mirror maker stores offset in zookeeper

[Ronald van de Kuil (JIRA)]

Ronald van de Kuil created KAFKA-6022:
-

 Summary: mirror maker stores offset in zookeeper
 Key: KAFKA-6022
 URL: https://issues.apache.org/jira/browse/KAFKA-6022
 Project: Kafka
  Issue Type: Improvement
Reporter: Ronald van de Kuil
Priority: Minor


I happened to notice that the mirror maker stores its offset in zookeeper. 

I do not see it using:

bin/kafka-consumer-groups.sh --bootstrap-server pi1:9092 --new-consumer --list

I do however see consumers that store their offset in kafka.

I would guess that storing the offset in zookeeper is old style?

Would it be an idea to update the mirror maker to the new consumer style?




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)