l.map(FileChannelImpl.java:904)
... 28 more
Thanks
-Zakee
Brokers failed repeatedly leaving behind page-cache in memory, which caused
broker restarts to fail with OOM every time.
After manually cleaning up page-cache, I was able to restart the broker.
However, still wondering what could have caused this state in the first place.
Any ideas?
-Zakee
+1
-Zakee
> On Feb 14, 2017, at 1:56 PM, Jay Kreps wrote:
>
> +1
>
> Nice improvement.
>
> -Jay
>
> On Tue, Feb 14, 2017 at 1:22 PM, Steven Schlansker <
> sschlans...@opentable.com> wrote:
>
>> Hi, it looks like I have 2 of the 3 minimum votes,
These errors are possibly caused by delete topic (esp. using v0.8.2.x), refer
below issues.
https://issues.apache.org/jira/browse/KAFKA-2231
https://issues.apache.org/jira/browse/KAFKA-1194
The replica fetchers still querying their leaders for partitions of deleted
topic. May need a restart of
-1
Thanks.
> On Oct 25, 2016, at 2:16 PM, Harsha Chintalapani wrote:
>
> Hi All,
> We are proposing to have a REST Server as part of Apache Kafka
> to provide producer/consumer/admin APIs. We Strongly believe having
> REST server functionality with Apache Kafka will help a lot of user
[
https://issues.apache.org/jira/browse/KAFKA-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15371402#comment-15371402
]
K Zakee commented on KAFKA-1464:
I agree with Ralph.
Lets say, we have a high pro
K Zakee created KAFKA-2011:
--
Summary: Rebalance with auto.leader.rebalance.enable=false
Key: KAFKA-2011
URL: https://issues.apache.org/jira/browse/KAFKA-2011
Project: Kafka
Issue Type: Bug
[
https://issues.apache.org/jira/browse/KAFKA-2011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14353465#comment-14353465
]
K Zakee commented on KAFKA-2011:
Nothing per se happened to brokers. No restarts or
[
https://issues.apache.org/jira/browse/KAFKA-2011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14353723#comment-14353723
]
K Zakee commented on KAFKA-2011:
Can following error trigger the controller migratio
[
https://issues.apache.org/jira/browse/KAFKA-2011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14353848#comment-14353848
]
K Zakee commented on KAFKA-2011:
Attached the controller logs for your refer
[
https://issues.apache.org/jira/browse/KAFKA-2011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
K Zakee updated KAFKA-2011:
---
Attachment: controller-logs-2.zip
controller-logs-1.zip
> Rebalance w
[
https://issues.apache.org/jira/browse/KAFKA-2011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14355936#comment-14355936
]
K Zakee commented on KAFKA-2011:
The preferred replica leader election occurred a
[
https://issues.apache.org/jira/browse/KAFKA-2011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14357426#comment-14357426
]
K Zakee commented on KAFKA-2011:
1) The zk timeout I see occurring when the contro
[
https://issues.apache.org/jira/browse/KAFKA-2011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14357643#comment-14357643
]
K Zakee commented on KAFKA-2011:
Did you mean 600 secs (10 mins)?
> Rebalan
[
https://issues.apache.org/jira/browse/KAFKA-2011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359513#comment-14359513
]
K Zakee commented on KAFKA-2011:
Increasing the timeout (to 60ms) has s
[
https://issues.apache.org/jira/browse/KAFKA-2011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359954#comment-14359954
]
K Zakee commented on KAFKA-2011:
Thanks Jiangjie.
Though the ZK client session tim
[
https://issues.apache.org/jira/browse/KAFKA-2011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14360863#comment-14360863
]
K Zakee commented on KAFKA-2011:
All right. Thanks for your help.
> Rebalan
K Zakee created KAFKA-2038:
--
Summary: Unable to restart brokers after it went down with no
space left on disk
Key: KAFKA-2038
URL: https://issues.apache.org/jira/browse/KAFKA-2038
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-2038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
K Zakee updated KAFKA-2038:
---
Description:
One of the 8 volumes on brokers disks were full and broker wen down with below
error, Cannot
[
https://issues.apache.org/jira/browse/KAFKA-2038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
K Zakee updated KAFKA-2038:
---
Description:
What should happen if one of the log directories configured with broker is 100%
full. Is it
[
https://issues.apache.org/jira/browse/KAFKA-2038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14379515#comment-14379515
]
K Zakee commented on KAFKA-2038:
On Mar 21, 2015, at 11:50 AM, svante karlsson w
[
https://issues.apache.org/jira/browse/KAFKA-2038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14380850#comment-14380850
]
K Zakee commented on KAFKA-2038:
Thanks, I was able to start the broker after manu
22 matches
Mail list logo
