You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@slider.apache.org by Sumit Mohanty <sm...@apache.org> on 2014/09/20 23:11:30 UTC
--queue as an input parameter
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
Re: --queue as an input parameter
Posted by Ted Yu <yu...@gmail.com>.
bq. add --queue as a parameter where the value will override the default in
slider-client.xml
+1
On Sat, Sep 20, 2014 at 2:11 PM, Sumit Mohanty <sm...@apache.org> 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.
>
> -Sumit
>
Re: --queue as an input parameter
Posted by Jon Maron <jm...@hortonworks.com>.
On Sep 20, 2014, at 5:26 PM, Sumit Mohanty <su...@gmail.com> wrote:
> Actually, update may not be a bad idea.
>
> Do we allow any updates today to configs internal/appConfig/resources?
>
I know we allow for appConfig updates - I’ve done so to update the app master jvm.opts value.
> On Sat, Sep 20, 2014 at 2:18 PM, Jon Maron <jm...@hortonworks.com> wrote:
>
>>
>> On Sep 20, 2014, at 5:11 PM, Sumit Mohanty <sm...@apache.org> 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.
>>
>
>
>
> --
> thanks
> 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.
Re: --queue as an input parameter
Posted by Sumit Mohanty <su...@gmail.com>.
Actually, update may not be a bad idea.
Do we allow any updates today to configs internal/appConfig/resources?
On Sat, Sep 20, 2014 at 2:18 PM, Jon Maron <jm...@hortonworks.com> wrote:
>
> On Sep 20, 2014, at 5:11 PM, Sumit Mohanty <sm...@apache.org> 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.
>
--
thanks
Sumit
Re: --queue as an input parameter
Posted by Jon Maron <jm...@hortonworks.com>.
On Sep 20, 2014, at 5:11 PM, Sumit Mohanty <sm...@apache.org> 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.