You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@giraph.apache.org by "Swapnil Gandhi (JIRA)" <ji...@apache.org> on 2018/07/30 07:23:00 UTC
[jira] [Updated] (GIRAPH-1199) Incorrect Logging Statement on #255
in GiraphYarnClient
[ https://issues.apache.org/jira/browse/GIRAPH-1199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Swapnil Gandhi updated GIRAPH-1199:
-----------------------------------
Description:
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]
was:
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 loop incorrectly states "minimum" instead of "maximum", which is misleading.
This change fixes it.
Pull Request : https://github.com/apache/giraph/pull/78
> 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)