[
https://issues.apache.org/jira/browse/YARN-10006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16989045#comment-16989045
]
Adam Antal commented on YARN-10006:
-----------------------------------
Fixed the test cases that my patch broke. The problem was the test was
expecting IllegalArgumentException, but now it receives {{ServiceException}}
since the {{YarnException}} was thrown in the
{{CapacityScheduler#serviceInit()}} function, and the {{CompositeService}}
catches it in its super function.
> IOException used in place of YARNException in CapacitySheduler
> --------------------------------------------------------------
>
> Key: YARN-10006
> URL: https://issues.apache.org/jira/browse/YARN-10006
> Project: Hadoop YARN
> Issue Type: Bug
> Components: capacity scheduler
> Affects Versions: 3.3.0
> Reporter: Prabhu Joseph
> Assignee: Adam Antal
> Priority: Minor
> Attachments: YARN-10006.001.patch, YARN-10006.002.patch
>
>
> IOException used in place of YARNException in CapacityScheduler. As per
> YARNException Doc,
> {code:java}
> /**
> * YarnException indicates exceptions from yarn servers. On the other hand,
> * IOExceptions indicates exceptions from RPC layer.
> */
> {code}
> Below methods throws IOException but it is suppose to throw YarnException.
> CapacitySchedulerQueueManager#parseQueue <- initializeQueues <-
> CapacityScheduler#initializeQueues <- initScheduler <- serviceInit
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
