Improve default ramdisk mounting behavior

Description

Previously we would always re-mount the ramdisk by default. The issue was that the user might accidentally delete Alluxio data that they want to keep. So we changed it so that we don't mount by default, and error out if the ramdisk doesn't exist. Now the user needs to use either "SudoMount" or "Mount" when they start Alluxio for the first time - omitting the mount option no longer works. I suggest changing the default behavior from "NoMount" to "SudoMount" and getting rid of "NoMount". This would make ramdisk/mount option more of an internal implementation detail of Alluxio. Users will only need to worry about mount option if they need to use Mount instead of SudoMount.

1 2 3 4 alluxio-start.sh worker SudoMount # sudo mount only if the ramdisk doesn't exist alluxio-start.sh worker # same as SudoMount alluxio-start.sh worker Mount # regular mount only if the ramdisk doesn't exist alluxio-start.sh worker NoMount # we can get rid of NoMount, just use Mount or SudoMount instead

Seeing as this is an API breaking change, we should target this for 2.0

Environment

None

Status

Assignee

Unassigned

Reporter

Andrew Audibert

Labels

None

Components

Affects versions

1.8.1

Priority

Major