[jira] [Created] (YARN-8328) NonAggregatingLogHandler needlessly waits upon shutdown if delayed deletion is scheduled
Jonathan Eagles created YARN-8328: - Summary: NonAggregatingLogHandler needlessly waits upon shutdown if delayed deletion is scheduled Key: YARN-8328 URL: https://issues.apache.org/jira/browse/YARN-8328 Project: Hadoop YARN Issue Type: Bug Reporter: Jonathan Eagles This happens frequently in the MiniYarnCluster setup where a job completes and then the cluster is shutdown. Often the jobs are scheduled to delay deletion of the log files so that container logs are available for debugging. A scheduled log deletion has a default value of 3 hours. When the NonAggregating LogHandler is stopped it waits 10 seconds for all delayed scheduled log deletions to occur and then shuts down. A test developer has to make a trade of to either 1) set the log deletion to 0 to have the tests quickly shutdown but get no container logs to debug or 2) keep the log deletion at 3 hours and incur the 10 second timeout for each test suit. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org
[jira] [Created] (YARN-8054) Improve robustness of the LocalDirsHandlerService MonitoringTimerTask thread
Jonathan Eagles created YARN-8054:
-
Summary: Improve robustness of the LocalDirsHandlerService
MonitoringTimerTask thread
Key: YARN-8054
URL: https://issues.apache.org/jira/browse/YARN-8054
Project: Hadoop YARN
Issue Type: Bug
Reporter: Jonathan Eagles
Assignee: Jonathan Eagles
The DeprecatedRawLocalFileStatus#loadPermissionInfo can throw a
RuntimeException which can kill the MonitoringTimerTask thread. This can leave
the node is a bad state where all NM local directories are marked "bad" and
there is no automatic recovery. In the below can the error was "too many open
files", but could be a number of other recoverable states.
{noformat}
2018-03-18 02:37:42,960 [DiskHealthMonitor-Timer] ERROR
yarn.YarnUncaughtExceptionHandler: Thread
Thread[DiskHealthMonitor-Timer,5,main] threw an Exception.
java.lang.RuntimeException: Error while running command to get file permissions
: java.io.IOException: Cannot run program "ls": error=24, Too many open files
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048)
at org.apache.hadoop.util.Shell.runCommand(Shell.java:942)
at org.apache.hadoop.util.Shell.run(Shell.java:898)
at
org.apache.hadoop.util.Shell$ShellCommandExecutor.execute(Shell.java:1213)
at org.apache.hadoop.util.Shell.execCommand(Shell.java:1307)
at org.apache.hadoop.util.Shell.execCommand(Shell.java:1289)
at org.apache.hadoop.fs.FileUtil.execCommand(FileUtil.java:1078)
at
org.apache.hadoop.fs.RawLocalFileSystem$DeprecatedRawLocalFileStatus.loadPermissionInfo(RawLocalFileSystem.java:697)
at
org.apache.hadoop.fs.RawLocalFileSystem$DeprecatedRawLocalFileStatus.getPermission(RawLocalFileSystem.java:672)
at
org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.ResourceLocalizationService.checkLocalDir(ResourceLocalizationService.java:1556)
at
org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.ResourceLocalizationService.checkAndInitializeLocalDirs(ResourceLocalizationService.java:1521)
at
org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.ResourceLocalizationService$1.onDirsChanged(ResourceLocalizationService.java:271)
at
org.apache.hadoop.yarn.server.nodemanager.DirectoryCollection.checkDirs(DirectoryCollection.java:381)
at
org.apache.hadoop.yarn.server.nodemanager.LocalDirsHandlerService.checkDirs(LocalDirsHandlerService.java:449)
at
org.apache.hadoop.yarn.server.nodemanager.LocalDirsHandlerService.access$500(LocalDirsHandlerService.java:52)
at
org.apache.hadoop.yarn.server.nodemanager.LocalDirsHandlerService$MonitoringTimerTask.run(LocalDirsHandlerService.java:166)
at java.util.TimerThread.mainLoop(Timer.java:555)
at java.util.TimerThread.run(Timer.java:505)
Caused by: java.io.IOException: error=24, Too many open files
at java.lang.UNIXProcess.forkAndExec(Native Method)
at java.lang.UNIXProcess.(UNIXProcess.java:247)
at java.lang.ProcessImpl.start(ProcessImpl.java:134)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029)
... 17 more
at
org.apache.hadoop.fs.RawLocalFileSystem$DeprecatedRawLocalFileStatus.loadPermissionInfo(RawLocalFileSystem.java:737)
at
org.apache.hadoop.fs.RawLocalFileSystem$DeprecatedRawLocalFileStatus.getPermission(RawLocalFileSystem.java:672)
at
org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.ResourceLocalizationService.checkLocalDir(ResourceLocalizationService.java:1556)
at
org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.ResourceLocalizationService.checkAndInitializeLocalDirs(ResourceLocalizationService.java:1521)
at
org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.ResourceLocalizationService$1.onDirsChanged(ResourceLocalizationService.java:271)
at
org.apache.hadoop.yarn.server.nodemanager.DirectoryCollection.checkDirs(DirectoryCollection.java:381)
at
org.apache.hadoop.yarn.server.nodemanager.LocalDirsHandlerService.checkDirs(LocalDirsHandlerService.java:449)
at
org.apache.hadoop.yarn.server.nodemanager.LocalDirsHandlerService.access$500(LocalDirsHandlerService.java:52)
at
org.apache.hadoop.yarn.server.nodemanager.LocalDirsHandlerService$MonitoringTimerTask.run(LocalDirsHandlerService.java:166)
at java.util.TimerThread.mainLoop(Timer.java:555)
at java.util.TimerThread.run(Timer.java:505)
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org
[jira] [Created] (YARN-7495) Improve robustness of the AggregatedLogDeletionService
Jonathan Eagles created YARN-7495: - Summary: Improve robustness of the AggregatedLogDeletionService Key: YARN-7495 URL: https://issues.apache.org/jira/browse/YARN-7495 Project: Hadoop YARN Issue Type: Improvement Components: log-aggregation Reporter: Jonathan Eagles Assignee: Jonathan Eagles The deletion tasks are scheduled with a TimerTask whose scheduler is a Timer scheduleAtFixedRate. If an exception occurs in the log deletion task, the Timer scheduler interprets this as a task cancelation and stops scheduling future deletion tasks. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org
[jira] [Created] (YARN-6987) Log app attempt during InvalidStateTransition
Jonathan Eagles created YARN-6987:
-
Summary: Log app attempt during InvalidStateTransition
Key: YARN-6987
URL: https://issues.apache.org/jira/browse/YARN-6987
Project: Hadoop YARN
Issue Type: Bug
Reporter: Jonathan Eagles
Assignee: Jonathan Eagles
Found this InvalidStateTransition logged in the resource manager log file with
no way to determine exactly which app attempt this was associated with.
{noformat}
2017-08-04 17:22:29,895 [AsyncDispatcher event handler] ERROR
attempt.RMAppAttemptImpl: Can't handle this event at current state
org.apache.hadoop.yarn.state.InvalidStateTransitonException: Invalid event:
UNREGISTERED at LAUNCHED
at
org.apache.hadoop.yarn.state.StateMachineFactory.doTransition(StateMachineFactory.java:305)
at
org.apache.hadoop.yarn.state.StateMachineFactory.access$300(StateMachineFactory.java:46)
at
org.apache.hadoop.yarn.state.StateMachineFactory$InternalStateMachine.doTransition(StateMachineFactory.java:448)
at
org.apache.hadoop.yarn.server.resourcemanager.rmapp.attempt.RMAppAttemptImpl.handle(RMAppAttemptImpl.java:802)
at
org.apache.hadoop.yarn.server.resourcemanager.rmapp.attempt.RMAppAttemptImpl.handle(RMAppAttemptImpl.java:108)
at
org.apache.hadoop.yarn.server.resourcemanager.ResourceManager$ApplicationAttemptEventDispatcher.handle(ResourceManager.java:803)
at
org.apache.hadoop.yarn.server.resourcemanager.ResourceManager$ApplicationAttemptEventDispatcher.handle(ResourceManager.java:784)
at
org.apache.hadoop.yarn.event.AsyncDispatcher.dispatch(AsyncDispatcher.java:184)
at
org.apache.hadoop.yarn.event.AsyncDispatcher$1.run(AsyncDispatcher.java:110)
at java.lang.Thread.run(Thread.java:745)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org
[jira] [Created] (YARN-6768) Improve performance of yarn api record toString and fromString
Jonathan Eagles created YARN-6768: - Summary: Improve performance of yarn api record toString and fromString Key: YARN-6768 URL: https://issues.apache.org/jira/browse/YARN-6768 Project: Hadoop YARN Issue Type: Improvement Reporter: Jonathan Eagles Assignee: Jonathan Eagles -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org
[jira] [Created] (YARN-6654) RollingLevelDBTimelineStore introduce minor backwards compatible change
Jonathan Eagles created YARN-6654:
-
Summary: RollingLevelDBTimelineStore introduce minor backwards
compatible change
Key: YARN-6654
URL: https://issues.apache.org/jira/browse/YARN-6654
Project: Hadoop YARN
Issue Type: Bug
Reporter: Jonathan Eagles
Assignee: Jonathan Eagles
Priority: Blocker
There is a small minor backwards compatible change introduced while upgrading
fst library from 2.24 to 2.50.
{code}
Exception in thread "main" java.io.IOException: java.lang.RuntimeException:
unable to find class for code 83
at
org.nustaq.serialization.FSTObjectInput.readObject(FSTObjectInput.java:243)
at
org.nustaq.serialization.FSTConfiguration.asObject(FSTConfiguration.java:1125)
at org.nustaq.serialization.FSTNoJackson.main(FSTNoJackson.java:31)
Caused by: java.lang.RuntimeException: unable to find class for code 83
at
org.nustaq.serialization.FSTClazzNameRegistry.decodeClass(FSTClazzNameRegistry.java:180)
at
org.nustaq.serialization.coders.FSTStreamDecoder.readClass(FSTStreamDecoder.java:472)
at
org.nustaq.serialization.FSTObjectInput.readClass(FSTObjectInput.java:933)
at
org.nustaq.serialization.FSTObjectInput.readObjectWithHeader(FSTObjectInput.java:343)
at
org.nustaq.serialization.FSTObjectInput.readObjectInternal(FSTObjectInput.java:327)
at
org.nustaq.serialization.serializers.FSTArrayListSerializer.instantiate(FSTArrayListSerializer.java:63)
at
org.nustaq.serialization.FSTObjectInput.instantiateAndReadWithSer(FSTObjectInput.java:497)
at
org.nustaq.serialization.FSTObjectInput.readObjectWithHeader(FSTObjectInput.java:366)
at
org.nustaq.serialization.FSTObjectInput.readObjectInternal(FSTObjectInput.java:327)
at
org.nustaq.serialization.serializers.FSTMapSerializer.instantiate(FSTMapSerializer.java:78)
at
org.nustaq.serialization.FSTObjectInput.instantiateAndReadWithSer(FSTObjectInput.java:497)
at
org.nustaq.serialization.FSTObjectInput.readObjectWithHeader(FSTObjectInput.java:366)
at
org.nustaq.serialization.FSTObjectInput.readObjectInternal(FSTObjectInput.java:327)
at
org.nustaq.serialization.FSTObjectInput.readObject(FSTObjectInput.java:307)
at
org.nustaq.serialization.FSTObjectInput.readObject(FSTObjectInput.java:241)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org
[jira] [Created] (YARN-6649) RollingLevelDBTimelineServer throws RuntimeException if object decoding ever fails runtime exception
Jonathan Eagles created YARN-6649: - Summary: RollingLevelDBTimelineServer throws RuntimeException if object decoding ever fails runtime exception Key: YARN-6649 URL: https://issues.apache.org/jira/browse/YARN-6649 Project: Hadoop YARN Issue Type: Bug Reporter: Jonathan Eagles Assignee: Jonathan Eagles Priority: Critical -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org
[jira] [Created] (YARN-4376) Memory Timeline Store return incorrect results on fromId paging
Jonathan Eagles created YARN-4376: - Summary: Memory Timeline Store return incorrect results on fromId paging Key: YARN-4376 URL: https://issues.apache.org/jira/browse/YARN-4376 Project: Hadoop YARN Issue Type: Bug Reporter: Jonathan Eagles Assignee: Jonathan Eagles As pointed out correctly by [~jlowe]. https://issues.apache.org/jira/browse/TEZ-2628?focusedCommentId=14715831=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14715831 The MemoryTimelineStore cannot page correctly when using fromId. This is due switching between data structures that apparently have different natural sorting. In addition, the approach of creating a new data structure every time from scratch is costly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (YARN-4186) Make WebAppUtils a public API for yarn
Jonathan Eagles created YARN-4186: - Summary: Make WebAppUtils a public API for yarn Key: YARN-4186 URL: https://issues.apache.org/jira/browse/YARN-4186 Project: Hadoop YARN Issue Type: Bug Reporter: Jonathan Eagles Application types like Tez will want to expose AM container log location to users without having to make a call to the RM. Exposing getRunningLogURL as public will provide this functionality. Jon -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (YARN-3625) RollingLevelDBTimelineStore Incorrectly Forbids Related Entity in Same Put
Jonathan Eagles created YARN-3625: - Summary: RollingLevelDBTimelineStore Incorrectly Forbids Related Entity in Same Put Key: YARN-3625 URL: https://issues.apache.org/jira/browse/YARN-3625 Project: Hadoop YARN Issue Type: Bug Reporter: Jonathan Eagles Assignee: Jonathan Eagles -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (YARN-3498) Improve Timeline Server Memory Usage
Jonathan Eagles created YARN-3498: - Summary: Improve Timeline Server Memory Usage Key: YARN-3498 URL: https://issues.apache.org/jira/browse/YARN-3498 Project: Hadoop YARN Issue Type: Bug Reporter: Jonathan Eagles Assignee: Jonathan Eagles -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (YARN-3448) Add Rolling Time To Lives Level DB Plugin Capabilities
Jonathan Eagles created YARN-3448: - Summary: Add Rolling Time To Lives Level DB Plugin Capabilities Key: YARN-3448 URL: https://issues.apache.org/jira/browse/YARN-3448 Project: Hadoop YARN Issue Type: Improvement Reporter: Jonathan Eagles For large applications, the majority of the time in LeveldbTimelineStore is spent deleting old entities record at a time. A write lock is held during the entire deletion phase which in practice can be hours. An alternative is to create a rolling set of databases that age out and can be efficiently removed via a recursive directory delete. The removes the lock in the deletion thread and clients and servers can share access to the underlying database which already implements its only internal locking mechanism. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (YARN-3287) TimelineClient kerberos authentication failure uses wrong login context.
Jonathan Eagles created YARN-3287: - Summary: TimelineClient kerberos authentication failure uses wrong login context. Key: YARN-3287 URL: https://issues.apache.org/jira/browse/YARN-3287 Project: Hadoop YARN Issue Type: Bug Reporter: Jonathan Eagles Assignee: Daryn Sharp TimelineClientImpl:doPosting is not wrapped in a doAs, which can cause failure for yarn clients to create timeline domains during job submission. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (YARN-3227) Timeline renew delegation token fails when RM user's TGT is expired
Jonathan Eagles created YARN-3227:
-
Summary: Timeline renew delegation token fails when RM user's TGT
is expired
Key: YARN-3227
URL: https://issues.apache.org/jira/browse/YARN-3227
Project: Hadoop YARN
Issue Type: Bug
Reporter: Jonathan Eagles
Priority: Critical
When the RM user's kerberos TGT is expired, the RM renew delegation token
operation fails as part of job submission. Expected behavior is that RM will
relogin to get a new TGT.
{quote}
2015-02-06 18:54:05,617 [DelegationTokenRenewer #25954] WARN
security.DelegationTokenRenewer: Unable to add the application to the
delegation token renewer.
java.io.IOException: Failed to renew token: Kind: TIMELINE_DELEGATION_TOKEN,
Service: timelineserver.example.com:4080, Ident: (owner=user,
renewer=rmuser, realUser=oozie, issueDate=1423248845528,
maxDate=1423853645528, sequenceNumber=9716, masterKeyId=9)
at
org.apache.hadoop.yarn.server.resourcemanager.security.DelegationTokenRenewer.handleAppSubmitEvent(DelegationTokenRenewer.java:443)
at
org.apache.hadoop.yarn.server.resourcemanager.security.DelegationTokenRenewer.access$800(DelegationTokenRenewer.java:77)
at
org.apache.hadoop.yarn.server.resourcemanager.security.DelegationTokenRenewer$DelegationTokenRenewerRunnable.handleDTRenewerAppSubmitEvent(DelegationTokenRenewer.java:808)
at
org.apache.hadoop.yarn.server.resourcemanager.security.DelegationTokenRenewer$DelegationTokenRenewerRunnable.run(DelegationTokenRenewer.java:789)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:722)
Caused by: java.io.IOException: HTTP status [401], message [Unauthorized]
at
org.apache.hadoop.util.HttpExceptionUtils.validateResponse(HttpExceptionUtils.java:169)
at
org.apache.hadoop.security.token.delegation.web.DelegationTokenAuthenticator.doDelegationTokenOperation(DelegationTokenAuthenticator.java:286)
at
org.apache.hadoop.security.token.delegation.web.DelegationTokenAuthenticator.renewDelegationToken(DelegationTokenAuthenticator.java:211)
at
org.apache.hadoop.security.token.delegation.web.DelegationTokenAuthenticatedURL.renewDelegationToken(DelegationTokenAuthenticatedURL.java:414)
at
org.apache.hadoop.yarn.client.api.impl.TimelineClientImpl$2.run(TimelineClientImpl.java:374)
at
org.apache.hadoop.yarn.client.api.impl.TimelineClientImpl$2.run(TimelineClientImpl.java:360)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:415)
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1694)
at
org.apache.hadoop.yarn.client.api.impl.TimelineClientImpl$4.run(TimelineClientImpl.java:429)
at
org.apache.hadoop.yarn.client.api.impl.TimelineClientImpl$TimelineClientConnectionRetry.retryOn(TimelineClientImpl.java:161)
at
org.apache.hadoop.yarn.client.api.impl.TimelineClientImpl.operateDelegationToken(TimelineClientImpl.java:444)
at
org.apache.hadoop.yarn.client.api.impl.TimelineClientImpl.renewDelegationToken(TimelineClientImpl.java:378)
at
org.apache.hadoop.yarn.security.client.TimelineDelegationTokenIdentifier$Renewer.renew(TimelineDelegationTokenIdentifier.java:81)
at org.apache.hadoop.security.token.Token.renew(Token.java:377)
at
org.apache.hadoop.yarn.server.resourcemanager.security.DelegationTokenRenewer$1.run(DelegationTokenRenewer.java:532)
at
org.apache.hadoop.yarn.server.resourcemanager.security.DelegationTokenRenewer$1.run(DelegationTokenRenewer.java:529)
{quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (YARN-3156) Allow RM timeline client renewDelegation exceptions to be non-fatal
Jonathan Eagles created YARN-3156: - Summary: Allow RM timeline client renewDelegation exceptions to be non-fatal Key: YARN-3156 URL: https://issues.apache.org/jira/browse/YARN-3156 Project: Hadoop YARN Issue Type: Improvement Reporter: Jonathan Eagles Assignee: Jonathan Eagles This is a follow-up to YARN-3144. In addition to YarnClientImpl, delegation token renew may also fail after client has successfully retrieved delegation token. This jira is to allow the exception generated in TimelineDelegationTokenIdentifier to be non-fatal if the RM has configured the yarn.timeline-service.client.best-effort flag. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (YARN-3144) Configuration for making delegation token failures to timeline server not-fatal
Jonathan Eagles created YARN-3144: - Summary: Configuration for making delegation token failures to timeline server not-fatal Key: YARN-3144 URL: https://issues.apache.org/jira/browse/YARN-3144 Project: Hadoop YARN Issue Type: Improvement Reporter: Jonathan Eagles Assignee: Jonathan Eagles Posting events to the timeline server is best-effort. However, getting the delegation tokens from the timeline server will kill the job. This patch adds a configuration to make get delegation token operations best-effort. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (YARN-2971) RM uses conf instead of service to renew timeline delegation tokens
Jonathan Eagles created YARN-2971: - Summary: RM uses conf instead of service to renew timeline delegation tokens Key: YARN-2971 URL: https://issues.apache.org/jira/browse/YARN-2971 Project: Hadoop YARN Issue Type: Sub-task Components: timelineserver Affects Versions: 2.6.0 Reporter: Jonathan Eagles Assignee: Jonathan Eagles The TimelineClientImpl renewDelegationToken uses the incorrect webaddress to renew Timeline DelegationTokens. It should read the service address out of the token to renew the delegation token. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (YARN-2900) Application Not Found in AHS throws Internal Server Error with NPE
Jonathan Eagles created YARN-2900: - Summary: Application Not Found in AHS throws Internal Server Error with NPE Key: YARN-2900 URL: https://issues.apache.org/jira/browse/YARN-2900 Project: Hadoop YARN Issue Type: Sub-task Reporter: Jonathan Eagles Assignee: Mit Desai -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (YARN-2556) Tool to measure the performance of the timeline server
Jonathan Eagles created YARN-2556: - Summary: Tool to measure the performance of the timeline server Key: YARN-2556 URL: https://issues.apache.org/jira/browse/YARN-2556 Project: Hadoop YARN Issue Type: Sub-task Components: timelineserver Reporter: Jonathan Eagles We need to be able to understand the capacity model for the timeline server to give users the tools they need to deploy a timeline server with the correct capacity. I propose we create a mapreduce job that can measure timeline server write and read performance. Transactions per second, I/O for both read and write would be a good start. This could be done as an example or test job that could be tied into gridmix. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (YARN-2547) Cross Origin Filter throws UnsupportedOperationException upon destroy
Jonathan Eagles created YARN-2547: - Summary: Cross Origin Filter throws UnsupportedOperationException upon destroy Key: YARN-2547 URL: https://issues.apache.org/jira/browse/YARN-2547 Project: Hadoop YARN Issue Type: Sub-task Components: timelineserver Reporter: Jonathan Eagles -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (YARN-2528) Cross Origin Filter Http response split vulnerability protection rejects valid origins
Jonathan Eagles created YARN-2528: - Summary: Cross Origin Filter Http response split vulnerability protection rejects valid origins Key: YARN-2528 URL: https://issues.apache.org/jira/browse/YARN-2528 Project: Hadoop YARN Issue Type: Sub-task Components: timelineserver Reporter: Jonathan Eagles Assignee: Jonathan Eagles URLEncoding is too strong of a protection for HTTP Response Split Vulnerability protection and major browser reject the encoded Origin. An adequate protection is simply to remove all CRs LFs as in the case of PHP's header function. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (YARN-2512) Allow for origin pattern matching in cross origin filter
Jonathan Eagles created YARN-2512: - Summary: Allow for origin pattern matching in cross origin filter Key: YARN-2512 URL: https://issues.apache.org/jira/browse/YARN-2512 Project: Hadoop YARN Issue Type: Sub-task Components: timelineserver Reporter: Jonathan Eagles -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (YARN-2513) Host framework UIs in YARN for use with the ATS
Jonathan Eagles created YARN-2513: - Summary: Host framework UIs in YARN for use with the ATS Key: YARN-2513 URL: https://issues.apache.org/jira/browse/YARN-2513 Project: Hadoop YARN Issue Type: Sub-task Components: timelineserver Reporter: Jonathan Eagles Allow for pluggable UIs as described by TEZ-8. Yarn can provide the infrastructure to host java script and possible java UIs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (YARN-2507) Document CORS configuration for ATS
Jonathan Eagles created YARN-2507: - Summary: Document CORS configuration for ATS Key: YARN-2507 URL: https://issues.apache.org/jira/browse/YARN-2507 Project: Hadoop YARN Issue Type: Sub-task Components: documentation Affects Versions: 2.6.0 Reporter: Jonathan Eagles Assignee: Mit Desai CORS support was added for ATS as part of YARN-2277. This jira is to document configuration for ATS CORS support. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (YARN-2509) Enable Cross Origin Filter for timeline server only and not all Yarn servers
Jonathan Eagles created YARN-2509: - Summary: Enable Cross Origin Filter for timeline server only and not all Yarn servers Key: YARN-2509 URL: https://issues.apache.org/jira/browse/YARN-2509 Project: Hadoop YARN Issue Type: Sub-task Reporter: Jonathan Eagles Assignee: Mit Desai -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (YARN-2511) Allow All Origins by default when Cross Origin Filter is enabled
Jonathan Eagles created YARN-2511: - Summary: Allow All Origins by default when Cross Origin Filter is enabled Key: YARN-2511 URL: https://issues.apache.org/jira/browse/YARN-2511 Project: Hadoop YARN Issue Type: Sub-task Components: timelineserver Reporter: Jonathan Eagles Assignee: Jonathan Eagles -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (YARN-2375) Allow enabling/disabling timeline server per framework
Jonathan Eagles created YARN-2375: - Summary: Allow enabling/disabling timeline server per framework Key: YARN-2375 URL: https://issues.apache.org/jira/browse/YARN-2375 Project: Hadoop YARN Issue Type: Improvement Reporter: Jonathan Eagles -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (YARN-2277) Add JSONP support to the ATS REST API
Jonathan Eagles created YARN-2277: - Summary: Add JSONP support to the ATS REST API Key: YARN-2277 URL: https://issues.apache.org/jira/browse/YARN-2277 Project: Hadoop YARN Issue Type: Sub-task Reporter: Jonathan Eagles As the Application Timeline Server is provided with built-in UI, it may make sense to enable JSONP Rest API capabilities to allow for remote UI to access the data directly via javascript without cross side server browser blocks coming into play. Example client may be like http://api.jquery.com/jQuery.getJSON/ This can alleviate the need to create a local proxy cache. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (YARN-1491) Upgrade JUnit3 TestCase to JUnit 4
Jonathan Eagles created YARN-1491: - Summary: Upgrade JUnit3 TestCase to JUnit 4 Key: YARN-1491 URL: https://issues.apache.org/jira/browse/YARN-1491 Project: Hadoop YARN Issue Type: Bug Affects Versions: 2.4.0 Reporter: Jonathan Eagles Assignee: Chen He There are still four references to test classes that extend from junit.framework.TestCase hadoop-yarn/hadoop-yarn-common/src/test/java/org/apache/hadoop/yarn/util/TestYarnVersionInfo.java hadoop-yarn/hadoop-yarn-common/src/test/java/org/apache/hadoop/yarn/util/TestWindowsResourceCalculatorPlugin.java hadoop-yarn/hadoop-yarn-common/src/test/java/org/apache/hadoop/yarn/util/TestLinuxResourceCalculatorPlugin.java hadoop-yarn/hadoop-yarn-common/src/test/java/org/apache/hadoop/yarn/util/TestWindowsBasedProcessTree.java -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Created] (YARN-1426) YARN Components need to unregister their beans upon shutdown
Jonathan Eagles created YARN-1426: - Summary: YARN Components need to unregister their beans upon shutdown Key: YARN-1426 URL: https://issues.apache.org/jira/browse/YARN-1426 Project: Hadoop YARN Issue Type: Improvement Affects Versions: 3.0.0, 2.3.0 Reporter: Jonathan Eagles -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (YARN-1031) JQuery UI components reference external css in branch-23
Jonathan Eagles created YARN-1031: - Summary: JQuery UI components reference external css in branch-23 Key: YARN-1031 URL: https://issues.apache.org/jira/browse/YARN-1031 Project: Hadoop YARN Issue Type: Bug Affects Versions: 0.23.9 Reporter: Jonathan Eagles Assignee: Jonathan Eagles -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (YARN-1031) JQuery UI components reference external css in branch-23
[ https://issues.apache.org/jira/browse/YARN-1031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Eagles resolved YARN-1031. --- Resolution: Fixed Fix Version/s: 0.23.10 Thanks for the review, Jason. JQuery UI components reference external css in branch-23 Key: YARN-1031 URL: https://issues.apache.org/jira/browse/YARN-1031 Project: Hadoop YARN Issue Type: Bug Affects Versions: 0.23.9 Reporter: Jonathan Eagles Assignee: Jonathan Eagles Fix For: 0.23.10 Attachments: YARN-1031-branch-0.23.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
