Miklos Szegedi created YARN-6361:
Summary: FSLeafQueue.fetchAppsWithDemand CPU usage is high with
big queues
Key: YARN-6361
URL: https://issues.apache.org/jira/browse/YARN-6361
Project: Hadoop YARN
Yufei Gu created YARN-6360:
--
Summary: Prevent FS state dump logger from inheriting parents'
appenders.
Key: YARN-6360
URL: https://issues.apache.org/jira/browse/YARN-6360
Project: Hadoop YARN
Issue
Robert Kanter created YARN-6359:
---
Summary: TestRM#testApplicationKillAtAcceptedState fails rarely
due to race condition
Key: YARN-6359
URL: https://issues.apache.org/jira/browse/YARN-6359
Project: Hadoo
Jose Miguel Arreola created YARN-6358:
-
Summary: Cache the resolved hosts prevent calls to
InetAddress.getByName and normalizeHost
Key: YARN-6358
URL: https://issues.apache.org/jira/browse/YARN-6358
Joep Rottinghuis created YARN-6357:
--
Summary: Implement TimelineCollector#putEntitiesAsync
Key: YARN-6357
URL: https://issues.apache.org/jira/browse/YARN-6357
Project: Hadoop YARN
Issue Type
Hey Sergiy,
I think a similar approach IIUC, where an AM for a app running on a cluster
acts as an unmanaged AM on another cluster. I believe they use a separate
UGI for each sub-cluster and wrap it around a doAs before the actual
allocate call.
Subru might be able to give more details.
Cheers
-
Robert Kanter created YARN-6356:
---
Summary: Allow different values of
yarn.log-aggregation.retain-seconds for succeeded and failed jobs
Key: YARN-6356
URL: https://issues.apache.org/jira/browse/YARN-6356
The doAs method in UserGroupInformation is what you want when dealing with
multiple UGIs. It determines what UGI instance the code within the doAs scope
gets when that code tries to lookup the current user.
Each AM is designed to run in a separate JVM, so each has some main()-like
entry point t
Arun Suresh created YARN-6355:
-
Summary: Interceptor framework for the YARN
ApplicationMasterService
Key: YARN-6355
URL: https://issues.apache.org/jira/browse/YARN-6355
Project: Hadoop YARN
Issu
Hi Jason,
Thanks a lot for your help again! Having two separate UserGroupInformation
instances is exactly what I had in mind. What I do not understand, though,
is how to make sure that our second call to .regsiterApplicationMaster()
will pick the right UserGroupInformation object. I would love to
[
https://issues.apache.org/jira/browse/YARN-4590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yufei Gu resolved YARN-4590.
Resolution: Duplicate
> SLS(Scheduler Load Simulator) web pages can't load css and js resource
> ---
Jason Lowe created YARN-6354:
Summary: RM fails to upgrade to 2.8 with leveldb state store
Key: YARN-6354
URL: https://issues.apache.org/jira/browse/YARN-6354
Project: Hadoop YARN
Issue Type: Bug
Daniel Templeton created YARN-6353:
--
Summary: Clean up OrderingPolicy javadoc
Key: YARN-6353
URL: https://issues.apache.org/jira/browse/YARN-6353
Project: Hadoop YARN
Issue Type: Bug
For more details, see
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/259/
[Mar 15, 2017 6:48:17 PM] (junping_du) YARN-6294. ATS client should better
handle Socket closed case.
[Mar 15, 2017 7:28:22 PM] (arp) HDFS-11419. DFSTopologyNodeImpl#chooseRandom
optimizations. Contributed
For more details, see
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/347/
[Mar 15, 2017 9:18:05 AM] (sunilg) YARN-6328. Fix a spelling mistake in
CapacityScheduler. Contributed by
[Mar 15, 2017 10:05:03 AM] (yqlin) HDFS-11420. Edit file should not be
processed by the same type p
[
https://issues.apache.org/jira/browse/YARN-3767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carlo Curino resolved YARN-3767.
Resolution: Won't Fix
>From my read of the conversation, I think this is not an actual issue. I will
Naganarasimha G R created YARN-6352:
---
Summary: Header injections are possible in the application proxy
servlet
Key: YARN-6352
URL: https://issues.apache.org/jira/browse/YARN-6352
Project: Hadoop YAR
Roni Burd created YARN-6351:
---
Summary: Have RM match relaxedLocality request via time instead of
missedOpportunities
Key: YARN-6351
URL: https://issues.apache.org/jira/browse/YARN-6351
Project: Hadoop YARN
Roni Burd created YARN-6350:
---
Summary: Add JMX counters to track locality matching (node, rack,
off_switch)
Key: YARN-6350
URL: https://issues.apache.org/jira/browse/YARN-6350
Project: Hadoop YARN
Thanks Steve. That's Awesome! I will kick off a new RC soon.
Shall we reopen HDFS-6200 given issues here? Making it in release note of 2.8.0
could confuse people as it doesn't work in HA deployment.
Thanks,
Junping
From: Steve Loughran
Sent: Thursday, Mar
I believe a cleaner way to solve this problem is to create two, _separate_
UserGroupInformation objects and wrap each AM instances in a UGI doAs so they
aren't trying to share the same credentials. This is one example of a token
bleeding over and causing problems. I suspect trying to fix these
Jason Lowe created YARN-6349:
Summary: Container kill request from AM can be lost if container
is still recovering
Key: YARN-6349
URL: https://issues.apache.org/jira/browse/YARN-6349
Project: Hadoop YARN
> On 16 Mar 2017, at 00:25, Junping Du wrote:
>
> bq. From my read of the poms, hadoop-client depends on hadoop-hdfs-client to
> pull in HDFS-related code. It doesn't have its own dependency on hadoop-hdfs.
> So I think this affects users of the hadoop-client artifact, which has
> existed for
+1 (non-binding)-Downloaded source.-Verified signatures.- Compiled the
source.-Ran sample jobs like MR sleep on pseudo distributed cluster. (Mac OS)
Thanks Junping and others!Regards,Kuhu
On Wednesday, March 15, 2017, 7:25:46 PM CDT, Junping Du
wrote:bq. From my read of the poms, hadoop-client d
24 matches
Mail list logo