[jira] [Created] (IGNITE-7252) No need to initialize BinaryMetadata working directory for client mode.

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Created] (IGNITE-7252) No need to initialize BinaryMetadata working directory for client mode.

Anton Vinogradov (Jira)
Stanilovsky Evgeny created IGNITE-7252:
------------------------------------------

             Summary: No need to initialize BinaryMetadata working directory for client mode.
                 Key: IGNITE-7252
                 URL: https://issues.apache.org/jira/browse/IGNITE-7252
             Project: Ignite
          Issue Type: Improvement
    Affects Versions: 2.3
            Reporter: Stanilovsky Evgeny
            Assignee: Sergey Chugunov
            Priority: Minor
             Fix For: 2.4


While node starts with client mode and pds enabled, it still tries to get access to lfs working directory in BinaryMetadataFileStore if no access granted it will fail with exception

{noformat}
Caused by: class org.apache.ignite.IgniteCheckedException: Cannot write to directory: /path/to/lfs/grid_name
 at org.apache.ignite.internal.util.IgniteUtils.resolveWorkDirectory(IgniteUtils.java:9128)
 at org.apache.ignite.internal.processors.cache.persistence.filename.PdsConsistentIdProcessor.resolvePersistentStoreBasePath(PdsConsistentIdProcessor.java:453)
 at org.apache.ignite.internal.processors.cache.persistence.filename.PdsConsistentIdProcessor.prepareNewSettings(PdsConsistentIdProcessor.java:157)
 at org.apache.ignite.internal.processors.cache.persistence.filename.PdsConsistentIdProcessor.resolveFolders(PdsConsistentIdProcessor.java:137)
 at org.apache.ignite.internal.processors.cache.binary.BinaryMetadataFileStore.<init>(BinaryMetadataFileStore.java:73)
 at org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.start(CacheObjectBinaryProcessorImpl.java:160)
 at org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1897)
{noformat}




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