[jira] [Commented] (YARN-4545) Allow YARN distributed shell to use ATS v1.5 APIs

[ https://issues.apache.org/jira/browse/YARN-4545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15188961#comment-15188961 ] Steve Loughran commented on YARN-4545: -- LGTM +1 > Allow YARN distributed shell to use ATS v1.5 APIs

[jira] [Updated] (YARN-4696) EntityGroupFSTimelineStore to work in the absence of an RM

[ https://issues.apache.org/jira/browse/YARN-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-4696: - Attachment: YARN-4696-014.patch Patch -014; address feedback h3.

[jira] [Commented] (YARN-4696) EntityGroupFSTimelineStore to work in the absence of an RM

[ https://issues.apache.org/jira/browse/YARN-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15185680#comment-15185680 ] Steve Loughran commented on YARN-4696: -- hi, I'll reply to these later; the current patches don't

[jira] [Updated] (YARN-4696) EntityGroupFSTimelineStore to work in the absence of an RM

[ https://issues.apache.org/jira/browse/YARN-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-4696: - Attachment: YARN-4696-013.patch Patch -013, "special scale edition" # the various log enum &

[jira] [Commented] (YARN-4233) YARN Timeline Service plugin: ATS v1.5

[ https://issues.apache.org/jira/browse/YARN-4233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15185620#comment-15185620 ] Steve Loughran commented on YARN-4233: -- HADOOP-12906 shows that AuthenticatedURL isn't helping things

[jira] [Commented] (YARN-4696) EntityGroupFSTimelineStore to work in the absence of an RM

[ https://issues.apache.org/jira/browse/YARN-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15185261#comment-15185261 ] Steve Loughran commented on YARN-4696: -- BTW, I managed to create an exception in scale tests; when the

[jira] [Commented] (YARN-4772) Overloaded leveljb can crash the ATS "pthread lock: Invalid argument"

[ https://issues.apache.org/jira/browse/YARN-4772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15185138#comment-15185138 ] Steve Loughran commented on YARN-4772: -- Assuming this is teardown, the root cause is that the

[jira] [Created] (YARN-4774) ATS can block in shutdown under heavy load

Steve Loughran created YARN-4774: Summary: ATS can block in shutdown under heavy load Key: YARN-4774 URL: https://issues.apache.org/jira/browse/YARN-4774 Project: Hadoop YARN Issue Type: Bug

[jira] [Updated] (YARN-4772) Overloaded leveljb can crash the ATS "pthread lock: Invalid argument"

[ https://issues.apache.org/jira/browse/YARN-4772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-4772: - Priority: Minor (was: Major) > Overloaded leveljb can crash the ATS "pthread lock: Invalid

[jira] [Commented] (YARN-4772) Overloaded leveljb can crash the ATS "pthread lock: Invalid argument"

[ https://issues.apache.org/jira/browse/YARN-4772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15184981#comment-15184981 ] Steve Loughran commented on YARN-4772: -- tail of the logs. Looking at the slf4j message, it may be

[jira] [Commented] (YARN-4772) Overloaded leveljb can crash the ATS "pthread lock: Invalid argument"

[ https://issues.apache.org/jira/browse/YARN-4772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15184976#comment-15184976 ] Steve Loughran commented on YARN-4772: -- Linking to the ATS1-5 work, as this was in the new code >

[jira] [Created] (YARN-4772) Overloaded leveljb can crash the ATS "pthread lock: Invalid argument"

Steve Loughran created YARN-4772: Summary: Overloaded leveljb can crash the ATS "pthread lock: Invalid argument" Key: YARN-4772 URL: https://issues.apache.org/jira/browse/YARN-4772 Project: Hadoop

[jira] [Commented] (YARN-4721) RM to try to auth with HDFS on startup, retry with max diagnostics on failure

[ https://issues.apache.org/jira/browse/YARN-4721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15184752#comment-15184752 ] Steve Loughran commented on YARN-4721: -- I'm trying to say, the test is "if this cluster has a default

[jira] [Commented] (YARN-4696) EntityGroupFSTimelineStore to work in the absence of an RM

[ https://issues.apache.org/jira/browse/YARN-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15183401#comment-15183401 ] Steve Loughran commented on YARN-4696: -- ignore the comment about numbers for now, something

[jira] [Commented] (YARN-4696) EntityGroupFSTimelineStore to work in the absence of an RM

[ https://issues.apache.org/jira/browse/YARN-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15183235#comment-15183235 ] Steve Loughran commented on YARN-4696: -- I should add that now I've started with some scale tests, my

[jira] [Updated] (YARN-4696) EntityGroupFSTimelineStore to work in the absence of an RM

[ https://issues.apache.org/jira/browse/YARN-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-4696: - Attachment: YARN-4696-012.patch Patch 012. This is what I've been successfully using in tests

[jira] [Commented] (YARN-4721) RM to try to auth with HDFS on startup, retry with max diagnostics on failure

[ https://issues.apache.org/jira/browse/YARN-4721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15182810#comment-15182810 ] Steve Loughran commented on YARN-4721: -- this patch, initially, sets up kerberos diagnostics without

[jira] [Updated] (YARN-4721) RM to try to auth with HDFS on startup, retry with max diagnostics on failure

[ https://issues.apache.org/jira/browse/YARN-4721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-4721: - Attachment: HADOOP-12889-001.patch > RM to try to auth with HDFS on startup, retry with max

[jira] [Commented] (YARN-4721) RM to try to auth with HDFS on startup, retry with max diagnostics on failure

[ https://issues.apache.org/jira/browse/YARN-4721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15180522#comment-15180522 ] Steve Loughran commented on YARN-4721: -- HADOOP-12889 covers the changes to KDiag & UGI for this > RM

[jira] [Commented] (YARN-4696) EntityGroupFSTimelineStore to work in the absence of an RM

[ https://issues.apache.org/jira/browse/YARN-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15175578#comment-15175578 ] Steve Loughran commented on YARN-4696: -- Findbugs is in code to determine scheme. It's correct; this is

[jira] [Updated] (YARN-4696) EntityGroupFSTimelineStore to work in the absence of an RM

[ https://issues.apache.org/jira/browse/YARN-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-4696: - Attachment: YARN-4696-010.patch YARN-4696 patch 010. Checkstyle warnings. The

[jira] [Commented] (YARN-4746) yarn web services should convert parse failures of appId to 400

[ https://issues.apache.org/jira/browse/YARN-4746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15173560#comment-15173560 ] Steve Loughran commented on YARN-4746: -- Having played with this some more, I think it's probably wise

[jira] [Updated] (YARN-4696) EntityGroupFSTimelineStore to work in the absence of an RM

[ https://issues.apache.org/jira/browse/YARN-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-4696: - Attachment: YARN-4696-009.patch This is the 009 patch; the difference with 008 is it is correctly

[jira] [Commented] (YARN-4593) Deadlock in AbstractService.getConfig()

[ https://issues.apache.org/jira/browse/YARN-4593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15172652#comment-15172652 ] Steve Loughran commented on YARN-4593: -- No tests. I'd have to think of a way to recreate the deadlock

[jira] [Created] (YARN-4746) yarn web services should convert parse failures of appId to 400

Steve Loughran created YARN-4746: Summary: yarn web services should convert parse failures of appId to 400 Key: YARN-4746 URL: https://issues.apache.org/jira/browse/YARN-4746 Project: Hadoop YARN

[jira] [Commented] (YARN-4705) ATS 1.5 parse pipeline to consider handling open() events recoverably

[ https://issues.apache.org/jira/browse/YARN-4705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15163232#comment-15163232 ] Steve Loughran commented on YARN-4705: -- All we need to know is "does flush() write data back so that

[jira] [Commented] (YARN-4705) ATS 1.5 parse pipeline to consider handling open() events recoverably

[ https://issues.apache.org/jira/browse/YARN-4705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15163205#comment-15163205 ] Steve Loughran commented on YARN-4705: -- YARN-4696 contains my current logic to handle failures to

[jira] [Updated] (YARN-4696) EntityGroupFSTimelineStore to work in the absence of an RM

[ https://issues.apache.org/jira/browse/YARN-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-4696: - Attachment: YARN-4696-008.patch Patch -008. This removes a subclass of RawLocalFileSystem that I'd

[jira] [Updated] (YARN-4696) EntityGroupFSTimelineStore to work in the absence of an RM

[ https://issues.apache.org/jira/browse/YARN-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-4696: - Attachment: YARN-4696-007.patch Patch 007 files that are stat-ed as empty are not skipped, but no

[jira] [Commented] (YARN-4705) ATS 1.5 parse pipeline to consider handling open() events recoverably

[ https://issues.apache.org/jira/browse/YARN-4705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15159115#comment-15159115 ] Steve Loughran commented on YARN-4705: -- yeah, thought of that... tried patch file:// but it didn't

[jira] [Commented] (YARN-4694) Document ATS v1.5

[ https://issues.apache.org/jira/browse/YARN-4694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15159015#comment-15159015 ] Steve Loughran commented on YARN-4694: -- As discussed in YARN-4705, this doc must cover which

[jira] [Commented] (YARN-4705) ATS 1.5 parse pipeline to consider handling open() events recoverably

[ https://issues.apache.org/jira/browse/YARN-4705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15159012#comment-15159012 ] Steve Loughran commented on YARN-4705: -- OK. so HDFS has guaranteed flush but no guarantees on modtime

[jira] [Commented] (YARN-4716) TimelineClient to implement Flushable; propagate to writer

[ https://issues.apache.org/jira/browse/YARN-4716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15158882#comment-15158882 ] Steve Loughran commented on YARN-4716: -- ..no, I'm expecting the reader to follow its normal

[jira] [Created] (YARN-4721) RM to try to auth with HDFS on startup, retry with max diagnostics on failure

Steve Loughran created YARN-4721: Summary: RM to try to auth with HDFS on startup, retry with max diagnostics on failure Key: YARN-4721 URL: https://issues.apache.org/jira/browse/YARN-4721 Project:

[jira] [Commented] (YARN-4705) ATS 1.5 parse pipeline to consider handling open() events recoverably

[ https://issues.apache.org/jira/browse/YARN-4705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15158680#comment-15158680 ] Steve Loughran commented on YARN-4705: -- That's what confuses me. After a scan of an empty file/failed

[jira] [Commented] (YARN-4716) TimelineClient to implement Flushable; propagate to writer

[ https://issues.apache.org/jira/browse/YARN-4716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15157822#comment-15157822 ] Steve Loughran commented on YARN-4716: -- For a flush I want them to be propagated to ATS; for an

[jira] [Updated] (YARN-4696) EntityGroupFSTimelineStore to work in the absence of an RM

[ https://issues.apache.org/jira/browse/YARN-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-4696: - Attachment: YARN-4696-006.patch Patch 006; ongoing (and currently unsuccessful) attempt to use

[jira] [Commented] (YARN-4696) EntityGroupFSTimelineStore to work in the absence of an RM

[ https://issues.apache.org/jira/browse/YARN-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15157187#comment-15157187 ] Steve Loughran commented on YARN-4696: -- the next patch I put up will implement YARN-4716; you can use

[jira] [Updated] (YARN-4716) TimelineClient to implement Flushable; propagate to writer

[ https://issues.apache.org/jira/browse/YARN-4716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-4716: - Target Version/s: 2.8.0 > TimelineClient to implement Flushable; propagate to writer >

[jira] [Created] (YARN-4716) TimelineClient to implement Flushable; propagate to writer

Steve Loughran created YARN-4716: Summary: TimelineClient to implement Flushable; propagate to writer Key: YARN-4716 URL: https://issues.apache.org/jira/browse/YARN-4716 Project: Hadoop YARN

[jira] [Commented] (YARN-4714) [Java 8] Over usage of virtual memory

[ https://issues.apache.org/jira/browse/YARN-4714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15156759#comment-15156759 ] Steve Loughran commented on YARN-4714: -- true, but it's still traumatic: cluster performance can

[jira] [Commented] (YARN-4696) EntityGroupFSTimelineStore to work in the absence of an RM

[ https://issues.apache.org/jira/browse/YARN-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15154989#comment-15154989 ] Steve Loughran commented on YARN-4696: -- This is another iteration with some other things needed to

[jira] [Updated] (YARN-4696) EntityGroupFSTimelineStore to work in the absence of an RM

[ https://issues.apache.org/jira/browse/YARN-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-4696: - Attachment: YARN-4696-005.patch Patch -005 (there was an -004, but I Don't think I submitted it)

[jira] [Commented] (YARN-4705) ATS 1.5 parse pipeline to consider handling open() events recoverably

[ https://issues.apache.org/jira/browse/YARN-4705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15154688#comment-15154688 ] Steve Loughran commented on YARN-4705: -- .. adding a check to skip 0-byte files stops the stack I've

[jira] [Commented] (YARN-4705) ATS 1.5 parse pipeline to consider handling open() events recoverably

[ https://issues.apache.org/jira/browse/YARN-4705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15154667#comment-15154667 ] Steve Loughran commented on YARN-4705: -- stack attached. Looking at the code, I'm not sure what the

[jira] [Created] (YARN-4705) ATS 1.5 parse pipeline to consider handling open() events recoverably

Steve Loughran created YARN-4705: Summary: ATS 1.5 parse pipeline to consider handling open() events recoverably Key: YARN-4705 URL: https://issues.apache.org/jira/browse/YARN-4705 Project: Hadoop

[jira] [Commented] (YARN-4545) Allow YARN distributed shell to use ATS v1.5 APIs

[ https://issues.apache.org/jira/browse/YARN-4545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15154059#comment-15154059 ] Steve Loughran commented on YARN-4545: -- regarding dependencies, I now understand. You are right: no

[jira] [Commented] (YARN-4696) EntityGroupFSTimelineStore to work in the absence of an RM

[ https://issues.apache.org/jira/browse/YARN-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15152656#comment-15152656 ] Steve Loughran commented on YARN-4696: -- Patch -003. Adds more robustness/diagnostics to the plugin

[jira] [Updated] (YARN-4696) EntityGroupFSTimelineStore to work in the absence of an RM

[ https://issues.apache.org/jira/browse/YARN-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-4696: - Attachment: YARN-4696-003.patch Patch -003 Addresses # discussion # checkstyle # javadocs Adds a

[jira] [Commented] (YARN-4696) EntityGroupFSTimelineStore to work in the absence of an RM

[ https://issues.apache.org/jira/browse/YARN-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15152148#comment-15152148 ] Steve Loughran commented on YARN-4696: -- # forgot about the -default.xml; will fix # anyone overrriding

[jira] [Updated] (YARN-4696) EntityGroupFSTimelineStore to work in the absence of an RM

[ https://issues.apache.org/jira/browse/YARN-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-4696: - Attachment: YARN-4696-002.patch Patch 002 # removes switch in exchange for making creation/use of

[jira] [Commented] (YARN-4694) Document ATS v1.5

[ https://issues.apache.org/jira/browse/YARN-4694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15150577#comment-15150577 ] Steve Loughran commented on YARN-4694: -- Things I'd like to see in here * overall concepts * how the

[jira] [Commented] (YARN-4696) EntityGroupFSTimelineStore to work in the absence of an RM

[ https://issues.apache.org/jira/browse/YARN-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15150557#comment-15150557 ] Steve Loughran commented on YARN-4696: -- It is for testing: the previous ATS ran happily standalone,

[jira] [Commented] (YARN-4695) EntityGroupFSTimelineStore to not log errors during shutdown

[ https://issues.apache.org/jira/browse/YARN-4695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15148961#comment-15148961 ] Steve Loughran commented on YARN-4695: -- [~gtCarrera9] -I've fixed this in YARN-4696; if you could

[jira] [Updated] (YARN-4696) EntityGroupFSTimelineStore to work in the absence of an RM

[ https://issues.apache.org/jira/browse/YARN-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-4696: - Attachment: YARN-4696-001.patch Patch -001; thing I had to to do to get my (external, spark

[jira] [Created] (YARN-4696) EntityGroupFSTimelineStore to work in the absence of an RM

Steve Loughran created YARN-4696: Summary: EntityGroupFSTimelineStore to work in the absence of an RM Key: YARN-4696 URL: https://issues.apache.org/jira/browse/YARN-4696 Project: Hadoop YARN

[jira] [Commented] (YARN-4695) EntityGroupFSTimelineStore to not log errors during shutdown

[ https://issues.apache.org/jira/browse/YARN-4695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15148644#comment-15148644 ] Steve Loughran commented on YARN-4695: -- ..hostname of www.bbc.co.uk/0.0.0.0:8032. is just 127.0.0.1

[jira] [Commented] (YARN-4695) EntityGroupFSTimelineStore to not log errors during shutdown

[ https://issues.apache.org/jira/browse/YARN-4695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15148643#comment-15148643 ] Steve Loughran commented on YARN-4695: -- Fuller stack. What's happening is the RM has been shut down

[jira] [Commented] (YARN-4695) EntityGroupFSTimelineStore to not log errors during shutdown

[ https://issues.apache.org/jira/browse/YARN-4695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15148624#comment-15148624 ] Steve Loughran commented on YARN-4695: -- stack. Note how the interrupted exception happened during RPC

[jira] [Created] (YARN-4695) EntityGroupFSTimelineStore to not log errors during shutdown

Steve Loughran created YARN-4695: Summary: EntityGroupFSTimelineStore to not log errors during shutdown Key: YARN-4695 URL: https://issues.apache.org/jira/browse/YARN-4695 Project: Hadoop YARN

[jira] [Commented] (YARN-4545) Allow YARN distributed shell to use ATS v1.5 APIs

[ https://issues.apache.org/jira/browse/YARN-4545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15147706#comment-15147706 ] Steve Loughran commented on YARN-4545: -- the new {{hadoop-yarn-server-timeline-pluginstorage}} JAR

[jira] [Commented] (YARN-4680) TimerTasks leak in ATS V1.5 Writer

[ https://issues.apache.org/jira/browse/YARN-4680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15147385#comment-15147385 ] Steve Loughran commented on YARN-4680: -- LGTM, though needs an entry in yarn-defaults.xml for the

[jira] [Commented] (YARN-4545) Allow YARN distributed shell to use ATS v1.5 APIs

[ https://issues.apache.org/jira/browse/YARN-4545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15147374#comment-15147374 ] Steve Loughran commented on YARN-4545: -- Or to put it differently, "why do you need to use UGI here at

[jira] [Commented] (YARN-4545) Allow YARN distributed shell to use ATS v1.5 APIs

[ https://issues.apache.org/jira/browse/YARN-4545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15147356#comment-15147356 ] Steve Loughran commented on YARN-4545: -- {publishContainerEndEvent}} doesn't try to put the event in a

[jira] [Commented] (YARN-4682) AMRM client to log when AMRM token updated

[ https://issues.apache.org/jira/browse/YARN-4682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144415#comment-15144415 ] Steve Loughran commented on YARN-4682: -- +1, committed to branch 2.8. It may seem a minor patch, but

[jira] [Commented] (YARN-4501) Document new put APIs in TimelineClient for ATS 1.5

[ https://issues.apache.org/jira/browse/YARN-4501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15142817#comment-15142817 ] Steve Loughran commented on YARN-4501: -- s/give/r/given/ > Document new put APIs in TimelineClient for

[jira] [Commented] (YARN-4501) Document new put APIs in TimelineClient for ATS 1.5

[ https://issues.apache.org/jira/browse/YARN-4501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15142815#comment-15142815 ] Steve Loughran commented on YARN-4501: -- give the imminent release of Hadoop 2.8, are there any drafts

[jira] [Updated] (YARN-4682) AMRM client to log when AMRM token updated

[ https://issues.apache.org/jira/browse/YARN-4682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-4682: - Attachment: YARN-4682-002.patch the issue is just that the lines of code above your patch had

[jira] [Updated] (YARN-4653) Document YARN security model from the perspective of Application Developers

[ https://issues.apache.org/jira/browse/YARN-4653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-4653: - Attachment: YARN-4653-004.patch Patch 004; write down my understanding of AM token renewal (based

[jira] [Commented] (YARN-4682) AMRM client to log when AMRM token updated

[ https://issues.apache.org/jira/browse/YARN-4682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15141304#comment-15141304 ] Steve Loughran commented on YARN-4682: -- to get a patch we can put into Hadoop, yes, you need to check

[jira] [Commented] (YARN-4629) Distributed shell breaks under strong security

[ https://issues.apache.org/jira/browse/YARN-4629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15140729#comment-15140729 ] Steve Loughran commented on YARN-4629: -- +1 I've already been testing a variant of this in slider; in

[jira] [Commented] (YARN-4653) Document YARN security model from the perspective of Application Developers

[ https://issues.apache.org/jira/browse/YARN-4653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15140742#comment-15140742 ] Steve Loughran commented on YARN-4653: -- ok, to confirm then # the token handed off by the RM to the

[jira] [Commented] (YARN-4682) AMRM client to log when AMRM token updated

[ https://issues.apache.org/jira/browse/YARN-4682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15140754#comment-15140754 ] Steve Loughran commented on YARN-4682: -- Prabhu, the patch isn't applying as it's against an old

[jira] [Created] (YARN-4682) AMRM client to log when AMRM token updated

Steve Loughran created YARN-4682: Summary: AMRM client to log when AMRM token updated Key: YARN-4682 URL: https://issues.apache.org/jira/browse/YARN-4682 Project: Hadoop YARN Issue Type:

[jira] [Commented] (YARN-4653) Document YARN security model from the perspective of Application Developers

[ https://issues.apache.org/jira/browse/YARN-4653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15135923#comment-15135923 ] Steve Loughran commented on YARN-4653: -- I know the apps need to sort out their own tokens; I've tried

[jira] [Commented] (YARN-4653) Document YARN security model from the perspective of Application Developers

[ https://issues.apache.org/jira/browse/YARN-4653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15134415#comment-15134415 ] Steve Loughran commented on YARN-4653: -- bq. Wonder how this works. Since container does not have

[jira] [Updated] (YARN-4653) Document YARN security model from the perspective of Application Developers

[ https://issues.apache.org/jira/browse/YARN-4653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-4653: - Attachment: YARN-4653-003.patch Patch 003. Try to clarify renewal vs regeneration, cut the

[jira] [Updated] (YARN-4653) Document YARN security model from the perspective of Application Developers

[ https://issues.apache.org/jira/browse/YARN-4653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-4653: - Attachment: YARN-4653-002.patch Patch -002; covers token extraction, renewal and cancellation.

[jira] [Commented] (YARN-4435) Add RM Delegation Token DtFetcher Implementation for DtUtil

[ https://issues.apache.org/jira/browse/YARN-4435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15130380#comment-15130380 ] Steve Loughran commented on YARN-4435: -- you'll need to add one for the timeline delegation token too

[jira] [Commented] (YARN-4435) Add RM Delegation Token DtFetcher Implementation for DtUtil

[ https://issues.apache.org/jira/browse/YARN-4435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15129082#comment-15129082 ] Steve Loughran commented on YARN-4435: -- # please use .patch as the suffix for ease of

[jira] [Updated] (YARN-4653) Document YARN security model from the perspective of Application Developers

[ https://issues.apache.org/jira/browse/YARN-4653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-4653: - Attachment: YARN-4653-001.patch Patch -001, document with checklist. > Document YARN security

[jira] [Commented] (YARN-4653) Document YARN security model from the perspective of Application Developers

[ https://issues.apache.org/jira/browse/YARN-4653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15126453#comment-15126453 ] Steve Loughran commented on YARN-4653: -- Rendered doc is at :

[jira] [Commented] (YARN-4629) Distributed shell breaks under strong security

[ https://issues.apache.org/jira/browse/YARN-4629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15123533#comment-15123533 ] Steve Loughran commented on YARN-4629: -- presumably this problem only surfaces when the RM is listed as

[jira] [Commented] (YARN-4629) Distributed shell breaks under strong security

[ https://issues.apache.org/jira/browse/YARN-4629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15123530#comment-15123530 ] Steve Loughran commented on YARN-4629: -- I like the patch, just some tweaks # you remove the date from

[jira] [Updated] (YARN-4629) Distributed shell breaks under strong security

[ https://issues.apache.org/jira/browse/YARN-4629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-4629: - Environment: Secure cluster with the RM principal listed with a /_HOST entry to be expanded, most

[jira] [Updated] (YARN-4653) Document YARN security model from the perspective of Application Developers

[ https://issues.apache.org/jira/browse/YARN-4653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-4653: - Summary: Document YARN security model from the perspective of Application Developers (was:

[jira] [Commented] (YARN-4653) Document YARN security model from the perspective of Application Developers

[ https://issues.apache.org/jira/browse/YARN-4653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15123315#comment-15123315 ] Steve Loughran commented on YARN-4653: -- thanks for the link ... hadn't seen that. nice. That's a

[jira] [Commented] (YARN-4629) Distributed shell breaks under strong security

[ https://issues.apache.org/jira/browse/YARN-4629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15123667#comment-15123667 ] Steve Loughran commented on YARN-4629: -- + add a check that the RM principal config option is

[jira] [Commented] (YARN-4629) Distributed shell breaks under strong security

[ https://issues.apache.org/jira/browse/YARN-4629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15123678#comment-15123678 ] Steve Loughran commented on YARN-4629: -- My variant {code} ... import static

[jira] [Created] (YARN-4653) Document YARN security model

Steve Loughran created YARN-4653: Summary: Document YARN security model Key: YARN-4653 URL: https://issues.apache.org/jira/browse/YARN-4653 Project: Hadoop YARN Issue Type: Task

[jira] [Commented] (YARN-4632) Replacing _HOST in RM_PRINCIPAL should not be the responsibility of the client code

[ https://issues.apache.org/jira/browse/YARN-4632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15121283#comment-15121283 ] Steve Loughran commented on YARN-4632: -- Dan, thanks for the details. I believe I did mention in

[jira] [Commented] (YARN-4629) Distributed shell breaks under strong security

[ https://issues.apache.org/jira/browse/YARN-4629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15115006#comment-15115006 ] Steve Loughran commented on YARN-4629: -- -1 to anything in YarnConfiguration. YarnClientUtils? Which

[jira] [Commented] (YARN-4577) Enable aux services to have their own custom classpath/jar file

[ https://issues.apache.org/jira/browse/YARN-4577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15098556#comment-15098556 ] Steve Loughran commented on YARN-4577: -- Test wise * {{testLoadAuxServiceLocally}} should be calling

[jira] [Created] (YARN-4593) Deadlock in AbstractService.getConfig()

Steve Loughran created YARN-4593: Summary: Deadlock in AbstractService.getConfig() Key: YARN-4593 URL: https://issues.apache.org/jira/browse/YARN-4593 Project: Hadoop YARN Issue Type: Bug

[jira] [Commented] (YARN-4593) Deadlock in AbstractService.getConfig()

[ https://issues.apache.org/jira/browse/YARN-4593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15098825#comment-15098825 ] Steve Loughran commented on YARN-4593: -- I don't see why we need this to be synchronized (it's that way

[jira] [Commented] (YARN-4593) Deadlock in AbstractService.getConfig()

[ https://issues.apache.org/jira/browse/YARN-4593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15098826#comment-15098826 ] Steve Loughran commented on YARN-4593: -- SLIDER-1052 shows this. I'm not going to blame this JIRA for

[jira] [Updated] (YARN-4593) Deadlock in AbstractService.getConfig()

[ https://issues.apache.org/jira/browse/YARN-4593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-4593: - Attachment: YARN-4593-001.patch Patch 001, removes the -synchronized attributed. The field is

[jira] [Commented] (YARN-4587) IllegalArgumentException in RMAppAttemptImpl#createApplicationAttemptReport

[ https://issues.apache.org/jira/browse/YARN-4587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15096444#comment-15096444 ] Steve Loughran commented on YARN-4587: -- Might want to add something in the javadocs of both classes

[jira] [Updated] (YARN-2031) YARN Proxy model doesn't support REST APIs in AMs

[ https://issues.apache.org/jira/browse/YARN-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-2031: - Attachment: YARN-2031-003.patch sync up with trunk; doesn't address any of the open issues > YARN

[jira] [Updated] (YARN-2031) YARN Proxy model doesn't support REST APIs in AMs

[ https://issues.apache.org/jira/browse/YARN-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-2031: - Attachment: YARN-2031-004.patch patch -004, address yetus issues. checkstyle is failing on method

<    1   2   3   4   5   6   7   8   9   10   >