And failover still works correct?
Migration works, everything is reporting right, I think we are safe to close the currently open ticket for the upgrade.
Did you get a change to find out anything about the striping and the handful of jobs taking down the OST?
Thank you so much @yguvvala, @johnsonw, and @jgrund for all your help
I have those in a text pad somewhere...
Depending on the number of OSTs, I’ve seen some of the big labs use 4 as a default stripe for the filesystem.
Other than user education, there’s not much you can do by force. Maybe OST-pools, but that doesn’t prevent someone from hammering a single OST.
or you can do it without a folder with a rename, copy, rm. it's not atomic though, obviously. it would be an interesting feature to be able to transparently re-stripe files, in place so that any processes that have it open don't notice the way they would with mv/cp/rm. i'm sure it's not an enhancement that has not been thought of.
Do you all know where I might look to figure out why they look like this now?
and wil ILM also configure zfspool over OSTs or that have to be done first manually ?
4 OST per 2 OSS --
also OST wl be based on zfs
and my second question is about that.. The 2OSS will be active/active but as zfs pools can only be imported in single OSS host in this case how to achieve active/active HA ?
As what i read is that for active/active both HA hosts should have access to a same sets of disks/volumes.
As what i read is that for active/active both HA hosts should have access to a same sets of disks/volumes.
Here’s a doc on how IML expects an HA setup in managed mode: https://whamcloud.github.io/Online-Help/docs/Install_Guide/ig_ch_03_building.html
active/active in the lustre context means that an OSS is active for a subset (usually half in the case of 2-node OSS pairs) of OSTs and it's peers (partner in the 2-node case again) is active for the remaining (other half in the 2-node case) OSTs. so it's active/active OSSes, not active/active OSTs.
I’ll update here if it works ok
Hello! Can somebody help me to understand how to deploy your software using Docker? I found the file https://github.com/whamcloud/integrated-manager-for-lustre/blob/master/docker/docker-compose.yml but
docker-compose up tells me that ERROR: for setup Cannot create container for service setup: invalid mount config for type "bind": bind mount source path does not exist: /tmp/iml_pw what the file is for?
Okay, I figured that one out. Now I'm trying to rebuild
iml-node-libzfs package because it conflicts with my version of nodejs(and if I force its installation, then it fails at runtime). But I stuck on part where libzfs-sys Rust package can't find libzfs_impl.h just because it is in libzfs folder in /usr/include. Does anybody know full recipe for cooking this thing? I'm targeting CentOS 7.4.
I am looking for some help on a project where I am trying to use the IML API to download Lustre performance metrics (bytes written to and read from the filesystem). I believe that this is possible because this of page: https://whamcloud.github.io/Online-Help/docs/api/rest_API.html. That document indicates that this task should be possible and it refers to downloading time series of data using the /metrics/ sub-URL, but I haven't been able to make this work yet. Would you be willing to help me see where I might be going wrong? I am running IML version 2.1.2, so that might be a complicating factor, but most things I am seeing with the API appear to be consistent with the current documentation. Thanks for any help you can give!