This repository has been archived by the owner on Jan 3, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 25
Cannot easily start plasma service on AWS EMR cluster. #152
Comments
@winningsix @zhixingheyi-tian Please help to track the issue. Thanks! |
To clarify further, we can install binary on each worker but can't do start service for each worker in initial script. Am I right? |
cc @yma11 |
maybe through the yarn service? https://github.com/oap-project/sql-ds-cache/blob/master/docs/User-Guide.md#configuration-for-enabling-pmem-cache |
@winningsix Yes, your description is clear. |
@yma11 wrong link? Didn't find how to use YARN to start the environment. @haojinIntel we should be able to start service via that way mentioned by @yma11 once she corrects that. |
Link is correct. There are contents about "Use Yarn to start Plasma service". |
@yma11 that part should work. @haojinIntel can you help have a try? |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
For OAP-1.2, we target to support all features on cloud. We choose emr-6.3.0 and the versions of software are showed below:
For plasma-sql-ds-cache it's not convenient to log on each workers to start plasma service. Can we start plasma service through yarn service? We hope that all the actions can only be executed on master.
The text was updated successfully, but these errors were encountered: