Hi Allen,
What if the commands are:
yarn application -deploy –f spec.json
yarn application -stop <service-name>
yarn application -restart <service-name>
yarn application -remove <service-name>
and
yarn application –list will display both application list from RM as well as
docker services?
I think the development team was concerned that command structure overload
between batch applications and long running services. In my view, there is no
difference, they are all applications. The only distinction is the launching
and shutdown of services may be different from batch jobs. I think user can
get used to these command structures without creating additional command
grouping. Your input is valuable to us.
Feedback from others can also help to improve the current work. Thank you.
Regards,
Eric
On 10/6/17, 4:27 PM, "Jian He" <j...@hortonworks.com> wrote:
Hi Allen,
Thanks for spending the time reviewing it.
A new patch was uploaded yesterday on YARN-7198 to address the
documentation of missing config, you might want to check.
The api-server is basically a REST server which accepts user requests to
deploy services, it now has an option to be run as part of RM, which eliminates
one separate daemon.
We are open to naming suggestions. So far we used ‘service’ keyword to
indicate this feature. E.g.
"yarn service” sub-command is used to manage services deployed on YARN such
as:
yarn service create -f service-spec.json
yarn service stop <service-name>
Jian
> On Oct 6, 2017, at 3:12 PM, Allen Wittenauer <a...@effectivemachines.com>
wrote:
>
>
>> On Oct 6, 2017, at 1:31 PM, Andrew Wang <andrew.w...@cloudera.com> wrote:
>>
>> - Still waiting on Allen to review YARN native services feature.
>
> Fake news.
>
> I’m still -1 on it, at least prior to a patch that posted late
yesterday. I’ll probably have a chance to play with it early next week.
>
>
> Key problems:
>
> * still haven’t been able to bring up dns daemon due to lacking
documentation
>
> * it really needs better naming and command structures. When put into
the larger YARN context, it’s very problematic:
>
> $ yarn —daemon start resourcemanager
>
> vs.
>
> $ yarn —daemon start apiserver
>
> if you awoke from a deep sleep from inside a cave, which one
would you expect to “start YARN”? Made worse that the feature is called
“YARN services” all over the place.
>
> $ yarn service foo
>
> … what does this even mean?
>
> It would be great if other outsiders really looked hard at this branch
to give the team feedback. Once it gets released, it’s gonna be too late to
change it….
>
> As a sidenote:
>
> It’d be great if the folks working on YARN spent some time
consolidating daemons. With this branch, it now feels like we’re approaching
the double digit area of daemons to turn on all the features. It’s well past
ridiculous, especially considering we still haven’t replaced the MRJHS’s
feature set to the point we can turn it off.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: mapreduce-dev-unsubscr...@hadoop.apache.org
> For additional commands, e-mail: mapreduce-dev-h...@hadoop.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org
