[jira] [Updated] (PHOENIX-5454) Phoenix scripts start foreground java processes as child processes
[ https://issues.apache.org/jira/browse/PHOENIX-5454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth updated PHOENIX-5454: - Component/s: queryserver core > Phoenix scripts start foreground java processes as child processes > -- > > Key: PHOENIX-5454 > URL: https://issues.apache.org/jira/browse/PHOENIX-5454 > Project: Phoenix > Issue Type: Improvement > Components: core, queryserver >Affects Versions: 4.15.0, 5.1.0 >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Minor > Fix For: 5.1.0, queryserver-6.0.0, 4.16.0 > > Attachments: PHOENIX-5454.master.v1.patch, > PHOENIX-5454.master.v2.patch > > Time Spent: 40m > Remaining Estimate: 0h > > Currently the phoenix scripts in python start the java process via > subprocess.call() or subprocess.popen() even when the java process has to run > in the foreground, and there is no cleanup required. > I propose that in these cases, we start java via os.exec*(). This has the > following advantages: > * There is no python process idling waiting for the java process to end, > reducing process count and memory consumption > * Signal handling is simplified (signals sent to the starting script are > received by the java process started) > * Return code handling is simplified (no need to check for and return error > codes from java in the startup script) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5454) Phoenix scripts start foreground java processes as child processes
[ https://issues.apache.org/jira/browse/PHOENIX-5454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth updated PHOENIX-5454: - Fix Version/s: queryserver-1.0.0 > Phoenix scripts start foreground java processes as child processes > -- > > Key: PHOENIX-5454 > URL: https://issues.apache.org/jira/browse/PHOENIX-5454 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 4.15.0, 5.1.0 >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Minor > Fix For: 5.1.0, queryserver-1.0.0, 4.16.0 > > Attachments: PHOENIX-5454.master.v1.patch, > PHOENIX-5454.master.v2.patch > > Time Spent: 40m > Remaining Estimate: 0h > > Currently the phoenix scripts in python start the java process via > subprocess.call() or subprocess.popen() even when the java process has to run > in the foreground, and there is no cleanup required. > I propose that in these cases, we start java via os.exec*(). This has the > following advantages: > * There is no python process idling waiting for the java process to end, > reducing process count and memory consumption > * Signal handling is simplified (signals sent to the starting script are > received by the java process started) > * Return code handling is simplified (no need to check for and return error > codes from java in the startup script) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5454) Phoenix scripts start foreground java processes as child processes
[ https://issues.apache.org/jira/browse/PHOENIX-5454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth updated PHOENIX-5454: - Fix Version/s: 4.16.0 Affects Version/s: 4.15.0 Backported to the 4.x branches as well, in case we stick with python. > Phoenix scripts start foreground java processes as child processes > -- > > Key: PHOENIX-5454 > URL: https://issues.apache.org/jira/browse/PHOENIX-5454 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 4.15.0, 5.1.0 >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Minor > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-5454.master.v1.patch, > PHOENIX-5454.master.v2.patch > > Time Spent: 40m > Remaining Estimate: 0h > > Currently the phoenix scripts in python start the java process via > subprocess.call() or subprocess.popen() even when the java process has to run > in the foreground, and there is no cleanup required. > I propose that in these cases, we start java via os.exec*(). This has the > following advantages: > * There is no python process idling waiting for the java process to end, > reducing process count and memory consumption > * Signal handling is simplified (signals sent to the starting script are > received by the java process started) > * Return code handling is simplified (no need to check for and return error > codes from java in the startup script) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5454) Phoenix scripts start foreground java processes as child processes
[ https://issues.apache.org/jira/browse/PHOENIX-5454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] István Tóth updated PHOENIX-5454: - Attachment: PHOENIX-5454.master.v2.patch > Phoenix scripts start foreground java processes as child processes > -- > > Key: PHOENIX-5454 > URL: https://issues.apache.org/jira/browse/PHOENIX-5454 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 5.1.0 >Reporter: István Tóth >Assignee: István Tóth >Priority: Minor > Attachments: PHOENIX-5454.master.v1.patch, > PHOENIX-5454.master.v2.patch > > Time Spent: 20m > Remaining Estimate: 0h > > Currently the phoenix scripts in python start the java process via > subprocess.call() or subprocess.popen() even when the java process has to run > in the foreground, and there is no cleanup required. > I propose that in these cases, we start java via os.exec*(). This has the > following advantages: > * There is no python process idling waiting for the java process to end, > reducing process count and memory consumption > * Signal handling is simplified (signals sent to the starting script are > received by the java process started) > * Return code handling is simplified (no need to check for and return error > codes from java in the startup script) -- This message was sent by Atlassian Jira (v8.3.2#803003)
