I also think that the current mechanism is weird. IMHO it makes sense to add the flag to both the start and stop scripts.
On Wed, Jun 1, 2016 at 2:09 PM, Ufuk Celebi <u...@apache.org> wrote: > Yes, it's expected, but you are certainly not the first one to be > confused by this behaviour. > > The reasoning behind the current behaviour is that we don't users > accidentally removing jobs, which seems worse than requiring users to > cancel manually. We thought about adding a flag to the start scripts > to either clear the jobs on start up or shut down. What's your opinion > on this? > > – Ufuk > > On Wed, Jun 1, 2016 at 1:42 PM, Gyula Fóra <gyula.f...@gmail.com> wrote: > > Hi, > > > > I have noticed some strange behaviour on a streaming cluster running in > HA > > mode. > > > > I have stopped a cluster with some deployed jobs (stop-cluster.sh without > > cancelling the jobs) and when I bring the cluster back up the jobs that > > were running before are restarted. > > > > Is this the expected behaviour? It feels strange that jobs will be > > automatically redeployed after specifically calling stop-cluster. > > > > Regards, > > Gyula >
