storm
storm copied to clipboard
mesos
Storm on Mesos!
Reap previously launched logviewer tasks if `mesos.logviewer.sidecar.enabled` is now `false` Fixes #239
Nimbus should kill already-launched logviewers if re-launched with `mesos.logviewer.sidecar.enabled=false`. The pertinent use case is: If Nimbus is initially launched with `mesos.logviewer.sidecar.enabled=true` (or absent, which will give it the default `true`...
The implementation we're adding for automatically launching the logviewer as a "sidecar" task on each host that holds one of our Mesos Framework's worker processes is only targeted for the...
After the merging of #200 and #213 rebalance of topologies no longer does anything. This is because there are no offers on which slots can be made when a rebalance...
Right now, the Task IDs for a task are determined by the following [code](https://github.com/mesos/storm/blob/72681481f4df0ab33da08f7b6e9d9ba3db17c85e/storm/src/main/storm/mesos/MesosNimbus.java#L729). ``` String taskName = frameworkName + " | worker | " + topologyAndNodeId + ":" +...
``` 6449 [main] INFO o.a.s.d.s.Supervisor - Starting supervisor with id 3f59c94d-4e2a-4b68-89f3-ab7d57a0ab8b at host wangchuanyi.ds.gome.com.cn. 6561 [main] WARN o.a.s.d.nimbus - Topology submission exception. (topology name='srslog') #error { :cause nil :via [{:type...
In our new (as of PR #212) functionality to auto-launch logviewers, we should try to ensure the port is actually available. Otherwise the storm logviewer will appear to come up...
As part of logviewer autolaunching we added a wrapper around the Apache Curator library for our code to directly manipulate state in ZooKeeper. This resulted in a bunch of noisy...
Some users want the option of running their topologies as a specific user. This on the surface would be easy to do by setting the FrameworkInfo.setUser() to that user. However...
As @eyalzek [pointed out](https://github.com/mesos/storm/pull/189), `nimbus.host` is deprecated in storm-1.0+. `nimbus.seeds` is the new config parameter we should be respecting in the MesosNimbus code. The Nimbus spits out the following warning...