giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GIRAPH-1199) Incorrect Logging Statement on #255 in GiraphYarnClient
Date Thu, 02 Aug 2018 02:59:00 GMT

    [ https://issues.apache.org/jira/browse/GIRAPH-1199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16566283#comment-16566283
] 

Hudson commented on GIRAPH-1199:
--------------------------------

SUCCESS: Integrated in Jenkins build Giraph-trunk-Commit #1755 (See [https://builds.apache.org/job/Giraph-trunk-Commit/1755/])
GIRAPH-1199 (dionysios: [http://git-wip-us.apache.org/repos/asf?p=giraph.git&a=commit&h=239ea8fb3cab9e2c052d933e8f0ae25648782e95])
* (edit) giraph-core/src/main/java/org/apache/giraph/yarn/GiraphYarnClient.java


> Incorrect Logging Statement on #255 in GiraphYarnClient
> -------------------------------------------------------
>
>                 Key: GIRAPH-1199
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-1199
>             Project: Giraph
>          Issue Type: Improvement
>            Reporter: Swapnil-Gandhi
>            Priority: Trivial
>
> Summary :
> In-case, Yarn-Heap-Size passed in Giraph Configuration exceeds max available capacity,
we downgrade its value to max capacity (Lines #253-#257).
> Currently, the logger message associated with this conditional statement incorrectly
states "minimum" instead of "maximum", which is misleading.
> This change fixes it.
> Pull Request : [https://github.com/apache/giraph/pull/78]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message