You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Jun Rao (JIRA)" <ji...@apache.org> on 2012/08/01 18:24:02 UTC
[jira] [Created] (KAFKA-433) ensurePartitionLeaderOnThisBroker
should not access ZK
Jun Rao created KAFKA-433:
-----------------------------
Summary: ensurePartitionLeaderOnThisBroker should not access ZK
Key: KAFKA-433
URL: https://issues.apache.org/jira/browse/KAFKA-433
Project: Kafka
Issue Type: Bug
Components: core
Affects Versions: 0.8
Reporter: Jun Rao
ensurePartitionLeaderOnThisBroker() is called for each produce and fetch request. So, it shouldn't check leadership assignment form ZK. Instead, it should read from the in-memory cache.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (KAFKA-433) ensurePartitionLeaderOnThisBroker
should not access ZK
Posted by "Jun Rao (JIRA)" <ji...@apache.org>.
[ 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
> ------------------------------------------------------
>
> Key: KAFKA-433
> URL: https://issues.apache.org/jira/browse/KAFKA-433
> Project: Kafka
> Issue Type: Bug
> Components: core
> Affects Versions: 0.8
> Reporter: Jun Rao
> Assignee: Jun Rao
> Labels: optimization
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> ensurePartitionLeaderOnThisBroker() is called for each produce and fetch request. So, it shouldn't check leadership assignment form ZK. Instead, it should read from the in-memory cache.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KAFKA-433) ensurePartitionLeaderOnThisBroker
should not access ZK
Posted by "Joel Koshy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joel Koshy updated KAFKA-433:
-----------------------------
Labels: optimization (was: )
> ensurePartitionLeaderOnThisBroker should not access ZK
> ------------------------------------------------------
>
> Key: KAFKA-433
> URL: https://issues.apache.org/jira/browse/KAFKA-433
> Project: Kafka
> Issue Type: Bug
> Components: core
> Affects Versions: 0.8
> Reporter: Jun Rao
> Labels: optimization
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> ensurePartitionLeaderOnThisBroker() is called for each produce and fetch request. So, it shouldn't check leadership assignment form ZK. Instead, it should read from the in-memory cache.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (KAFKA-433) ensurePartitionLeaderOnThisBroker
should not access ZK
Posted by "Jun Rao (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jun Rao closed KAFKA-433.
-------------------------
> ensurePartitionLeaderOnThisBroker should not access ZK
> ------------------------------------------------------
>
> Key: KAFKA-433
> URL: https://issues.apache.org/jira/browse/KAFKA-433
> Project: Kafka
> Issue Type: Bug
> Components: core
> Affects Versions: 0.8
> Reporter: Jun Rao
> Assignee: Jun Rao
> Labels: optimization
> Fix For: 0.8
>
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> ensurePartitionLeaderOnThisBroker() is called for each produce and fetch request. So, it shouldn't check leadership assignment form ZK. Instead, it should read from the in-memory cache.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (KAFKA-433) ensurePartitionLeaderOnThisBroker
should not access ZK
Posted by "Jun Rao (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jun Rao resolved KAFKA-433.
---------------------------
Resolution: Duplicate
Fix Version/s: 0.8
Fixed as part of kafka-351
> ensurePartitionLeaderOnThisBroker should not access ZK
> ------------------------------------------------------
>
> Key: KAFKA-433
> URL: https://issues.apache.org/jira/browse/KAFKA-433
> Project: Kafka
> Issue Type: Bug
> Components: core
> Affects Versions: 0.8
> Reporter: Jun Rao
> Assignee: Jun Rao
> Labels: optimization
> Fix For: 0.8
>
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> ensurePartitionLeaderOnThisBroker() is called for each produce and fetch request. So, it shouldn't check leadership assignment form ZK. Instead, it should read from the in-memory cache.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira