Hans K. Rosbach wrote:
-SCTP support, this might not be a silver bullet but it feels
[...]
Features that might need glusterfs code changes:
[...]
-Multihoming (failover when one nic dies)
How is this different to what can be achieved (probably much more cleanly) with NIC bonding?
[...]
-Ability to have the storage nodes autosync themselves. In our setup the normal nodes have 2x1Gbit connections while the storage boxes have 2x10Gbit connections, so having the storage boxes use their own bandwidth and resources to sync would be nice.
Sounds like you want server-side rather than client-side replication. You could do this by using afr/replicate on the servers, and export via NFS to the clients. Have failover handled as for any normal NFS server.
-An ability for the clients to subscribe to metadata updates for a specific directory would also be nice, so that it can cache that folders stats while working there and still know that it will not miss any changes. This would perhaps increase overhead in large clusters but could improve performance by a lot in clusters where several nodes work in the same folder (mail spool folder for example).
You have a shared mail spool on your nodes? How do you avoid race conditions on deferred mail?
Gordan
