The remaining jiras for 0.8 are listed in the following dashboard. We will
be focusing on the blocker jiras first. Contributions are welcome. We hope
to have an early version for people to try out in mid to late Oct.
https://cwiki.apache.org/confluence/display/KAFKA/Kafka+replication+development
[
https://issues.apache.org/jira/browse/KAFKA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13456309#comment-13456309
]
Otis Gospodnetic commented on KAFKA-133:
+1 for this. Funny, it looks like it has
[
https://issues.apache.org/jira/browse/KAFKA-500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapnil Ghike updated KAFKA-500:
Attachment: kafka-500-v1.patch
1. Created java apis for TopicMetadataRequest and TopicMetadataRespon
[
https://issues.apache.org/jira/browse/KAFKA-500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapnil Ghike reassigned KAFKA-500:
---
Assignee: Swapnil Ghike
> javaapi support for getTopoicMetaData
>
[
https://issues.apache.org/jira/browse/KAFKA-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy updated KAFKA-391:
-
Attachment: KAFKA-391-v4.patch
Here is the rebased patch. I also had to include a small edit to
ReplicaFe
[
https://issues.apache.org/jira/browse/KAFKA-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy resolved KAFKA-6.
Resolution: Invalid (was: Unresolved)
> Support replicating from more than 1 remote kafka cluster
> -
[
https://issues.apache.org/jira/browse/KAFKA-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy resolved KAFKA-401.
--
Resolution: Duplicate
Should be covered by KAFKA-408
> producer-perf-test does not enfo
[
https://issues.apache.org/jira/browse/KAFKA-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy updated KAFKA-435:
-
Affects Version/s: 0.8
> Keep track of the transient test failure for Kafka-343 on Apache Jenkins
> --
[
https://issues.apache.org/jira/browse/KAFKA-430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy updated KAFKA-430:
-
Affects Version/s: 0.8
> Improve the "waitUntilLeaderIsElectedOrChanged" function in TestUtils class
>
[
https://issues.apache.org/jira/browse/KAFKA-484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy updated KAFKA-484:
-
Affects Version/s: 0.8
Labels: replication-testing (was: )
> Move log settings in the
[
https://issues.apache.org/jira/browse/KAFKA-402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy updated KAFKA-402:
-
Affects Version/s: 0.8
> Adding handling various kind of exception support at server side
> --
[
https://issues.apache.org/jira/browse/KAFKA-485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy updated KAFKA-485:
-
Affects Version/s: 0.8
Fix Version/s: 0.8
Labels: replication-testing (was: )
[
https://issues.apache.org/jira/browse/KAFKA-485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy updated KAFKA-485:
-
Description: John Fung (was: Currently this test framework doesn't work
properly in MacOS due to the diff
[
https://issues.apache.org/jira/browse/KAFKA-485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy updated KAFKA-485:
-
Description: Currently this test framework doesn't work properly in MacOS
due to the different "ps" argume
[
https://issues.apache.org/jira/browse/KAFKA-488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy updated KAFKA-488:
-
Affects Version/s: 0.8
Fix Version/s: 0.8
Labels: replication-testing (was: )
[
https://issues.apache.org/jira/browse/KAFKA-492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy updated KAFKA-492:
-
Affects Version/s: 0.8
Fix Version/s: 0.8
Labels: replication-testing (was: )
[
https://issues.apache.org/jira/browse/KAFKA-478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy updated KAFKA-478:
-
Affects Version/s: 0.8
Fix Version/s: 0.8
Labels: replication-testing (was: )
[
https://issues.apache.org/jira/browse/KAFKA-494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy updated KAFKA-494:
-
Affects Version/s: 0.8
Fix Version/s: 0.8
Labels: replication-testing (was: )
[
https://issues.apache.org/jira/browse/KAFKA-494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy updated KAFKA-494:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
Closing - per comment.
[
https://issues.apache.org/jira/browse/KAFKA-502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy updated KAFKA-502:
-
Affects Version/s: 0.8
Fix Version/s: 0.8
Labels: replication-testing (was: )
[
https://issues.apache.org/jira/browse/KAFKA-503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy updated KAFKA-503:
-
Affects Version/s: 0.8
Fix Version/s: 0.8
Labels: replication-testing (was: )
[
https://issues.apache.org/jira/browse/KAFKA-507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy updated KAFKA-507:
-
Affects Version/s: 0.8
Fix Version/s: 0.8
Labels: replication-testing (was: )
[
https://issues.apache.org/jira/browse/KAFKA-514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy updated KAFKA-514:
-
Labels: replication-testing (was: )
> Replication with Leader Failure Test: Log segment files checksu
[
https://issues.apache.org/jira/browse/KAFKA-516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy updated KAFKA-516:
-
Labels: bugs (was: )
> Consider catching all exceptions in ShutdownableThread
> -
[
https://issues.apache.org/jira/browse/KAFKA-517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy updated KAFKA-517:
-
Labels: bugs (was: )
> Ensure that we escape the metric names if they include user strings
>
[
https://issues.apache.org/jira/browse/KAFKA-516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy updated KAFKA-516:
-
Affects Version/s: 0.8
Fix Version/s: 0.8
> Consider catching all exceptions in ShutdownableTh
[
https://issues.apache.org/jira/browse/KAFKA-517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy updated KAFKA-517:
-
Affects Version/s: 0.8
> Ensure that we escape the metric names if they include user strings
> ---
[
https://issues.apache.org/jira/browse/KAFKA-482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy updated KAFKA-482:
-
Affects Version/s: 0.8
Fix Version/s: 0.8
> Make producer to run for the entire duration of th
[
https://issues.apache.org/jira/browse/KAFKA-513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy updated KAFKA-513:
-
Affects Version/s: 0.8
Fix Version/s: 0.8
> Add state change log to Kafka brokers
> --
[
https://issues.apache.org/jira/browse/KAFKA-514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy updated KAFKA-514:
-
Priority: Blocker (was: Major)
Affects Version/s: 0.8
Fix Version/s: 0.8
> Repli
[
https://issues.apache.org/jira/browse/KAFKA-515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13456210#comment-13456210
]
Jay Kreps commented on KAFKA-515:
-
A simpler approach then reference counting would be to d
[
https://issues.apache.org/jira/browse/KAFKA-506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13456207#comment-13456207
]
Jay Kreps commented on KAFKA-506:
-
I am going to begin phase two of this, implementing the
[
https://issues.apache.org/jira/browse/KAFKA-506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps updated KAFKA-506:
Attachment: KAFKA-506-v1.patch
Updated the patch. This patch fixes the remaining failing tests and correctly
Jay Kreps created KAFKA-517:
---
Summary: Ensure that we escape the metric names if they include
user strings
Key: KAFKA-517
URL: https://issues.apache.org/jira/browse/KAFKA-517
Project: Kafka
Issue
[
https://issues.apache.org/jira/browse/KAFKA-463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapnil Ghike updated KAFKA-463:
Attachment: kafka-463-v3.patch
20.1. Letting the constructor be as it is as discussed.
20.2. Made t
Jay Kreps created KAFKA-516:
---
Summary: Consider catching all exceptions in ShutdownableThread
Key: KAFKA-516
URL: https://issues.apache.org/jira/browse/KAFKA-516
Project: Kafka
Issue Type: Bug
[
https://issues.apache.org/jira/browse/KAFKA-499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede updated KAFKA-499:
Attachment: kafka-499-v2.patch
Rebased and fixed a minor JMX bean issue
> Refactor
Swapnil Ghike created KAFKA-515:
---
Summary: Log cleanup can close a file channel opnened by Log.read
before the transfer completes
Key: KAFKA-515
URL: https://issues.apache.org/jira/browse/KAFKA-515
Proj
[
https://issues.apache.org/jira/browse/KAFKA-449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao closed KAFKA-449.
-
> Leader election test
>
>
> Key: KAFKA-449
> URL: https://is
[
https://issues.apache.org/jira/browse/KAFKA-512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-512:
--
Priority: Blocker (was: Major)
Labels: bugs (was: )
> Remove checksum from ByteBufferMessageSet.iter
+1
On Fri, Sep 14, 2012 at 7:50 AM, Joe Stein wrote:
> +1
>
> On Thu, Sep 13, 2012 at 11:51 PM, Jakob Homan wrote:
>
>> +1
>>
>> On Thu, Sep 13, 2012 at 5:38 PM, Joel Koshy wrote:
>>
>> > In KAFKA-391 I tried switching from (topic, partition) tuples to a
>> > TopicPartition case class in the pr
John Fung created KAFKA-514:
---
Summary: Replication with Leader Failure Test: Log segment files
checksum mismatch
Key: KAFKA-514
URL: https://issues.apache.org/jira/browse/KAFKA-514
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede updated KAFKA-513:
Description:
Once KAFKA-499 is checked in, every controller to broker communication can be
modelled
Neha Narkhede created KAFKA-513:
---
Summary: Add state change log to Kafka brokers
Key: KAFKA-513
URL: https://issues.apache.org/jira/browse/KAFKA-513
Project: Kafka
Issue Type: Sub-task
[
https://issues.apache.org/jira/browse/KAFKA-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede updated KAFKA-344:
Parent Issue: KAFKA-327 (was: KAFKA-50)
> migration tool from 0.7 to 0.8
>
Makes sense, I will leave it for now.
-Jay
On Fri, Sep 14, 2012 at 10:14 AM, Jun Rao wrote:
> The current semantics of those exceptions are:
> InvalidMessageException: message is corrupted (crc doesn't match payload)
> InvalidMessageSizeException: message size is larger than the payload size.
>
Yes, we should remove the crc check in the iterator of
ByteBufferMessageSet. Log.append already checks crc, which protects the
server. Consumer, if wants to, could explicitly check the crc on each
message on its own.
Thanks,
Jun
On Fri, Sep 14, 2012 at 9:19 AM, Jay Kreps wrote:
> Okay, I check
[
https://issues.apache.org/jira/browse/KAFKA-449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede updated KAFKA-449:
Resolution: Fixed
Status: Resolved (was: Patch Available)
Just committed this
[
https://issues.apache.org/jira/browse/KAFKA-449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13455952#comment-13455952
]
Neha Narkhede commented on KAFKA-449:
-
+1 on v2. Thanks for the patch !
The current semantics of those exceptions are:
InvalidMessageException: message is corrupted (crc doesn't match payload)
InvalidMessageSizeException: message size is larger than the payload size.
This is mostly used on the consumer side in case we fetch a chunk of bytes
on a wrong starting offset.
[
https://issues.apache.org/jira/browse/KAFKA-499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede updated KAFKA-499:
Attachment: (was: kafka-499-v1.patch)
> Refactor controller state machine
> ---
[
https://issues.apache.org/jira/browse/KAFKA-463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13455942#comment-13455942
]
Jun Rao commented on KAFKA-463:
---
Thanks for patch v2. Some more comments:
20. Log:
20.1 roll
[
https://issues.apache.org/jira/browse/KAFKA-499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede updated KAFKA-499:
Attachment: kafka-499-v1.patch
> Refactor controller state machine
> --
[
https://issues.apache.org/jira/browse/KAFKA-499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede updated KAFKA-499:
Status: Patch Available (was: Open)
> Refactor controller state machine
>
[
https://issues.apache.org/jira/browse/KAFKA-499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede updated KAFKA-499:
Attachment: kafka-499-v1.patch
This patch refactors (almost rewrites) the controller. The controller
[
https://issues.apache.org/jira/browse/KAFKA-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13455928#comment-13455928
]
Joel Koshy commented on KAFKA-391:
--
Ok nm - I see it's because we removed SyncProducer and
[
https://issues.apache.org/jira/browse/KAFKA-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13455927#comment-13455927
]
Joel Koshy commented on KAFKA-391:
--
30 - Why should it be removed?
> Prod
[
https://issues.apache.org/jira/browse/KAFKA-512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps updated KAFKA-512:
Summary: Remove checksum from ByteBufferMessageSet.iterator (was: Remove
checksum from ByteBufferMessageSet
Jay Kreps created KAFKA-512:
---
Summary: Remove checksum from ByteBufferMessageSet
Key: KAFKA-512
URL: https://issues.apache.org/jira/browse/KAFKA-512
Project: Kafka
Issue Type: Bug
Repor
Okay, I checked on this. The producer computes the checksum twice, which is
once too many. The server computes the checksum an astounding 39 times in
0.8 branch! I think this answers the earlier questions: The right thing to
do is clearly to remove the check from the iterator as people are iteratin
I actually think the validBytes() call is looping and hence computing CRCs
too. So actually at least three times.
-Jay
On Fri, Sep 14, 2012 at 9:10 AM, Jay Kreps wrote:
> Hey guys,
>
> I noticed that our ByteBufferMessageSet iterator computes the message CRC
> on iteration. Log.append also loop
Hey guys,
I noticed that our ByteBufferMessageSet iterator computes the message CRC
on iteration. Log.append also loops through all messages and checks the
same checksum. This means we are effectively computing the CRC32 twice
inside Log.append (we may actually be doing it more than that we would
On Thu, Sep 13, 2012 at 10:35 PM, Chris Burroughs wrote:
> On 2012-09-13 13:15, Joe Stein wrote:
> > I am working on a new product that has 0.7.1 in it don't mind even
> > pushing 0.7.2 into or 0.8 and releasing both in succession.
>
> Do yo want help with the mechanics of the release itself?
>
+1
On Thu, Sep 13, 2012 at 11:51 PM, Jakob Homan wrote:
> +1
>
> On Thu, Sep 13, 2012 at 5:38 PM, Joel Koshy wrote:
>
> > In KAFKA-391 I tried switching from (topic, partition) tuples to a
> > TopicPartition case class in the producer/fetch request handling code. I
> > think it helped quite a b
64 matches
Mail list logo
