Phil Winder
Phil Winder
@jbirch I did all my manual testing on AWS, so I'm surprised there's a problem here. But I used vanilla Mesos, not DCOS, so I assume it's some difference there....
@WalterDalton I'm sorry, I've only just seen this. This is a separate issue and I will open a bug. @systeminsightsbuild It could be said there are two reasons. 1) clarity....
Yes fair point. It was originaly thought that this was causing crashes, but it turned out to be an out of disk error.
The current healthcheck mechanism uses Mesos's timestamp on each Status update, which is written to Zookeeper. If you don't write to zookeeper on every status update, then the status of...
A bit strange. This line: ``` Task status for elasticsearch_54.215.156.251_20160413T044508.235Z exists, using old state: TASK_RUNNING ``` Is saying that there is an instance of ES in it's state. I.e. the...
Ok, thanks. I think the issue is the master failure/shutdown. The ES framework stores its state in ZooKeeper. Because you've persisted that information, it reloads the state once everything starts...
Do you have `cgroups/mem` isolation turned on in Mesos? You need to specify ram isolation. http://mesos.apache.org/documentation/latest/configuration/ Look for `--isolation`.
@ryane Thanks for the debugging. This is interesting, since we simply start the jar inside a mesos command. I would have expected that Mesos would ensure that started processes have...
Those commands are trying to run elasticsearch on minimesos. I haven't tried it in a while. A `./gradlew clean buildDockerImage` should suffice.
Hi @vitalif, yes that's exactly what I mean. Exposing the interfaces required to implement a new backend, or maybe even add functionality to an existing backend. Then allowing that backend...