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 (Created) (JIRA)" <ji...@apache.org> on 2012/04/03 20:28:23 UTC
[jira] [Created] (KAFKA-325) revisit broker config in 0.8
revisit broker config in 0.8
----------------------------
Key: KAFKA-325
URL: https://issues.apache.org/jira/browse/KAFKA-325
Project: Kafka
Issue Type: Improvement
Components: core
Affects Versions: 0.8
Reporter: Jun Rao
With the create topic ddl, some of the broker configs like topic.partition.count.map probably don't make sense anymore.
--
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-325) revisit broker config in 0.8
Posted by "Jun Rao (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jun Rao updated KAFKA-325:
--------------------------
Labels: optimization (was: replication)
> revisit broker config in 0.8
> ----------------------------
>
> Key: KAFKA-325
> URL: https://issues.apache.org/jira/browse/KAFKA-325
> Project: Kafka
> Issue Type: Improvement
> Components: core
> Affects Versions: 0.8
> Reporter: Jun Rao
> Labels: optimization
>
> With the create topic ddl, some of the broker configs like topic.partition.count.map probably don't make sense anymore.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (KAFKA-325) revisit broker config in 0.8
Posted by "Jun Rao (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jun Rao resolved KAFKA-325.
---------------------------
Resolution: Fixed
Fix Version/s: 0.8
Thanks for patch v3. Committed to 0.8.
> revisit broker config in 0.8
> ----------------------------
>
> Key: KAFKA-325
> URL: https://issues.apache.org/jira/browse/KAFKA-325
> Project: Kafka
> Issue Type: Improvement
> Components: core
> Affects Versions: 0.8
> Reporter: Jun Rao
> Assignee: Swapnil Ghike
> Priority: Blocker
> Labels: optimization
> Fix For: 0.8
>
> Attachments: kafka-300-v1.patch, kafka-325-v2.patch, kafka-325-v3.patch
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> With the create topic ddl, some of the broker configs like topic.partition.count.map probably don't make sense anymore.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KAFKA-325) revisit broker config in 0.8
Posted by "Neha Narkhede (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Neha Narkhede updated KAFKA-325:
--------------------------------
Labels: replication (was: )
> revisit broker config in 0.8
> ----------------------------
>
> Key: KAFKA-325
> URL: https://issues.apache.org/jira/browse/KAFKA-325
> Project: Kafka
> Issue Type: Improvement
> Components: core
> Affects Versions: 0.8
> Reporter: Jun Rao
> Labels: replication
>
> With the create topic ddl, some of the broker configs like topic.partition.count.map probably don't make sense anymore.
--
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-325) revisit broker config in 0.8
Posted by "Joel Koshy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joel Koshy updated KAFKA-325:
-----------------------------
Priority: Blocker (was: Major)
> revisit broker config in 0.8
> ----------------------------
>
> Key: KAFKA-325
> URL: https://issues.apache.org/jira/browse/KAFKA-325
> Project: Kafka
> Issue Type: Improvement
> Components: core
> Affects Versions: 0.8
> Reporter: Jun Rao
> Priority: Blocker
> Labels: optimization
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> With the create topic ddl, some of the broker configs like topic.partition.count.map probably don't make sense anymore.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KAFKA-325) revisit broker config in 0.8
Posted by "Jun Rao (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13454917#comment-13454917 ]
Jun Rao commented on KAFKA-325:
-------------------------------
Thanks for the patch. Just one comment.
KafkaConfig: Could you remove stateChangeQSize and monitoringPeriodSecs? Neither is actually used.
> revisit broker config in 0.8
> ----------------------------
>
> Key: KAFKA-325
> URL: https://issues.apache.org/jira/browse/KAFKA-325
> Project: Kafka
> Issue Type: Improvement
> Components: core
> Affects Versions: 0.8
> Reporter: Jun Rao
> Assignee: Swapnil Ghike
> Priority: Blocker
> Labels: optimization
> Attachments: kafka-300-v1.patch, kafka-325-v2.patch
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> With the create topic ddl, some of the broker configs like topic.partition.count.map probably don't make sense anymore.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (KAFKA-325) revisit broker config in 0.8
Posted by "Swapnil Ghike (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Swapnil Ghike reassigned KAFKA-325:
-----------------------------------
Assignee: Swapnil Ghike
> revisit broker config in 0.8
> ----------------------------
>
> Key: KAFKA-325
> URL: https://issues.apache.org/jira/browse/KAFKA-325
> Project: Kafka
> Issue Type: Improvement
> Components: core
> Affects Versions: 0.8
> Reporter: Jun Rao
> Assignee: Swapnil Ghike
> Priority: Blocker
> Labels: optimization
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> With the create topic ddl, some of the broker configs like topic.partition.count.map probably don't make sense anymore.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KAFKA-325) revisit broker config in 0.8
Posted by "Jun Rao (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jun Rao updated KAFKA-325:
--------------------------
Remaining Estimate: 24h
Original Estimate: 24h
> revisit broker config in 0.8
> ----------------------------
>
> Key: KAFKA-325
> URL: https://issues.apache.org/jira/browse/KAFKA-325
> Project: Kafka
> Issue Type: Improvement
> Components: core
> Affects Versions: 0.8
> Reporter: Jun Rao
> Labels: optimization
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> With the create topic ddl, some of the broker configs like topic.partition.count.map probably don't make sense anymore.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KAFKA-325) revisit broker config in 0.8
Posted by "Swapnil Ghike (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Swapnil Ghike updated KAFKA-325:
--------------------------------
Attachment: kafka-325-v3.patch
Rebased and made the change.
> revisit broker config in 0.8
> ----------------------------
>
> Key: KAFKA-325
> URL: https://issues.apache.org/jira/browse/KAFKA-325
> Project: Kafka
> Issue Type: Improvement
> Components: core
> Affects Versions: 0.8
> Reporter: Jun Rao
> Assignee: Swapnil Ghike
> Priority: Blocker
> Labels: optimization
> Attachments: kafka-300-v1.patch, kafka-325-v2.patch, kafka-325-v3.patch
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> With the create topic ddl, some of the broker configs like topic.partition.count.map probably don't make sense anymore.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Work started] (KAFKA-325) revisit broker config in 0.8
Posted by "Swapnil Ghike (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on KAFKA-325 started by Swapnil Ghike.
> revisit broker config in 0.8
> ----------------------------
>
> Key: KAFKA-325
> URL: https://issues.apache.org/jira/browse/KAFKA-325
> Project: Kafka
> Issue Type: Improvement
> Components: core
> Affects Versions: 0.8
> Reporter: Jun Rao
> Assignee: Swapnil Ghike
> Priority: Blocker
> Labels: optimization
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> With the create topic ddl, some of the broker configs like topic.partition.count.map probably don't make sense anymore.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (KAFKA-325) revisit broker config in 0.8
Posted by "Jun Rao (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jun Rao closed KAFKA-325.
-------------------------
> revisit broker config in 0.8
> ----------------------------
>
> Key: KAFKA-325
> URL: https://issues.apache.org/jira/browse/KAFKA-325
> Project: Kafka
> Issue Type: Improvement
> Components: core
> Affects Versions: 0.8
> Reporter: Jun Rao
> Assignee: Swapnil Ghike
> Priority: Blocker
> Labels: optimization
> Fix For: 0.8
>
> Attachments: kafka-300-v1.patch, kafka-325-v2.patch, kafka-325-v3.patch
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> With the create topic ddl, some of the broker configs like topic.partition.count.map probably don't make sense anymore.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KAFKA-325) revisit broker config in 0.8
Posted by "Swapnil Ghike (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13455079#comment-13455079 ]
Swapnil Ghike commented on KAFKA-325:
-------------------------------------
monitoringPeriodSecs seems to be used in SocketServer in starting a new processor and registerMBean.
> revisit broker config in 0.8
> ----------------------------
>
> Key: KAFKA-325
> URL: https://issues.apache.org/jira/browse/KAFKA-325
> Project: Kafka
> Issue Type: Improvement
> Components: core
> Affects Versions: 0.8
> Reporter: Jun Rao
> Assignee: Swapnil Ghike
> Priority: Blocker
> Labels: optimization
> Attachments: kafka-300-v1.patch, kafka-325-v2.patch
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> With the create topic ddl, some of the broker configs like topic.partition.count.map probably don't make sense anymore.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KAFKA-325) revisit broker config in 0.8
Posted by "Swapnil Ghike (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Swapnil Ghike updated KAFKA-325:
--------------------------------
Attachment: kafka-325-v2.patch
Rebased.
> revisit broker config in 0.8
> ----------------------------
>
> Key: KAFKA-325
> URL: https://issues.apache.org/jira/browse/KAFKA-325
> Project: Kafka
> Issue Type: Improvement
> Components: core
> Affects Versions: 0.8
> Reporter: Jun Rao
> Assignee: Swapnil Ghike
> Priority: Blocker
> Labels: optimization
> Attachments: kafka-300-v1.patch, kafka-325-v2.patch
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> With the create topic ddl, some of the broker configs like topic.partition.count.map probably don't make sense anymore.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KAFKA-325) revisit broker config in 0.8
Posted by "Swapnil Ghike (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Swapnil Ghike updated KAFKA-325:
--------------------------------
Attachment: kafka-300-v1.patch
This patch will conflict with the last patch in KAFKA-495.
- Removed topic.partition.count.map from KafkaConfig.
- Removed the check on partition id in LogManager.createLog.
- Removed one unit test from LogManagerTest.
> revisit broker config in 0.8
> ----------------------------
>
> Key: KAFKA-325
> URL: https://issues.apache.org/jira/browse/KAFKA-325
> Project: Kafka
> Issue Type: Improvement
> Components: core
> Affects Versions: 0.8
> Reporter: Jun Rao
> Assignee: Swapnil Ghike
> Priority: Blocker
> Labels: optimization
> Attachments: kafka-300-v1.patch
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> With the create topic ddl, some of the broker configs like topic.partition.count.map probably don't make sense anymore.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira