[jira] [Commented] (HDFS-8768) Erasure Coding: block group ID displayed in WebUI is not consistent with fsck
[
https://issues.apache.org/jira/browse/HDFS-8768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14643719#comment-14643719
]
GAO Rui commented on HDFS-8768:
---
Yes, I think so too. But It seems like that I could not make this jira to the
status of closed. Can you help me to close this JIRA? Thank you [~zhz]
> Erasure Coding: block group ID displayed in WebUI is not consistent with fsck
> -
>
> Key: HDFS-8768
> URL: https://issues.apache.org/jira/browse/HDFS-8768
> Project: Hadoop HDFS
> Issue Type: Sub-task
>Reporter: GAO Rui
> Attachments: Screen Shot 2015-07-14 at 15.33.08.png,
> screen-shot-with-HDFS-8779-patch.PNG
>
>
> This is duplicated by [HDFS-8779].
> For example, In WebUI( usually, namenode port: 50070) , one Erasure Code
> file with one block group was displayed as the attached screenshot [^Screen
> Shot 2015-07-14 at 15.33.08.png]. But, with fsck command, the block group of
> the same file was displayed like: {{0.
> BP-1130999596-172.23.38.10-1433791629728:blk_-9223372036854740160_3384
> len=6438256640}}
> After checking block file names in datanodes, we believe WebUI may have some
> problem with Erasure Code block group display.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HDFS-8768) Erasure Coding: block group ID displayed in WebUI is not consistent with fsck
[
https://issues.apache.org/jira/browse/HDFS-8768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14641204#comment-14641204
]
Zhe Zhang commented on HDFS-8768:
-
I think we should close this JIRA and rely on the solution of HDFS-8779. We
need a solution for randomly generated IDs anyway. [~sinall] [~walter.k.su] let
me know if you agree.
> Erasure Coding: block group ID displayed in WebUI is not consistent with fsck
> -
>
> Key: HDFS-8768
> URL: https://issues.apache.org/jira/browse/HDFS-8768
> Project: Hadoop HDFS
> Issue Type: Sub-task
>Reporter: GAO Rui
> Attachments: Screen Shot 2015-07-14 at 15.33.08.png,
> screen-shot-with-HDFS-8779-patch.PNG
>
>
> This is duplicated by [HDFS-8779].
> For example, In WebUI( usually, namenode port: 50070) , one Erasure Code
> file with one block group was displayed as the attached screenshot [^Screen
> Shot 2015-07-14 at 15.33.08.png]. But, with fsck command, the block group of
> the same file was displayed like: {{0.
> BP-1130999596-172.23.38.10-1433791629728:blk_-9223372036854740160_3384
> len=6438256640}}
> After checking block file names in datanodes, we believe WebUI may have some
> problem with Erasure Code block group display.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HDFS-8768) Erasure Coding: block group ID displayed in WebUI is not consistent with fsck
[
https://issues.apache.org/jira/browse/HDFS-8768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628157#comment-14628157
]
Walter Su commented on HDFS-8768:
-
HDFS-8779 will break API. I think a workaroud is to make block group id start
from -2^53
> Erasure Coding: block group ID displayed in WebUI is not consistent with fsck
> -
>
> Key: HDFS-8768
> URL: https://issues.apache.org/jira/browse/HDFS-8768
> Project: Hadoop HDFS
> Issue Type: Sub-task
>Reporter: GAO Rui
> Attachments: Screen Shot 2015-07-14 at 15.33.08.png,
> screen-shot-with-HDFS-8779-patch.PNG
>
>
> This is duplicated by [HDFS-8779].
> For example, In WebUI( usually, namenode port: 50070) , one Erasure Code
> file with one block group was displayed as the attached screenshot [^Screen
> Shot 2015-07-14 at 15.33.08.png]. But, with fsck command, the block group of
> the same file was displayed like: {{0.
> BP-1130999596-172.23.38.10-1433791629728:blk_-9223372036854740160_3384
> len=6438256640}}
> After checking block file names in datanodes, we believe WebUI may have some
> problem with Erasure Code block group display.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HDFS-8768) Erasure Coding: block group ID displayed in WebUI is not consistent with fsck
[
https://issues.apache.org/jira/browse/HDFS-8768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14627889#comment-14627889
]
GAO Rui commented on HDFS-8768:
---
Thank you [~walter.k.su] very much!
> Erasure Coding: block group ID displayed in WebUI is not consistent with fsck
> -
>
> Key: HDFS-8768
> URL: https://issues.apache.org/jira/browse/HDFS-8768
> Project: Hadoop HDFS
> Issue Type: Sub-task
>Reporter: GAO Rui
> Attachments: Screen Shot 2015-07-14 at 15.33.08.png,
> screen-shot-with-HDFS-8779-patch.PNG
>
>
> For example, In WebUI( usually, namenode port: 50070) , one Erasure Code
> file with one block group was displayed as the attached screenshot [^Screen
> Shot 2015-07-14 at 15.33.08.png]. But, with fsck command, the block group of
> the same file was displayed like: {{0.
> BP-1130999596-172.23.38.10-1433791629728:blk_-9223372036854740160_3384
> len=6438256640}}
> After checking block file names in datanodes, we believe WebUI may have some
> problem with Erasure Code block group display.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HDFS-8768) Erasure Coding: block group ID displayed in WebUI is not consistent with fsck
[
https://issues.apache.org/jira/browse/HDFS-8768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14627693#comment-14627693
]
Walter Su commented on HDFS-8768:
-
That's because In JavaScript, all numbers are 64 bits floating point numbers.
And block group ID counting from Long.MIN_VALUE in NN. The json got from
webhdfs is correct.
> Erasure Coding: block group ID displayed in WebUI is not consistent with fsck
> -
>
> Key: HDFS-8768
> URL: https://issues.apache.org/jira/browse/HDFS-8768
> Project: Hadoop HDFS
> Issue Type: Sub-task
>Reporter: GAO Rui
> Attachments: Screen Shot 2015-07-14 at 15.33.08.png
>
>
> For example, In WebUI( usually, namenode port: 50070) , one Erasure Code
> file with one block group was displayed as the attached screenshot [^Screen
> Shot 2015-07-14 at 15.33.08.png]. But, with fsck command, the block group of
> the same file was displayed like: {{0.
> BP-1130999596-172.23.38.10-1433791629728:blk_-9223372036854740160_3384
> len=6438256640}}
> After checking block file names in datanodes, we believe WebUI may have some
> problem with Erasure Code block group display.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
