[jira] [Commented] (KAFKA-3665) Default ssl.endpoint.identification.algorithm should be https

[ https://issues.apache.org/jira/browse/KAFKA-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15273931#comment-15273931 ] Ismael Juma commented on KAFKA-3665: Thanks [~rsivaram]. I agree that this could catch some people.

[jira] [Commented] (KAFKA-3587) LogCleaner fails due to incorrect offset map computation on a replica

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

Re: KAFKA-3112

It said this is a duplication. This is the https://issues.apache.org/jira/browse/KAFKA-2657 that KAKFA-3112 duplicates to. On Thu, 5 May 2016 at 22:13 Raj Tanneru wrote: > > Hi All, > Does anyone know if KAFKA-3112 is merged to 0.9.0.1? Is there a place to > check which

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

See Changes: [me] KAFKA-3627: consumer fails to execute delayed tasks in poll when records -- [...truncated 6384 lines...] org.apache.kafka.connect.runtime.distributed.DistributedHerderTest >

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

See Changes: [me] KAFKA-3627: consumer fails to execute delayed tasks in poll when records -- [...truncated 2968 lines...] kafka.integration.SslTopicMetadataTest >

[GitHub] kafka pull request: KAFKA-3587 Improve logic to build offsetMap in...

GitHub user alekar opened a pull request: https://github.com/apache/kafka/pull/1329 KAFKA-3587 Improve logic to build offsetMap in log.Cleaner. You can merge this pull request into a Git repository by running: $ git pull https://github.com/alekar/kafka trunk Alternatively

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

See Changes: [me] KAFKA-3627: consumer fails to execute delayed tasks in poll when records -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on

[jira] [Created] (KAFKA-3665) Default ssl.endpoint.identification.algorithm should be https

Ismael Juma created KAFKA-3665: -- Summary: Default ssl.endpoint.identification.algorithm should be https Key: KAFKA-3665 URL: https://issues.apache.org/jira/browse/KAFKA-3665 Project: Kafka

[jira] [Commented] (KAFKA-3587) LogCleaner fails due to incorrect offset map computation on a replica

[ https://issues.apache.org/jira/browse/KAFKA-3587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15273821#comment-15273821 ] Edoardo Comar commented on KAFKA-3587: -- [~junrao] I was thinking of two possible optimistic

[jira] [Resolved] (KAFKA-725) Broker Exception: Attempt to read with a maximum offset less than start offset

[ https://issues.apache.org/jira/browse/KAFKA-725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-725. --- Resolution: Fixed [~guozhang]'s PR was merged to trunk and 0.10. > Broker Exception: Attempt to read

[jira] [Commented] (KAFKA-3665) Default ssl.endpoint.identification.algorithm should be https

[ https://issues.apache.org/jira/browse/KAFKA-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15274001#comment-15274001 ] Ryan P commented on KAFKA-3665: --- [~ijuma], just a nit but [RFC 6125|https://tools.ietf.org/search/rfc6125]

[jira] [Commented] (KAFKA-3665) Default ssl.endpoint.identification.algorithm should be https

[ https://issues.apache.org/jira/browse/KAFKA-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15274012#comment-15274012 ] Ismael Juma commented on KAFKA-3665: [~Ryan P], I agree that this would be better. The paper also

[jira] [Updated] (KAFKA-3665) Default ssl.endpoint.identification.algorithm should be https

[ https://issues.apache.org/jira/browse/KAFKA-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3665: --- Description: The default `ssl.endpoint.identification.algorithm` is `null` which is not a secure

[GitHub] kafka pull request: KAFKA-3665; Default ssl.endpoint.identificatio...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/1330 KAFKA-3665; Default ssl.endpoint.identification.algorithm should be https You can merge this pull request into a Git repository by running: $ git pull https://github.com/ijuma/kafka

[jira] [Commented] (KAFKA-3665) Default ssl.endpoint.identification.algorithm should be https

[ https://issues.apache.org/jira/browse/KAFKA-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15273902#comment-15273902 ] Ismael Juma commented on KAFKA-3665: Thoughts [~rsivaram], [~junrao], [~gwenshap], [~harsha_ch]? >

[jira] [Commented] (KAFKA-3665) Default ssl.endpoint.identification.algorithm should be https

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

[jira] [Updated] (KAFKA-3665) Default ssl.endpoint.identification.algorithm should be https

[ https://issues.apache.org/jira/browse/KAFKA-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3665: --- Status: Patch Available (was: Open) > Default ssl.endpoint.identification.algorithm should be https

[GitHub] kafka pull request: KAFKA-3312: Add utility offset methods to ZkUt...

GitHub user vahidhashemian reopened a pull request: https://github.com/apache/kafka/pull/1025 KAFKA-3312: Add utility offset methods to ZkUtils Create utility getOffset(...) and updateOffset(...) methods to replace readData(...), readDataMaybeNull(...) and updatePersistentPath(...)

[GitHub] kafka pull request: KAFKA-3312: Add utility offset methods to ZkUt...

Github user vahidhashemian closed the pull request at: https://github.com/apache/kafka/pull/1025 --- 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-3312) Add a offsets methods to ZkUtils and replace relevant usages

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

[jira] [Commented] (KAFKA-3312) Add a offsets methods to ZkUtils and replace relevant usages

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

[jira] [Updated] (KAFKA-3670) ControlledShutdownLeaderSelector should pick the preferred replica as the new leader, if possible

[ https://issues.apache.org/jira/browse/KAFKA-3670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3670: --- Reviewer: Jun Rao Status: Patch Available (was: In Progress) >

[jira] [Commented] (KAFKA-1981) Make log compaction point configurable

[ https://issues.apache.org/jira/browse/KAFKA-1981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15275027#comment-15275027 ] Ismael Juma commented on KAFKA-1981: I don't see your account, are you sure you created an account for

[jira] [Commented] (KAFKA-3587) LogCleaner fails due to incorrect offset map computation on a replica

[ https://issues.apache.org/jira/browse/KAFKA-3587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15274977#comment-15274977 ] Edoardo Comar commented on KAFKA-3587: -- [~junrao] the difference between option 1 and option 2 is

[GitHub] kafka pull request: KAFKA-3670; ControlledShutdownLeaderSelector s...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/1338 KAFKA-3670; ControlledShutdownLeaderSelector should pick the preferred replica as the new leader, if possible You can merge this pull request into a Git repository by running: $ git pull

[jira] [Commented] (KAFKA-3670) ControlledShutdownLeaderSelector should pick the preferred replica as the new leader, if possible

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

[GitHub] kafka pull request: HOTFIX: Ensure connector target state changes ...

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/1339 HOTFIX: Ensure connector target state changes propagated to worker You can merge this pull request into a Git repository by running: $ git pull https://github.com/hachikuji/kafka

[jira] [Created] (KAFKA-3673) Connect tests dont handle concurrent config changes

Liquan Pei created KAFKA-3673: - Summary: Connect tests dont handle concurrent config changes Key: KAFKA-3673 URL: https://issues.apache.org/jira/browse/KAFKA-3673 Project: Kafka Issue Type: Bug

[jira] [Updated] (KAFKA-3673) Connect tests dont handle concurrent config changes

[ https://issues.apache.org/jira/browse/KAFKA-3673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liquan Pei updated KAFKA-3673: -- Description: [INFO - 2016-04-28 18:42:45,346 - runner - log - lineno:221]: SerialTestRunner:

[jira] [Commented] (KAFKA-1981) Make log compaction point configurable

[ https://issues.apache.org/jira/browse/KAFKA-1981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15275024#comment-15275024 ] Eric Wasserman commented on KAFKA-1981: --- I think it must be the same as my Jira user: ewasserman >

[GitHub] kafka pull request: KAFKA-3144: Report members with no assigned pa...

GitHub user vahidhashemian opened a pull request: https://github.com/apache/kafka/pull/1336 KAFKA-3144: Report members with no assigned partitions in ConsumerGroupCommand This PR makes a couple of enhancements to the `--describe` option of `ConsumerGroupCommand`: 1. Listing

[GitHub] kafka pull request: KAFKA-3658: Validate retention period be longe...

GitHub user guozhangwang opened a pull request: https://github.com/apache/kafka/pull/1337 KAFKA-3658: Validate retention period be longer than window size You can merge this pull request into a Git repository by running: $ git pull https://github.com/guozhangwang/kafka K3658

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

See Changes: [cshapi] Minor: added description for lag in consumer group command [ismael] KAFKA-3669; Add secondary constructor for KafkaConfig with a default [ismael] KAFKA-3655; awaitFlushCompletion() in RecordAccumulator should

How to submit a KIP?

Hi, I have created a Jira Issue - https://issues.apache.org/jira/browse/KAFKA-3663  and was wondering what is the next step?Should I create a KIP? If so, how do I do that, as I do not have permissions to do that. Thanks,Jayesh Thakrar

<    1   2