Tim wrote : Ok, so it looks like good progress is being made on failover :)
|
| What is there left to do?
|
| ...
|
| Load balancing policy for determining which server to initially connect to. (Re-use
from remoting).
At this point, there is a HAConnectionFactory, registered in JNDI, that will LoadBalance
Connectionso on createConnection.
Tim wrote : Mechanism for propagating changes in the client side server list from the
server to the client when a jgroups view change occurs. I.e. when a new node joins /
leaves. (Do we re-use from remoting here too?)
|
There is one thing I've done on this direction. If you do a lookup on
HAConnectionFactory, you will have the list updated on the new de-serialized
HAConnectionFactory. I don't know yet how we could update existent instances.
"Valve" functionality to stall any activity on connections when server failover
is occurring.
|
I'm not sure... but I guess we are locking write on failOver. Isn't that enough?
We shall test it anyway.
anonymous wrote : Replaying of delivered messages to the ServerConmsumerEndpoint so the
delivery list can be recreated.
|
What you mean? I didn't understand.
Tim wrote : Anything else?
- Finish implementing the FailOverPolicy (Next node assumes the previous node)
- Establish a relationship between HAConnectionFactories and specific ConnectionFactories.
(In case there is more than one Connection Factory, e.g. HTTP, JMS...)
- Failure on HA at this point is only done when ConnectionListener receives an event,
which is pretty much done only at leasing. We should also change interceptors to take
actions when Exceptions are occuring and take actions such as retry... retry... failOver
- We should have a MAP of failed nodes. (When a node assumes another node)
- The redirect protocol. Are you ready for this node? (What would be a good method name
BTW?)
- Go over the current design on HAConnectionFactories.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3988894#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...