The API layer effort as in https://issues.apache.org/jira/browse/YARN-4793
is REST, defined in swagger format (the first draft version is uploaded to
YARN-4793). Proposal is to source control this as the entry point for the
APIs. The server side stubs (Java) will be generated from this definition,
+1,
>From user's point of view, the high-level resource management API
without any additional dependency is much comfortable than using
low-level APIs. I believe the way should increase YARN applications
including long-running services. From developer's point of view, the
integration make YARN
+1
It is definitely a step in the right direction and it's about time YARN
recognizes services as first-class citizens.
I would also like to see this effort encompass not just services but also
general long-lived applications such as say storm/heron topologies, samza
and possibly support for
+1. It would be great if it becomes the default way for services to run on
YARN. That would also make it easier to make YARN features support services
better. As you mentioned, there would be a lot of logistics to work out,
and we'll need to talk about them in more detail as they come up.
Daniel Templeton created YARN-5400:
--
Summary: Light cleanup in ZKRMStateStore
Key: YARN-5400
URL: https://issues.apache.org/jira/browse/YARN-5400
Project: Hadoop YARN
Issue Type:
Ray Chiang created YARN-5399:
Summary: Add configuration to remember ad-hoc queues upon
configuration reload
Key: YARN-5399
URL: https://issues.apache.org/jira/browse/YARN-5399
Project: Hadoop YARN
Ray Chiang created YARN-5398:
Summary: Standardize whitespace trimming and splitting in
FairScheduler code
Key: YARN-5398
URL: https://issues.apache.org/jira/browse/YARN-5398
Project: Hadoop YARN
Ray Chiang created YARN-5397:
Summary: [Umbrella] Usability improvements in FairScheduler
Key: YARN-5397
URL: https://issues.apache.org/jira/browse/YARN-5397
Project: Hadoop YARN
Issue Type:
+1 forwarding from the discussion in Slider DL
Note: On the Slider side, we plan to create a branch corresponding to this
YARN branch. In this, we intend to remove all the pieces which will move
to the YARN branch (Slider core, AM, client). We will retain the Agent and
app-packages which will
Zhiyuan Yang created YARN-5396:
--
Summary: YARN large file broadcast service
Key: YARN-5396
URL: https://issues.apache.org/jira/browse/YARN-5396
Project: Hadoop YARN
Issue Type: New Feature
For more details, see
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/98/
No changes
-1 overall
The following subsystems voted -1:
asflicense unit
The following subsystems voted -1 but
were configured to be filtered/ignored:
cc checkstyle javac javadoc pylint
sandflee created YARN-5395:
--
Summary: All node are Lost in sls test for big cluster
Key: YARN-5395
URL: https://issues.apache.org/jira/browse/YARN-5395
Project: Hadoop YARN
Issue Type: Improvement
12 matches
Mail list logo
