[
https://issues.apache.org/jira/browse/HDDS-6588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siyao Meng updated HDDS-6588:
-----------------------------
Description:
Need to investigate. Possibly
`./compose/upgrade/compose/ha/docker-compose.yaml` has incorrect configs that
prevents Recon from getting Datanodes information?
Repro (just boot the compose cluster up, without doing anything else):
{code}
mvn clean install -Pdist -DskipTests -e -Dmaven.javadoc.skip=true
cd hadoop-ozone/dist/target/ozone-1.3.0-SNAPSHOT/compose/upgrade/compose/ha
docker-compose up -d --scale datanode=3
# Wait for a minute for the Docker Compose cluster to boot up
{code}
Then navigate to http://localhost:9888/, you will be greeted with {{0/0
Datanodes}}:
!bug_recon_1.png!
Clicking into the Datanodes page gives nothing:
!bug_recon_2.png!
But in the Pipelines page it clearly shows live datanodes with OPEN Ratis 1 and
3 pipelines:
!bug_recon_3.png!
SCM Web UI shows 3 healthy, in-service datanodes correctly:
!good_scm_1.png!
This bug was also observed in [this
comment|https://issues.apache.org/jira/browse/HDDS-6546?focusedCommentId=17522504&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17522504]
(unrelated issue), which uses the same docker-compose.yaml.
Note that {{./compose/ozone}} wasn't bothered with the same issue (Recon
displays datanodes just fine).
was:
Need to investigate. Possibly
`./compose/upgrade/compose/ha/docker-compose.yaml` has incorrect configs that
prevents Recon from getting Datanodes information?
Repro (just boot the compose cluster up, without doing anything else):
{code}
mvn clean install -Pdist -DskipTests -e -Dmaven.javadoc.skip=true
cd hadoop-ozone/dist/target/ozone-1.3.0-SNAPSHOT/compose/upgrade/compose/ha
docker-compose up -d --scale datanode=3
# Wait for a minute for the Docker Compose cluster to boot up
{code}
Then navigate to http://localhost:9888/, you will be greeted with {{0/0
Datanodes}}:
!bug_recon_1.png!
Clicking into the Datanodes page gives nothing:
!bug_recon_2.png!
But in the Pipelines page it clearly shows live datanodes with OPEN Ratis 1 and
3 pipelines:
!bug_recon_3.png!
SCM Web UI shows 3 healthy, in-service datanodes correctly:
This bug was also observed in [this
comment|https://issues.apache.org/jira/browse/HDDS-6546?focusedCommentId=17522504&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17522504]
(unrelated issue), which uses the same docker-compose.yaml.
Note that {{./compose/ozone}} wasn't bothered with the same issue (Recon
displays datanodes just fine).
> Recon does not show Datanodes info in `./compose/upgrade/compose/ha/`
> ---------------------------------------------------------------------
>
> Key: HDDS-6588
> URL: https://issues.apache.org/jira/browse/HDDS-6588
> Project: Apache Ozone
> Issue Type: Bug
> Components: Ozone Recon
> Reporter: Siyao Meng
> Priority: Major
> Attachments: bug_recon_1.png, bug_recon_2.png, bug_recon_3.png,
> good_scm_1.png
>
>
> Need to investigate. Possibly
> `./compose/upgrade/compose/ha/docker-compose.yaml` has incorrect configs that
> prevents Recon from getting Datanodes information?
> Repro (just boot the compose cluster up, without doing anything else):
> {code}
> mvn clean install -Pdist -DskipTests -e -Dmaven.javadoc.skip=true
> cd hadoop-ozone/dist/target/ozone-1.3.0-SNAPSHOT/compose/upgrade/compose/ha
> docker-compose up -d --scale datanode=3
> # Wait for a minute for the Docker Compose cluster to boot up
> {code}
> Then navigate to http://localhost:9888/, you will be greeted with {{0/0
> Datanodes}}:
> !bug_recon_1.png!
> Clicking into the Datanodes page gives nothing:
> !bug_recon_2.png!
> But in the Pipelines page it clearly shows live datanodes with OPEN Ratis 1
> and 3 pipelines:
> !bug_recon_3.png!
> SCM Web UI shows 3 healthy, in-service datanodes correctly:
> !good_scm_1.png!
> This bug was also observed in [this
> comment|https://issues.apache.org/jira/browse/HDDS-6546?focusedCommentId=17522504&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17522504]
> (unrelated issue), which uses the same docker-compose.yaml.
> Note that {{./compose/ozone}} wasn't bothered with the same issue (Recon
> displays datanodes just fine).
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
