You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2016/08/04 06:25:20 UTC
[jira] [Commented] (IGNITE-3597) IgniteConfiguration.igniteWorkDir
has no effect
[ https://issues.apache.org/jira/browse/IGNITE-3597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15407264#comment-15407264 ]
Vladimir Ozerov commented on IGNITE-3597:
-----------------------------------------
Sorry for missing description, I forgot to move it here from dev list discussion. Essentially, we need to do the following:
1) When Ignite is about to start, we must resolve it's work directory and put it to {{IgniteConfiguration.workDirectory}} field.
Relevant code pieces: {{IgnitionEx$IgniteNamedInstance.intializeConfiguration}}.
Note that we should not put anything to static variables.
2) Rework all places (I see 18) where {{IgniteUtils.resolveWorkDirectory}} is called. Now it should accept three arguments:
- instance's work dir you set on the step 1;
- path;
- "delIfExists" flag.
The main challenge here is to get the first argument in all the places where {{IgniteUtils.resolveWorkDirectory}} is called.
> IgniteConfiguration.igniteWorkDir has no effect
> -----------------------------------------------
>
> Key: IGNITE-3597
> URL: https://issues.apache.org/jira/browse/IGNITE-3597
> Project: Ignite
> Issue Type: Bug
> Components: general
> Affects Versions: 1.5.0.final
> Reporter: Pavel Tupitsyn
> Assignee: Andrew Mashenkov
> Priority: Critical
> Fix For: 1.8
>
>
> U.setWorkDirectory method ensures that work dir is set only once.
> If there are multiple nodes in a process, or a node is stopped and then started, IgniteConfiguration.igniteWorkDir is ignored.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)