[jira] [Comment Edited] (KAFKA-3355) GetOffsetShell command doesn't work with SASL enabled Kafka

[ https://issues.apache.org/jira/browse/KAFKA-3355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15735361#comment-15735361 ] Mohammed amine GARMES edited comment on KAFKA-3355 at 12/10/16 10:20 AM:

Re: Reg: ACLS

Hi Ashish, Ismael Thanks for Info. So on Kafka Cluster (With out any security enabled) I can add ACLS with IP address. Is that correct? Thanks, Bharat On Fri, Dec 9, 2016 at 11:14 AM, Ashish Singh wrote: > Ismael, thanks for the correction. I assumed the question was

[jira] [Commented] (KAFKA-3008) Connect should parallelize task start/stop

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

[GitHub] kafka pull request #2232: HOTFIX: Fix HerderRequest.compareTo()

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2232 --- 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 #2240: MINOR: Update Log Compaction Details in design.htm...

GitHub user curlup opened a pull request: https://github.com/apache/kafka/pull/2240 MINOR: Update Log Compaction Details in design.html You can merge this pull request into a Git repository by running: $ git pull https://github.com/curlup/kafka trunk Alternatively you can

Re: Reg: ACLS

Hi, bin/kafka-acls.sh --topic kafka-testtopic --add -allow-host 9.30.15.19 --operation Write --authorizer-properties zookeeper.connect=hostname.abc.com:2181 Below message I am getting. You must specify one of: --allow-principal, --deny-principal when trying to add ACLs. So, as kerberos is not

Re: [VOTE] KIP-87 - Add Compaction Tombstone Flag

Hi Jay, Good point this detail is missing in the KIP write up. Ive added this now. Essentially simply just upgrading the clients we do not expect any client app code change needed. Cheers Mike From: Jay Kreps Sent: Saturday, December

[GitHub] kafka pull request #2227: KAFKA-4510: StreamThread must finish rebalance in ...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2227 --- 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-4510) StreamThread must finish rebalance in state PENDING_SHUTDOWN

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

[jira] [Updated] (KAFKA-4510) StreamThread must finish rebalance in state PENDING_SHUTDOWN

[ https://issues.apache.org/jira/browse/KAFKA-4510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-4510: - Resolution: Fixed Fix Version/s: 0.10.2.0 Status: Resolved (was: Patch

[GitHub] kafka pull request #2241: KAFKA-4521; MirrorMaker should flush all messages ...

GitHub user lindong28 opened a pull request: https://github.com/apache/kafka/pull/2241 KAFKA-4521; MirrorMaker should flush all messages before releasing partition ownership during rebalance You can merge this pull request into a Git repository by running: $ git pull

Re: [VOTE]: KIP-97: The client compatibility KIP

+1 (binding) -Ewen On Sat, Dec 10, 2016 at 2:41 PM, Jay Kreps wrote: > +1 (binding) > > -Jay > > On Wed, Dec 7, 2016 at 9:17 AM, Colin McCabe wrote: > > > Hi all, > > > > I heard that the VOTE and DISCUSS threads for the KIP-97 discussion > > appeared to

Re: [VOTE]: KIP-97: The client compatibility KIP

+1 (binding) -Jay On Wed, Dec 7, 2016 at 9:17 AM, Colin McCabe wrote: > Hi all, > > I heard that the VOTE and DISCUSS threads for the KIP-97 discussion > appeared to be in the same email thread for some people using gmail. So > I'm reposting in hopes of getting a separate

Re: [DISCUSS] KIP-97: Improved Kafka Client RPC Compatibility Policy

Hi,   as a user I find this concept interesting, but not important enough. I just want to share my personal thoughts, potentially leaning myself somewhat out of the window, that came to my mind during reading:   - I think it is of utmost importance for the Kafka project to continue the good

[jira] [Commented] (KAFKA-4497) log cleaner breaks on timeindex

[ https://issues.apache.org/jira/browse/KAFKA-4497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15739018#comment-15739018 ] Jiangjie Qin commented on KAFKA-4497: - I looked at the log cleaner code in 0.10.1. There is a bug

[jira] [Assigned] (KAFKA-4497) log cleaner breaks on timeindex

[ https://issues.apache.org/jira/browse/KAFKA-4497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin reassigned KAFKA-4497: --- Assignee: Jiangjie Qin > log cleaner breaks on timeindex > --- >

[jira] [Commented] (KAFKA-4497) log cleaner breaks on timeindex

[ https://issues.apache.org/jira/browse/KAFKA-4497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15739035#comment-15739035 ] Jiangjie Qin commented on KAFKA-4497: - To be more clear, this part of the code has been changed in the

Re: [VOTE] KIP-87 - Add Compaction Tombstone Flag

It seemed like this was addressed in the migration section, wasn't it? The V2 vs V3 requests and the fact that the broker will downgrade the message format (losing zero copy) if you issues a V2 request to a broker using V3 format handles compatibility, does it not? The existing consumers won't see

[jira] [Commented] (KAFKA-4476) Kafka Streams gets stuck if metadata is missing

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

[GitHub] kafka pull request #2209: KAFKA-4476: Kafka Streams gets stuck if metadata i...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2209 --- 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-4476) Kafka Streams gets stuck if metadata is missing

[ https://issues.apache.org/jira/browse/KAFKA-4476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-4476: - Resolution: Fixed Fix Version/s: 0.10.2.0 Status: Resolved (was: Patch

[jira] [Updated] (KAFKA-4521) MirrorMaker should flush all messages before releasing partition ownership during rebalance

[ https://issues.apache.org/jira/browse/KAFKA-4521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-4521: Description: In order to ensure that messages from a given partition in the source cluster are mirrored to

[jira] [Created] (KAFKA-4521) MirrorMaker should flush all messages before releasing partition ownership during rebalance

Dong Lin created KAFKA-4521: --- Summary: MirrorMaker should flush all messages before releasing partition ownership during rebalance Key: KAFKA-4521 URL: https://issues.apache.org/jira/browse/KAFKA-4521

Re: [DISCUSS] KIP-81: Max in-flight fetches

Jason, it's not just decompression but also the conversion from packed bytes to java objects, right? That can be even larger than the decompression blow up. I think this may be okay, the problem may just be that the naming is a bit misleading. In the producer you are literally allocating a buffer

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

See

Re: [VOTE] KIP-87 - Add Compaction Tombstone Flag

Michael, The compatibility section goes through the migration path, but isn't the bigger compatibility issue with existing apps? There are many (probably thousands) of apps in production that use this feature and send null to mean delete. It seems like this would break compatibility with them,

Re: [DISCUSS] KIP-97: Improved Kafka Client RPC Compatibility Policy

On Sat, Dec 10, 2016 at 5:23 PM, Sven Ludwig wrote: > Hi, > > as a user I find this concept interesting, but not important enough. I > just want to share my personal thoughts, potentially leaning myself > somewhat out of the window, that came to my mind during reading: > > - I

Re: [DISCUSS] KIP-95: Incremental Batch Processing for Kafka Streams

A few thoughts: > introduce a Streams metadata topic (single partitioned and log compacted; one for each application-ID) I would consider whether the single partition is a strict requirement. A single partition increases the likelihood of outages. This is something I'd like to see changed in

Re: [DISCUSS] KIP-66 Kafka Connect Transformers for messages

If anyone has time to review here, it'd be great to get feedback. I'd imagine that the proposal itself won't be too controversial -- keeps transformations simple (by only allowing map/filter), doesn't affect the rest of the framework much, and fits in with general config structure we've used

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

See Changes: [wangguoz] KAFKA-4476: Kafka Streams gets stuck if metadata is missing [wangguoz] KAFKA-4510: StreamThread must finish rebalance in state PENDING_SHUTDOWN -- [...truncated 14543