Possible use for memcache?
mike503 at gmail.com
Mon Nov 28 00:34:11 PST 2005
On 11/28/05, Ask Bjørn Hansen <ask at develooper.com> wrote:
> If I'm reading what you are writing right, then you need to read up a
> bit on how the file systems work. :-)
> If you have two servers file system drivers use the same physical
> storage then you need block level locking (not "file level" locking).
Both reasons why I simply posed a question to people more knowledgable
than myself about filesystems and such. This isn't the right place to
ask, so I won't. But going further down this path I'd ask what
consistitutes a block (is it a physical device as in /dev/foo, or just
an inode, whatever...) - but that's not for this list. Also, perhaps
my thinking may spur some ideas that others may have missed - there's
a lot of coders out there who know C and filesystem semantics, and
maybe it took the uneducated view of someone who thinks in scripting
terms to help separate them from specific concepts or roadblocks.
> You should subscribe to another list that's more relevant and then
> take a few steps back and figure out what you need and then get help
> to find the best solution. You are asking "How can I get X to do Y"
> when you really want to ask "How do I do Z".
I've been asking that question for weeks. I think I have clearly
defined what I want - quite easily only a couple high level
requirements - multipath I/O to a shared storage unit (i.e. same
physical storage array) that can scale easily.
I've been looking into solution space since then, and this was one of
my ideas/routes to explore. Like I said, it may involve memcached, so
I posed the question here. Even if memcached isn't part of the
solution, perhaps someone would have a quick answer.
>  the scalable list maybe, scalable-subscribe at arctic.org.
I'll look into that.
More information about the memcached