https://issues.apache.org/jira/browse/KAFKA-760
On Wed, Feb 20, 2013 at 9:02 PM, Neha Narkhede wrote:
> Joe,
>
> What is the JIRA for this issue ?
>
> Thanks,
> Neha
>
>
> On Sun, Feb 17, 2013 at 4:14 PM, Joe Stein wrote:
>
> > for #1 we should come up with some way for folks to deal with that a
Yes, I think that section of the protocol guide could be improved.
Specifically, it would be useful to explain what the " Time" and
"MaxNumberOfOffsets" parameters are used for, as well documenting these
two magic numbers (-1 and -2).
-David
On 2/21/13 12:13 AM, Neha Narkhede wrote:
David,
In the old protocol description the -1 and -2 values are explicitly
mentioned.
https://cwiki.apache.org/confluence/display/KAFKA/Wire+Format
It looks like it had been left out of the new 0.8 docs, however I just
added it.
https://cwiki.apache.org/confluence/display/KAFKA/A+Guide+To+The+Kafka+P
Issue Subscription
Filter: outstanding kafka patches (62 issues)
The list of outstanding kafka patches
Subscriber: kafka-mailing-list
Key Summary
KAFKA-763 Add an option to replica from the largest offset during unclean
leader election
https://issues.apache.org/jira/
Thank you for the feedback on documentation and also for improving it. That
is the best way to have effective documentation.
Thanks,
Neha
On Thu, Feb 21, 2013 at 8:53 AM, Colin Blower wrote:
> In the old protocol description the -1 and -2 values are explicitly
> mentioned.
> https://cwiki.apac
Jun Rao created KAFKA-768:
-
Summary: broker should exit if hitting exceptions durin startup
Key: KAFKA-768
URL: https://issues.apache.org/jira/browse/KAFKA-768
Project: Kafka
Issue Type: Bug
[
https://issues.apache.org/jira/browse/KAFKA-768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-768:
--
Assignee: Jun Rao
Status: Patch Available (was: Open)
> broker should exit if hitting exceptions duri
[
https://issues.apache.org/jira/browse/KAFKA-768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-768:
--
Attachment: kafka-768.patch
Attach a patch.
> broker should exit if hitting exceptions durin st
[
https://issues.apache.org/jira/browse/KAFKA-768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13583555#comment-13583555
]
Sriram Subramanian commented on KAFKA-768:
--
+1
> broker should ex
[
https://issues.apache.org/jira/browse/KAFKA-768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13583582#comment-13583582
]
Swapnil Ghike commented on KAFKA-768:
-
+1
> broker should exit if hitt
[
https://issues.apache.org/jira/browse/KAFKA-768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13583586#comment-13583586
]
Swapnil Ghike commented on KAFKA-768:
-
Also to maintain consistency with Producer/Consu
[
https://issues.apache.org/jira/browse/KAFKA-604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapnil Ghike reassigned KAFKA-604:
---
Assignee: Swapnil Ghike
> Add missing metrics in 0.8
> --
>
>
I'm having trouble building the project with sbt, specifically I am
unable to run package and have the kafka-server-start.sh script work
git clone git://github.com/apache/kafka.git
./sbt update
./sbt "++2.8.0 package"
./bin/kafka-server-start.sh config/server.properties
Exception in thread "mai
The two simplest approaches (short of parsing SBT output for classpaths)
would be to either use https://github.com/n8han/conscript or
https://github.com/sbt/sbt-assembly. Assembly would give you a nice,
self-contained JAR with all deps. Conscript essentially uses SBT to fetch
deps and run. I'm more
[
https://issues.apache.org/jira/browse/KAFKA-768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13583672#comment-13583672
]
Neha Narkhede commented on KAFKA-768:
-
+1
> broker should exit if hitt
Hi Derek,
We probably have a patch for adding assembly at
https://issues.apache.org/jira/browse/KAFKA-733. Can you review it?
Thanks,
Swapnil
On 2/21/13 2:46 PM, "Derek Chen-Becker" wrote:
>The two simplest approaches (short of parsing SBT output for classpaths)
>would be to either use https:/
[
https://issues.apache.org/jira/browse/KAFKA-733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapnil Ghike updated KAFKA-733:
Labels: bugs patch (was: patch)
> Fat jar option for build, or override for ivy cache location
[
https://issues.apache.org/jira/browse/KAFKA-733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapnil Ghike updated KAFKA-733:
Labels: bugs (was: bugs patch)
> Fat jar option for build, or override for ivy cache location
[
https://issues.apache.org/jira/browse/KAFKA-733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapnil Ghike updated KAFKA-733:
Status: Patch Available (was: Open)
> Fat jar option for build, or override for ivy cache locat
[
https://issues.apache.org/jira/browse/KAFKA-733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapnil Ghike updated KAFKA-733:
Assignee: Dave DeMaagd
> Fat jar option for build, or override for ivy cache location
> ---
[
https://issues.apache.org/jira/browse/KAFKA-733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13583772#comment-13583772
]
derek commented on KAFKA-733:
-
Patch looks good. Two questions: why was the merge strategy over
Reviewed. I added my comments on the ticket. Thanks!
On Thu, Feb 21, 2013 at 5:03 PM, Swapnil Ghike wrote:
> Hi Derek,
>
> We probably have a patch for adding assembly at
> https://issues.apache.org/jira/browse/KAFKA-733. Can you review it?
>
> Thanks,
> Swapnil
>
> On 2/21/13 2:46 PM, "Derek C
Sriram Subramanian created KAFKA-769:
Summary: On startup, a brokers highwatermark for every topic
partition gets reset to zero
Key: KAFKA-769
URL: https://issues.apache.org/jira/browse/KAFKA-769
[
https://issues.apache.org/jira/browse/KAFKA-769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede reassigned KAFKA-769:
---
Assignee: Neha Narkhede (was: Sriram Subramanian)
> On startup, a brokers highwatermark f
[
https://issues.apache.org/jira/browse/KAFKA-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13583808#comment-13583808
]
Neha Narkhede commented on KAFKA-769:
-
I will take a look at this.
> O
[
https://issues.apache.org/jira/browse/KAFKA-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13583811#comment-13583811
]
Sriram Subramanian commented on KAFKA-769:
--
I have a fix for this. Do you still wa
[
https://issues.apache.org/jira/browse/KAFKA-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13583813#comment-13583813
]
Neha Narkhede commented on KAFKA-769:
-
Sure, go ahead and attach a patch, if you alread
[
https://issues.apache.org/jira/browse/KAFKA-755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13583829#comment-13583829
]
Jun Rao commented on KAFKA-755:
---
Thanks for the patch. Some comments.
1. Broker.createBroker
[
https://issues.apache.org/jira/browse/KAFKA-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13583883#comment-13583883
]
Sriram Subramanian commented on KAFKA-769:
--
Assigning this back based on the email
[
https://issues.apache.org/jira/browse/KAFKA-769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sriram Subramanian reassigned KAFKA-769:
Assignee: Sriram Subramanian (was: Neha Narkhede)
> On startup, a brokers highw
[
https://issues.apache.org/jira/browse/KAFKA-765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13583886#comment-13583886
]
Sriram Subramanian commented on KAFKA-765:
--
Assigning to Neha as per mail conversa
[
https://issues.apache.org/jira/browse/KAFKA-765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sriram Subramanian reassigned KAFKA-765:
Assignee: Neha Narkhede (was: Sriram Subramanian)
> Corrupted messages in produ
[
https://issues.apache.org/jira/browse/KAFKA-767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sriram Subramanian updated KAFKA-767:
-
Priority: Blocker (was: Major)
> Message Size check should be done after assigning th
[
https://issues.apache.org/jira/browse/KAFKA-756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede closed KAFKA-756.
---
> Processor thread blocks due to infinite loop during fetch response send
> --
[
https://issues.apache.org/jira/browse/KAFKA-753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede closed KAFKA-753.
---
> Kafka broker shuts down while loading segments
> --
>
>
[
https://issues.apache.org/jira/browse/KAFKA-757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede closed KAFKA-757.
---
> System Test Hard Failure cases : "Fatal error during KafkaServerStable
> startup" when hard-failed
[
https://issues.apache.org/jira/browse/KAFKA-750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede closed KAFKA-750.
---
> inconsistent index offset during broker startup
> ---
>
[
https://issues.apache.org/jira/browse/KAFKA-748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede closed KAFKA-748.
---
> Append to index fails due to invalid offset
> ---
>
>
[
https://issues.apache.org/jira/browse/KAFKA-765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede updated KAFKA-765:
Labels: p1 (was: )
> Corrupted messages in produce request could shutdown the broker
>
[
https://issues.apache.org/jira/browse/KAFKA-769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede updated KAFKA-769:
Labels: p1 (was: )
> On startup, a brokers highwatermark for every topic partition gets reset t
[
https://issues.apache.org/jira/browse/KAFKA-768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede updated KAFKA-768:
Labels: p1 (was: )
> broker should exit if hitting exceptions durin startup
> -
[
https://issues.apache.org/jira/browse/KAFKA-755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede updated KAFKA-755:
Labels: p1 (was: )
> standardizing json values stored in ZK
> -
[
https://issues.apache.org/jira/browse/KAFKA-732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede updated KAFKA-732:
Affects Version/s: (was: 0.8)
0.8.1
> MirrorMaker with shallow.iterat
[
https://issues.apache.org/jira/browse/KAFKA-732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede updated KAFKA-732:
Labels: (was: p2)
> MirrorMaker with shallow.iterator.enable=true produces unreadble messages
[
https://issues.apache.org/jira/browse/KAFKA-732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13583930#comment-13583930
]
Neha Narkhede commented on KAFKA-732:
-
Moving this out of 0.8 as per discussion on mail
[
https://issues.apache.org/jira/browse/KAFKA-604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede updated KAFKA-604:
Labels: p1 (was: )
> Add missing metrics in 0.8
> --
>
>
[
https://issues.apache.org/jira/browse/KAFKA-767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede updated KAFKA-767:
Labels: p1 (was: )
> Message Size check should be done after assigning the offsets
> --
[
https://issues.apache.org/jira/browse/KAFKA-767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede updated KAFKA-767:
Component/s: log
> Message Size check should be done after assigning the offsets
> -
[
https://issues.apache.org/jira/browse/KAFKA-762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede updated KAFKA-762:
Labels: p2 (was: )
> Improve second replica assignment
> -
>
>
[
https://issues.apache.org/jira/browse/KAFKA-763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13583932#comment-13583932
]
Neha Narkhede commented on KAFKA-763:
-
Why is this option useful ? The reason we set th
[
https://issues.apache.org/jira/browse/KAFKA-763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede updated KAFKA-763:
Labels: p2 (was: )
> Add an option to replica from the largest offset during unclean leader
>
[
https://issues.apache.org/jira/browse/KAFKA-762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-762:
--
Resolution: Fixed
Fix Version/s: 0.8
Status: Resolved (was: Patch Available)
Thanks for the r
[
https://issues.apache.org/jira/browse/KAFKA-768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-768:
--
Resolution: Fixed
Fix Version/s: 0.8
Status: Resolved (was: Patch Available)
Thanks for the r
[
https://issues.apache.org/jira/browse/KAFKA-763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13583941#comment-13583941
]
Jun Rao commented on KAFKA-763:
---
Unclean leader election happens when we have to select a rep
[
https://issues.apache.org/jira/browse/KAFKA-755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapnil Ghike updated KAFKA-755:
Attachment: kafka-755-v2.patch
Addressed all points.
i. Renamed valueAsString flag to valueInQuotes
Swapnil Ghike created KAFKA-770:
---
Summary: KafkaConfig properties should be verified in the
constructor
Key: KAFKA-770
URL: https://issues.apache.org/jira/browse/KAFKA-770
Project: Kafka
Issue
[
https://issues.apache.org/jira/browse/KAFKA-770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapnil Ghike updated KAFKA-770:
Attachment: kafka-770.patch
Attached a patch.
> KafkaConfig properties should be ve
[
https://issues.apache.org/jira/browse/KAFKA-770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapnil Ghike reassigned KAFKA-770:
---
Assignee: Swapnil Ghike
> KafkaConfig properties should be verified in the constructor
> -
[
https://issues.apache.org/jira/browse/KAFKA-768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13584045#comment-13584045
]
Swapnil Ghike commented on KAFKA-768:
-
Filed KAFKA-770 with a patch.
>
[
https://issues.apache.org/jira/browse/KAFKA-767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sriram Subramanian updated KAFKA-767:
-
Attachment: KAFKA-767-v1.patch
> Message Size check should be done after assigning the
[
https://issues.apache.org/jira/browse/KAFKA-767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13584065#comment-13584065
]
Sriram Subramanian commented on KAFKA-767:
--
Changes
core/src/main/scala/kafka/log
[
https://issues.apache.org/jira/browse/KAFKA-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13584068#comment-13584068
]
Sriram Subramanian commented on KAFKA-706:
--
It has been verified that v2 patch fix
[
https://issues.apache.org/jira/browse/KAFKA-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sriram Subramanian resolved KAFKA-706.
--
Resolution: Fixed
> broker appears to be encoding ProduceResponse, but never sending
63 matches
Mail list logo
