On May 28, 2022, at 9:02 AM, fge...@gmail.com wrote: > > Has anybody considered (or maybe even implemented) a 9p server to > multiply incoming 9p messages to 2 or more 9p servers? > Maybe with 2 different strategies for responding to the original request? > 1. respond as soon as at least 1 response from one of the 9p servers > is received, > 2. respond only after all responses had been received.
Some variation of this would be interesting for a clustered or distributed filesystem. The challenge would be doing this in an understandable way, cleanly and with good performance. Probably using separate namespaces for control & management operations. [Just brainstorming here...] May be think about this using a clean slate approach. Features that can be of use: - fault tolerance (more than one node storing the same bits) - scalable (in capacity, throughput, clients and server nodes) - consistent view of the "same" FS by its clients - file migration (transparent to a client e.g. to reduce latency) - controlled sharing - file size that can exceed the capacity of a single node - allow storing files bigger than can fit on a node - nodes can show up/go away dynamically - provide multiple security domains (one bank, many customers!) - access to older snapshots - allow use of any local FS for storage - easy to provision & manage ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/T769854fafd2b7d35-M30f1ef13e6748428ffc79346 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
