[JBossCache] - Re: Buddy replication behavior
by puggelli
Hello again,
the point 1) is clear, but I have some doubts about the point 2).
Let me divide the data stored in a cache in primary and backup. When a node die, to avoid network storm, the primary data is not automatically gravitated. If so, why the automatic gravitation is done for the backup ?
In fact in the example that I posted, the primary data contained in the node C or cache 2 (the node three) is automatically copied in the backup data of the node B (or cache 1).
And then, when a node die, the cluster is not 'homogeneous' anymore. Some data has a backup and some other don't. In this situation, without a specific application code that force the gravitation, another fault can cause information loss.
thanks and regards
gianluca
--
Gianluca Puggelli
skype:pugg1138
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4003415#4003415
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4003415
19 years, 3 months
[Clustering/JBoss] - Re: JBoss5.0.0.Beta1 multiple instances error
by JerryGauth
I've used the separate ports approach (e.g., the binding file) successfully in the past but stopped because I would frequently encounter problems which required me to make changes to the port configurations.
For developers at least, using the IP address binding approach is generally simpler. If you have multiple IP addresses on your machine, you can simply bind each server instance to one of your IP addresses when you start the server (e.g., run.bat -c server1 -b 192.168.1.101)
If you have a laptop with a wired connection and a wireless connection, you can use their IP addresses as the two IP addresses for a two node network. If you only have a single connection, you should be able to follow your OS's instructions for enabling a loopback address to be used as the second IP address. Presumably you can configure a three node network on your machine using wired/wireless/loopback but I haven't tried this.
If you need to use the binding file and it always fails on port 8080, try debugging the problem by modifying the use of port 8080 to another port in the file. If the problem manifests itself on the new port, then you know that the override entries in the file aren't correct. This could be because you didn't specify the correct node name or it could be because the file overrides themselves are wrong. If the problem still shows up on port 8080, then look for uses of port 8080 in your server's service files and try changing them there. This would indicate that either you haven't configured the override file process correctly or else the use of port 8080 has been changed and the format in the bindings file is no longer adequate to provide the override.
I've had far fewer problems since I started using the IP address approach. The one caveat there is that you need to be aware of IP address changes if your machine has dynamic addresses. In my case at least, this is rarely a problem.
Hope this helps.
Jerry
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4003400#4003400
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4003400
19 years, 3 months