| http service in gyrex cluster [message #1716512] |
Fri, 04 December 2015 13:22  |
|
Finally, I decide to move standalone to cluster in production environment, it is more stable than standalone application.
I have done a simple test for cluster environment before deploying to production. There are two gyrex servers A (192.168.31.151) and B (192.168.31.156), and I have setup the http connectors on port 8080, and then set the tags for these two servers. A has three tags (webserver, scheduler, worker), and B has only one tag (webserver).
Then I try to access the web service through following two urls:
http://192.168.31.151:8080/service/xxx/yyy/zzz
http://192.168.31.156:8080/service/xxx/yyy/zzz
But, the first one cannot access with err connection refused, while the second one can access successfully.
Is there any mistake with my configuration?
Thanks
Study every day, and love every day!
|
|
|
|
| Re: http service in gyrex cluster [message #1716577 is a reply to message #1716528] |
Sat, 05 December 2015 10:25  |
|
Hi Gunnar,
I'm running a seperate zookeeper cluster.
Yeah, after restarting the gyrex node, everything is ok now.
Then, I reset everything and want to re-produce the problem, and then found that after setup the http service, the nodes need to be restarted.
Thank you.
Study every day, and love every day!
|
|
|
| Re: http service in gyrex cluster [message #1719261 is a reply to message #1716577] |
Wed, 06 January 2016 16:21 |
|
On 2015-12-05 10:25:52 +0000, Sean Zhang said:
> Then, I reset everything and want to re-produce the problem, and then
> found that after setup the http service, the nodes need to be restarted.
That's probably a lack of dynamics in the implementation. It's not
intended to be that way. Sometimes we just haven't had the time to
finish/polish all the dynamics. In such a case, a node restart helps.
-Gunnar
--
Gunnar Wagenknecht
gunnar@xxxxxxxx
|
|
|
Powered by
FUDForum. Page generated in 0.02301 seconds
] 
Search
Help
Register
Login
Home
