[ 
https://issues.apache.org/jira/browse/YARN-2123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Johannes Simon updated YARN-2123:
---------------------------------

    Description: In our cluster setup, the YARN web UI always shows progress 
bars at 100% (see screenshot, progress of the reduce step is roughly at 
32.82%). I opened the HTML source code to check (also see screenshot), and it 
seems the problem is that it uses a comma as decimal mark, where most browsers 
expect a dot for floating-point numbers. This could possibly be due to 
localized number formatting being used in the wrong place, which would also 
explain why this bug is not always visible.  (was: In our cluster setup, the 
YARN web UI always shows progress bars at 100% (see screenshot, progress is 
roughly at 32.82%). I opened the HTML source code to check (also see 
screenshot), and it seems the problem is that it uses a comma as decimal mark, 
where most browsers expect a dot for floating-point numbers. This could 
possibly be due to localized number formatting being used in the wrong place, 
which would also explain why this bug is not always visible.)

> Progress bars in Web UI always at 100% (likely due to non-US locale)
> --------------------------------------------------------------------
>
>                 Key: YARN-2123
>                 URL: https://issues.apache.org/jira/browse/YARN-2123
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: webapp
>    Affects Versions: 2.3.0
>            Reporter: Johannes Simon
>            Priority: Minor
>         Attachments: screenshot.png
>
>
> In our cluster setup, the YARN web UI always shows progress bars at 100% (see 
> screenshot, progress of the reduce step is roughly at 32.82%). I opened the 
> HTML source code to check (also see screenshot), and it seems the problem is 
> that it uses a comma as decimal mark, where most browsers expect a dot for 
> floating-point numbers. This could possibly be due to localized number 
> formatting being used in the wrong place, which would also explain why this 
> bug is not always visible.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to