Raymond, I think most of Ignite users run on ipv4. So, issues with v6 in
this case are hardly possible =)
--Yakov
Setrakyan
*Subject:* Re: Specifying location of persistent storage location
Ignite.NET does not have IgniteConfiguration.ConsistentId, here is the
ticket:
https://issues.apache.org/jira/browse/IGNITE-6249
Workaround is to use Spring XML for that particular property (keep
everything else in .NET
,
Raymond
*From:* Yakov Zhdanov [mailto:yzhda...@apache.org]
*Sent:* Tuesday, September 5, 2017 8:51 PM
*To:* user@ignite.apache.org; d...@ignite.apache.org
*Cc:* Dmitriy Setrakyan
*Subject:* Re: Specifying location of persistent storage location
+ dev
Pavel Tupitsin, can you please check that
; cause
> > problems when a node restarts and decides the location of its data is
> > different.
> >
> >
> >
> > Do you know how GridGain manage this in their enterprise deployments
> using
> > persistence?
> >
> >
> >
> > Thanks,
> >
decides the location of its data is
> different.
>
>
>
> Do you know how GridGain manage this in their enterprise deployments using
> persistence?
>
>
>
> Thanks,
> Raymond.
>
>
>
> *From:* Dmitriy Setrakyan [mailto:dsetrak...@apache.org]
> *Sent
:* Re: Specifying location of persistent storage location
On Mon, Sep 4, 2017 at 8:40 PM, Raymond Wilson
wrote:
Thanks.
I get the utility of specifying the network address to bind to; I’m not
convinced using that to derive the name of the internal data store is a
good idea! J
For instance
t you may wish to look at the
3rd party solutions, e.g. the one provided by GridGain -
https://docs.gridgain.com/docs/data-snapshots
>
>
> *From:* Dmitriy Setrakyan [mailto:dsetrak...@apache.org]
> *Sent:* Tuesday, September 5, 2017 3:09 PM
> *To:* user
>
> *Subject:*
LocalHost or 120.0.0.1
to ensure the folder name is always essentially local host?
*From:* Dmitriy Setrakyan [mailto:dsetrak...@apache.org]
*Sent:* Tuesday, September 5, 2017 3:09 PM
*To:* user
*Subject:* Re: Specifying location of persistent storage location
On Mon, Sep 4, 2017 at 6:07 PM
sers explicitly specify which network address to bind to,
just like you did. This helps avoid any kind of magic in production.
>
>
> Thanks,
> Raymond.
>
>
>
> *From:* Dmitriy Setrakyan [mailto:dsetrak...@apache.org]
> *Sent:* Tuesday, September 5, 2017 11:41 AM
>
&g
*To:* user
*Cc:* Raymond Wilson
*Subject:* Re: Specifying location of persistent storage location
On Mon, Sep 4, 2017 at 4:28 PM, Raymond Wilson
wrote:
Hi,
It’s possible this could cause change in the folder name, though I do not
think this is an issue in my case. Below are three
y suggestions will ensure that you explicitly bind to the
same address every time.
>
> Thanks,
>
> Raymond.
>
>
>
> *From:* Dmitriy Setrakyan [mailto:dsetrak...@apache.org]
> *Sent:* Tuesday, September 5, 2017 11:17 AM
> *To:* user
> *Cc:* Raymond Wilson
> *Subject:
:* Dmitriy Setrakyan [mailto:dsetrak...@apache.org]
*Sent:* Tuesday, September 5, 2017 11:17 AM
*To:* user
*Cc:* Raymond Wilson
*Subject:* Re: Specifying location of persistent storage location
On Mon, Sep 4, 2017 at 3:37 PM, Raymond Wilson
wrote:
Hi,
I definitely have not had more
On Mon, Sep 4, 2017 at 3:37 PM, Raymond Wilson
wrote:
> Hi,
>
>
>
> I definitely have not had more than one server node running at the same
> time (though there have been more than one client node running on the same
> machine).
>
>
>
> I suspect what is happening is that one or more of the netwo
: Specifying location of persistent storage location
Hi Raymond,
Sorry for the initial confusion. The consistent ID is the combination of
the local IP and port. You DO NOT need to do anything special to configure
it.
If you had different folders created under the work folder, you probably
had more
@gmail.com]
> *Sent:* Tuesday, September 5, 2017 9:24 AM
>
> *To:* user@ignite.apache.org
> *Subject:* Re: Specifying location of persistent storage location
>
>
>
> Hi Ramond,
>
>
>
> Node.Consistent ID by default is the sorted set of local IP addresses and
configure this?
Thanks,
Raymond.
*From:* Dmitry Pavlov [mailto:dpavlov@gmail.com]
*Sent:* Tuesday, September 5, 2017 9:24 AM
*To:* user@ignite.apache.org
*Subject:* Re: Specifying location of persistent storage location
Hi Ramond,
Node.Consistent ID by default is the sorted set of
getter for the consistent ID, I need to be able to set it.
>
>
>
> *From:* Raymond Wilson [mailto:raymond_wil...@trimble.com]
> *Sent:* Tuesday, September 5, 2017 9:06 AM
> *To:* 'user@ignite.apache.org'
> *Subject:* RE: Specifying location of persistent storage
, September 5, 2017 9:06 AM
*To:* 'user@ignite.apache.org'
*Subject:* RE: Specifying location of persistent storage location
Apologies if this is a silly question, but I’m struggling to see how to get
at the consistentID member of ClusterNode on the C# client.
If I look at IClusterNode
:* Raymond Wilson [mailto:raymond_wil...@trimble.com]
*Sent:* Tuesday, September 5, 2017 6:04 AM
*To:* user@ignite.apache.org
*Subject:* Re: Specifying location of persistent storage location
Thank you Dmitry!
Sent from my iPhone
On 5/09/2017, at 1:12 AM, Dmitry Pavlov wrote:
Hi Raymond
Thank you Dmitry!
Sent from my iPhone
> On 5/09/2017, at 1:12 AM, Dmitry Pavlov wrote:
>
> Hi Raymond,
>
> Ignite Persistent Store includes consistentID parameter of cluster node into
> folders name. It is required because there is possible that 2 nodes would be
> started at same physical m
Hi Raymond,
Ignite Persistent Store includes consistentID parameter of cluster node
into folders name. It is required because there is possible that 2 nodes
would be started at same physical machine.
Consistency of using same folder each time is provided by this property,
ClusterNode.consistentID
Hi,
I’m running a POC looking at the Ignite Persistent Store feature.
I have added a section to the configuration for the Ignite grid as follows:
cfg.PersistentStoreConfiguration = new
PersistentStoreConfiguration()
{
PersistentStorePath = Persiste
22 matches
Mail list logo
