-
Notifications
You must be signed in to change notification settings - Fork 9.1k
HDDS-1138. Ozone Client should avoid talking to SCM directly #585
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
💔 -1 overall
This message was automatically generated. |
Thanks for working on this @xiaoyuyao. |
Rebase after the following two conflicting changes: |
💔 -1 overall
This message was automatically generated. |
Currently in standalone, by default hostName of the standalone processor is used as LocationId. However, for containerized environments like azure cloud, kubernetes this defaulting does not work. Standalone processors can be launched from different kubernetes container on a physical machine(where each kubernetes container has different locatliyID than other kubernetes container within same machine). To solve this problem, we introduce locationID abstraction to allow users to plugin a uniqueId identifying the execution environment of the processor. In containerized environments, LocationId is a composite key of multiple fields: (sliceId, containerId, hostname) By default hostname will be used as LocationId(if not configured by the user). All the processors of an application registered from an locationID should be able to share(read/write) their local state stores. Any custom LocationIdProvider is expected to honor this contract when generating the locationID. This patch is part of SEP-11. Please refer to it for more details. Author: Shanthoosh Venkataraman <spvenkat@usc.edu> Reviewers: Jagadish<jagadish@apache.org> Closes apache#585 from shanthoosh/add_location_id_interface
This PR is build based on @mukul1987 's initial patch to optimize write path only.
The difference are