The term admin functionality itself means something that only an admin
should be able to do. We had been through a discussion on admin
functionality earlier and reviewed the following options -
1. Expose admin commands as RPC and in addition to that, provide command
line tools that talk to the con
David,
The benefit of the strategy used in Solr is that it simplifies client
routing. The downside is potential additional RPC overhead and a bit more
logic in the server. Technically, you can achieve what Solr does in the
client layer too. You can run a proxy that runs the java version of Kafka
p
[
https://issues.apache.org/jira/browse/KAFKA-756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13576705#comment-13576705
]
Jay Kreps commented on KAFKA-756:
-
Ah, I get it. I was wondering about the loop. Usually yo
[
https://issues.apache.org/jira/browse/KAFKA-743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-743:
--
Resolution: Fixed
Fix Version/s: 0.8
Assignee: Jun Rao
Status: Resolved (was: Patch A
[
https://issues.apache.org/jira/browse/KAFKA-756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13576813#comment-13576813
]
Jay Kreps commented on KAFKA-756:
-
+1
It would be good to understand how you tested this.
John Fung created KAFKA-757:
---
Summary: System Test Hard Failure cases : "Fatal error during
KafkaServerStable startup" when hard-failure broker is re-started
Key: KAFKA-757
URL: https://issues.apache.org/jira/browse/KAF
[
https://issues.apache.org/jira/browse/KAFKA-757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Fung updated KAFKA-757:
Summary: System Test Hard Failure cases : "Fatal error during
KafkaServerStable startup" when hard-failed br
[
https://issues.apache.org/jira/browse/KAFKA-757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13576856#comment-13576856
]
John Fung commented on KAFKA-757:
-
This is happening in all Hard-failure testcases in Syste
[
https://issues.apache.org/jira/browse/KAFKA-756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sriram Subramanian updated KAFKA-756:
-
Attachment: KAFKA-756-v3.patch
Added some more tracing
> Processor thread
[
https://issues.apache.org/jira/browse/KAFKA-756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-756.
---
Resolution: Fixed
Fix Version/s: 0.8
Thanks for patch v3. Committed to 0.8 with the following minor cha
[
https://issues.apache.org/jira/browse/KAFKA-757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapnil Ghike updated KAFKA-757:
Labels: 0.8 replication-testing (was: replication-testing)
> System Test Hard Failure cases : "
[
https://issues.apache.org/jira/browse/KAFKA-757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapnil Ghike reassigned KAFKA-757:
---
Assignee: Swapnil Ghike
> System Test Hard Failure cases : "Fatal error during KafkaServer
[
https://issues.apache.org/jira/browse/KAFKA-755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-755:
--
Fix Version/s: 0.8
Description:
Currently, we have the following paths in ZK that stores non-singl
[
https://issues.apache.org/jira/browse/KAFKA-755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13577218#comment-13577218
]
Jun Rao commented on KAFKA-755:
---
Proposed the new format in
https://cwiki.apache.org/conflue
14 matches
Mail list logo