2015-10-17 43 views
1

我將在apache mesos上設置一個kafka集羣。 我遵循kafka-mesos on github的說明。我安裝了一個mesos羣集(使用Mesosphere,沒有Marathon),每個羣集有3個節點,每個節點有2個CPU和4GB內存。我用hello world示例成功測試了羣集。Mesos Kafka任務失敗的內存限制

我可以在其上運行kafka-mesos調度程序,並可以爲其添加代理。 但是,當我想啓動代理時,出現內存限制。

broker-191-.... TASK_FAILED slave:#c3-S1 reason:REASON_MEMORY_LIMIT 

儘管集羣有12GB內存,但代理只需要3GB內存和1GB堆。 (我用512M到3GB的各種配置進行測試,但沒有工作)

問題是什麼?什麼是解決方案?

完整的故事就在這裏:

2015-10-17 17:39:24,748 [Jetty-17] INFO ly.stealth.mesos.kafka.HttpServer$ - handling - http://192.168.11.191:7000/api/broker/start 
2015-10-17 17:39:28,202 [Thread-605] INFO ly.stealth.mesos.kafka.Scheduler$ - [resourceOffers] 
mesos-2#O1160 cpus:2.00 mem:4098.00 disk:9869.00 ports:[31000..32000] 
mesos-3#O1161 cpus:2.00 mem:4098.00 disk:9869.00 ports:[31000..32000] 
mesos-1#O1162 cpus:2.00 mem:4098.00 disk:9869.00 ports:[31000..32000] 
2015-10-17 17:39:28,204 [Thread-605] INFO ly.stealth.mesos.kafka.Scheduler$ - Starting broker 191: launching task broker-191-0abe9e57-b0fb-4d87-a1b4-529acb111940 by offer mesos-2#O1160 
broker-191-0abe9e57-b0fb-4d87-a1b4-529acb111940 slave:#c6-S3 cpus:1.00 mem:3096.00 ports:[31000..31000] data:defaults=broker.id\=191\,log.dirs\=kafka-logs\,port\=31000\,zookeeper.connect\=192.168.11.191:2181\\\,192.168.11.192:2181\\\,192.168.11.193:2181\,host.name\=mesos-2\,log.retention.bytes\=10737418240,broker={"stickiness" : {"period" : "10m"\, "stopTime" : "2015-10-17 13:43:29.278"}\, "id" : "191"\, "mem" : 3096\, "cpus" : 1.0\, "heap" : 1024\, "failover" : {"delay" : "1m"\, "maxDelay" : "10m"}\, "active" : true} 
2015-10-17 17:39:28,417 [Thread-606] INFO ly.stealth.mesos.kafka.Scheduler$ - [statusUpdate] broker-191-0abe9e57-b0fb-4d87-a1b4-529acb111940 TASK_FAILED slave:#c6-S3 reason:REASON_MEMORY_LIMIT 
2015-10-17 17:39:28,418 [Thread-606] INFO ly.stealth.mesos.kafka.Scheduler$ - Broker 191 failed 1, waiting 1m, next start ~ 2015-10-17 17:40:28+03 
2015-10-17 17:39:29,202 [Thread-607] INFO ly.stealth.mesos.kafka.Scheduler$ - [resourceOffers] 

我發現Mesos主日誌如下:

...validation.cpp:422] Executor broker-191-... for task broker-191-... uses less CPUs (None) than the minimum required (0.01). Please update your executor, as this will be mandatory in future releases. 
...validation.cpp:434] Executor broker-191-... for task broker-191-... uses less memory (None) than the minimum required (32MB). Please update your executor, as this will be mandatory in future releases. 

,但我通過代理添加(更新)設置經紀CPU和MEM:

broker updated: 
id: 191 
active: false 
state: stopped 
resources: cpus:1.00, mem:2048, heap:1024, port:auto 
failover: delay:1m, max-delay:10m 
stickiness: period:10m, expires:2015-10-19 11:15:53+03 
+0

REASON_MEMORY_LIMIT並不一定意味着任務因OOM而被殺害。你可以請附上執行者的stderr嗎? – serejja

+0

我將'kafka-mesos.properties'中的'user = vagrant'更改爲'user = root',並重新啓動引起問題解決的mesos。 –

回答