[
https://issues.apache.org/jira/browse/KAFKA-369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-369:
--
Fix Version/s: (was: 0.7.2)
0.8
remove ZK dependency on producer
[
https://issues.apache.org/jira/browse/KAFKA-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13434184#comment-13434184
]
Jun Rao commented on KAFKA-376:
---
Thanks for patch v1. It looks good overall. Some comments
[
https://issues.apache.org/jira/browse/KAFKA-452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-452.
---
Resolution: Duplicate
same as kafka-451
follower replica may need to backoff the fetching
[
https://issues.apache.org/jira/browse/KAFKA-382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-382.
---
Resolution: Not A Problem
Write ordering guarantee violated
[
https://issues.apache.org/jira/browse/KAFKA-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-258.
---
Resolution: Fixed
Assignee: Yang Ye
fixed as part of kafka-369
Remove broker.id from
Jun Rao created KAFKA-458:
-
Summary: remove errorcode from ByteBufferMessageSet
Key: KAFKA-458
URL: https://issues.apache.org/jira/browse/KAFKA-458
Project: Kafka
Issue Type: Sub-task
Jun Rao created KAFKA-459:
-
Summary: KafkaController.RequestSendThread can throw exception on
broker socket
Key: KAFKA-459
URL: https://issues.apache.org/jira/browse/KAFKA-459
Project: Kafka
Issue
Jun Rao created KAFKA-461:
-
Summary: remove support for format for magic byte 0 in 0.8
Key: KAFKA-461
URL: https://issues.apache.org/jira/browse/KAFKA-461
Project: Kafka
Issue Type: Bug
[
https://issues.apache.org/jira/browse/KAFKA-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-371.
---
Resolution: Fixed
Creating topic of empty string puts broker in a bad state
[
https://issues.apache.org/jira/browse/KAFKA-356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13434357#comment-13434357
]
Jun Rao commented on KAFKA-356:
---
The patch seems to miss a new class KafkaThread
[
https://issues.apache.org/jira/browse/KAFKA-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-351:
--
Labels: optimization (was: )
Refactor some new components introduced for replication
[
https://issues.apache.org/jira/browse/KAFKA-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-351:
--
Fix Version/s: 0.8
Refactor some new components introduced for replication
[
https://issues.apache.org/jira/browse/KAFKA-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao reassigned KAFKA-434:
-
Assignee: Jun Rao
IllegalMonitorStateException in ReplicaManager.makerFollower
[
https://issues.apache.org/jira/browse/KAFKA-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao reassigned KAFKA-433:
-
Assignee: Jun Rao
ensurePartitionLeaderOnThisBroker should not access ZK
[
https://issues.apache.org/jira/browse/KAFKA-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-453.
---
Resolution: Duplicate
Fix Version/s: 0.8
same as kafka-451
follower replica may need
[
https://issues.apache.org/jira/browse/KAFKA-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao closed KAFKA-453.
-
follower replica may need to backoff the fetching if leader is not ready yet
[
https://issues.apache.org/jira/browse/KAFKA-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-42:
-
Fix Version/s: 0.8
Labels: optimization (was: )
Support rebalancing the partitions
[
https://issues.apache.org/jira/browse/KAFKA-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-43:
-
Component/s: core
Fix Version/s: 0.8
Labels: optimization (was: )
Rebalance to preferred
[
https://issues.apache.org/jira/browse/KAFKA-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-181:
--
Labels: optimization (was: )
Log errors for unrecognized config options
[
https://issues.apache.org/jira/browse/KAFKA-356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13434603#comment-13434603
]
Jun Rao commented on KAFKA-356:
---
Thanks for patch v2. Some comments:
1. KafkaThread:
1.1
[
https://issues.apache.org/jira/browse/KAFKA-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-351:
--
Attachment: kafka-351_v1.patch
Attach patch v1. An overview of the patch.
A. Use synchronized instead of lock
[
https://issues.apache.org/jira/browse/KAFKA-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-351:
--
Status: Patch Available (was: Open)
Refactor some new components introduced for replication
[
https://issues.apache.org/jira/browse/KAFKA-351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13433322#comment-13433322
]
Jun Rao commented on KAFKA-351:
---
I still see some transient failures in unit tests, most
[
https://issues.apache.org/jira/browse/KAFKA-351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13433385#comment-13433385
]
Jun Rao commented on KAFKA-351:
---
Another change in the patch:
M. Currently, on leaderAndISR
[
https://issues.apache.org/jira/browse/KAFKA-369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-369.
---
Resolution: Fixed
Fix Version/s: 0.7.2
Thanks for the patch. Committed v9 to 0.8
[
https://issues.apache.org/jira/browse/KAFKA-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13431220#comment-13431220
]
Jun Rao commented on KAFKA-369:
---
Thanks for patch v5. A few more comments:
50
[
https://issues.apache.org/jira/browse/KAFKA-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13431475#comment-13431475
]
Jun Rao commented on KAFKA-385:
---
Thanks for the patch. Overall, it seems that metrics-core
[
https://issues.apache.org/jira/browse/KAFKA-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao reassigned KAFKA-351:
-
Assignee: Jun Rao
Refactor some new components introduced for replication
[
https://issues.apache.org/jira/browse/KAFKA-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13429239#comment-13429239
]
Jun Rao commented on KAFKA-369:
---
Thanks for patch v2. Some more comments:
20. ProducerConfig
[
https://issues.apache.org/jira/browse/KAFKA-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13427443#comment-13427443
]
Jun Rao commented on KAFKA-369:
---
Thanks for patch v1. Some comments:
1. ProducerConfig:
1.1
[
https://issues.apache.org/jira/browse/KAFKA-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13427683#comment-13427683
]
Jun Rao commented on KAFKA-435:
---
Trace of first test failure.
[0m[[0minfo[0m] [0mTest
[
https://issues.apache.org/jira/browse/KAFKA-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13427686#comment-13427686
]
Jun Rao commented on KAFKA-435:
---
2nd failure:
[0m[[0minfo[0m] [0mTest Starting
[
https://issues.apache.org/jira/browse/KAFKA-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13427688#comment-13427688
]
Jun Rao commented on KAFKA-435:
---
3rd failure:
[0m[[0minfo[0m] [0mTest Starting
[
https://issues.apache.org/jira/browse/KAFKA-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13426692#comment-13426692
]
Jun Rao commented on KAFKA-376:
---
For 1, yes, you are right. We actually ensure that fetch
[
https://issues.apache.org/jira/browse/KAFKA-343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-343.
---
Resolution: Fixed
Thanks for patch v8. Committed to 0.8.
revisit the become leader
[
https://issues.apache.org/jira/browse/KAFKA-342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-342.
---
Resolution: Fixed
Assignee: Yang Ye
Committed as part of kafka-343
revisit the broker
[
https://issues.apache.org/jira/browse/KAFKA-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-338.
---
Resolution: Fixed
Assignee: Yang Ye (was: Prashanth Menon)
Committed as part of kafka-343
Jun Rao created KAFKA-432:
-
Summary: allow consumer to read from followers
Key: KAFKA-432
URL: https://issues.apache.org/jira/browse/KAFKA-432
Project: Kafka
Issue Type: Bug
Components
Jun Rao created KAFKA-434:
-
Summary: IllegalMonitorStateException in
ReplicaManager.makerFollower
Key: KAFKA-434
URL: https://issues.apache.org/jira/browse/KAFKA-434
Project: Kafka
Issue Type: Bug
[
https://issues.apache.org/jira/browse/KAFKA-379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-379:
--
Attachment: kafka-379_0.8_v1.patch
Attach patch v1 in 0.8. Just created a synchronized singleton that wraps
[
https://issues.apache.org/jira/browse/KAFKA-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13426790#comment-13426790
]
Jun Rao commented on KAFKA-405:
---
Just had a look of v4. A couple of minor comments:
40
Jun Rao created KAFKA-427:
-
Summary:
LogRecoverTest.testHWCheckpointWithFailuresSingleLogSegment has transient
failure
Key: KAFKA-427
URL: https://issues.apache.org/jira/browse/KAFKA-427
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13425852#comment-13425852
]
Jun Rao commented on KAFKA-330:
---
During controller failover, we need to remove unneeded
Jun Rao created KAFKA-428:
-
Summary: need to update leaderAndISR path in ZK conditionally in
ReplicaManager
Key: KAFKA-428
URL: https://issues.apache.org/jira/browse/KAFKA-428
Project: Kafka
Issue
[
https://issues.apache.org/jira/browse/KAFKA-343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-343.
---
Resolution: Fixed
Thanks for patch v6. Committed to 0.8. Filed kafka-427 and kafka-428 as
followup jiras
Chris,
Thanks for following up with this. Do we lose the commit history when
moving to git? If so, maybe it's better to wait until 0.8 is released.
Jun
On Mon, Jul 30, 2012 at 5:40 PM, Chris Burroughs
chris.burrou...@gmail.comwrote:
I was originally going to follow this was a [VOTE] thread,
[
https://issues.apache.org/jira/browse/KAFKA-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13426223#comment-13426223
]
Jun Rao commented on KAFKA-343:
---
Revert commit due to unit test failure
[
https://issues.apache.org/jira/browse/KAFKA-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13426226#comment-13426226
]
Jun Rao commented on KAFKA-431:
---
Not sure if this is due to that JSON.parseFull is not thread
[
https://issues.apache.org/jira/browse/KAFKA-411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13424952#comment-13424952
]
Jun Rao commented on KAFKA-411:
---
Thanks for the patch. It may not be the right fix though
[
https://issues.apache.org/jira/browse/KAFKA-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13425024#comment-13425024
]
Jun Rao commented on KAFKA-376:
---
Prashanth,
Thanks for the patch. Some comments:
1
[
https://issues.apache.org/jira/browse/KAFKA-384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13425180#comment-13425180
]
Jun Rao commented on KAFKA-384:
---
Thanks for the patch. It looks good. Just 1 comment:
1
[
https://issues.apache.org/jira/browse/KAFKA-384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13425294#comment-13425294
]
Jun Rao commented on KAFKA-384:
---
+1 on v2 too.
Fix intermittent test
[
https://issues.apache.org/jira/browse/KAFKA-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao reassigned KAFKA-181:
-
Assignee: Jun Rao
Log errors for unrecognized config options
[
https://issues.apache.org/jira/browse/KAFKA-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-181:
--
Attachment: kafka_181_v1.patch
Log errors for unrecognized config options
[
https://issues.apache.org/jira/browse/KAFKA-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-181:
--
Affects Version/s: 0.8
Status: Patch Available (was: Open)
Attach patch v1. Added a wrapper
[
https://issues.apache.org/jira/browse/KAFKA-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13424141#comment-13424141
]
Jun Rao commented on KAFKA-343:
---
Thanks for patch v4. Some more comments:
50
[
https://issues.apache.org/jira/browse/KAFKA-412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-412:
--
Attachment: kafka-412_v1.patch
deal with empty TopicData list in producer and fetch request
[
https://issues.apache.org/jira/browse/KAFKA-412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-412:
--
Fix Version/s: 0.8
Assignee: Jun Rao
Status: Patch Available (was: Open)
Attach patch v1
[
https://issues.apache.org/jira/browse/KAFKA-413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-413:
--
Resolution: Fixed
Fix Version/s: 0.8
Status: Resolved (was: Patch Available)
Thanks
[
https://issues.apache.org/jira/browse/KAFKA-420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13423248#comment-13423248
]
Jun Rao commented on KAFKA-420:
---
First of all, we need to think through what message commits
[
https://issues.apache.org/jira/browse/KAFKA-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13423292#comment-13423292
]
Jun Rao commented on KAFKA-181:
---
That sounds like a good idea. However, how do we know
[
https://issues.apache.org/jira/browse/KAFKA-418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-418:
--
Status: Patch Available (was: Open)
NullPointerException in ConsumerFetcherManager
[
https://issues.apache.org/jira/browse/KAFKA-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13423578#comment-13423578
]
Jun Rao commented on KAFKA-181:
---
That's reasonable for broker configs. What about configs
[
https://issues.apache.org/jira/browse/KAFKA-412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-412:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Changed the naming. Committed to 0.8
[
https://issues.apache.org/jira/browse/KAFKA-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13421235#comment-13421235
]
Jun Rao commented on KAFKA-350:
---
Thanks for patch v3.
For 21, my point
Jun Rao created KAFKA-412:
-
Summary: deal with empty TopicData list in producer and fetch
request
Key: KAFKA-412
URL: https://issues.apache.org/jira/browse/KAFKA-412
Project: Kafka
Issue Type: Bug
[
https://issues.apache.org/jira/browse/KAFKA-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13421590#comment-13421590
]
Jun Rao commented on KAFKA-350:
---
Thanks for patch v4. We are almost there.
21
Jun Rao created KAFKA-413:
-
Summary: single_host_multi_brokers system test fails on laptop
Key: KAFKA-413
URL: https://issues.apache.org/jira/browse/KAFKA-413
Project: Kafka
Issue Type: Bug
[
https://issues.apache.org/jira/browse/KAFKA-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13420734#comment-13420734
]
Jun Rao commented on KAFKA-350:
---
Thanks for patch v2. Some comments:
20. PartitionMetadata
[
https://issues.apache.org/jira/browse/KAFKA-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13421086#comment-13421086
]
Jun Rao commented on KAFKA-405:
---
Thanks for patch v2. Some comments:
20. Log.truncateTo
[
https://issues.apache.org/jira/browse/KAFKA-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13420325#comment-13420325
]
Jun Rao commented on KAFKA-407:
---
In this case, we probably just want to throw the exception
It seems that the error is introduced when parsing the topic string. Do you
know what topic triggered the error?
Thanks,
Jun
On Thu, Jul 12, 2012 at 6:12 PM, Jonathan Creasy jcre...@box.com wrote:
I think a poorly implemented Producer in our dev environment may have
triggered a bug in Kafka.
[
https://issues.apache.org/jira/browse/KAFKA-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13414122#comment-13414122
]
Jun Rao commented on KAFKA-343:
---
Thanks for patch v3. A few more comments:
40
Hi,
We close the following jira this week.
KAFKA-362: ZKConsumerConnector needs to reconnect to new leader after
leader change in a partition
The following jiras are under review.
KAFKA-343: Leader election, become leader, become follower (v3. A,C)
KAFKA-338: controller failover (V3. D)
We have
[
https://issues.apache.org/jira/browse/KAFKA-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13412975#comment-13412975
]
Jun Rao commented on KAFKA-343:
---
Thanks for patch v2. It's in a much better shape now. Some
[
https://issues.apache.org/jira/browse/KAFKA-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13411723#comment-13411723
]
Jun Rao commented on KAFKA-380:
---
Thanks for patch v3. Shouldn't we set invoke_failures
[
https://issues.apache.org/jira/browse/KAFKA-362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-362:
--
Attachment: kafka-362_v3.patch
Thanks for the review. Attach patch v3.
1a. fixed
1b. Didn't notice those
[
https://issues.apache.org/jira/browse/KAFKA-306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-306:
--
Resolution: Fixed
Fix Version/s: 0.8
Status: Resolved (was: Patch Available)
John, thanks
[
https://issues.apache.org/jira/browse/KAFKA-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13410646#comment-13410646
]
Jun Rao commented on KAFKA-380:
---
Patch v2 doesn't apply after kafka-306 is committed. Could
[
https://issues.apache.org/jira/browse/KAFKA-397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13410671#comment-13410671
]
Jun Rao commented on KAFKA-397:
---
Yes, if you wipe off the log. You need to clean up offsets
[
https://issues.apache.org/jira/browse/KAFKA-362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-362:
--
Attachment: kafka-362_v2.patch
Attache patch v2 with minor changes to make sure that no more fetcher threads
[
https://issues.apache.org/jira/browse/KAFKA-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13409804#comment-13409804
]
Jun Rao commented on KAFKA-139:
---
I did a new checkout of 0.8 branch, applied patch v3
[
https://issues.apache.org/jira/browse/KAFKA-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13409864#comment-13409864
]
Jun Rao commented on KAFKA-139:
---
Also, does DefaultEventHandler.partitionAndCollate fail
[
https://issues.apache.org/jira/browse/KAFKA-306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13409985#comment-13409985
]
Jun Rao commented on KAFKA-306:
---
Patch v8 looks good overall. Some minor comments
[
https://issues.apache.org/jira/browse/KAFKA-362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-362:
--
Fix Version/s: 0.8
Status: Patch Available (was: Open)
ZookeeperConsumerConnector needs
[
https://issues.apache.org/jira/browse/KAFKA-362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-362:
--
Attachment: kafka-362_v1.patch
Attach patch v1. The patch replaces Fetcher and FetcherRunnable
[
https://issues.apache.org/jira/browse/KAFKA-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13408062#comment-13408062
]
Jun Rao commented on KAFKA-139:
---
Derek,
For the 0.8 branch
[
https://issues.apache.org/jira/browse/KAFKA-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13408224#comment-13408224
]
Jun Rao commented on KAFKA-139:
---
I applied the patch and did ./sbt +clean +package
, Jun Rao jun...@gmail.com wrote:
Joe,
Since this is still fresh in your mind, could you write a short
description
of the release process (probably under developer on the site) including
copying the artifact to the dist directory?
Also, are you still able to do svn up under /www
[
https://issues.apache.org/jira/browse/KAFKA-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13408462#comment-13408462
]
Jun Rao commented on KAFKA-139:
---
Derek, thanks for the new patch. A few more comments:
10
Hi,
We didn't close any jira this week, but have patch under review for the
following jiras.
KAFKA-343: Leader election, become leader, become follower (v3. A,C)
KAFKA-338: controller failover (V3. D)
We have people signed up on the following jiras:
KAFKA-350: Improve the highwatermark
[
https://issues.apache.org/jira/browse/KAFKA-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13407233#comment-13407233
]
Jun Rao commented on KAFKA-383:
---
+1
copied the 0.7.0 release to the dist
Joe,
Since this is still fresh in your mind, could you write a short description
of the release process (probably under developer on the site) including
copying the artifact to the dist directory?
Also, are you still able to do svn up under /www/
incubator.apache.org/content/kafka? It complains
[
https://issues.apache.org/jira/browse/KAFKA-393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13407252#comment-13407252
]
Jun Rao commented on KAFKA-393:
---
Since this is not very critical, we probably should only fix
[
https://issues.apache.org/jira/browse/KAFKA-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13407453#comment-13407453
]
Jun Rao commented on KAFKA-139:
---
Thanks for the patch. Can't apply the patch to 0.8 cleanly
Derek,
Thanks for your help. Could you attach the patch to this jira:
https://issues.apache.org/jira/browse/KAFKA-139?
Jun
On Mon, Jul 2, 2012 at 8:34 AM, Derek Chen-Becker de...@precog.com wrote:
I've put together an preliminary patch (attached) against kafka to build
using SBT 0.11.3 with
[
https://issues.apache.org/jira/browse/KAFKA-382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13404010#comment-13404010
]
Jun Rao commented on KAFKA-382:
---
Currently, each produce request blocks on a response, which
[
https://issues.apache.org/jira/browse/KAFKA-381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13404021#comment-13404021
]
Jun Rao commented on KAFKA-381:
---
The problem is likely due to what Guozhang described. In 0.7
[
https://issues.apache.org/jira/browse/KAFKA-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13404182#comment-13404182
]
Jun Rao commented on KAFKA-353:
---
It's ok to handle the remaining issues in separate jiras. +1
[
https://issues.apache.org/jira/browse/KAFKA-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13403148#comment-13403148
]
Jun Rao commented on KAFKA-378:
---
+1
mirrors but must never be used
401 - 500 of 990 matches
Mail list logo
