When using the evaluating and testing, I was trying to manually take a server out of rotation, as documented in the example at http://siag.nu/hypermail/pen/0038.html
Using for example :
penctl localhost:8888 server 0 blacklist 300
The server was not being taking out of rotation. As far as I could tell, try_server(), which should update server[x].status was not being called in the DSR mode. In additionally, in pen.c:do_cmd(), when running penctl socket server X ... for any of the servers settings the DSR hashing table is never invalidated server_alg ^= ALG_HASH_VALID
Also, there was no regular checking for for the blacklist timeout. The logical place seemed to be dsr.c:dsr_arp(). Added one new global last_hash_rebuild, and using the blacklist_time global as the a forced periodic server table rehashing, and is of course forced when penctl updates a server.
Added some more debugging to help follow the logic and verify. I have not verified the do_cmd() outside of DSR mode.
When using the evaluating and testing, I was trying to manually take a server out of rotation, as documented in the example at http://siag.nu/hypermail/pen/0038.html
Using for example :
penctl localhost:8888 server 0 blacklist 300The server was not being taking out of rotation. As far as I could tell, try_server(), which should update server[x].status was not being called in the DSR mode. In additionally, in pen.c:do_cmd(), when running
penctl socket server X ...for any of the servers settings the DSR hashing table is never invalidatedserver_alg ^= ALG_HASH_VALIDAlso, there was no regular checking for for the blacklist timeout. The logical place seemed to be dsr.c:dsr_arp(). Added one new global last_hash_rebuild, and using the blacklist_time global as the a forced periodic server table rehashing, and is of course forced when penctl updates a server.
Added some more debugging to help follow the logic and verify. I have not verified the do_cmd() outside of DSR mode.