[jira] [Updated] (KAFKA-3965) Mirror maker sync send fails will lose messages

[ https://issues.apache.org/jira/browse/KAFKA-3965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-3965: Status: Patch Available (was: Open) > Mirror maker sync send fails will lose messages >

[jira] [Updated] (KAFKA-3994) Deadlock between consumer heartbeat expiration and offset commit.

[ https://issues.apache.org/jira/browse/KAFKA-3994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-3994: --- Fix Version/s: 0.10.1.0 > Deadlock between consumer heartbeat expiration and offset commit. >

[GitHub] kafka pull request #1915: KAFKA-3965 mirror maker should not commit offset w...

GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/1915 KAFKA-3965 mirror maker should not commit offset when exception is thrown from producer.send() You can merge this pull request into a Git repository by running: $ git pull

[jira] [Commented] (KAFKA-3965) Mirror maker sync send fails will lose messages

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

[jira] [Assigned] (KAFKA-3965) Mirror maker sync send fails will lose messages

[ https://issues.apache.org/jira/browse/KAFKA-3965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin reassigned KAFKA-3965: --- Assignee: Jiangjie Qin > Mirror maker sync send fails will lose messages >

[jira] [Updated] (KAFKA-3266) List/Alter Acls - protocol and server side implementation

[ https://issues.apache.org/jira/browse/KAFKA-3266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-3266: --- Fix Version/s: (was: 0.10.1.0) 0.10.2.0 > List/Alter Acls - protocol

[jira] [Updated] (KAFKA-3405) Deduplicate and break out release tasks

[ https://issues.apache.org/jira/browse/KAFKA-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-3405: --- Fix Version/s: (was: 0.10.1.0) 0.10.2.0 > Deduplicate and break out

[jira] [Commented] (KAFKA-3965) Mirror maker sync send fails will lose messages

[ https://issues.apache.org/jira/browse/KAFKA-3965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15525079#comment-15525079 ] Jiangjie Qin commented on KAFKA-3965: - Yeah, there is a bug that may cause this problem. We need to

[jira] [Updated] (KAFKA-1548) Refactor the "replica_id" in requests

[ https://issues.apache.org/jira/browse/KAFKA-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-1548: --- Fix Version/s: (was: 0.10.1.0) 0.10.2.0 > Refactor the "replica_id" in

[jira] [Updated] (KAFKA-1043) Time-consuming FetchRequest could block other request in the response queue

[ https://issues.apache.org/jira/browse/KAFKA-1043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-1043: --- Fix Version/s: (was: 0.10.1.0) 0.10.2.0 > Time-consuming FetchRequest

[jira] [Resolved] (KAFKA-3913) Old consumer's metrics error when using IPv6

[ https://issues.apache.org/jira/browse/KAFKA-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-3913. Resolution: Duplicate Marking this as a duplicate of KAFKA-3930, which already has a patch

[jira] [Commented] (KAFKA-4222) Transient failure in QueryableStateIntegrationTest.queryOnRebalance

[ https://issues.apache.org/jira/browse/KAFKA-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15525049#comment-15525049 ] Guozhang Wang commented on KAFKA-4222: -- [~enothereska] Could you take a look at this? > Transient

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

See

[jira] [Updated] (KAFKA-4222) Transient failure in QueryableStateIntegrationTest.queryOnRebalance

[ https://issues.apache.org/jira/browse/KAFKA-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-4222: - Assignee: Eno Thereska (was: Guozhang Wang) > Transient failure in

[jira] [Updated] (KAFKA-3947) kafka-reassign-partitions.sh should support dumping current assignment

[ https://issues.apache.org/jira/browse/KAFKA-3947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-3947: --- Fix Version/s: (was: 0.10.1.0) 0.10.2.0 > kafka-reassign-partitions.sh

[jira] [Updated] (KAFKA-3989) Add JMH module for Benchmarks

[ https://issues.apache.org/jira/browse/KAFKA-3989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-3989: --- Fix Version/s: (was: 0.10.1.0) 0.10.2.0 > Add JMH module for

[jira] [Updated] (KAFKA-2334) Prevent HW from going back during leader failover

[ https://issues.apache.org/jira/browse/KAFKA-2334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-2334: --- Fix Version/s: (was: 0.10.1.0) 0.10.2.0 > Prevent HW from going back

[jira] [Updated] (KAFKA-1063) run log cleanup at startup

[ https://issues.apache.org/jira/browse/KAFKA-1063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-1063: --- Fix Version/s: (was: 0.10.1.0) 0.10.2.0 > run log cleanup at startup >

[jira] [Updated] (KAFKA-4011) allow sizing RequestQueue in bytes

[ https://issues.apache.org/jira/browse/KAFKA-4011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-4011: --- Fix Version/s: (was: 0.10.1.0) 0.10.2.0 > allow sizing RequestQueue in

[jira] [Updated] (KAFKA-3719) Pattern regex org.apache.kafka.common.utils.Utils.HOST_PORT_PATTERN is too narrow

[ https://issues.apache.org/jira/browse/KAFKA-3719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-3719: --- Status: Resolved (was: Closed) > Pattern regex

[jira] [Closed] (KAFKA-3719) Pattern regex org.apache.kafka.common.utils.Utils.HOST_PORT_PATTERN is too narrow

[ https://issues.apache.org/jira/browse/KAFKA-3719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson closed KAFKA-3719. -- > Pattern regex org.apache.kafka.common.utils.Utils.HOST_PORT_PATTERN is too > narrow >

[jira] [Updated] (KAFKA-984) Avoid a full rebalance in cases when a new topic is discovered but container/broker set stay the same

[ https://issues.apache.org/jira/browse/KAFKA-984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-984: -- Fix Version/s: (was: 0.10.1.0) 0.10.2.0 > Avoid a full rebalance in cases

[jira] [Updated] (KAFKA-806) Index may not always observe log.index.interval.bytes

[ https://issues.apache.org/jira/browse/KAFKA-806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-806: -- Fix Version/s: (was: 0.10.1.0) 0.10.2.0 > Index may not always observe

[jira] [Updated] (KAFKA-1342) Slow controlled shutdowns can result in stale shutdown requests

[ https://issues.apache.org/jira/browse/KAFKA-1342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-1342: --- Priority: Critical (was: Blocker) > Slow controlled shutdowns can result in stale shutdown

[jira] [Commented] (KAFKA-1342) Slow controlled shutdowns can result in stale shutdown requests

[ https://issues.apache.org/jira/browse/KAFKA-1342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15525019#comment-15525019 ] Jason Gustafson commented on KAFKA-1342: Downgrading this to "Critical" since it has not actually

[GitHub] kafka pull request #1901: MINOR: Fix Javadoc for KafkaConsumer.poll

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1901 --- 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

?????? it this a bug? - message disorder in async send mode -- 0.9.0java client sdk InFlightRequests

hi, Json I know the server logic: the server use selector mute/unmute , whenever the socket receive a request, it will mute until the response return, it become unmute. -- -- ??: "";; :

Build failed in Jenkins: kafka-0.10.1-jdk7 #12

See Changes: [junrao] KAFKA-4214; kafka-reassign-partitions fails all the time when brokers -- [...truncated 11742 lines...]

?????? it this a bug? - message disorder in async send mode -- 0.9.0java client sdk InFlightRequests

hi, Jason can you explain the "head of line request blocking" in more detail? I am very curious, thanks! below is the code: class RequestChannel(val numProcessors: Int, val queueSize: Int) extends KafkaMetricsGroup { private var responseListeners: List[(Int) => Unit] = Nil private val

[jira] [Assigned] (KAFKA-4165) Add 0.10.0.1 as a source for compatibility tests where relevant

[ https://issues.apache.org/jira/browse/KAFKA-4165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson reassigned KAFKA-4165: -- Assignee: Jason Gustafson > Add 0.10.0.1 as a source for compatibility tests where

[jira] [Commented] (KAFKA-3965) Mirror maker sync send fails will lose messages

[ https://issues.apache.org/jira/browse/KAFKA-3965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15524965#comment-15524965 ] NieWang commented on KAFKA-3965: The mirror maker version that I running is 0.10.0.0. You can follow the

[jira] [Created] (KAFKA-4222) Transient failure in QueryableStateIntegrationTest.queryOnRebalance

Jason Gustafson created KAFKA-4222: -- Summary: Transient failure in QueryableStateIntegrationTest.queryOnRebalance Key: KAFKA-4222 URL: https://issues.apache.org/jira/browse/KAFKA-4222 Project: Kafka

[GitHub] kafka pull request #1914: MINOR: Make new consumer default for Mirror Maker

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/1914 MINOR: Make new consumer default for Mirror Maker You can merge this pull request into a Git repository by running: $ git pull https://github.com/hachikuji/kafka mm-default-new-consumer

Re: [DISCUSS] KIP-73: Replication Quotas

Hi Ben, Just for my understanding : When you said : What we really want to do is apply: LeaderThrottle [104,107,109] FollowerThrottle [105,113] ---> This means that we want to apply leader throttle to only replica that is the leader out of 104, 107, 109 right? Also when you said :

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

See Changes: [jason] KAFKA-3831; Prepare for updating new-consumer-based Mirror Maker's -- [...truncated 13543 lines...] org.apache.kafka.streams.processor.internals.StreamThreadTest >

[jira] [Commented] (KAFKA-3175) topic not accessible after deletion even when delete.topic.enable is disabled

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

[GitHub] kafka pull request #1913: KAFKA-3175 (Rebased) : topic not accessible after ...

GitHub user MayureshGharat opened a pull request: https://github.com/apache/kafka/pull/1913 KAFKA-3175 (Rebased) : topic not accessible after deletion even when delete.topic.enable is disabled Rebased the patch with current trunk. You can merge this pull request into a Git

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

See Changes: [junrao] KAFKA-4214; kafka-reassign-partitions fails all the time when brokers -- [...truncated 6124 lines...] kafka.api.SaslPlainSslEndToEndAuthorizationTest > testNoConsumeAcl

Re: [DISCUSS] KIP-73: Replication Quotas

Makes sense to me. Thanks Ben! On Mon, Sep 26, 2016 at 9:39 AM Jun Rao wrote: > Yes, this change makes sense to me since it gives the admin better control. > > Thanks, > > Jun > > On Sun, Sep 25, 2016 at 7:35 AM, Ben Stopford wrote: > > > Hi All > > > >

[jira] [Updated] (KAFKA-3831) Preparation for updating the default partition assignment strategy of Mirror Maker to round robin

[ https://issues.apache.org/jira/browse/KAFKA-3831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-3831: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Preparation for updating

[jira] [Commented] (KAFKA-3831) Preparation for updating the default partition assignment strategy of Mirror Maker to round robin

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

[GitHub] kafka pull request #1499: KAFKA-3831: Prepare for updating new-consumer-base...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1499 --- 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

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

See Changes: [junrao] KAFKA-4214; kafka-reassign-partitions fails all the time when brokers -- [...truncated 3611 lines...] kafka.integration.SaslPlaintextTopicMetadataTest >

Build failed in Jenkins: kafka-0.10.1-jdk7 #11

See Changes: [me] MINOR: Wakeups propagated from commitOffsets in WorkerSinkTask should be -- [...truncated 7390 lines...] kafka.network.SocketServerTest > tooBigRequestIsRejected STARTED

[jira] [Updated] (KAFKA-4201) Add an --assignment-strategy option to new-consumer-based Mirror Maker

[ https://issues.apache.org/jira/browse/KAFKA-4201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vahid Hashemian updated KAFKA-4201: --- Status: Patch Available (was: Open) > Add an --assignment-strategy option to

[jira] [Commented] (KAFKA-4201) Add an --assignment-strategy option to new-consumer-based Mirror Maker

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

[GitHub] kafka pull request #1912: KAFKA-4201: Add an `assignment.strategy` option to...

GitHub user vahidhashemian opened a pull request: https://github.com/apache/kafka/pull/1912 KAFKA-4201: Add an `assignment.strategy` option to new-consumer-based Mirror Maker A command line option `assignment.strategy` is added to new-consumer-based Mirror Maker that overwrites

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

See Changes: [me] MINOR: Wakeups propagated from commitOffsets in WorkerSinkTask should be -- [...truncated 7403 lines...] kafka.integration.SaslPlaintextTopicMetadataTest >

[jira] [Commented] (KAFKA-4214) kafka-reassign-partitions fails all the time when brokers are bounced during reassignment

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

[jira] [Resolved] (KAFKA-4214) kafka-reassign-partitions fails all the time when brokers are bounced during reassignment

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

[GitHub] kafka pull request #1910: KAFKA-4214:kafka-reassign-partitions fails all the...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1910 --- 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

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

See

[jira] [Commented] (KAFKA-3829) Warn that kafka-connect group.id must not conflict with connector names

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

[GitHub] kafka pull request #1911: KAFKA-3829: Ensure valid configuration prior to cr...

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/1911 KAFKA-3829: Ensure valid configuration prior to creating connector You can merge this pull request into a Git repository by running: $ git pull https://github.com/hachikuji/kafka KAFKA-3829

[jira] [Commented] (KAFKA-4212) Add a key-value store that is a TTL persistent cache

[ https://issues.apache.org/jira/browse/KAFKA-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15524513#comment-15524513 ] Elias Levy commented on KAFKA-4212: --- More generally, the use case is: I've told a bunch of folks about

[jira] [Commented] (KAFKA-3919) Broker faills to start after ungraceful shutdown due to non-monotonically incrementing offsets in logs

[ https://issues.apache.org/jira/browse/KAFKA-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15524480#comment-15524480 ] Jun Rao commented on KAFKA-3919: [~BigAndy], the error trace in the description of the jira only happens

[jira] [Commented] (KAFKA-4207) Partitions stopped after a rapid restart of a broker

[ https://issues.apache.org/jira/browse/KAFKA-4207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15524443#comment-15524443 ] Joel Koshy commented on KAFKA-4207: --- I have a KIP draft that has been sitting around for a while. I

[jira] [Updated] (KAFKA-1211) Hold the produce request with ack > 1 in purgatory until replicas' HW has larger than the produce offset

[ https://issues.apache.org/jira/browse/KAFKA-1211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1211: --- Assignee: (was: Guozhang Wang) > Hold the produce request with ack > 1 in purgatory until replicas' HW

[jira] [Commented] (KAFKA-4212) Add a key-value store that is a TTL persistent cache

[ https://issues.apache.org/jira/browse/KAFKA-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15524402#comment-15524402 ] Elias Levy commented on KAFKA-4212: --- The general use case is the joining of updates to two tables over a

[jira] [Commented] (KAFKA-3965) Mirror maker sync send fails will lose messages

[ https://issues.apache.org/jira/browse/KAFKA-3965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15524370#comment-15524370 ] Jiangjie Qin commented on KAFKA-3965: - [~niew37] Could you confirm the mirror maker version you are

[jira] [Commented] (KAFKA-1342) Slow controlled shutdowns can result in stale shutdown requests

[ https://issues.apache.org/jira/browse/KAFKA-1342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15524361#comment-15524361 ] Jun Rao commented on KAFKA-1342: A similar incident was reported in

[GitHub] kafka pull request #1907: MINOR: Wakeups propagated from commitOffsets in Wo...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1907 --- 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-4214) kafka-reassign-partitions fails all the time when brokers are bounced during reassignment

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

[GitHub] kafka pull request #1910: KAFKA-4214:kafka-reassign-partitions fails all the...

GitHub user apurvam opened a pull request: https://github.com/apache/kafka/pull/1910 KAFKA-4214:kafka-reassign-partitions fails all the time when brokers are bounced during reassignment There is a corner case bug, where during partition reassignment, if the controller and a

[jira] [Commented] (KAFKA-3999) Consumer bytes-fetched metric uses decompressed message size

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

[jira] [Commented] (KAFKA-3999) Consumer bytes-fetched metric uses decompressed message size

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

[GitHub] kafka pull request #1698: KAFKA-3999: Record raw size of fetch responses as ...

GitHub user vahidhashemian reopened a pull request: https://github.com/apache/kafka/pull/1698 KAFKA-3999: Record raw size of fetch responses as part of consumer metrics Currently, only the decompressed size of fetch responses is recorded. This PR adds a sensor to keep track of the

[GitHub] kafka pull request #1698: KAFKA-3999: Record raw size of fetch responses as ...

Github user vahidhashemian closed the pull request at: https://github.com/apache/kafka/pull/1698 --- 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

[jira] [Commented] (KAFKA-3708) Rethink exception handling in KafkaStreams

[ https://issues.apache.org/jira/browse/KAFKA-3708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15524190#comment-15524190 ] Guozhang Wang commented on KAFKA-3708: -- PR submitted from [~damianguy]:

[jira] [Commented] (KAFKA-4212) Add a key-value store that is a TTL persistent cache

[ https://issues.apache.org/jira/browse/KAFKA-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15524186#comment-15524186 ] Guozhang Wang commented on KAFKA-4212: -- Hello [~elevy], thanks for reporting this feature request.

[jira] [Updated] (KAFKA-3174) Re-evaluate the CRC32 class performance.

[ https://issues.apache.org/jira/browse/KAFKA-3174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-3174: Fix Version/s: (was: 0.10.1.0) 0.10.2.0 > Re-evaluate the CRC32 class

[jira] [Commented] (KAFKA-3331) Refactor TopicCommand to make it testable and add unit tests

[ https://issues.apache.org/jira/browse/KAFKA-3331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15524171#comment-15524171 ] Jiangjie Qin commented on KAFKA-3331: - It seem the patch has been there for quite some time.

[jira] [Commented] (KAFKA-4120) byte[] keys in RocksDB state stores do not work as expected

[ https://issues.apache.org/jira/browse/KAFKA-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15524168#comment-15524168 ] Guozhang Wang commented on KAFKA-4120: -- [~elevy] {{o.a.k.common.utils.Bytes}} is added in trunk after

[GitHub] kafka pull request #1909: MINOR: Allow for asynchronous start of producer co...

GitHub user kkonstantine opened a pull request: https://github.com/apache/kafka/pull/1909 MINOR: Allow for asynchronous start of producer consumer in validatio… …n test You can merge this pull request into a Git repository by running: $ git pull

SendFailedException

Hi there, Can anyone please help us as we are getting the SendFailedException when Kafka consumer is starting and not able to consume any message? Thanks Achintya

[jira] [Commented] (KAFKA-3697) Clean-up website documentation when it comes to clients

[ https://issues.apache.org/jira/browse/KAFKA-3697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15523884#comment-15523884 ] Vahid Hashemian commented on KAFKA-3697: [~ijuma] Starting to look at this and wondering if we

[jira] [Work started] (KAFKA-4220) Clean up & provide better error message when incorrect argument types are provided in the command line client

[ https://issues.apache.org/jira/browse/KAFKA-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-4220 started by Ishita Mandhan. - > Clean up & provide better error message when incorrect argument types are >

[GitHub] kafka pull request #1908: Kafka 3396

GitHub user edoardocomar opened a pull request: https://github.com/apache/kafka/pull/1908 Kafka 3396 Reopening of https://github.com/apache/kafka/pull/1428 You can merge this pull request into a Git repository by running: $ git pull https://github.com/edoardocomar/kafka

Re: it this a bug? - message disorder in async send mode -- 0.9.0 java client sdk InFlightRequests

Hi there, The Kafka server implements head of line request blocking, which means that it will only handle one request a time from a given socket. That means that the responses will always be returned in the same order as the requests were sent. -Jason On Sat, Sep 24, 2016 at 1:19 AM, 一生有你

[GitHub] kafka pull request #1907: MINOR: Wakeups propagated from commitOffsets in Wo...

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/1907 MINOR: Wakeups propagated from commitOffsets in WorkerSinkTask should be caught You can merge this pull request into a Git repository by running: $ git pull

[jira] [Updated] (KAFKA-4216) Replication Quotas: Control Leader & Follower Throttled Replicas Separately

[ https://issues.apache.org/jira/browse/KAFKA-4216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Stopford updated KAFKA-4216: Status: Patch Available (was: In Progress) > Replication Quotas: Control Leader & Follower

[jira] [Work started] (KAFKA-4216) Replication Quotas: Control Leader & Follower Throttled Replicas Separately

[ https://issues.apache.org/jira/browse/KAFKA-4216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-4216 started by Ben Stopford. --- > Replication Quotas: Control Leader & Follower Throttled Replicas Separately >

[jira] [Created] (KAFKA-4221) KafkaConsumer Fetcher can send ListOffsets requests in parallel when initializing position

Jason Gustafson created KAFKA-4221: -- Summary: KafkaConsumer Fetcher can send ListOffsets requests in parallel when initializing position Key: KAFKA-4221 URL: https://issues.apache.org/jira/browse/KAFKA-4221

Re: [DISCUSS] KIP-73: Replication Quotas

Yes, this change makes sense to me since it gives the admin better control. Thanks, Jun On Sun, Sep 25, 2016 at 7:35 AM, Ben Stopford wrote: > Hi All > > We’ve made an adjustment to KIP-73: Replication Quotas which I’d like to > open up to the community for approval. > >

[GitHub] kafka pull request #1906: KAFKA 4216: Control Leader & Follower Throttled Re...

GitHub user benstopford opened a pull request: https://github.com/apache/kafka/pull/1906 KAFKA 4216: Control Leader & Follower Throttled Replicas Separately Splits the throttled replica configuration (the list of which replicas should be throttled for each topic) into two. One for

[jira] [Commented] (KAFKA-3102) Kafka server unable to connect to zookeeper

[ https://issues.apache.org/jira/browse/KAFKA-3102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15523330#comment-15523330 ] SOFT COMPANY - NEJJAR, Azeddine commented on KAFKA-3102: Hello, Have you find any

Re: Permission to edit KIP pages

Hello Ismael, My wiki user name is khurrumnasimm. Thanks, KN On Sun, Sep 18, 2016 at 3:52 PM, Ismael Juma wrote: > Hi KN, > > What's your wiki user name? > > Ismael > > On Sun, Sep 18, 2016 at 3:02 AM, Khurrum Nasim > wrote: > > > Hi, > > > > I

[jira] [Commented] (KAFKA-3919) Broker faills to start after ungraceful shutdown due to non-monotonically incrementing offsets in logs

[ https://issues.apache.org/jira/browse/KAFKA-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15522746#comment-15522746 ] Andy Coates commented on KAFKA-3919: Thanks [~ijuma]. Given that the problems I'm experiencing are

[jira] [Commented] (KAFKA-3919) Broker faills to start after ungraceful shutdown due to non-monotonically incrementing offsets in logs

[ https://issues.apache.org/jira/browse/KAFKA-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15522629#comment-15522629 ] Ismael Juma commented on KAFKA-3919: Thanks [~BigAndy]. It's worth noting that the discussion moved to

[jira] [Commented] (KAFKA-3919) Broker faills to start after ungraceful shutdown due to non-monotonically incrementing offsets in logs

[ https://issues.apache.org/jira/browse/KAFKA-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15522583#comment-15522583 ] Andy Coates commented on KAFKA-3919: We experienced a similar incident again recently. This time the

[jira] [Resolved] (KAFKA-3404) Issues running the kafka system test Sasl

[ https://issues.apache.org/jira/browse/KAFKA-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mickael Maison resolved KAFKA-3404. --- Resolution: Cannot Reproduce > Issues running the kafka system test Sasl >

[jira] [Commented] (KAFKA-3404) Issues running the kafka system test Sasl

[ https://issues.apache.org/jira/browse/KAFKA-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15522523#comment-15522523 ] Mickael Maison commented on KAFKA-3404: --- Reran the system tests on Ubuntu 16.04 and didn't hit the

Re: Help related to KStreams and Stateful event processing.

Arvind, your use cases sound very similar to what Bobby Calderwell recently described and presented at StrangeLoop this year: Commander: Better Distributed Applications through CQRS, Event Sourcing, and Immutable Logs

Re: Help related to KStreams and Stateful event processing.

PS: Arvind, I think typically such questions should be sent to the kafka-user mailing list (not to kafka-dev). On Mon, Sep 26, 2016 at 3:41 AM, Matthias J. Sax wrote: > Hi Arvind, > > short answer, Kafka Streams does definitely help you! > > Long answer, Kafka Streams

[GitHub] kafka pull request #1900: [DOCS]: fix ambiguity - consuming by multiple cons...

Github user pilloPl closed the pull request at: https://github.com/apache/kafka/pull/1900 --- 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

[GitHub] kafka pull request #1900: [DOCS]: fix ambiguity - consuming by multiple cons...

GitHub user pilloPl reopened a pull request: https://github.com/apache/kafka/pull/1900 [DOCS]: fix ambiguity - consuming by multiple consumers, but by exact… In doc it stays: _"Our topic is divided into a set of totally ordered partitions, each of which is consumed by

[jira] [Updated] (KAFKA-4216) Replication Quotas: Control Leader & Follower Throttled Replicas Separately

[ https://issues.apache.org/jira/browse/KAFKA-4216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Stopford updated KAFKA-4216: Summary: Replication Quotas: Control Leader & Follower Throttled Replicas Separately (was: