Skip to content

fix: setup nvme disk for data/historical/middlemanager #16

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

Merged
merged 1 commit into from
May 2, 2024

Conversation

sydefz
Copy link
Contributor

@sydefz sydefz commented May 2, 2024

Description of changes:

we recently noticed the solution is creating task and processing folders for middle manager using a hard coded approach (/mnt/disk2), in some cases, we want to choose which disk to use by setting runtime.properties i.e. "druid.worker.baseTaskDirs": ["/mnt/disk3/var/druid/task"]

this PR

  • makes sure the solution creates tmp, task and processing folders on all disks to make it possible to config task dir
  • makes sure when running middlaManager alone the user_data also mounts disks and creates folders

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@chn217 chn217 merged commit f189f43 into aws-solutions:main May 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants