Hi Filip, Rajith, AllThanks to all the resources from Filip I guess we can now get a good undestanding of tribes and use it for an implementation of the ClusterManager. As u guys had mentioned the session updates hv to be done periodically. I guess this can be decided based on the Axis2 contexts
Hi All,As Chamikara pointed out we have left the proposal for about a week now for any comments/concerns.I guess people are happy so far with the proposal.Shall we move on to the implementation stage?
Filip could you please have a look and let us know your ideas?Regards,RajithOn 8/25/06, Rajith
it all looks kosher to me. the logic that you are talking about is axis
invocation logic.
in tomcat for example, we intercept the request with a valve, and after
the request is complete, we simple check to see if the session was updated,
and then notify the replicated map to flush out the
Filip,Thank you for picking up the baton. Can u please provide a list of resources that people should be looking at if they are to use Tribes?like where to download, documentation ...etc?Chamikar and Chathura (and everybody else interested)... shall we get started on the impl?
We can each choose
Sure, resources can be found at:
A brief introduction
http://people.apache.org/~fhanik/tribes/docs/introduction.html
http://people.apache.org/%7Efhanik/tribes/docs/introduction.html
Simple summary
http://people.apache.org/~fhanik/tribes/javadoc/org/apache/catalina/trib
Hi Deepal,Please see below.On 8/24/06, Deepal Jayasinghe [EMAIL PROTECTED] wrote:
Hi Chamikara;Chamikara Jayalath wrote: Hi All, Here is a summary of the ideas we discussed in the hackathon. -
1. It is
Hi Ajith,Please see my comments below.On 8/25/06, Ajith Ranabahu [EMAIL PROTECTED] wrote:
Hi Guys,This seems to be a very good proposal and +1 to go ahead. I am +1*not* to cluster operation contexts and message contexts since the
overhead will be enormous and we would probably loose the advantage
Thanks guys for the comments.My comments are inline, marked with [RA]Regards,RajithOn 8/25/06, Ajith Ranabahu
[EMAIL PROTECTED] wrote:Hi Guys,This seems to be a very good proposal and +1 to go ahead. I am +1
*not* to cluster operation contexts and message contexts since theoverhead will be
Chamikara,I guess the other point that we don't have a clear grasp is the specific points where axis2 will invoke the cluster interface.We should try to make this as easy and non-intrusive as possible.
If we add this in AbstractMessageReceiver and the AbstractTransportSender then we clearly need
-
From:
Chamikara
Jayalath
To:
axis-dev@ws.apache.org
Sent: Thursday, August 10, 2006 8:22
PM
Subject: Re: [Axis2] An approach for
clustering Axis2
Hi Chinthaka,The main reason for not doing this was the
cost they would produce. Think of a cluster with 5 machines
:[EMAIL PROTECTED]
*To:* axis-dev@ws.apache.org mailto:axis-dev@ws.apache.org
*Sent:* Thursday, August 10, 2006 8:22 PM
*Subject:* Re: [Axis2] An approach for clustering Axis2
Hi Chinthaka,
The main reason for not doing this was the cost
Hi Guys,
This seems to be a very good proposal and +1 to go ahead. I am +1
*not* to cluster operation contexts and message contexts since the
overhead will be enormous and we would probably loose the advantage of
the clustering!
Anyway have you guys thought about the following issues ? (I'm not
to the
cluster. So IMHO what you has proposed is a good step towards
clustering.
-Jaliya
- Original Message -
From:
Chamikara
Jayalath
To:
axis-dev@ws.apache.org
Sent: Thursday, August 10, 2006 8:22
PM
Subject: Re: [Axis2] An approach for
clustering Axis2
Hi
-
From:
Chamikara
Jayalath
To: axis-dev@ws.apache.org
Sent: Thursday, August 10, 2006 8:22
PM
Subject: Re: [Axis2] An approach for
clustering Axis2
Hi Chinthaka,The main reason for not doing this was the
cost they would produce. Think of a cluster with 5 machines. Every machine
Hi All,
As you know, sometime back that there
were some discussion on clustering Axis2. Quite a set of ideas came
up, specially from Rajith.
Me and Chathura Ekanayake thought of
bringing this discussion back to life by coming up with a proposal to
enable context replication in Axis2. Upon
One simple question?
Why did u forget the replication of message contexts and operation
contexts, whilst replicating ConfigurationContexts and the others. IIRC,
operation context map is maintained in the config context.
Another point. Think of IN-IN-OUT mep. You first route the first IN
message
Hi Chinthaka,
The main reason for not doing this was the cost they would produce.
Think of a cluster with 5 machines. Every machine getting 5 requests
per second. We will be trying to replicate 25 Message Contexts every
second. If all these are InOnly requests that would need the
replication of
+1 .. basically we need to decide at what level to cluster for high
availability. This proposal is that we do it at operation boundaries ..
that is if stuff falls apart in the midst of an operation we can't do
anything about that. If you need that level of reliability then you
should be using
18 matches
Mail list logo
