[
https://issues.apache.org/jira/browse/THRIFT-4515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James E. King, III updated THRIFT-4515:
---------------------------------------
Description:
The cross test suite kills the server process after the client is done, see
test/crosstest/run.py:_scoped, the process is killed. In the C++ TestServer
code at the end of main it sits in a TIGHT while loop unnecessarily causing CPU
usage and slowing down the system.
There should be a signal (like SIGINT) that each server waits for, and on
receiving that signal stops the thrift server cleanly. This ensures we
properly test teardown.
was:
The cross test suite kills the server process after the client is done, see
test/crosstest/run.py:_scoped, the process is killed. In the C++ TestServer
code at the end of main it sits in a TIGHT while loop unnecessarily causing CPU
usage and slowing down the system.
There should be a signal (like SIGUSR1) that each server waits for, and on
receiving that signal stops the thrift server cleanly.
> Gracefully shutdown cross-test servers to fully test teardown
> -------------------------------------------------------------
>
> Key: THRIFT-4515
> URL: https://issues.apache.org/jira/browse/THRIFT-4515
> Project: Thrift
> Issue Type: Improvement
> Components: Test Suite
> Affects Versions: 0.11.0
> Reporter: James E. King, III
> Assignee: James E. King, III
> Priority: Major
>
> The cross test suite kills the server process after the client is done, see
> test/crosstest/run.py:_scoped, the process is killed. In the C++ TestServer
> code at the end of main it sits in a TIGHT while loop unnecessarily causing
> CPU usage and slowing down the system.
> There should be a signal (like SIGINT) that each server waits for, and on
> receiving that signal stops the thrift server cleanly. This ensures we
> properly test teardown.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
