You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by GitBox <gi...@apache.org> on 2020/01/29 17:16:00 UTC

[GitHub] [hadoop-ozone] avijayanhwx commented on issue #466: HDDS-2869. Handle pipeline bootstrap from SCM and create pipeline use case in Recon.

avijayanhwx commented on issue #466: HDDS-2869. Handle pipeline bootstrap from SCM and create pipeline use case in Recon.
URL: https://github.com/apache/hadoop-ozone/pull/466#issuecomment-579863624
 
 
   > Thanks @avijayanhwx for implementing this. I tried it locally on a docker-compose cluster and found that Recon does not get new pipeline information.
   > 
   > 1. Since now the recon container does not wait with startup, it received 0 pipelines initially:
   >    ```
   >    recon_1     | 2020-01-29 08:41:05,263 [main] INFO scm.ReconStorageContainerManagerFacade: Obtained 0 pipelines from SCM.
   >    recon_1     | 2020-01-29 08:41:05,264 [main] INFO scm.ReconPipelineManager: Recon has 0 pipelines in house.
   >    ```
   >    
   >    
   >    That would be OK, but when the pipelines were created a bit later, they did not show up in Recon.  (I also checked with `WAITFOR` restored, 3+1 initial pipelines were received in that case, but I feel it's a bit timing-dependent.)
   > 2. Closed the initial 3-node pipeline via `scmcli`, which eventually triggered creation of new one in SCM, but Recon never noticed.
   > 
   > Can you please check?
   
   @adoroszlai I have not wired up the DN-> Recon path by default since that may cause some unintended test failures before finishing the whole "Recon as a Passive SCM" feature. In my local, I test with the following configs added. 
   
   > OZONE-SITE.XML_ozone.recon.datanode.address=recon:9891
   > OZONE-SITE.XML_ozone.recon.address=recon:9891
   > OZONE-SITE.XML_ozone.recon.datanode.bind.host=recon 
   
   That will lead to pipelines being picked up by Recon.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-issues-help@hadoop.apache.org