Hello!
Try setting IgniteConfiguration.workDirectory to some writable path.
Regards,
--
Ilya Kasnacheev
чт, 11 июн. 2020 г. в 18:58, narges saleh <snarges...@gmail.com>:
> Hi Ilya,
> IGNITE_HOME is /opt/ignite and in ignite-log4j, the log file set to
> <param name="File" value="${IGNITE_HOME}/work/log/ignite.log"/>
> I don't have any issue on the server side.
>
> This is the exception I get on the client side:
>
> Caused by: class org.apache.ignite.IgniteCheckedException: Work directory
> does not exist and cannot be created: /ignite/work
> at
> org.apache.ignite.internal.util.IgniteUtils.workDirectory(IgniteUtils.java:9440)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.initializeConfiguration(IgnitionEx.java:2181)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1697)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1117)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:615)
> at
> org.apache.ignite.internal.jdbc2.JdbcConnection.getIgnite(JdbcConnection.java:311)
> at
> org.apache.ignite.internal.jdbc2.JdbcConnection.<init>(JdbcConnection.java:240)
> ... 39 more
>
> On Thu, Jun 11, 2020 at 10:04 AM Ilya Kasnacheev <
> ilya.kasnach...@gmail.com> wrote:
>
>> Hello!
>>
>> I recommend setting the property workDirectory of IgniteConfiguration
>> class to desired value. And leaving IGNITE_HOME and IGNITE_WORK_DIR not
>> specified.
>>
>> This may still cause exception if your e.g. logging subsystem is
>> configured to use /ignite/work. Need to see the exception.
>>
>> Regards,
>> --
>> Ilya Kasnacheev
>>
>>
>> чт, 11 июн. 2020 г. в 17:55, narges saleh <snarges...@gmail.com>:
>>
>>> Hi All,
>>>
>>> What's the best way to set ignite's work dir on the client side,
>>> considering that the client and server nodes run under different users.
>>> I am setting both IGNITE_HOME and IGNITE_WORK_DIR system variables (on
>>> client), but I am still getting the exception "/ignite/work" cannot be
>>> created.
>>>
>>> thanks.
>>>
>>
