ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexei Scherbakov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-2942) Use getOrStart in IgniteContext instead of current try-catch structure
Date Fri, 15 Apr 2016 09:56:25 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-2942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15242722#comment-15242722

Alexei Scherbakov commented on IGNITE-2942:

The task is about to be finished. Waiting for TC results right now.

Ignite context currently uses method getOrStart which was added as requested in IGNITE-2941.
In addition to that, I found some other issues.

1) JavaIgniteContext had no option to be used in embedded mode.
Flag "client" was not available in the constructor. Added it.

2) Added option to stop all Ignite instances from the driver program.
IgniteContext.close(shutdownIgniteOnWorkers: Boolean = false)
Has no effect on workers

3) There was no test for embedded mode Spark integration.
Added JavaEmbeddedIgniteRDDSelfTest.
The main idea of test is to start Spark in local workers mode, run Ignite on
worker threads ( each thread uses it's own grid instance ), do some grid operations,
shutdown Ignite on workers and the spark context afterwards.

> Use getOrStart in IgniteContext instead of current try-catch structure
> ----------------------------------------------------------------------
>                 Key: IGNITE-2942
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2942
>             Project: Ignite
>          Issue Type: Bug
>          Components: Ignite RDD
>    Affects Versions: 1.5.0.final
>            Reporter: Alexey Goncharuk
>            Assignee: Alexei Scherbakov
> IgniteContext initialization code will throw an IgniteIllegalStateException in a case
when configuration is invalid: start() will throw an exception, exception is caught and, assuming
that Ignite instance is already started, Ignition.ignite() is called again.
> Need to use getOrStart() method instead.

This message was sent by Atlassian JIRA

View raw message