Hi,
I'm evaluating OrangeFS here at RAL at the moment for possible future use as a
distributed FS for our LHC disk storage system. I've got the FS working, and
have run some performance tests. My configuration looks like this:
- 6*10TB storage nodes, each set up to hold both data and metadata.
- One client box that mounts the FS for external use.
- db4.8.30 on every box.
I've got some questions:
1) Is there any way to make changes to the system without bringing
everything down first? We need to be able to add or remove nodes to or from the
OrangeFS instance on the fly, without bringing everything down or losing data.
i. Can the
system be made extensible by initially only allocating part of the available
namespace in orangefs-server.conf, and then adding more servers into the unused
regions of the namespace?
2) Is the loss of a node from the FS as catastrophic as it appears to be?
Turning off the daemon on one storage/metadata node brought down the whole
system. I'm aware of the documented solution using Heartbeat , but that only
appears to keep the system upright, rather than helping us to preserve data in
the event of a failure.
3) Is there a timescale for the results of the development work into
improving redundancy?
Thanks very much,
Rob Appleyard
RAL
--
Scanned by iCritical.
_______________________________________________
Pvfs2-users mailing list
[email protected]
http://www.beowulf-underground.org/mailman/listinfo/pvfs2-users
