On Sep 20, 2014, at 5:11 PM, Sumit Mohanty <[email protected]> wrote:
> 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. May not be a bad idea, but it does seem similar to the “update” scenarios we support. Should it just be something else we can “update”? > > -Sumit -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
