This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-08-06
Channels
- # alda (3)
- # beginners (109)
- # boot (24)
- # cljsrn (17)
- # clojure (41)
- # clojure-brasil (2)
- # clojure-china (1)
- # clojure-russia (19)
- # clojure-spec (9)
- # clojure-uk (5)
- # clojurescript (44)
- # cloverage (5)
- # core-async (3)
- # css (2)
- # datascript (6)
- # datomic (26)
- # emacs (2)
- # events (10)
- # hoplon (24)
- # lambdaisland (1)
- # om (2)
- # onyx (16)
- # other-languages (10)
- # proto-repl (2)
- # re-frame (14)
- # spacemacs (2)
- # untangled (4)
- # videos (1)
@michaeldrogalis: I got passed the issue by running the containers in host mode and binding to $PORT0 which is the ephemeral port. All nodes started working, however, I then very shortly saw these to things
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGBUS (0x7) at pc=0x00007f11a216d97e, pid=96, tid=0x00007f11841b9700
#
# JRE version: Java(TM) SE Runtime Environment (8.0_92-b14) (build 1.8.0_92-b14)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.92-b14 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# V [libjvm.so+0xa8d97e] Unsafe_SetInt+0x4e
#
# Core dump written. Default location: /var/run/s6/services/media_driver/core or core.96
#
# An error report file with more information is saved as:
# /var/run/s6/services/media_driver/hs_err_pid96.log
#
# If you would like to submit a bug report, please visit:
#
#
along with these warning on each node
16-Aug-06 00:11:41 WARN [onyx.messaging.aeron] -
[37mjava.lang.Thread.run[m [32m Thread.java: 745[m
[37muk.co.real_logic.agrona.concurrent.AgentRunner.run[m [32m AgentRunner.java: 105[m
[37muk.co.real_logic.aeron.ClientConductor.doWork[m [32mClientConductor.java: 113[m
[37muk.co.real_logic.aeron.ClientConductor.doWork[m [32mClientConductor.java: 293[m
[37muk.co.real_logic.aeron.ClientConductor.onCheckTimeouts[m [32mClientConductor.java: 346[m
[37muk.co.real_logic.aeron.ClientConductor.checkDriverHeartbeat[m [32mClientConductor.java: 275[m
[1;31muk.co.real_logic.aeron.exceptions.DriverTimeoutException[m: [3mDriver has been inactive for over 10000ms[m
16-Aug-06 00:11:41 WARN [onyx.messaging.aeron] -
[37mjava.lang.Thread.run[m [32m Thread.java: 745[m
[37muk.co.real_logic.agrona.concurrent.AgentRunner.run[m [32m AgentRunner.java: 105[m
[37muk.co.real_logic.aeron.ClientConductor.doWork[m [32mClientConductor.java: 113[m
[37muk.co.real_logic.aeron.ClientConductor.doWork[m [32mClientConductor.java: 293[m
[37muk.co.real_logic.aeron.ClientConductor.onCheckTimeouts[m [32mClientConductor.java: 346[m
[37muk.co.real_logic.aeron.ClientConductor.checkDriverHeartbeat[m [32mClientConductor.java: 275[m
[1;31muk.co.real_logic.aeron.exceptions.DriverTimeoutException[m: [3mDriver has been inactive for over 10000ms[m
@camechis: https://github.com/onyx-platform/onyx/blob/develop/doc/user-guide/faq.md#aeron-mediadriver-crashes-the-jvm-with-sigbus
How are you setting it in Mesos
Your likely not setting it correctly, 512mb is plenty
so in my marathon definition I am setting it like this
"parameters": [
{
"key": "shm-size",
"value": "512mb"
}
under the container sectioni assumed this was the way to do it since I left that out before and it failed immediately until i put that in
That's not really a reliable test, I would check up on the docs wrt setting shm size. In kubernetes we sidestep this by mounting a memory volume at /dev/shm
@gardnervickers: I was trying to determine if my shm_size setting was actually working or not. So I execed into the running docker container on the node that the peer started up in and ran the mount command to see if I could determine the shm_size that the docker container was using here is what I got.
shm on /dev/shm type tmpfs (rw,seclabel,nosuid,nodev,noexec,relatime,size=524288k)
so it looks like it really is set to 512mb but I still got the aeron seg fault.@mccraigmccraig, @michaeldrogalis: hah! we launched in September 🙂
@robert-stuttaford: damn, but #2 is good too - the only even prime :)