ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmitriy Pavlov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-7069) Ignite PDS compatibilty framework: implement configurable classpath, JVM options, node startup timeout
Date Wed, 29 Nov 2017 13:19:00 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-7069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dmitriy Pavlov updated IGNITE-7069:
-----------------------------------
    Fix Version/s:     (was: 2.4)

> Ignite PDS compatibilty framework: implement configurable classpath, JVM options, node
startup timeout
> ------------------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-7069
>                 URL: https://issues.apache.org/jira/browse/IGNITE-7069
>             Project: Ignite
>          Issue Type: Bug
>          Components: persistence
>            Reporter: Dmitriy Pavlov
>            Assignee: Dmitriy Pavlov
>            Priority: Critical
>
> 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



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message