[jira] [Created] (KAFKA-3178) Expose a method in AdminUtils to manually truncate a specific partition to a particular offset

Bill Warshaw created KAFKA-3178: --- Summary: Expose a method in AdminUtils to manually truncate a specific partition to a particular offset Key: KAFKA-3178 URL: https://issues.apache.org/jira/browse/KAFKA-3178

[jira] [Updated] (KAFKA-3178) Expose a method in AdminUtils to manually truncate a specific partition to a particular offset

[ https://issues.apache.org/jira/browse/KAFKA-3178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Warshaw updated KAFKA-3178: Description: h3. Description One of Kafka's officially-described use cases is a distributed commit

[jira] [Created] (KAFKA-3179) Kafka consumer delivers message whose offset is earlier than sought offset.

Jiangjie Qin created KAFKA-3179: --- Summary: Kafka consumer delivers message whose offset is earlier than sought offset. Key: KAFKA-3179 URL: https://issues.apache.org/jira/browse/KAFKA-3179 Project:

Broker down when expand partitions

Hello Kafka Developers, I'm running a 16 nodes kafka cluster for my company. Today I tried to expand one topic from 3 partitions to 5 partitions. It works well before, but this morning, it turned down the new brokers. It seems the "Append" happens before "Index Ready". Following is the

Re: Pluggable Log Compaction Policy

You should be good to go now. On Sun, Jan 31, 2016 at 10:09 PM, Bill Warshaw wrote: > wdwars...@gmail.com > Bill Warshaw > > Thanks! > > On Mon, Feb 1, 2016 at 1:08 AM, Gwen Shapira wrote: > > > What is your wiki user name? > > > > On Sat, Jan 30,

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

Could we support separate SASL mechanisms via separate ports? This was the main reason we separated the ports in first place, to avoid adding protocol negotiation protocol and allow the server to expect the correct packets when they arrive to the correct listener. It will be nice if new additions

Re: Pluggable Log Compaction Policy

What is your wiki user name? On Sat, Jan 30, 2016 at 11:35 PM, Bill Warshaw wrote: > Hello again, > > Is there anyone on this thread who has admin access to the Kafka Confluence > wiki? I want to create a KIP but I don't have permissions to actually > create a page. >

Re: Pluggable Log Compaction Policy

wdwars...@gmail.com Bill Warshaw Thanks! On Mon, Feb 1, 2016 at 1:08 AM, Gwen Shapira wrote: > What is your wiki user name? > > On Sat, Jan 30, 2016 at 11:35 PM, Bill Warshaw > wrote: > > > Hello again, > > > > Is there anyone on this thread who has

[jira] [Commented] (KAFKA-3086) unused handle method in MirrorMakerMessageHandler

[ https://issues.apache.org/jira/browse/KAFKA-3086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15125822#comment-15125822 ] Gwen Shapira commented on KAFKA-3086: - Doesn't this change mean that MessageHandlers written for

[GitHub] kafka pull request: KAFKA-3179 Fix seek on compressed messages

GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/842 KAFKA-3179 Fix seek on compressed messages The fix itself is simple. Some explanation on unit tests. Currently we the vast majority of unit test is running with uncompressed messages. I

[jira] [Updated] (KAFKA-3179) Kafka consumer delivers message whose offset is earlier than sought offset.

[ https://issues.apache.org/jira/browse/KAFKA-3179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-3179: Status: Patch Available (was: Open) > Kafka consumer delivers message whose offset is earlier than

[jira] [Commented] (KAFKA-3179) Kafka consumer delivers message whose offset is earlier than sought offset.

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

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

Harsha/Gwen, Thank you both for reviewing the KIP. SASL mechanism negotiation was added specifically to support multiple SASL mechanisms within a broker. This was brought up at the last KIP meeting and the consensus was that it would be useful to support this. It would become harder to add