[jira] [Commented] (KAFKA-3774) GetOffsetShell tool reports 'Missing required argument "[time]"' despite the default

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

[jira] [Updated] (KAFKA-3774) GetOffsetShell tool reports 'Missing required argument "[time]"' despite the default

[ https://issues.apache.org/jira/browse/KAFKA-3774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-3774: - Resolution: Fixed Reviewer: Ewen Cheslack-Postava Fix Version/s:

[GitHub] kafka pull request #1457: KAFKA-3774: Make 'time' an optional argument of Ge...

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

See Changes: [me] MINOR: Add a newline to a Javadoc sample in KafkaConsumer -- [...truncated 85 lines...]

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

See

[jira] [Commented] (KAFKA-3764) Error processing append operation on partition

[ https://issues.apache.org/jira/browse/KAFKA-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311765#comment-15311765 ] Ewen Cheslack-Postava commented on KAFKA-3764: -- Given that the issue is in decompression, it

Re: [DISCUSS] KIP-62: Allow consumer to send heartbeats from a background thread

Hi Onur, Jason: Here are some thoughts about reusing process timeout as server-side rebalance timeout: First of all, my understanding is that 1) session timeout is for detecting consumer crash / hard failures (in this case the heartbeat thread will be dead as well, hence coordinator realized

[GitHub] kafka pull request #1390: Add a newline to a Javadoc sample in KafkaConsumer

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1390 --- 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-3711) Allow configuration of MetricsReporter subclasses

[ https://issues.apache.org/jira/browse/KAFKA-3711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311714#comment-15311714 ] Ewen Cheslack-Postava commented on KAFKA-3711: -- [~jeff.klu...@gmail.com] I'm pretty sure this

Build failed in Jenkins: kafka-0.10.0-jdk7 #111

See Changes: [me] KAFKA-3660: Log exception message in ControllerBrokerRequestBatch -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on H10

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

See Changes: [me] KAFKA-3660: Log exception message in ControllerBrokerRequestBatch -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on ubuntu3

[jira] [Resolved] (KAFKA-3660) Log exception message in ControllerBrokerRequestBatch

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

[jira] [Commented] (KAFKA-3660) Log exception message in ControllerBrokerRequestBatch

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

[GitHub] kafka pull request #1325: KAFKA-3660: Log exception message in ControllerBro...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1325 --- 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: How to write Connect logs to file?

For Connect we use a different filename, connect-log4j.properties, just as the tools use a tools-log4j.properties. Note that this is just the default from the connect-standalone.sh or connect-distributed.sh scripts. You can also override that by setting the KAFKA_LOG4J_OPTS environment variable to

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

See Changes: [ismael] MINOR; Close parenthesis in PartitionInfo.toString -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on H11 (docker Ubuntu

[jira] [Commented] (KAFKA-3755) tightening the offset check in ReplicaFetcherThread

[ https://issues.apache.org/jira/browse/KAFKA-3755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311436#comment-15311436 ] Ishita Mandhan commented on KAFKA-3755: --- [~junrao]What would be easiest way to produce an error to

[jira] [Work started] (KAFKA-3748) Add consumer-property to console tools consumer (similar to --producer-property)

[ https://issues.apache.org/jira/browse/KAFKA-3748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-3748 started by Bharat Viswanadham. - > Add consumer-property to console tools consumer (similar to >

[GitHub] kafka pull request #1458: MINOR: close parenthesis in PartitionInfo.toString

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1458 --- 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-3763) Remove deprecated APIs

[ https://issues.apache.org/jira/browse/KAFKA-3763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311399#comment-15311399 ] Amey commented on KAFKA-3763: - [~ijuma] Yes that should be fine. I want to start contributing in this project.

[jira] [Updated] (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 ] Vahid Hashemian updated KAFKA-3129: --- Affects Version/s: 0.10.0.0 Component/s: (was: consumer) > Console producer

[GitHub] kafka pull request #1459: KAFKA-3748: Add consumer-property to console tools...

GitHub user bharatviswa504 opened a pull request: https://github.com/apache/kafka/pull/1459 KAFKA-3748: Add consumer-property to console tools consumer You can merge this pull request into a Git repository by running: $ git pull https://github.com/bharatviswa504/kafka

[jira] [Commented] (KAFKA-3748) Add consumer-property to console tools consumer (similar to --producer-property)

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

[jira] [Commented] (KAFKA-1995) JMS to Kafka: Inbuilt JMSAdaptor/JMSProxy/JMSBridge (Client can speak JMS but hit Kafka)

[ https://issues.apache.org/jira/browse/KAFKA-1995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311268#comment-15311268 ] John Lonergan commented on KAFKA-1995: -- Is it problematic that JMS reads (rather the commits) are

[jira] [Updated] (KAFKA-3774) GetOffsetShell tool reports 'Missing required argument "[time]"' despite the default

[ https://issues.apache.org/jira/browse/KAFKA-3774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vahid Hashemian updated KAFKA-3774: --- Status: Patch Available (was: Open) > GetOffsetShell tool reports 'Missing required argument

[GitHub] kafka pull request #1458: MINOR: close parenthesis in PartitionInfo.toString

GitHub user magnusr opened a pull request: https://github.com/apache/kafka/pull/1458 MINOR: close parenthesis in PartitionInfo.toString Trivial patch is trivial. You can merge this pull request into a Git repository by running: $ git pull https://github.com/magnusr/kafka

[jira] [Commented] (KAFKA-3769) KStream job spending 60% of time writing metrics

[ https://issues.apache.org/jira/browse/KAFKA-3769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311179#comment-15311179 ] Greg Fodor commented on KAFKA-3769: --- Thanks Jay! Guozhang, what are your thoughts on instead of trying

[jira] [Commented] (KAFKA-3774) GetOffsetShell tool reports 'Missing required argument "[time]"' despite the default

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

[GitHub] kafka pull request #1457: KAFKA-3774: Make 'time' an optional argument of Ge...

GitHub user vahidhashemian opened a pull request: https://github.com/apache/kafka/pull/1457 KAFKA-3774: Make 'time' an optional argument of GetOffsetShell tool Since the 'time' argument has a default value of -1, it makes sense to make it an optional argument. You can merge this

[jira] [Updated] (KAFKA-3774) GetOffsetShell tool reports 'Missing required argument "[time]"' despite the default

[ https://issues.apache.org/jira/browse/KAFKA-3774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vahid Hashemian updated KAFKA-3774: --- Description: If the {{--time}} argument is not provided to the GetOffsetShell tool, even

[jira] [Created] (KAFKA-3774) GetOffsetShell tool reports 'Missing required argument "[time]"' despite the default

Vahid Hashemian created KAFKA-3774: -- Summary: GetOffsetShell tool reports 'Missing required argument "[time]"' despite the default Key: KAFKA-3774 URL: https://issues.apache.org/jira/browse/KAFKA-3774

[jira] [Commented] (KAFKA-3129) Console Producer/Consumer Issue

[ https://issues.apache.org/jira/browse/KAFKA-3129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311048#comment-15311048 ] Vahid Hashemian commented on KAFKA-3129: I can still produce this issue with the current trunk

[jira] [Updated] (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 ] Vahid Hashemian updated KAFKA-3129: --- Summary: Console producer issue when request-required-acks=0 (was: Console Producer/Consumer

[jira] [Issue Comment Deleted] (KAFKA-3129) Console Producer/Consumer Issue

[ https://issues.apache.org/jira/browse/KAFKA-3129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vahid Hashemian updated KAFKA-3129: --- Comment: was deleted (was: I can still produce this issue with the current trunk code, when

[jira] [Commented] (KAFKA-3129) Console Producer/Consumer Issue

[ https://issues.apache.org/jira/browse/KAFKA-3129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311047#comment-15311047 ] Vahid Hashemian commented on KAFKA-3129: I can still produce this issue with the current trunk

[GitHub] kafka pull request #1456: MINOR: Add user overridden test logging events

GitHub user guozhangwang opened a pull request: https://github.com/apache/kafka/pull/1456 MINOR: Add user overridden test logging events You can merge this pull request into a Git repository by running: $ git pull https://github.com/guozhangwang/kafka Kminor-test-logging

KStreams Rewind Offset

All,   I think it's great that the ProcessorContext offers the partition and offset of the current record being processed; however, it offers no way for me to actually use the information. I would like to be able to rewind to a particular offset on a partition if I needed to. The consumer is

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

See Changes: [wangguoz] MINOR: added spacing in streams doc in section 9.2 -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on H11 (docker Ubuntu

[GitHub] kafka pull request #1455: MINOR: Fix setting of ACLs and ZK shutdown in test...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/1455 MINOR: Fix setting of ACLs and ZK shutdown in test harnesses I found both issues while investigating the issue described in PR #1425. You can merge this pull request into a Git repository by running:

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

See Changes: [wangguoz] MINOR: added spacing in streams doc in section 9.2 -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on H10 (docker Ubuntu

[GitHub] kafka pull request #1454: MINOR: added spacing in streams doc in section 9.2

GitHub user coughman opened a pull request: https://github.com/apache/kafka/pull/1454 MINOR: added spacing in streams doc in section 9.2 You can merge this pull request into a Git repository by running: $ git pull https://github.com/coughman/kafka trunk Alternatively you can

[jira] [Commented] (KAFKA-3561) Auto create through topic for KStream aggregation and join

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

[GitHub] kafka pull request: KAFKA-3561: Auto create through topic for KStream aggreg...

GitHub user dguy opened a pull request: https://github.com/apache/kafka/pull/1453 KAFKA-3561: Auto create through topic for KStream aggregation and join [WIP] @guozhangwang can you please take a look at this? It is not close to being done but i'd like some feedback to ensure i'm

Re: Using zookeeper vs gossip protocols in Kafka

Are you referring to something like this: https://github.com/edwardcapriolo/gossip ZooKeeper and other systems with a consensus core give you strong guarantees with respect to the order of updates, and for example, you won't be able to avoid split brain with current ISRs if you don't have this

Using zookeeper vs gossip protocols in Kafka

Hi, I see that Kafka uses zookeeper for group membership and leader election. Curious to know if Kafka developers ever discussed to move away from Zookeeper and use Gossip based protocols. Is there any specific advantage of using Zookeeper over Gossip based implementation or vice versa? Thanks,

[jira] [Commented] (KAFKA-1379) Partition reassignment resets clock for time-based retention

[ https://issues.apache.org/jira/browse/KAFKA-1379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15310068#comment-15310068 ] Luca Toscano commented on KAFKA-1379: - Hi Moritz, thanks a lot for pointing us to this Jira in

Re: [jira] [Updated] (KAFKA-3772) MirrorMaker crashes on Corrupted Message

Just had a look at the code, as I would like some way to prevent such a scenario happening to us. It seems you can't prevent the mirror maker from exiting. In the 0.10 mirror maker, any exception which is not an ConsumerTimeoutException, or an WakeupException, will cause the whole mirror maker to