checkstatus create many sessions in short time

[yaoweibin]

checkstatus create many sessions in short time

[yaoweibin]

Could you disable the session creation for the your health check URL?

[seanloook]

those sessions is created every 3 second(interval=3000), not created by my health check URL. My loadbalancer can handle failover well, so I don't want to know the backend servers status until I refresh the healcheck URL.

[seanloook]

Reply to: I know the session is created by the tomcat. Could you disable the tomcat to create the session with the specific health check URL?

I know. I mean there must be a mechanism you check backend tomcats status, such as send a request to tomcat every 3 seconds, I don't know THIS request URL to disable session (NOT my health ckeck URL like http://hostname/nginx_status) .

[seanloook]

In my mind, what's the nginx_upstream_check_module do is that nginx communicat with tomcats throght some way. According to what I see, there must be a request sent erery interval time. My browser can keep the same sessionID for serveral request, but not this healcheck module--one request,one new session in tomcat. It's not about the URL because it has nothing to do with whether I vist the url to see status.

[seanloook]

this situation will appear when I "curl http://localhost:80/", every time I get a new sessionID, but not in my browser. Coud you explain it for me? 谢谢! （还是习惯用中文。。）

[seanloook]

你好，我看见有个Closed Issue说upstream_check模块跟jvm_route不兼容。我没试过jvm_route，但我看它好像与nginx_sticky_module模块实现的功能是一样的，我在ngnix_sticky_module里面看到这么一句话“Warnings: sticky module does not work with the nginx_http_upstream_check_module.”, is there any difference? And this healthcheck_nginx_upstreams module...pretty confused. Thanks!

[yaoweibin]

都是需要patch结合，使用这个patch就可以用sticky模块：https://github.com/yaoweibin/nginx_upstream_check_module/blob/master/nginx-sticky-module.patch

[yaoweibin]

Now the upstream check module can support keepalive connection