Sahil Takiar has posted comments on this change. ( http://gerrit.cloudera.org:8080/15334 )
Change subject: IMPALA-9400: Initial Ozone support ...................................................................... Patch Set 1: (1 comment) http://gerrit.cloudera.org:8080/#/c/15334/1//COMMIT_MSG Commit Message: http://gerrit.cloudera.org:8080/#/c/15334/1//COMMIT_MSG@18 PS1, Line 18: > I have some questions about the block locations and scheduling. Does this l >From what I know so far, Ozone does expose block locations. This patch changes supportsStorageIds so that it returns true for Ozone filesystems as well (this should make the HdfsScanNode fetch the block locations and perform scheduling based on the block locations). However, I think I might revert that part of the patch. I believe, for the most part, we expect to deploy Ozone on a dedicated storage cluster that is separate from the Impala compute cluster - e.g. separate compute vs storage cluster. So I think, at least for now, its okay if we treat Ozone as remote storage (similar to what we do for ABFS and S3A). Even with separate storage + compute clusters, block locations might help with rack-aware scheduling, but I don't think we support that in Impala yet? I'll make the fixes for the DiskIoMgr. -- To view, visit http://gerrit.cloudera.org:8080/15334 To unsubscribe, visit http://gerrit.cloudera.org:8080/settings Gerrit-Project: Impala-ASF Gerrit-Branch: master Gerrit-MessageType: comment Gerrit-Change-Id: I2544ff61e8767f061253a62a01ce2b7dfc384a99 Gerrit-Change-Number: 15334 Gerrit-PatchSet: 1 Gerrit-Owner: Sahil Takiar <[email protected]> Gerrit-Reviewer: Impala Public Jenkins <[email protected]> Gerrit-Reviewer: Joe McDonnell <[email protected]> Gerrit-Reviewer: Sahil Takiar <[email protected]> Gerrit-Reviewer: Tim Armstrong <[email protected]> Gerrit-Comment-Date: Mon, 02 Mar 2020 17:37:17 +0000 Gerrit-HasComments: Yes
