Jun Rao created KAFKA-579:
-
Summary: remove connection timeout in SyncProducer
Key: KAFKA-579
URL: https://issues.apache.org/jira/browse/KAFKA-579
Project: Kafka
Issue Type: Bug
Components
[
https://issues.apache.org/jira/browse/KAFKA-340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13479056#comment-13479056
]
Jun Rao commented on KAFKA-340:
---
Thanks for the patch. Looks good overall. Some comments:
10
Jun Rao created KAFKA-577:
-
Summary: extend DumpLogSegments to verify consistency btw data and
index
Key: KAFKA-577
URL: https://issues.apache.org/jira/browse/KAFKA-577
Project: Kafka
Issue Type
Jun Rao created KAFKA-578:
-
Summary: Leader finder thread in ConsumerFetcherManager needs to
handle exceptions
Key: KAFKA-578
URL: https://issues.apache.org/jira/browse/KAFKA-578
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-573:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Thanks for the review. Removed
[
https://issues.apache.org/jira/browse/KAFKA-566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13477973#comment-13477973
]
Jun Rao commented on KAFKA-566:
---
Madhusudan,
Your understanding is correct. However
[
https://issues.apache.org/jira/browse/KAFKA-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-573:
--
Attachment: kafka-573.patch
Attach a patch. There are 2 problems. The first one is the most severe one. We
[
https://issues.apache.org/jira/browse/KAFKA-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-573:
--
Fix Version/s: 0.8
Affects Version/s: 0.8
Status: Patch Available (was: Open
[
https://issues.apache.org/jira/browse/KAFKA-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao reassigned KAFKA-573:
-
Assignee: Jun Rao
System Test : Leader Failure Log Segment Checksum Mismatched When
request-num
Jun Rao created KAFKA-574:
-
Summary: KafkaController unnecessarily reads leaderAndIsr info
from ZK
Key: KAFKA-574
URL: https://issues.apache.org/jira/browse/KAFKA-574
Project: Kafka
Issue Type: Bug
Jun Rao created KAFKA-575:
-
Summary: Partition.makeFollower() reads broker info from ZK
Key: KAFKA-575
URL: https://issues.apache.org/jira/browse/KAFKA-575
Project: Kafka
Issue Type: Bug
[
https://issues.apache.org/jira/browse/KAFKA-557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao closed KAFKA-557.
-
Replica fetch thread doesn't need to recompute message id
[
https://issues.apache.org/jira/browse/KAFKA-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao closed KAFKA-42.
Support rebalancing the partitions with replication
[
https://issues.apache.org/jira/browse/KAFKA-543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao closed KAFKA-543.
-
Metadata request from DefaultEventHandler.handle repeats same topic over and
over
[
https://issues.apache.org/jira/browse/KAFKA-525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-525.
---
Resolution: Duplicate
Fix Version/s: 0.8
newly created partitions are not added
[
https://issues.apache.org/jira/browse/KAFKA-525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao closed KAFKA-525.
-
Fixed in kafka-42.
newly created partitions are not added to ReplicaStateMachine
[
https://issues.apache.org/jira/browse/KAFKA-188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13475735#comment-13475735
]
Jun Rao commented on KAFKA-188:
---
Thanks for the patch. A couple of comments:
1. It's
[
https://issues.apache.org/jira/browse/KAFKA-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-567:
--
Status: Patch Available (was: Open)
Replication Data Loss in Mirror Maker Bouncing testcase
[
https://issues.apache.org/jira/browse/KAFKA-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao closed KAFKA-567.
-
Replication Data Loss in Mirror Maker Bouncing testcase
[
https://issues.apache.org/jira/browse/KAFKA-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-567:
--
Resolution: Fixed
Fix Version/s: 0.8
Status: Resolved (was: Patch Available)
Thanks
[
https://issues.apache.org/jira/browse/KAFKA-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13475429#comment-13475429
]
Jun Rao commented on KAFKA-43:
--
Overall, patch looks good. It would useful to add an option so
[
https://issues.apache.org/jira/browse/KAFKA-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13475461#comment-13475461
]
Jun Rao commented on KAFKA-43:
--
Thanks for patch v2.
Thanks for patch v2. Just some minor
[
https://issues.apache.org/jira/browse/KAFKA-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13474299#comment-13474299
]
Jun Rao commented on KAFKA-267:
---
Thanks for patch v3. The code is still pretty messy, mostly
[
https://issues.apache.org/jira/browse/KAFKA-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13474428#comment-13474428
]
Jun Rao commented on KAFKA-567:
---
Took a quick look.
Log in source broker
[
https://issues.apache.org/jira/browse/KAFKA-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-567:
--
Attachment: kafka-567.patch
Attach a patch. The problem is that async producer didn't drain the last batch
[
https://issues.apache.org/jira/browse/KAFKA-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao reassigned KAFKA-567:
-
Assignee: Jun Rao
Replication Data Loss in Mirror Maker Bouncing testcase
[
https://issues.apache.org/jira/browse/KAFKA-553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-553:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Thanks for the patch. Committed to 0.8
[
https://issues.apache.org/jira/browse/KAFKA-553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao closed KAFKA-553.
-
confusing reference to zk.connect in config/producer.properties
[
https://issues.apache.org/jira/browse/KAFKA-510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao closed KAFKA-510.
-
broker needs to know the replication factor per partition
[
https://issues.apache.org/jira/browse/KAFKA-510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-510.
---
Resolution: Fixed
Thanks for patch v7. Committed to 0.8 with the following minor refactoring
[
https://issues.apache.org/jira/browse/KAFKA-550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13473346#comment-13473346
]
Jun Rao commented on KAFKA-550:
---
Could you open a separate jira for improving partition
[
https://issues.apache.org/jira/browse/KAFKA-563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-563.
---
Resolution: Fixed
Committed a trivial fix to 0.8.
KafkaScheduler shutdown
[
https://issues.apache.org/jira/browse/KAFKA-563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao closed KAFKA-563.
-
KafkaScheduler shutdown in ZookeeperConsumerConnector should check for
config.autocommit
[
https://issues.apache.org/jira/browse/KAFKA-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13473359#comment-13473359
]
Jun Rao commented on KAFKA-42:
--
+1 on the patch. Still see
[
https://issues.apache.org/jira/browse/KAFKA-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13473373#comment-13473373
]
Jun Rao commented on KAFKA-510:
---
Unfortunately, the jira module that we use is no-reopen
[
https://issues.apache.org/jira/browse/KAFKA-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13473382#comment-13473382
]
Jun Rao commented on KAFKA-267:
---
Can't find a revision that I can apply the patch cleanly
[
https://issues.apache.org/jira/browse/KAFKA-551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13472470#comment-13472470
]
Jun Rao commented on KAFKA-551:
---
Yes, you are right. The code looks good. The confusion
[
https://issues.apache.org/jira/browse/KAFKA-516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao closed KAFKA-516.
-
Consider catching all exceptions in ShutdownableThread
[
https://issues.apache.org/jira/browse/KAFKA-511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-511:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Fixed in KAFKA-506
offset
[
https://issues.apache.org/jira/browse/KAFKA-512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao closed KAFKA-512.
-
Assignee: Jay Kreps
Remove checksum from ByteBufferMessageSet.iterator
[
https://issues.apache.org/jira/browse/KAFKA-512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-512.
---
Resolution: Fixed
Fixed in KAFKA-506.
Remove checksum from ByteBufferMessageSet.iterator
[
https://issues.apache.org/jira/browse/KAFKA-497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-497.
---
Resolution: Fixed
With KAFKA-506, this is no longer an issue. Since offsets are logical, the
consumer can
[
https://issues.apache.org/jira/browse/KAFKA-497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao closed KAFKA-497.
-
recover consumer during unclean leadership change
[
https://issues.apache.org/jira/browse/KAFKA-547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13472497#comment-13472497
]
Jun Rao commented on KAFKA-547:
---
Thanks for the patch. Committed to trunk. Could you patch
[
https://issues.apache.org/jira/browse/KAFKA-543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-543:
--
Priority: Blocker (was: Major)
Labels: bugs (was: )
Metadata request from
[
https://issues.apache.org/jira/browse/KAFKA-531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-531.
---
Resolution: Duplicate
Fix Version/s: 0.8
Duplicate of kafka-551. Caused by the same problem
[
https://issues.apache.org/jira/browse/KAFKA-531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao closed KAFKA-531.
-
kafka.server.ReplicaManager: java.nio.channels.NonWritableChannelException
[
https://issues.apache.org/jira/browse/KAFKA-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-544:
--
Priority: Blocker (was: Major)
Labels: bugs (was: )
Retain key in producer
[
https://issues.apache.org/jira/browse/KAFKA-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13472511#comment-13472511
]
Jun Rao commented on KAFKA-544:
---
This plan sounds good to me.
Retain key
Jun Rao created KAFKA-556:
-
Summary: limit log segment size to 2GB in broker config
Key: KAFKA-556
URL: https://issues.apache.org/jira/browse/KAFKA-556
Project: Kafka
Issue Type: Bug
[
https://issues.apache.org/jira/browse/KAFKA-551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao closed KAFKA-551.
-
Log.truncateTo() may need to trucate immutable log segment
[
https://issues.apache.org/jira/browse/KAFKA-511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao closed KAFKA-511.
-
offset returned in Producer response may not be correct
[
https://issues.apache.org/jira/browse/KAFKA-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao closed KAFKA-474.
-
support changing host/port of a broker
--
Key: KAFKA-474
[
https://issues.apache.org/jira/browse/KAFKA-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-474.
---
Resolution: Fixed
Assignee: David Arthur
Thanks for the patch. Committed to 0.8
[
https://issues.apache.org/jira/browse/KAFKA-502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13471616#comment-13471616
]
Jun Rao commented on KAFKA-502:
---
Thanks for patch v6. A few more comments:
60. Most
[
https://issues.apache.org/jira/browse/KAFKA-506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13471698#comment-13471698
]
Jun Rao commented on KAFKA-506:
---
+1 from me.
Store logical offset in log
[
https://issues.apache.org/jira/browse/KAFKA-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13471733#comment-13471733
]
Jun Rao commented on KAFKA-42:
--
Thanks for patch v3. Looks good to me overall. Just one comment
[
https://issues.apache.org/jira/browse/KAFKA-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13472121#comment-13472121
]
Jun Rao commented on KAFKA-42:
--
Thanks for patch v4
[
https://issues.apache.org/jira/browse/KAFKA-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13472123#comment-13472123
]
Jun Rao commented on KAFKA-42:
--
Also, could you make the two new scripts in bin/ executable
[
https://issues.apache.org/jira/browse/KAFKA-432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13472126#comment-13472126
]
Jun Rao commented on KAFKA-432:
---
Patch no longer applies. Could you rebase
[
https://issues.apache.org/jira/browse/KAFKA-551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13472133#comment-13472133
]
Jun Rao commented on KAFKA-551:
---
Thanks for the patch. Looks good. Just one comment.
1
[
https://issues.apache.org/jira/browse/KAFKA-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-539.
---
Resolution: Fixed
Fix Version/s: 0.8
Thanks for the patch. Committed to 0.8
[
https://issues.apache.org/jira/browse/KAFKA-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao closed KAFKA-539.
-
Replica.hw should be initialized to the smaller of checkedpointed HW and log
end offset
[
https://issues.apache.org/jira/browse/KAFKA-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13472145#comment-13472145
]
Jun Rao commented on KAFKA-510:
---
Patch doesn't seem to apply to 0.8.
The text leading up
[
https://issues.apache.org/jira/browse/KAFKA-550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13472158#comment-13472158
]
Jun Rao commented on KAFKA-550:
---
Thanks for the patch. What was the bug? Is it the implicit
Benson,
Thanks for checking. Since Apache Kafka was started, we have added 3 new
committers, each from a different company. The adoption of Kafka has also
been increasing significantly. In the Oct report, we just documented the
incremental change since last quater. Now that we are preparing for
Alan,
Committer list is now updated. Could you sign off?
Thanks,
Jun
On Wed, Sep 26, 2012 at 3:50 PM, Alan D. Cabrera l...@toolazydogs.comwrote:
On Sep 26, 2012, at 3:18 PM, Jakob Homan wrote:
OK, everybody's good to go. I'll add the new three new committers in the
text to be VOTED on
[
https://issues.apache.org/jira/browse/KAFKA-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-42:
-
Attachment: kafka-514_v1.patch
This seems to be the same problem as in kafka-525, which is supposed to be
fixed
[
https://issues.apache.org/jira/browse/KAFKA-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-42:
-
Comment: was deleted
(was: This seems to be the same problem as in kafka-525, which is supposed to
be fixed
[
https://issues.apache.org/jira/browse/KAFKA-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-42:
-
Attachment: (was: kafka-514_v1.patch)
Support rebalancing the partitions with replication
Jun Rao created KAFKA-551:
-
Summary: Log.truncateTo() may need to trucate immutable log segment
Key: KAFKA-551
URL: https://issues.apache.org/jira/browse/KAFKA-551
Project: Kafka
Issue Type: Bug
[
https://issues.apache.org/jira/browse/KAFKA-551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13470900#comment-13470900
]
Jun Rao commented on KAFKA-551:
---
Currently, we mark the first n-1 segments as read-only
[
https://issues.apache.org/jira/browse/KAFKA-514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-514:
--
Attachment: kafka-514_v2.patch
Attach patch v2 (includes v1 changes). This is just a temporary fix for
kafka
[
https://issues.apache.org/jira/browse/KAFKA-502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13469506#comment-13469506
]
Jun Rao commented on KAFKA-502:
---
Thanks for patch v3. This looks great.
0. Do all new tests
[
https://issues.apache.org/jira/browse/KAFKA-474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13469522#comment-13469522
]
Jun Rao commented on KAFKA-474:
---
Yes, fetcherSourceBroker is actually no longer needed
[
https://issues.apache.org/jira/browse/KAFKA-456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13469530#comment-13469530
]
Jun Rao commented on KAFKA-456:
---
Thanks for the patch. Committed to 0.8.
This performance
[
https://issues.apache.org/jira/browse/KAFKA-456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-456:
--
Resolution: Fixed
Assignee: David Arthur
Status: Resolved (was: Patch Available
[
https://issues.apache.org/jira/browse/KAFKA-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13469604#comment-13469604
]
Jun Rao commented on KAFKA-543:
---
Thanks for the patch. Good catch. +1
[
https://issues.apache.org/jira/browse/KAFKA-506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13469655#comment-13469655
]
Jun Rao commented on KAFKA-506:
---
Thanks for patch v5.
50. There is still a potential issue
[
https://issues.apache.org/jira/browse/KAFKA-506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13469945#comment-13469945
]
Jun Rao commented on KAFKA-506:
---
What we can do is to hold off committing other conflicting
[
https://issues.apache.org/jira/browse/KAFKA-502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13469960#comment-13469960
]
Jun Rao commented on KAFKA-502:
---
Thanks for patch v4. A comment and a couple of questions
[
https://issues.apache.org/jira/browse/KAFKA-502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13469960#comment-13469960
]
Jun Rao edited comment on KAFKA-502 at 10/5/12 12:43 PM:
-
Thanks
Joe,
From https://incubator.apache.org/guides/releasemanagement.html#rules, the
rules are:
Each release requires a positive vote binding on Apache. This means a .
There is usually no need for this vote to be private. (A rare exception
might be a -1 due to a nearly discovered security issue, for
, that was my question is if
Joel's vote is binding now... it would be upon graduating as would mine
but was not sure what the rules were now, more for my own edification than
anything else I am going to send email for IPMC to get a vote going there
On Wed, Oct 3, 2012 at 11:26 AM, Jun Rao jun
[
https://issues.apache.org/jira/browse/KAFKA-506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13468644#comment-13468644
]
Jun Rao commented on KAFKA-506:
---
There is another issue:
45. ConsumerIterator: Now that we
I think you mean DefaultEventHandler. Yes, kafka-409 has been created for
that.
Thanks,
Jun
On Tue, Oct 2, 2012 at 4:50 PM, Jay Kreps jay.kr...@gmail.com wrote:
Hey Guys,
The code in the Producer has gotten very dense and spaghetti-like. I see a
lot of types like
Map[TopicAndPartition,
[
https://issues.apache.org/jira/browse/KAFKA-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13468825#comment-13468825
]
Jun Rao commented on KAFKA-508:
---
Hi, Joe,
Do you still plan to work on this jira? Thanks
[
https://issues.apache.org/jira/browse/KAFKA-506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13468896#comment-13468896
]
Jun Rao commented on KAFKA-506:
---
Patch v4 looks good overall. A couple of remaining issues
[
https://issues.apache.org/jira/browse/KAFKA-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-540:
--
Fix Version/s: 0.8
Status: Patch Available (was: Open)
log.append() should halt on IOException
[
https://issues.apache.org/jira/browse/KAFKA-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-540:
--
Attachment: kafka-540.patch
Attach a patch to fix the issue.
log.append() should halt
[
https://issues.apache.org/jira/browse/KAFKA-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao reassigned KAFKA-540:
-
Assignee: Jun Rao
log.append() should halt on IOException
[
https://issues.apache.org/jira/browse/KAFKA-432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13469034#comment-13469034
]
Jun Rao commented on KAFKA-432:
---
Thanks for patch v2. A few other minor comments:
10
[
https://issues.apache.org/jira/browse/KAFKA-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-540:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Thanks for the review. Committed 0.8
[
https://issues.apache.org/jira/browse/KAFKA-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao closed KAFKA-540.
-
log.append() should halt on IOException
---
Key: KAFKA
Could other people help on the vote?
Thanks,
Jun
On Fri, Sep 28, 2012 at 7:40 PM, Joe Stein crypt...@gmail.com wrote:
Hello,
This is the fifth candidate for the third incubator release for Apache
Kafka, version 0.7.2-incubating.
This release fixes the following issues
[
https://issues.apache.org/jira/browse/KAFKA-509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-509.
---
Resolution: Fixed
Thanks for patch v2. Removed unused import in LogManager and added a comment.
Committed
[
https://issues.apache.org/jira/browse/KAFKA-432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13467868#comment-13467868
]
Jun Rao commented on KAFKA-432:
---
Thanks for patch v1. Some comments:
1
[
https://issues.apache.org/jira/browse/KAFKA-506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13468350#comment-13468350
]
Jun Rao commented on KAFKA-506:
---
Thanks for patch v3. We are almost there. A few more
[
https://issues.apache.org/jira/browse/KAFKA-495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-495:
--
Fix Version/s: 0.7.2
Handle topic names with / on Kafka server
[
https://issues.apache.org/jira/browse/KAFKA-495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-495:
--
Fix Version/s: (was: 0.7.1)
Handle topic names with / on Kafka server
101 - 200 of 990 matches
Mail list logo
