RE: Loosing cache data when persistence is enabled

[Zhenya Stanilovsky]

If nodes are partially offline and still in baseline, as was mentioned earlier 
— you really can loose your data
check for example :
[1  https://apacheignite.readme.io/docs/partition-loss-policies ]
[2]  https://www.gridgain.com/docs/latest/developers-guide/partition-loss-policy
 
if all nodes are online you can`t obtain such case, i hope.  
>
>
>--- Forwarded message ---
>From: "BEELA GAYATRI" < beela.gaya...@tcs.com >
>To: "user@ignite.apache.org" < user@ignite.apache.org >, VincentCE < 
>v...@cephei.com >
>Cc:
>Subject: RE: Loosing cache data when persistence is enabled
>Date: Thu, 10 Dec 2020 16:54:57 +0300
> 
>Hi,
> 
>  The nodes are  not getting  out of  Baseline topology. They are showing 
>offline , after restart of the nodes data is getting deleted from persistence 
>folders(some time data not getting deleted and some times getting deleted). 
>PFA web console
> 
>Sent from  Mail for Windows 10
> 
>From:  VincentCE
>Sent:  Thursday, December 10, 2020 6:10 PM
>To:  user@ignite.apache.org
>Subject:  Re: Loosing cache data when persistence is enabled
> 
>"External email. Open with Caution"
>
>Hi Beela,
>
>could the root cause be that you had changes in your baseline topology when
>you saw the data loss? According to my understanding and the answer I got on
>my question
>http://apache-ignite-users.70518.x6.nabble.com/Ignite-persistence-Data-of-node-is-lost-after-being-excluded-from-baseline-topology-td34675.html
>some weeks ago the data of nodes that got excluded from the baseline
>topology will be deleted for consistency reasons.
>
>This is just an immediate guess from my side, I did not have a look into
>your attachments so far.
>
>Best,
>Vincent
>
>
>
>--
>Sent from:  http://apache-ignite-users.70518.x6.nabble.com/
> 
>=-=-=
>Notice: The information contained in this e-mail
>message and/or attachments to it may contain
>confidential or privileged information. If you are
>not the intended recipient, any dissemination, use,
>review, distribution, printing or copying of the
>information contained in this e-mail message
>and/or attachments to it are strictly prohibited. If
>you have received this communication in error,
>please notify us by reply e-mail or telephone and
>immediately and permanently delete the message
>and any attachments. Thank you
> 
>
>  
 
 
 
 

   
--
 
 
 

Re: C#/.NET: Possible to assign different nodes different roles?

[Raymond Wilson]

It is possible to do this via node filters or attributes.

We use differentiated fleets of client nodes that interact with server
nodes to pull data processed at the server node level and then further
process it at a cluster level. We assign a 'ROLE' attribute to each node
and then filter those nodes from the Ignite cluster to form the compute
projection to Apply() or Broadcast() a request to.

We do this in an auto scaled Kubernetes deployment on AWS.

Cheers,
Raymond.


On Fri, Dec 11, 2020 at 9:37 AM akorensh  wrote:

> Hi,
>   You could use node filters:
> https://ignite.apache.org/docs/latest/services/services#node-filter
>   example of node filter:
>
> https://github.com/apache/ignite/blob/master/examples/src/main/java/org/apache/ignite/examples/computegrid/ComputeFibonacciContinuationExample.java
>
>   In general, it is not recommended to segregate nodes based on individual
> responsibility, as it negates the main advantage of automatic scaling,
> failover and backup.
>
> see here:
>
> https://ignite.apache.org/docs/latest/distributed-computing/distributed-computing
>
> Thanks, Alex
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>


-- 

Raymond Wilson
Solution Architect, Civil Construction Software Systems (CCSS)
11 Birmingham Drive | Christchurch, New Zealand
+64-21-2013317 Mobile
raymond_wil...@trimble.com

Re: C#/.NET: Possible to assign different nodes different roles?

[akorensh]

Hi,
  You could use node filters:
https://ignite.apache.org/docs/latest/services/services#node-filter
  example of node filter:
https://github.com/apache/ignite/blob/master/examples/src/main/java/org/apache/ignite/examples/computegrid/ComputeFibonacciContinuationExample.java

  In general, it is not recommended to segregate nodes based on individual
responsibility, as it negates the main advantage of automatic scaling,
failover and backup. 

see here:
https://ignite.apache.org/docs/latest/distributed-computing/distributed-computing

Thanks, Alex



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: C#/.NET: Possible to assign different nodes different roles?

[adumalagan]

 



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

streaming behaviour with streamingPerNodeBufferSize parameter

[shivakumar]

Hi 
I'm trying to do SQL stream to load data to ignite cluster from my program
(insert sql with streaming set to ON)
My program connects to ignite over JDBC using
org.apache.ignite.IgniteJdbcThinDriver driver (Thin driver)
when i start my application with very small records rate then i don't see
records immediately inserted into my Ignite table but I'm able to see after
inserting few records(>10K records) are pushed or when i close the JDBC
connection.
when I searched about streaming in Ignite document, it says there is a
parameter streamingPerNodeBufferSize with default value set to 1024.
Is this parameter applicable in my scenario with JdbcThinDriver ?
If it is applicable what is 1024 ? Is it 1024 KB(1MB)  ??

Ref:
https://apacheignite-sql.readme.io/v2.5/docs/jdbc-client-driver#streaming-mode


Regards,
Shiva



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Client App Object Allocation Rate

[ssansoy]

Hi did you get a response for this out of interest? also is there a ticket we
can follow? We really need to understand this - and ideally turn it off



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

C#/.NET: Possible to assign different nodes different roles?

[adumalagan]

Hello,
I was assigned a POC where a cluster should not have a single point of
failure -- more specifically, each node should be assigned a different role.
This means that loading the cache, querying, storage, etc. would be seen as
their own individual roles and therefore kept separate, hosting on different
ports. 
For example, a node would be assigned the role of querying the cache;
ideally, a port would be set up so that a client would connect to that port. 

I was just wondering if (1) this was possible, and (2) if possible, how
would I go about it? 

Right now, I have  this XML file
  
where I start a cluster from a remote machine; I have a  one C# project
  
that connects to the cluster, creates a cache, and loads entries from an
underlying RDBMS. Additionally, I have   another C# project
  
that connects a thin client to the cluster and queries the cache once
loaded. 
If I were to implement nodes operating separately with their own roles,
would I need to have different XML files with the same [remoteHost] but
different ports under the addresses property for each XML file? (i.e. XML
file #1 has [remoteHost], [remoteHost]:10800; XML file #2 has [remoteHost],
[remoteHost]:47500..47509).




--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Unable to free disk space after keys are removed in ignite 2.7.0

[VeenaMithare]

Hi Ilya,

I have a question related to this : 
>>Then, WAL will usually only grow and db/ will grow too, they will not
shrink from the deletion of data from caches. Dropping a cache will free
space.

>>This is tolerable because modern server instances are usually
single-purpose. You expect an instance's storage to be used for Ignite data
only and the amount of data is expected to be stable not grow monotonously.

We store audit data for our cache modifications. And audit data will grow
monotonously over a period of time. What is the best way of housekeeping
audit records ?

regards,
Veena.





--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Regarding Partition Map exchange Triggers

[VeenaMithare]

Hi ,


I can see the triggers for PME initiation here :
https://cwiki.apache.org/confluence/display/IGNITE/%28Partition+Map%29+Exchange+-+under+the+hood

Triggers
Events which causes exchange

Topology events:

Node Join (EVT_NODE_JOINED) - new node discovered and joined topology
(exchange is done after a node is included into the ring). This event
doesn't trigger the PME if a thick client connects the cluster and an Ignite
version is 2.8 or later.
*/-- This means in ignite 2.8 or higher, this is triggered only if nodes
that participate in the baseline topology are added ?/*
Node Left (EVT_NODE_LEFT) - correct shutdown with call ignite.close. This
event doesn't trigger the PME in Ignite 2.8 and later versions if a node
belonging to an existing baseline topology leaves.
*/-- This means this is not triggered at all 2.8.1 or higher if shutdown
cleanly ? i.e. if this is called : Ignition.stop(false) /*
Node Failed (EVT_NODE_FAILED) - detected unresponsive node, probably crashed
and is considered failed
*/-- This means this is  triggered at all 2.8.1 or higher for baseline nodes
or any thick client node ?/*

Custom events:

Activation / Deactivation / Baseline topology set - ChangeGlobalStateMessage
Dynamic cache start / Dynamic cache stop - DynamicCacheChangeBatch
*/ for the end user , is this invoked when we do ignite.getOrCreate( xx )
and ignite.cache(xx )/*

Snapshot create / restore - SnapshotDiscoveryMessage
Global WAL enable / disable - WalStateAbstractMessage
Late affinity assignment - CacheAffinityChangeMessage


regards,
Veena.



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Regarding partition map exchange triggers

[VeenaMithare]

Hi , 


I can see the triggers for PME initiation here : 
https://cwiki.apache.org/confluence/display/IGNITE/%28Partition+Map%29+Exchange+-+under+the+hood

Triggers
Events which causes exchange

Topology events:

Node Join (EVT_NODE_JOINED) - new node discovered and joined topology
(exchange is done after a node is included into the ring). This event
doesn't trigger the PME if a thick client connects the cluster and an Ignite
version is 2.8 or later. 
/*-- This means in ignite 2.8 or higher, this is triggered only if nodes
that participate in the baseline topology are added ?*/
Node Left (EVT_NODE_LEFT) - correct shutdown with call ignite.close. This
event doesn't trigger the PME in Ignite 2.8 and later versions if a node
belonging to an existing baseline topology leaves.
/*-- This means this is not triggered at all 2.8.1 or higher if shutdown
cleanly ? i.e. if this is called : Ignition.stop(false) */
Node Failed (EVT_NODE_FAILED) - detected unresponsive node, probably crashed
and is considered failed
/*-- This means this is  triggered at all 2.8.1 or higher for baseline nodes
or any thick client node ?*/

Custom events:

Activation / Deactivation / Baseline topology set - ChangeGlobalStateMessage 
Dynamic cache start / Dynamic cache stop - DynamicCacheChangeBatch
/* for the end user , is this invoked when we do ignite.getOrCreate( xx )
and ignite.cache(xx )*/

Snapshot create / restore - SnapshotDiscoveryMessage
Global WAL enable / disable - WalStateAbstractMessage
Late affinity assignment - CacheAffinityChangeMessage


regards,
Veena.




--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Regarding partition map exchange triggers

[VeenaMithare]

Hi , 


I can see the triggers for PME initiation here : 
https://cwiki.apache.org/confluence/display/IGNITE/%28Partition+Map%29+Exchange+-+under+the+hood

Triggers
Events which causes exchange

Topology events:

Node Join (EVT_NODE_JOINED) - new node discovered and joined topology
(exchange is done after a node is included into the ring). This event
doesn't trigger the PME if a thick client connects the cluster and an Ignite
version is 2.8 or later. 
/*-- This means in ignite 2.8 or higher, this is triggered only if nodes
that participate in the baseline topology are added ?*/
Node Left (EVT_NODE_LEFT) - correct shutdown with call ignite.close. This
event doesn't trigger the PME in Ignite 2.8 and later versions if a node
belonging to an existing baseline topology leaves.
/*-- This means this is not triggered at all 2.8.1 or higher if shutdown
cleanly ? i.e. if this is called : Ignition.stop(false) */
Node Failed (EVT_NODE_FAILED) - detected unresponsive node, probably crashed
and is considered failed
/*-- This means this is  triggered at all 2.8.1 or higher for baseline nodes
or any thick client node ?*/

Custom events:

Activation / Deactivation / Baseline topology set - ChangeGlobalStateMessage 
Dynamic cache start / Dynamic cache stop - DynamicCacheChangeBatch
/* for the end user , is this invoked when we do ignite.getOrCreate( xx )
and ignite.cache(xx )*/

Snapshot create / restore - SnapshotDiscoveryMessage
Global WAL enable / disable - WalStateAbstractMessage
Late affinity assignment - CacheAffinityChangeMessage


regards,
Veena.




--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

RE: Loosing cache data when persistence is enabled

[BEELA GAYATRI]

Hi,

  The nodes are  not getting  out of  Baseline topology. They are showing 
offline , after restart of the nodes data is getting deleted from persistence 
folders(some time data not getting deleted and some times getting deleted). PFA 
web console

Sent from Mail for Windows 10

From: VincentCE
Sent: Thursday, December 10, 2020 6:10 PM
To: user@ignite.apache.org
Subject: Re: Loosing cache data when persistence is enabled

"External email. Open with Caution"

Hi Beela,

could the root cause be that you had changes in your baseline topology when
you saw the data loss? According to my understanding and the answer I got on
my question
http://apache-ignite-users.70518.x6.nabble.com/Ignite-persistence-Data-of-node-is-lost-after-being-excluded-from-baseline-topology-td34675.html
some weeks ago the data of nodes that got excluded from the baseline
topology will be deleted for consistency reasons.

This is just an immediate guess from my side, I did not have a look into
your attachments so far.

Best,
Vincent



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

=-=-=
Notice: The information contained in this e-mail
message and/or attachments to it may contain 
confidential or privileged information. If you are 
not the intended recipient, any dissemination, use, 
review, distribution, printing or copying of the 
information contained in this e-mail message 
and/or attachments to it are strictly prohibited. If 
you have received this communication in error, 
please notify us by reply e-mail or telephone and 
immediately and permanently delete the message 
and any attachments. Thank you

Regarding long running transaction

[VeenaMithare]

Hi , 

I see this in my transaction log : 
2020-12-10T07:32:59,525 WARN  o.a.i.i.diagnostic
[grid-timeout-worker-#1035%config-sync-GREEN-igniteclient-SINGLE%]: First 10
long running transactions [total=1]
2020-12-10T07:32:59,525 WARN  o.a.i.i.diagnostic
[grid-timeout-worker-#1035%config-sync-GREEN-igniteclient-SINGLE%]: >>>
Transaction [startTime=07:31:22.861, curTime=07:32:59.392, systemTime=0,
userTime=96531, tx=GridNearTxLocal [mappings=IgniteTxMappingsImpl [],
nearLocallyMapped=false, colocatedLocallyMapped=false, needCheckBackup=null,
hasRemoteLocks=false, trackTimeout=true, systemTime=0, systemStartTime=0,
prepareStartTime=0, prepareTime=0, commitOrRollbackStartTime=0,
commitOrRollbackTime=0,
txDumpsThrottling=o.a.i.i.processors.cache.transactions.IgniteTxManager$TxDumpsThrottling@f46affc,
lb=null, mvccOp=null, qryId=-1, crdVer=0, thread=, mappings=IgniteTxMappingsImpl [], super=GridDhtTxLocalAdapter
[nearOnOriginatingNode=false, nearNodes=KeySetView [], dhtNodes=KeySetView
[], explicitLock=false, super=IgniteTxLocalAdapter [completedBase=null,
sndTransformedVals=false, depEnabled=false, txState=IgniteTxStateImpl
[activeCacheIds=[], recovery=null, mvccEnabled=null, mvccCachingCacheIds=[],
txMap=EmptySet []], super=IgniteTxAdapter [xidVer=GridCacheVersion
[topVer=218929849, order=1607454902519, nodeOrder=6], writeVer=null,
implicit=false, loc=true, threadId=39198, startTime=1607585482861,
nodeId=e25ecc8b-66e4-4856-9da5-5eebeec67a45, startVer=GridCacheVersion
[topVer=218929849, order=1607454902519, nodeOrder=6], endVer=null,
isolation=READ_COMMITTED, concurrency=PESSIMISTIC, timeout=90,
sysInvalidate=false, sys=false, plc=2, commitVer=null, finalizing=NONE,
invalidParts=null, state=ACTIVE, timedOut=false,
topVer=AffinityTopologyVersion [topVer=-1, minorTopVer=0],
mvccSnapshot=null, skipCompletedVers=false, parentTx=null, duration=96531ms,
onePhaseCommit=false], size=0

How do I know the cause for this long running transaction ?

I see this in the log above : thread=.
What does this mean. 

I am updating around 50k records in a transaction and have given the tx
timeout as 120 secs. 
What is the threshold for ignite to decide that a transaction is long
running ?I can see that this is showing a usertime of 96531. 

I dont see any other WARN or ERROR messages after this log , ( there is one
more warn message about 'dumping the stack trace of near node that started
this transaction' , but that is not helpful )

regards,
Veena.




--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Native persistence and upgrading

[xero]

Hi Dimitry and community,
Is this still true? My intention is to do it between versions 2.7.6 and
2.8.1/2.9. Basically, I want to only update the docker image keeping the
volumes so that I can recover the persisted data. I couldn't find
documentation regarding this topic.

On the other hand, release_2.9 introduced Cluster Snapshots. Are these
snapshots version agnostic? or there are some considerations regarding which
versions are compatible with the created snapshot? Could this be an
alternative to solve my issue (upgrading without losing the persisted data)? 

Thanks in advance for the time.



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: BaselineTopology branching error

[rakshita04]

What if i delete "metastorage" folder created on older node?
Will it solve the problem?
Will i loose all Database entries(key,value) if i delete this folder?



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Loosing cache data when persistence is enabled

[VincentCE]

Hi Beela,

could the root cause be that you had changes in your baseline topology when
you saw the data loss? According to my understanding and the answer I got on
my question
http://apache-ignite-users.70518.x6.nabble.com/Ignite-persistence-Data-of-node-is-lost-after-being-excluded-from-baseline-topology-td34675.html
some weeks ago the data of nodes that got excluded from the baseline
topology will be deleted for consistency reasons.

This is just an immediate guess from my side, I did not have a look into
your attachments so far.

Best,
Vincent



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/