lpad detect_lostruns --fizzle
On one cluster, and having multiple jobs running across multiple clusters (ie. some on Savio, some on Lawrencium). Anything that is running on a different cluster than where the command was executed gets marked as FIZZLED even if the job is still running on the other cluster.
Is there a way to only execute that command on fireworks running on the cluster the command is run or, could this be fixed by implementing the “host” field from the firework’s launch document in the future?