You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By default, all Distem vnode data and configuration are stored in /tmp/distem on the main disk, which makes the vnodes compete for disk read/write. Since vnodes in my experiment will each use the disk, I was wondering if there is a way to isolate the vnodes disks.
Assuming the physical node has multiple disks, and that we format them, create a partition, and mount them, I thought I found a way to do this:
if I set the "path" parameter in the "vfilesystem" hash to a different mount point for each vnode on the same pnode host:
path [r]: The path to the unique directory used to store this virtual node files
I tried it but it seemed to ignore the parameter completely and just used the default:
"/tmp/distem/rootfs-unique" + node name
Update: I realize now this is a read-only parameter. Would it be possible to use different disks if you could make this parameter writeable?
Thanks!
The text was updated successfully, but these errors were encountered:
By default, all Distem vnode data and configuration are stored in /tmp/distem on the main disk, which makes the vnodes compete for disk read/write. Since vnodes in my experiment will each use the disk, I was wondering if there is a way to isolate the vnodes disks.
Assuming the physical node has multiple disks, and that we format them, create a partition, and mount them, I thought I found a way to do this:
if I set the "path" parameter in the "vfilesystem" hash to a different mount point for each vnode on the same pnode host:
I tried it but it seemed to ignore the parameter completely and just used the default:
Update: I realize now this is a read-only parameter. Would it be possible to use different disks if you could make this parameter writeable?
Thanks!
The text was updated successfully, but these errors were encountered: