What steps will reproduce the problem?
1. Launch a continuous computation based on a MapReduce job.
2. Wait for the job to fail (which will probably happen eventually due to
random production issues).
3. Restart the job.
What is the expected output? What do you see instead?
I expect the job to cleanly abort and its status to go back to 'idle', so that
I can restart it. However, it instead ends up as 'stopping', so I can't do so.
Original issue reported on code.google.com by s...@google.com on 21 May 2015 at 2:32
Original issue reported on code.google.com by
s...@google.com
on 21 May 2015 at 2:32