https://bz.apache.org/bugzilla/show_bug.cgi?id=60553
Bug ID: 60553
Summary: After segmentation fault balancer do not work properly
Product: Apache httpd-2
Version: 2.4.25
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: mod_proxy_hcheck
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
Created attachment 34593
--> https://bz.apache.org/bugzilla/attachment.cgi?id=34593&action=edit
Three files with coredump and error log
S.O Version:
Red Hat Enterprise Linux Server release 7.2 (Maipo)
uname -a
Linux ejld1132.ejgvdns 3.10.0-327.13.1.el7.x86_64 #1 SMP Mon Feb 29 13:22:02
EST 2016 x86_64 x86_64 x86_64 GNU/Linux
Apache httpd version:
/opt/apache2/bin/httpd -v
Server version: Apache/2.4.25 (Unix)
Server built: Jan 4 2017 09:34:36
/opt/apache2/bin/httpd -l
Compiled in modules:
core.c
mod_so.c
http_core.c
worker.c
-----------------------------------------------------------
Problem:
When we run apache httpd with a balancer configured
<Proxy balancer://cluster_namenode>
BalancerMember http://ejld1132.ejgvdns:8170 hcmethod=GET hcinterval=5
hcpasses=1 hcfails=1 hcuri=/webhdfs/v1/data?op=GETFILESTATUS
BalancerMember http://ejld1131.ejgvdns:8170 hcmethod=GET hcinterval=5
hcpasses=1 hcfails=1 hcuri=/webhdfs/v1/data?op=GETFILESTATUS
</Proxy>
We are using this balancer to deal with the hdfs namenode high availability.
Usually ejld1131 is the active one, and the other is in standby mode. So
requests to ejld1132 responds with 403 code and is marked as DISABLED. Ejld1131
responds with 200 code.
it starts working properly. We have make tests with jmeter with good results
but sometimes "Segmentation Fault" alert appears on error log.
Anyway it continues working but not everytime. After segmentation fault
sometimes mod_proxy_hcheck doesn't find defined workers properly and requests
don't work. After another "Segmentation Fault" workers are restarted again and
it starts working well.
Fragments of error log with this problem located are attached.
Thanks
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
