Dmitriy,

Ok, I’ll take care of the docs.

—
Denis

> On Oct 5, 2017, at 9:41 AM, Dmitry Pavlov <dpavlov....@gmail.com> wrote:
> 
> Hi Denis,
> 
> Thank you for providing access.
> 
> Unfortunately I will not be able to start description of this change before
> 16 Oct. Is it OK?
> 
> Alternatively can someone from the community pick up this change? All
> details, algorithm and code references are provided in
> https://cwiki.apache.org/confluence/display/IGNITE/Ignite+Persistent+Store+-+under+the+hood#IgnitePersistentStore-underthehood-Subfoldersgeneration
> (in expandable section).
> 
> Sincerely,
> Dmitriy Pavlov
> 
> чт, 5 окт. 2017 г. в 1:01, Denis Magda <dma...@apache.org>:
> 
>> Hi Dmitriy,
>> 
>> Good improvement and right in time, thanks!
>> 
>> Thinking of a high level documentation, the user has to know:
>> * how to start nodes from different clusters on a single box. They need to
>> specify unique paths for storage files.
>> * how to tackle the error described as Option 3 on wiki.
>> * how to bind storage files to specific node instance (consistent ID
>> option).
>> 
>> Could you put all this together under this doc section?
>> 
>> https://apacheignite.readme.io/v2.2/docs/ignite-persistence-23#section-configuration
>> <
>> https://apacheignite.readme.io/v2.2/docs/ignite-persistence-23#section-configuration
>>> 
>> 
>> That page is hidden and will be released along with 2.3. Provided you with
>> required permissions.
>> 
>> Please send me for review once you’re ready.
>> 
>> —
>> Denis
>> 
>>> On Oct 4, 2017, at 10:26 AM, Dmitry Pavlov <dpavlov....@gmail.com>
>> wrote:
>>> 
>>> Hi Igniters,
>>> 
>>> Issue for improve persistent store paths
>>> https://issues.apache.org/jira/browse/IGNITE-6285 has been resolved.
>> Thanks
>>> to Alexey G. and Yakov for review.
>>> 
>>> Details of change are available in wiki
>>> 
>> https://cwiki.apache.org/confluence/display/IGNITE/Ignite+Persistent+Store+-+under+the+hood#IgnitePersistentStore-underthehood-Foldersstructure
>>> 
>>> Ignite has now new style persistent store sub folder naming. Internal
>>> folder names are based on randomly generated consistent ID.
>>> 
>>> Existing instances will be running with existing folders. Same for
>> manually
>>> set consistent ID, in this case configuration parameter is used.
>>> 
>>> Sincerely,
>>> Dmitriy Pavlov
>> 
>> 

Reply via email to