You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "ivandika3 (via GitHub)" <gi...@apache.org> on 2026/07/02 01:36:21 UTC

Re: [PR] HDDS-15059. Shift streaming write sortDatanodes logic to OM [ozone]

ivandika3 commented on PR #10633:
URL: https://github.com/apache/ozone/pull/10633#issuecomment-4861424530

   @peterxcli thanks for checking.
   
   > Is there any risk that a block ends up allocated on a suboptimal datanodes/pipeline because the OM cache topology is somehow stale?⁠
   
   Should have effect on performance but not correctness, since Streaming Write Pipeline should be able to pick an arbitrary topology as the data path (streaming WriteChunk data) which can be sent to any primary (first node) is separated from the metadata path (PutBlock) which will be sent to the DN leader. The impact of suboptimal Streaming write pipeline topology should be a worse write latency (e.g. if the topology picks the furthest node as the primary node). But this possible performance penalty also apply to read path so I think it should be acceptable. Please let me know if I miss something.
   
   @chihsuan Thanks for the patch, I'll review this soon.


-- 
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.

To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


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