Currently, the queue to submit an application is defined in
slider-client.xml. It is possible that the same deployment of slider-client
can be used to submit to different queues.

We can add --queue as a parameter where the value will override the default
in slider-client.xml.

Going further, the queue value can also be persisted in "internal.json"
file in HDFS for future starts after stops.

If we go the above route, should we also allow over-riding the stored value
of queue when issuing a start. I am thinking of scenarios where queue
configuration might have changed and application need to be restarted with
a different queue.

-Sumit

Reply via email to