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

See

Re: Protocol Documentation WIP

Agreed w/ Jay's comment on the PR that this is a great idea. What if we included this as is, but instead of putting it all on the docs page we put it on its own page? This: 1. Gets us something useful wrt protocol docs immediately. As you point out, this is already useful to a bunch of people. 2.

[jira] [Commented] (KAFKA-3279) SASL implementation checks for unused System property java.security.auth.login.config

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

[GitHub] kafka pull request: KAFKA-3279: Remove checks for JAAS system prop...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/967 --- 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-3279) SASL implementation checks for unused System property java.security.auth.login.config

[ https://issues.apache.org/jira/browse/KAFKA-3279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-3279: - Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved

[GitHub] kafka pull request: [MINOR] Fixed documenation of parameter "block...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/954 --- 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] [Created] (KAFKA-3356) Remove ConsumerOffsetChecker, deprecated in 0.9, in 0.11

Ashish K Singh created KAFKA-3356: - Summary: Remove ConsumerOffsetChecker, deprecated in 0.9, in 0.11 Key: KAFKA-3356 URL: https://issues.apache.org/jira/browse/KAFKA-3356 Project: Kafka

[jira] [Commented] (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=15186615#comment-15186615 ] Ashish K Singh commented on KAFKA-3355: --- [~xiaotao183] you are correct and this problem persists in

[jira] [Updated] (KAFKA-3252) compression type for a topic should be used during log compaction

[ https://issues.apache.org/jira/browse/KAFKA-3252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish K Singh updated KAFKA-3252: -- Status: Patch Available (was: Open) > compression type for a topic should be used during log

[jira] [Updated] (KAFKA-3247) kafka-topic tool can use an option to see just "unbalanced partitions"

[ https://issues.apache.org/jira/browse/KAFKA-3247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish K Singh updated KAFKA-3247: -- Status: Patch Available (was: Open) > kafka-topic tool can use an option to see just

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

TAO XIAO created KAFKA-3355: --- Summary: GetOffsetShell command doesn't work with SASL enabled Kafka Key: KAFKA-3355 URL: https://issues.apache.org/jira/browse/KAFKA-3355 Project: Kafka Issue Type:

[jira] [Updated] (KAFKA-3237) ConfigDef validators require a default value

[ https://issues.apache.org/jira/browse/KAFKA-3237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-3237: - Assignee: Jeremy Custenborder > ConfigDef validators require a default value >

[jira] [Commented] (KAFKA-3237) ConfigDef validators require a default value

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

[GitHub] kafka pull request: KAFKA-3237 - Remove test cases testInvalidDefa...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/936 --- 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] [Resolved] (KAFKA-3237) ConfigDef validators require a default value

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

[jira] [Updated] (KAFKA-3354) Streams system tests fail in trunk

[ https://issues.apache.org/jira/browse/KAFKA-3354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3354: - Priority: Blocker (was: Major) > Streams system tests fail in trunk >

[jira] [Commented] (KAFKA-3354) Streams system tests fail in trunk

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

[jira] [Updated] (KAFKA-3354) Streams system tests fail in trunk

[ https://issues.apache.org/jira/browse/KAFKA-3354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3354: - Fix Version/s: 0.10.0.0 > Streams system tests fail in trunk > --

[GitHub] kafka pull request: MINOR: Ignoring streams tests until there is f...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1031 --- 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: Additional Kafka Connect schema logical types?

On Fri, Mar 4, 2016 at 1:37 PM, Randall Hauch wrote: > I’m working on a Kafka Connect connector that reads a MySQL binlog to > provide near real-time change data capture, and I also plan connectors for > other DBMSes. The problem is that I’m not able to map all of the MySQL

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

See Changes: [junrao] KAFKA-3343; Use NoTimestamp in GroupMetadataManager when message v0 i… -- [...truncated 5802 lines...] org.apache.kafka.connect.runtime.WorkerTest >

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

See

[GitHub] kafka pull request: MINOR: Ignoring streams tests until there is f...

GitHub user granders opened a pull request: https://github.com/apache/kafka/pull/1031 MINOR: Ignoring streams tests until there is fix for KAFKA-3354 Per discussion with @guozhangwang, `@ignore` failing streams system tests until fix for KAFKA-3354 is checked in. You can merge

[jira] [Commented] (KAFKA-3354) Streams system tests fail in trunk

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

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

See Changes: [jjkoshy] KAFKA-3197; Fix producer sending records out of order -- [...truncated 3568 lines...] org.apache.kafka.clients.ClientUtilsTest > testNoPort PASSED

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

See Changes: [jjkoshy] KAFKA-3197; Fix producer sending records out of order -- [...truncated 2971 lines...] kafka.integration.SaslSslTopicMetadataTest > testGetAllTopicMetadata PASSED

Re: [DISCUSS] KIP-43: Kafka SASL enhancements

"Since smart card logins are not built into Kafka (or the JDK), you need a developer to build the login module. So the developer implements example.SmartcardLoginModule. In addition, the developer may also implement callback handlers for the SASL client or server and a login class to keep this

[jira] [Updated] (KAFKA-3353) Remove deprecated producer configs.

[ https://issues.apache.org/jira/browse/KAFKA-3353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish K Singh updated KAFKA-3353: -- Description: Following producer configs were deprecated in 0.9, it will be a good idea to

[jira] [Updated] (KAFKA-3353) Remove deprecated producer configs.

[ https://issues.apache.org/jira/browse/KAFKA-3353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish K Singh updated KAFKA-3353: -- Affects Version/s: 0.11.0.0 > Remove deprecated producer configs. >

[jira] [Updated] (KAFKA-3353) Remove deprecated producer configs.

[ https://issues.apache.org/jira/browse/KAFKA-3353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish K Singh updated KAFKA-3353: -- Description: Following producer configs were deprecated in 0.9, it will be a good idea to

Re: [Discuss] Remove producer configs deprecated in 0.9

OK, in that case I will move the JIRA to target for 0.11 instead. On Tue, Mar 8, 2016 at 4:26 PM, Gwen Shapira wrote: > We are planning on supporting direct 0.8.2 to 0.10 upgrades (and are > adding tests to that effect). So we expect that quite a few users will > never see

Re: [Discuss] Remove producer configs deprecated in 0.9

Thanks Gwen, I was going to say the exact same thing. :) Ismael On Wed, Mar 9, 2016 at 12:26 AM, Gwen Shapira wrote: > We are planning on supporting direct 0.8.2 to 0.10 upgrades (and are > adding tests to that effect). So we expect that quite a few users will > never see

[jira] [Updated] (KAFKA-3343) GroupMetadataManager should use NoTimestamp for message v0

[ https://issues.apache.org/jira/browse/KAFKA-3343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-3343: --- Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request 1023

[jira] [Commented] (KAFKA-3343) GroupMetadataManager should use NoTimestamp for message v0

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

[GitHub] kafka pull request: KAFKA-3343: Use NoTimestamp in GroupMetadataMa...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1023 --- 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: [Discuss] Remove producer configs deprecated in 0.9

We are planning on supporting direct 0.8.2 to 0.10 upgrades (and are adding tests to that effect). So we expect that quite a few users will never see 0.9 and therefore never see the deprecation notice. I don't think this allows us to remove them at this release. On Tue, Mar 8, 2016 at 3:59 PM,

[jira] [Created] (KAFKA-3354) Streams system tests fail in trunk

Geoff Anderson created KAFKA-3354: - Summary: Streams system tests fail in trunk Key: KAFKA-3354 URL: https://issues.apache.org/jira/browse/KAFKA-3354 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-3353) Remove deprecated producer configs.

[ https://issues.apache.org/jira/browse/KAFKA-3353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15186113#comment-15186113 ] Ashish K Singh commented on KAFKA-3353: --- Sent a mail to dev list just a few seconds back :). If

[Discuss] Remove producer configs deprecated in 0.9

Hey Guys, Following producer configs were deprecated in 0.9, it might be a good idea to remove them in 0.10. - block.on.buffer.full - metadata.fetch.timeout.ms - timeout.ms Does this sound OK? KAFKA-3353 is tracking this. -- Regards, Ashish

[jira] [Commented] (KAFKA-3353) Remove deprecated producer configs.

[ https://issues.apache.org/jira/browse/KAFKA-3353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15186107#comment-15186107 ] Ismael Juma commented on KAFKA-3353: Given the short release cycle, I think it may make sense to

[jira] [Created] (KAFKA-3353) Remove deprecated producer configs.

Ashish K Singh created KAFKA-3353: - Summary: Remove deprecated producer configs. Key: KAFKA-3353 URL: https://issues.apache.org/jira/browse/KAFKA-3353 Project: Kafka Issue Type: Bug

Re: [DISCUSS] KIP-43: Kafka SASL enhancements

As an admin, you would configure login modules using standard JAAS configuration. So, if you are supporting Kerberos and smart card login modules within a single broker, in your jaas.conf you would specify: KafkaServer { com.ibm.security.auth.module.Krb5LoginModule required credsType=both

[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=15186032#comment-15186032 ] ASF GitHub Bot commented on KAFKA-3312: --- GitHub user vahidhashemian reopened a pull request:

[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

[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 You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka KAFKA-3312

[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=15186031#comment-15186031 ] ASF GitHub Bot commented on KAFKA-3312: --- Github user vahidhashemian closed the pull request at:

[jira] [Updated] (KAFKA-3352) Avoid DNS reverse lookups

[ https://issues.apache.org/jira/browse/KAFKA-3352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3352: --- Status: Patch Available (was: Open) > Avoid DNS reverse lookups > - > >

[jira] [Updated] (KAFKA-3352) Avoid DNS reverse lookups

[ https://issues.apache.org/jira/browse/KAFKA-3352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3352: --- Fix Version/s: 0.10.0.0 > Avoid DNS reverse lookups > - > >

[jira] [Commented] (KAFKA-3352) Avoid DNS reverse lookups

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

[GitHub] kafka pull request: KAFKA-3352: Avoid DNS reverse lookups

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/1030 KAFKA-3352: Avoid DNS reverse lookups By using `getHostString` (introduced in Java 7) instead of `getHostName`. You can merge this pull request into a Git repository by running: $ git pull

[jira] [Updated] (KAFKA-3197) Producer can send message out of order even when in flight request is set to 1.

[ https://issues.apache.org/jira/browse/KAFKA-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy updated KAFKA-3197: -- Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to trunk. > Producer can

[jira] [Updated] (KAFKA-3352) Avoid DNS reverse lookups

[ https://issues.apache.org/jira/browse/KAFKA-3352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3352: --- Description: We use `InetSocketAddress.getHostName` in `Cluster.bootstrap` and `SocketServer` This

[GitHub] kafka pull request: KAFKA-3197 Fix producer sending records out of...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/857 --- 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-3197) Producer can send message out of order even when in flight request is set to 1.

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

[jira] [Updated] (KAFKA-3352) Avoid DNS reverse lookups

[ https://issues.apache.org/jira/browse/KAFKA-3352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3352: --- Summary: Avoid DNS reverse lookups (was: Avoid DNS reverse lookup in Cluster.bootstrap) > Avoid DNS

[jira] [Created] (KAFKA-3352) Avoid DNS reverse lookup in Cluster.bootstrap

Ismael Juma created KAFKA-3352: -- Summary: Avoid DNS reverse lookup in Cluster.bootstrap Key: KAFKA-3352 URL: https://issues.apache.org/jira/browse/KAFKA-3352 Project: Kafka Issue Type:

[jira] [Commented] (KAFKA-3323) Negative offsets in Log Segment Index files due to Integer overflow when compaction is enabled

[ https://issues.apache.org/jira/browse/KAFKA-3323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15185889#comment-15185889 ] Michael Schiff commented on KAFKA-3323: --- [~gwenshap] [~ijuma]

[jira] [Commented] (KAFKA-3342) https://cwiki.apache.org/confluence/display/KAFKA/Log+Compaction has log.cleaner.min.cleanable.ratio listed twice in error

[ https://issues.apache.org/jira/browse/KAFKA-3342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15185864#comment-15185864 ] Vahid Hashemian commented on KAFKA-3342: I believe the second one should read

[jira] [Commented] (KAFKA-2066) Replace FetchRequest / FetchResponse with their org.apache.kafka.common.requests equivalents

[ https://issues.apache.org/jira/browse/KAFKA-2066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15185779#comment-15185779 ] Grant Henke commented on KAFKA-2066: [~dajac] Are you still working on this? > Replace FetchRequest /

[jira] [Commented] (KAFKA-3323) Negative offsets in Log Segment Index files due to Integer overflow when compaction is enabled

[ https://issues.apache.org/jira/browse/KAFKA-3323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15185767#comment-15185767 ] Ismael Juma commented on KAFKA-3323: Yes, thank you Michael. :) > Negative offsets in Log Segment

[jira] [Commented] (KAFKA-3323) Negative offsets in Log Segment Index files due to Integer overflow when compaction is enabled

[ https://issues.apache.org/jira/browse/KAFKA-3323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15185766#comment-15185766 ] Gwen Shapira commented on KAFKA-3323: - You rock! Thank you. > Negative offsets in Log Segment Index

[jira] [Updated] (KAFKA-3306) Change metdata response to include required additional fields

[ https://issues.apache.org/jira/browse/KAFKA-3306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-3306: --- Description: This includes: - Rack information from KAFKA-1215 (KIP-36) - A boolean to indicate if a

Re: [DISCUSS] KIP-43: Kafka SASL enhancements

I guess what is unclear to me is: 1. How does the proposed Login class interact with LoginContext and LoginModule. 2. Do we really need a pluggable Login class, when users (administrators, not developers) are more likely to want to specify LoginModules? 3. How will users get to specify multiple

[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=15185731#comment-15185731 ] ASF GitHub Bot commented on KAFKA-3312: --- GitHub user vahidhashemian reopened a pull request:

[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

[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 You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka KAFKA-3312

[jira] [Updated] (KAFKA-3306) Change metdata response to include required additional fields

[ https://issues.apache.org/jira/browse/KAFKA-3306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-3306: --- Priority: Critical (was: Major) > Change metdata response to include required additional fields >

[jira] [Updated] (KAFKA-3306) Change metdata response to include required additional fields

[ https://issues.apache.org/jira/browse/KAFKA-3306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-3306: --- Fix Version/s: 0.10.0.0 > Change metdata response to include required additional fields >

[jira] [Resolved] (KAFKA-3269) Update topic metadata request to included needed information for polling

[ https://issues.apache.org/jira/browse/KAFKA-3269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke resolved KAFKA-3269. Resolution: Duplicate > Update topic metadata request to included needed information for polling >

[jira] [Updated] (KAFKA-3306) Change metdata response to include required additional fields

[ https://issues.apache.org/jira/browse/KAFKA-3306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-3306: --- Description: This includes: - Rack information from KAFKA-1215 (KIP-36) - A boolean to indicate if a

[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 ] Grant Henke updated KAFKA-3266: --- Status: Patch Available (was: In Progress) > List/Alter Acls - protocol and server side

[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 ] Grant Henke updated KAFKA-3266: --- Fix Version/s: 0.10.0.0 > List/Alter Acls - protocol and server side implementation >

Re: [DISCUSS] KIP-43: Kafka SASL enhancements

Gwen, I am not sure I understand your concern. Java login contexts support multiple login modules precisely to support this type of real-world scenario. >From Javadoc of *javax.security.auth.login.LoginContext*: *In addition to supporting pluggable authentication, this class also supports the

[jira] [Commented] (KAFKA-3323) Negative offsets in Log Segment Index files due to Integer overflow when compaction is enabled

[ https://issues.apache.org/jira/browse/KAFKA-3323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15185624#comment-15185624 ] Gwen Shapira commented on KAFKA-3323: - [~michael.schiff] Yeah, i was thinking that you can host this

Re: [VOTE] KIP-33 - Add a time based log index to Kafka

I updated the wiki to make the following change: Instead of maintaining a globally monotonically increasing time index. We only make sure the time index for each log segment is monotonically increasing. By doing that everything seems much simpler. we avoid empty time index. Enforcing log

[jira] [Comment Edited] (KAFKA-3323) Negative offsets in Log Segment Index files due to Integer overflow when compaction is enabled

[ https://issues.apache.org/jira/browse/KAFKA-3323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15185540#comment-15185540 ] Michael Schiff edited comment on KAFKA-3323 at 3/8/16 7:33 PM: --- [~ijuma] I

[jira] [Commented] (KAFKA-3323) Negative offsets in Log Segment Index files due to Integer overflow when compaction is enabled

[ https://issues.apache.org/jira/browse/KAFKA-3323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15185540#comment-15185540 ] Michael Schiff commented on KAFKA-3323: --- [~ijuma] I went to submit the patch, but this didn't seem

[jira] [Comment Edited] (KAFKA-1843) Metadata fetch/refresh in new producer should handle all node connection states gracefully

[ https://issues.apache.org/jira/browse/KAFKA-1843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15185525#comment-15185525 ] venu edited comment on KAFKA-1843 at 3/8/16 7:11 PM: - I am having similar problem ,

[jira] [Updated] (KAFKA-3323) Negative offsets in Log Segment Index files due to Integer overflow when compaction is enabled

[ https://issues.apache.org/jira/browse/KAFKA-3323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Schiff updated KAFKA-3323: -- Status: Open (was: Patch Available) > Negative offsets in Log Segment Index files due to

[jira] [Issue Comment Deleted] (KAFKA-3323) Negative offsets in Log Segment Index files due to Integer overflow when compaction is enabled

[ https://issues.apache.org/jira/browse/KAFKA-3323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Schiff updated KAFKA-3323: -- Comment: was deleted (was: Re-opening so that I can attach the log-splitter patch) > Negative

[jira] [Comment Edited] (KAFKA-1843) Metadata fetch/refresh in new producer should handle all node connection states gracefully

[ https://issues.apache.org/jira/browse/KAFKA-1843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15185525#comment-15185525 ] venu edited comment on KAFKA-1843 at 3/8/16 7:08 PM: - I am having similar problem ,

[jira] [Issue Comment Deleted] (KAFKA-3323) Negative offsets in Log Segment Index files due to Integer overflow when compaction is enabled

[ https://issues.apache.org/jira/browse/KAFKA-3323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Schiff updated KAFKA-3323: -- Comment: was deleted (was: Log Splitter utility. For those with production log files that are

[jira] [Updated] (KAFKA-3323) Negative offsets in Log Segment Index files due to Integer overflow when compaction is enabled

[ https://issues.apache.org/jira/browse/KAFKA-3323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Schiff updated KAFKA-3323: -- Affects Version/s: 0.8.2.1 Status: Patch Available (was: Reopened) Log Splitter

[jira] [Reopened] (KAFKA-3323) Negative offsets in Log Segment Index files due to Integer overflow when compaction is enabled

[ https://issues.apache.org/jira/browse/KAFKA-3323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Schiff reopened KAFKA-3323: --- Re-opening so that I can attach the log-splitter patch > Negative offsets in Log Segment Index

[jira] [Comment Edited] (KAFKA-1843) Metadata fetch/refresh in new producer should handle all node connection states gracefully

[ https://issues.apache.org/jira/browse/KAFKA-1843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15185525#comment-15185525 ] venu edited comment on KAFKA-1843 at 3/8/16 7:06 PM: - I am having similar problem ,

[jira] [Updated] (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:all-tabpanel ] Vahid Hashemian updated KAFKA-3312: --- Affects Version/s: (was: 0.9.0.1) Status: Patch Available (was: Open) >

[jira] [Updated] (KAFKA-2273) Add rebalance with a minimal number of reassignments to server-defined strategy list

[ https://issues.apache.org/jira/browse/KAFKA-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vahid Hashemian updated KAFKA-2273: --- Status: Patch Available (was: Reopened) > Add rebalance with a minimal number of

[jira] [Reopened] (KAFKA-2273) Add rebalance with a minimal number of reassignments to server-defined strategy list

[ https://issues.apache.org/jira/browse/KAFKA-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vahid Hashemian reopened KAFKA-2273: > Add rebalance with a minimal number of reassignments to server-defined > strategy list >

[jira] [Resolved] (KAFKA-2273) Add rebalance with a minimal number of reassignments to server-defined strategy list

[ https://issues.apache.org/jira/browse/KAFKA-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vahid Hashemian resolved KAFKA-2273. Resolution: Fixed > Add rebalance with a minimal number of reassignments to server-defined

[jira] [Commented] (KAFKA-1843) Metadata fetch/refresh in new producer should handle all node connection states gracefully

[ https://issues.apache.org/jira/browse/KAFKA-1843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15185525#comment-15185525 ] venu commented on KAFKA-1843: - I am having similar problem , when partition is down, metadata is still

[jira] [Updated] (KAFKA-2073) Replace TopicMetadata request/response with o.a.k.requests.metadata

[ https://issues.apache.org/jira/browse/KAFKA-2073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-2073: --- Fix Version/s: 0.10.0.0 > Replace TopicMetadata request/response with o.a.k.requests.metadata >

[jira] [Resolved] (KAFKA-3032) Broken documentation link

[ https://issues.apache.org/jira/browse/KAFKA-3032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke resolved KAFKA-3032. Resolution: Fixed Assignee: Grant Henke This was resolved via

[jira] [Resolved] (KAFKA-3323) Negative offsets in Log Segment Index files due to Integer overflow when compaction is enabled

[ https://issues.apache.org/jira/browse/KAFKA-3323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-3323. Resolution: Duplicate Thanks for confirming Michael. Closing as duplicate. Maybe you can attach a

[jira] [Comment Edited] (KAFKA-3323) Negative offsets in Log Segment Index files due to Integer overflow when compaction is enabled

[ https://issues.apache.org/jira/browse/KAFKA-3323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15185488#comment-15185488 ] Michael Schiff edited comment on KAFKA-3323 at 3/8/16 6:52 PM: --- [~ijuma]

[jira] [Commented] (KAFKA-3323) Negative offsets in Log Segment Index files due to Integer overflow when compaction is enabled

[ https://issues.apache.org/jira/browse/KAFKA-3323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15185488#comment-15185488 ] Michael Schiff commented on KAFKA-3323: --- [~ijuma] Yes, it is a duplicate. The accepted solution was

[jira] [Updated] (KAFKA-3038) Speeding up partition reassignment after broker failure

[ https://issues.apache.org/jira/browse/KAFKA-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-3038: --- Fix Version/s: 0.11.0.0 > Speeding up partition reassignment after broker failure >

[jira] [Updated] (KAFKA-3038) Speeding up partition reassignment after broker failure

[ https://issues.apache.org/jira/browse/KAFKA-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-3038: --- Fix Version/s: (was: 0.9.0.0) > Speeding up partition reassignment after broker failure >

[jira] [Commented] (KAFKA-3309) Update Protocol Documentation WIP patch

[ https://issues.apache.org/jira/browse/KAFKA-3309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15185233#comment-15185233 ] Ashish K Singh commented on KAFKA-3309: --- [~granthenke] it might need an update based on whether or

Re: [DISCUSS] KIP-43: Kafka SASL enhancements

Yes, I understand that. However, because the current configuration only allows a single callback and a single login module, I need to supply a class that supports callbacks or logins for every single mechanism that I need to support. I question whether this is applicable in real-world scenario

Re: [VOTE] Release plan - Kafka 0.10.0

+1 (non-binding). I will review and update any jiras I think should be tracked today. Gwen the release tracking page is awesome! +1 (non-binding) One clarification: there are currently 11 issues marked as blockers, is that an accurate list? http://bit.ly/21YCthZ -Flavio > On 08 Mar 2016, at

  1   2   >