[IGNITE-7070] Ignite PDS compatibilty framework: implement configurable classpath, JVM options, node startup timeout

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 2.4
• Component/s: persistence
• Assignee: Dmitry Pavlov
• Reporter: Dmitry Pavlov
• Created: 29/Nov/17 12:54
• Updated: 30/Nov/17 13:26
• Resolved: 30/Nov/17 13:24

Description

Ignite PDS compatibilty framework filters out classpath from current test classpath.
It involves only ignite-core and there is no warning about it in pom.xml
During extending scope of testing it is requied to extend CP with ignite-indexing, spring etc.

It is required to add ability to configure filtered out classpath element by test.
Additional fixes:

• dump classpath in case multi-jvm mode startup failed
• dump classpath in case multi-jvm mode startup hangs
• make node join timeout configurable (post startup may require considerable amount of time
• wait detached node not in assert (assert with side effect)

Fixes are prepared in
https://github.com/apache/ignite/pull/3106

Issue Links

• is duplicated by: IGNITE-7069 Ignite PDS compatibilty framework: implement configurable classpath, JVM options, node startup timeout
• links to: GitHub Pull Request #3106