=== TODO ===

We need to update the time of the Community Meeting wiki page: after the daylight saving changes it's not clear what is the right time (some people joined after the call :-((( )


=== 0.5.0-RC2 is OUT ===

PLEASE TEST AND SHARE YOUR FEEDBACK


> Nanda: there is a problem on the Datanode side when it's restarted it checks the container db for deletion records. We need to optimize that part. (Not a blocker for the release)


=== Ongoing discussions ===

---> Edge cases of the Rack-aware replication (Stephen) ------------

* Open question: close pipelines vs. migrating containers between open containers

* Jitendra: we need to make the pipeline creation / close faster anyway

* Some questions raised by Pifta about sharing code between the replication strategies of Open / closed containers

* Marton: We might need different implementation but we can share some code

* Xiaoyu: There were some decisions regarding how the rack awareness code has been implemented but it can be revisited based on our experiences. (It was hard to share between open / close pipelines)

* Arpit: can we just deny the creation of the non-rack-aware pipelines if the rack aware configuration exists? It would simplify the questions. (Agreement: let's check how the script works. Good idea, if it works... We can make it more sophisticated if we can see business requirements...)

* Proposal to add / remove new / old nodes from Ratis ring seems to be complex.

* Jitendra: Pipelines should be more lightweight long-term (create / close more easily). It should be easy to close/create new pipelines. (Especially with having multi-raft)

---> S3 vs volume names (Marton) ------------

* Arpit: there are multiple problems with volumes: the whole notion of ownership with volumes needs to be revisited

   * We need further discussion and understanding the importance of Volumes

---> SCM HA design (Li Chen) ------------

   * work in progress (see the mailing list)

---> Design doc for NFS (HDDS-3001)

  * work in progress: will be published soon



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to