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

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.3
• Fix Version/s: 2.5
• Assignee: Sergey Chugunov
• Reporter: Evgeny Stanilovsky
• Created: 20/Dec/17 05:49
• Updated: 10/May/18 16:04
• Resolved: 10/May/18 16:04

Description

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

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)