while it is nothing new, that much is true, the proper implementation of it
for ejb is still a bit up in the air. We will take a crack at it.
marc
|-----Original Message-----
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Ryan Marsh
|Sent: Friday, January 12, 2001 3:41 PM
|To: jBoss Developer
|Subject: Re: [jBoss-Dev] Clustering - second try
|
|
|Clustering is not a new problem. I'm sure there are some design paradigms
|and best practices we can learn from. Let's not try to reinvent the wheel.
|
|Regards,
|-ryan
|
|The three great virtues of programming are laziness, impatience,
|and hubris,
|but bigotry makes the open-source world go round.
|----- Original Message -----
|From: Filip Hanik <[EMAIL PROTECTED]>
|To: <[EMAIL PROTECTED]>
|Sent: Friday, January 12, 2001 1:16 PM
|Subject: [jBoss-Dev] Clustering - second try
|
|
|> the email didn't seem to go through the first time.
|>
|> Marc,
|> I read the bugzilla note on clustering.
|> the "herd", "shepard", "sheep" and "food" paradigms.
|> in my humble opinion the herd,shepard etc words makes the document
|extremely
|> hard to read.
|> because I kept forgetting what they all meant. "Animals hunting for land"
|is
|> not an intuitive language, :) (no harm intended)
|>
|> This document is based on a component called the cluster manager (CM).
|> and it says in the docs that "if the CM dies, the cluster vanishes".
|> doesn't this create the same "single-point-of failure" that Gemstone had
|in
|> their server a couple of years ago?
|>
|> It would be nicer if any server in the cluster could act as the cluster
|> manager, and if one server dies, another server can assume the same
|> responsibilities and carry the cluster from that point. When the original
|CM
|> comes up again, it should become secondary CM and be ready to take over
|the
|> CM responsibilities at any point.
|>
|> Am I making any sense or is it all jibberish?
|>
|> Filip
|>
|>
|> Filip Hanik
|> Technical Architect
|> Pakana Corporation
|> [EMAIL PROTECTED]
|> 415-371 9200 ext 3529
|>
|> "Windows is a 32 bit patch to a 16 bit GUI based on a 8 bit operating
|system
|> written for a 4 bit processor by a 2 bit company which can not
|stand 1 bit
|> of competition."
|>
|>
|
|
|
