Default Timeout for Cluster Actions


Is it possible to set a default timeout for cluster actions? The current case is that I have an environment with lots of data and one master. Occasionally it happens that a user executes a command that can possibly run for over 20 minutes, which in turn can run into memory and performance issues for other users. Is there maybe a better solution than a timeout?