Skip to content

Conversation

@ptupitsyn
Copy link
Contributor

@ptupitsyn ptupitsyn commented Oct 8, 2020

Use Java code to start and stop processes to avoid SIGCHLD conflicts.

Java and .NET both install SIGCHLD handler to deal with child processes. Since Ignite direct-io already uses Java process API, we can't use .NET process API in tests.

@ptupitsyn ptupitsyn self-assigned this Oct 8, 2020
Copy link
Contributor

@isapego isapego left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me.

Comment on lines +49 to +50
if (process != null)
throw new Exception("PlatformProcessUtils can't start more than one process at a time.");
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this a limitation, or do we just not need several processes right now and this was the simpliest implementation?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would be great to return PID and then use it to kill the process. Unfortunately, Process.pid() was only added in Java 9, and we have to be able to run on Java 8.

So yes, this is a simplification - good enough for tests.

@ptupitsyn ptupitsyn merged commit 51fe6de into apache:master Oct 9, 2020
@ptupitsyn ptupitsyn deleted the ignite-13551 branch October 9, 2020 09:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants