Re: [2.9.0]NPE on invoke IgniteCache.destroy()

[slava.koptilin]

Hello,

This is definitely a bug.
The good news is that it looks like
https://issues.apache.org/jira/browse/IGNITE-13207 &
https://issues.apache.org/jira/browse/IGNITE-13151 are fixing this issue.
Both fixes are included in AI-2.10

Thanks,
S.



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

Re: partition-exchanger system-critical thread blocked

[Gangaiah Gundeboina]

Hi Ilya,

We have configured atomictyMode 'ATOMIC' for all caches it's not
transactional, below is our cache configuration for one of the caches. 

### Cache Configuration 











 

I have searched with word 'tcp-comm-worker' in whole log file, could see
single thread tcp-comm-worker-#1

 And also attached whole log file, please check  ignite.log
  

You can refer logs from 2020-12-11 12:50:00 to 12:54:00, we can see the
tread blocked while multiple clients trying to connect to cluster.

#

Line 2351: [2020-12-07T02:22:17,350][WARN
][tcp-disco-msg-worker-#2%EDIFCustomerCC%][G] Thread
[name="tcp-comm-worker-#1%EDIFCustomerCC%", id=369, state=RUNNABLE,
blockCnt=1514, waitCnt=7411]

Line 4507: Thread
[name="tcp-comm-worker-#1%EDIFCustomerCC%", id=369, state=RUNNABLE,
blockCnt=1514, waitCnt=7411]

Line 50755: [2020-12-10T05:14:53,287][WARN
][sys-stripe-97-#98%EDIFCustomerCC%][G] Thread
[name="tcp-comm-worker-#1%EDIFCustomerCC%", id=369, state=RUNNABLE,
blockCnt=1556, waitCnt=7861]

Line 54210: Thread
[name="tcp-comm-worker-#1%EDIFCustomerCC%", id=369, state=RUNNABLE,
blockCnt=1556, waitCnt=7861]

Line 60084: [2020-12-10T14:30:33,360][WARN
][sys-stripe-33-#34%EDIFCustomerCC%][G] Thread
[name="tcp-comm-worker-#1%EDIFCustomerCC%", id=369, state=RUNNABLE,
blockCnt=1561, waitCnt=7918]

Line 62467: Thread
[name="tcp-comm-worker-#1%EDIFCustomerCC%", id=369, state=RUNNABLE,
blockCnt=1561, waitCnt=7918]

Line 69864: Thread
[name="tcp-comm-worker-#1%EDIFCustomerCC%", id=369, state=RUNNABLE,
blockCnt=1561, waitCnt=7918]

Line 76870: Thread
[name="tcp-comm-worker-#1%EDIFCustomerCC%", id=369, state=RUNNABLE,
blockCnt=1561, waitCnt=7918]

Line 84077: Thread
[name="tcp-comm-worker-#1%EDIFCustomerCC%", id=369, state=RUNNABLE,
blockCnt=1561, waitCnt=7918]

Line 90968: Thread
[name="tcp-comm-worker-#1%EDIFCustomerCC%", id=369, state=RUNNABLE,
blockCnt=1561, waitCnt=7918]

Line 97851: Thread
[name="tcp-comm-worker-#1%EDIFCustomerCC%", id=369, state=RUNNABLE,
blockCnt=1561, waitCnt=7918]

Line 105066: Thread
[name="tcp-comm-worker-#1%EDIFCustomerCC%", id=369, state=RUNNABLE,
blockCnt=1561, waitCnt=7918]

Line 113229: Thread
[name="tcp-comm-worker-#1%EDIFCustomerCC%", id=369, state=RUNNABLE,
blockCnt=1561, waitCnt=7918]

Line 120851: Thread
[name="tcp-comm-worker-#1%EDIFCustomerCC%", id=369, state=RUNNABLE,
blockCnt=1561, waitCnt=7918]

Line 124129: [2020-12-10T14:32:36,828][WARN
][tcp-disco-msg-worker-#2%EDIFCustomerCC%][G] Thread
[name="tcp-comm-worker-#1%EDIFCustomerCC%", id=369, state=RUNNABLE,
blockCnt=1561, waitCnt=7918]

Line 128469: Thread
[name="tcp-comm-worker-#1%EDIFCustomerCC%", id=369, state=RUNNABLE,
blockCnt=1561, waitCnt=7918]

Line 136378: Thread
[name="tcp-comm-worker-#1%EDIFCustomerCC%", id=369, state=RUNNABLE,
blockCnt=1561, waitCnt=7918]

Line 144518: Thread
[name="tcp-comm-worker-#1%EDIFCustomerCC%", id=369, state=RUNNABLE,
blockCnt=1561, waitCnt=7918]

Line 150128: [2020-12-10T14:34:40,071][WARN
][tcp-disco-msg-worker-#2%EDIFCustomerCC%][G] Thread
[name="tcp-comm-worker-#1%EDIFCustomerCC%", id=369, state=RUNNABLE,
blockCnt=1561, waitCnt=7918]

Line 155898: Thread
[name="tcp-comm-worker-#1%EDIFCustomerCC%", id=369, state=RUNNABLE,
blockCnt=1561, waitCnt=7918]

Line 164791: Thread
[name="tcp-comm-worker-#1%EDIFCustomerCC%", id=369, state=RUNNABLE,
blockCnt=1561, waitCnt=7918]

Line 168214: [2020-12-10T14:35:43,175][WARN
][tcp-disco-msg-worker-#2%EDIFCustomerCC%][G] Thread
[name="tcp-comm-worker-#1%EDIFCustomerCC%", id=369, state=RUNNABLE,
blockCnt=1561, waitCnt=7918]

Line 172241: Thread
[name="tcp-comm-worker-#1%EDIFCustomerCC%", id=369, state=RUNNABLE,
blockCnt=1561, waitCnt=7918]

Line 175537: [2020-12-10T14:37:46,346][WARN
][sys-stripe-64-#65%EDIFCustomerCC%][G] Thread
[name="tcp-comm-worker-#1%EDIFCustomerCC%", id=369, state=RUNNABLE,
blockCnt=1561, waitCnt=7918]

Line 179032: Thread
[name="tcp-comm-worker-#1%EDIFCustomerCC%", id=369, state=RUNNABLE,
blockCnt=1561, waitCnt=7918]

Line 190529: [2020-12-11T12:52:19,275][WARN
][sys-stripe-111-#112%EDIFCustomerCC%][G] Thread
[name="tcp-comm-worker-#1%EDIFCustomerCC%", id=369, state=RUNNABLE,
blockCnt=1570, waitCnt=8053]

Line 194008: Thread
[name="tcp-comm-worker-#1%EDIFCustomerCC%", id=369, state=RUNNABLE,
blockCnt=1570, waitCnt=8053]

Line 197166: [2020-12-11T12:54:26,461][WARN
][sys-stripe-28-#29%EDIFCustomerCC%][G] Thread
[n

Re: Regarding Partition Map exchange Triggers

[VeenaMithare]

Hi Ilya,

thank you !

regards,
Veena



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

Re: Why does TextQuery failed to find result

[Ilya Kasnacheev]

Hello!

Ok, I see. Seems I have answered in a different thread.

Regards,
-- 
Ilya Kasnacheev


пн, 14 дек. 2020 г. в 19:15, siva :

> Hi,
> Not sure why format code ,images are not receiving in email.
> Please find
> Here is the Nabble code  link
> <
> http://apache-ignite-users.70518.x6.nabble.com/Why-does-TextQuery-failed-to-find-result-td34759.html#a34877>
>
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Why does TextQuery failed to find result

[siva]

Hi,
Not sure why format code ,images are not receiving in email.
Please find 
Here is the Nabble code  link

  




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

Re: Ignite cache TextQuery on JsonString data Field

[Ilya Kasnacheev]

Hello!

I'm not sure that our text indexing will tokenize your JSON correctly. Can
you try just putting some simple word in that field and trying text search?

Regards,
-- 
Ilya Kasnacheev


пн, 30 нояб. 2020 г. в 16:39, siva :

> Hi All,
> I am using ApacheIgnite2.7.6 .Net Core.And I have .Net ClientServer App.And
> for Cache creation using QueryEntity CacheConfiguration.And for
> Data loading in Ignite cache using DataStreamer AddData(key,model) method.
> *
> Model class:*
>
>
>
> where Payload field contains jsonstring as data.
> *for example Payload data*
>
>
> *
> <
> http://apache-ignite-users.70518.x6.nabble.com/file/t1379/TextQueryTableResult.png
> >
> *
>
> *Code:*
>
>
> cursor cacheEntry contains no result.
>
> How to get data in result and what i need to change?
>
> Thanks.
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: partition-exchanger system-critical thread blocked

[Ilya Kasnacheev]

Hello!

Can you provide stack trace from that thread?

No, this is a different thread than exchange worker.

I don't think that cluster is supposed to fail clients in this case. We
have timeout for transactions waiting on PME now.

Regards,
-- 
Ilya Kasnacheev


сб, 12 дек. 2020 г. в 10:23, Gangaiah Gundeboina :

> Hi Ilya,
>
> Again we got same issue 'tcp-comm-worker-#1' blocked. We have observed one
> thing whenever multiple clients joining to cluster at same time, the error
> is printing. I could see there is only one thread(tcp-comm-worker), checked
> from logs and also from visualvm.
>
> From documentation also, could see there is only one thread per node below
> are details. Is it same thread?
>
> ###
> Initialization of exchange means adding future
> GridDhtPartitionsExchangeFuture to queue on each node.
>
> Put to this queue (GridCachePartitionExchangeManager.ExchangeWorker#futQ)
> is
> done from the discovery thread.
>
> 'Exchange worker' thread manages this queue. Using only one exchange worker
> thread per node provides a strict processing order for futures.
> 
>
> And also I heard cluster will kick the clients where more
> transactions/atomic updates happening while waiting for partition-exchange
> to complete. Is it could be reason, could you please help us to find out
> the
> cause and fix the issue.
>
> Thanks and Regards,
> Gangaiah
>
>
>
> -
> Thanks and Regards,
> Gangaiah
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Ignite cache TextQuery on JsonString data Field

[Pavel Tupitsyn]

I can't see any details in the email too.
However, code is visible on Nabble [1]
Weird.

[1]
http://apache-ignite-users.70518.x6.nabble.com/Ignite-cache-TextQuery-on-JsonString-data-Field-td34743.html

On Mon, Dec 14, 2020 at 5:03 PM Ilya Kasnacheev 
wrote:

> Hello!
>
> Unfortunately, nothing is visible in your e-mails.
> Please provide images/files as links.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> пн, 30 нояб. 2020 г. в 20:00, siva :
>
>> Hi,
>> please find the Cache configuration details give below.
>>
>>
>>
>>
>>
>>
>>
>> --
>> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>>
>

Re: Issue with BaselineTopology Branching History

[andrei]

Just try not to change the baseline after each server node restart to 
avoid this problem. The base topology will wait for this node.


BR,
Andrei

12/12/2020 4:44 PM, rakshita04 пишет:

If by any chance, someone messes up this sequence, sometimes ignite is
throwing error which is great on which we can take some action but sometimes
its getting stuck and making our process also stuck.
Is there a way that the node(new node) does not get stuck and throws some
error or exception after a certain time?

Regards,
Rakshita



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

Re: Why does TextQuery failed to find result

[Ilya Kasnacheev]

Hello!

Unfortunately I can't see any image here. Please provide a link or plain
text.

Regards,
-- 
Ilya Kasnacheev


пн, 14 дек. 2020 г. в 17:55, siva :

> Hi,
> Actually I am creating Indexing and creating cache with typeof(interface)
> which is implemented by model class.
>
> Can you please look into this Given class methods cache configuration etc
> and give me suggestion what is the wrong. I am not getting result from
> textquery but sql  query working fine.
>
> *Full details:*
> IgniteClient,CacheConfiguration and QueryEntity and my start method
>
>
>
>
>
> Thanks
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: BaselineTopology branching error

[andrei]

Hi,

When the baseline of your nodes is different, they will not be able to 
connect to each other. Before attaching to such a node, you must remove 
all data from the working directory (db, wal, wal archive, etc).


BR,
Andrei

12/10/2020 3:53 PM, 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: Why does TextQuery failed to find result

[siva]

Hi,
Actually I am creating Indexing and creating cache with typeof(interface)
which is implemented by model class.

Can you please look into this Given class methods cache configuration etc
and give me suggestion what is the wrong. I am not getting result from
textquery but sql  query working fine.

*Full details:*
IgniteClient,CacheConfiguration and QueryEntity and my start method 





Thanks



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

Re: Regarding Partition Map exchange Triggers

[Ilya Kasnacheev]

Hello!

cache.close() will not cause a PME. cache.destroy() (or DROP TABLE) will.

Regards,
-- 
Ilya Kasnacheev


пн, 14 дек. 2020 г. в 12:39, VeenaMithare :

> >>Looking at your stack traces it seems that the cache you accessed in the
> SQL query was stopped right before the new client node is joined.
> >>All topology events are processed one-by-one, so the initial blocking
> time
> was caused by cache stop PME rather than client node join.
>
>
> What is the guidance regarding cleanly shutting down an client or server (
> for deployment etc. )? Is it a good practice to call cache.close when a
> client or a server node is being shutdown ?
>
> Cache closed but not destroyed means it can be still accessed by other
> nodes
> by calling ignite.cache - what is the purpose of calling PME when
> cache.close is invoked ?
>
> Is there any difference in calling cache.close on the client( non baselined
> node ) or server( baselined node ) node ?
>
> regards,
> Veena.
>
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Ignite cache TextQuery on JsonString data Field

[Ilya Kasnacheev]

Hello!

Unfortunately, nothing is visible in your e-mails.
Please provide images/files as links.

Regards,
-- 
Ilya Kasnacheev


пн, 30 нояб. 2020 г. в 20:00, siva :

> Hi,
> please find the Cache configuration details give below.
>
>
>
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Re[2]: [2.9.0]NPE on invoke IgniteCache.destroy()

[Ilya Kasnacheev]

Hello!

Why don't you do it yourself if you have the understanding of the issue? It
seems you're the only one ATM.

Regards,
-- 
Ilya Kasnacheev


ср, 9 дек. 2020 г. в 09:27, Zhenya Stanilovsky :

> looks like we deactivate pageMem concurrently with cp pageWrite, plz
> someone fill the ticket with appropriate logs.
>
>
>
> Среда, 9 декабря 2020, 4:52 +03:00 от 38797715 <38797...@qq.com>:
>
>
> Hi Ilya,
>
> This issue is not easy to reproduce.
>
> However, judging from the exception stack, the issue may be related to the
> checkpoint process during the destruction of the cache.
> 在 2020/12/9 上午9:33, Ilya Kazakov 写道:
>
> Hello! Can you provide some details, or show some short reproducer?
>
> -
> Ilya Kazakov
>
> пн, 7 дек. 2020 г. в 21:31, 38797715 <38797...@qq.com
> >:
>
> Hi community,
>
> Call IgniteCache.destroy Method, NPE appears,logs are as follows:
> 2020-12-07 17:32:18.870 [] [exchange-worker-#54%tradecore%] INFO
> o.a.i.i.e.time - Started exchange init [topVer=AffinityTopologyVersion
> [topVer=1, minorTopVer=279], crd=true, evt=DISCOVERY_CUSTOM_EVT, evtNode=
> 320935f6-3516-4b0b-9e5f-e80768696522, customEvt=DynamicCacheChangeBatch
> [id=1f2a90e2671-562b8f51-fa6a-4094-928c-6976ce87614a, reqs=ArrayList
> [DynamicCacheChangeRequest [cacheName=PksQuota, hasCfg=false, nodeId=
> 320935f6-3516-4b0b-9e5f-e80768696522, clientStartOnly=false, stop=true,
> destroy=false, disabledAfterStartfalse]], exchangeActions=ExchangeActions
> [startCaches=null, stopCaches=[PksQuota], startGrps=[],
> stopGrps=[PksQuota, destroy=true], resetParts=null, stateChangeRequest=
> null], startCaches=false], allowMerge=false, exchangeFreeSwitch=false]
> 2020-12-07 17:32:18.873 [] [exchange-worker-#54%tradecore%] INFO
> o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture - Finished waiting for
> partition release future [topVer=AffinityTopologyVersion [topVer=1,
> minorTopVer=279], waitTime=0ms, futInfo=NA, mode=DISTRIBUTED]
> 2020-12-07 17:32:18.873 [] [exchange-worker-#54%tradecore%] INFO
> o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture - Finished waiting for
> partitions release latch: ServerLatch [permits=0, pendingAcks=HashSet [],
> super=CompletableLatch [id=CompletableLatchUid [id=exchange,
> topVer=AffinityTopologyVersion [topVer=1, minorTopVer=279
> 2020-12-07 17:32:18.873 [] [exchange-worker-#54%tradecore%] INFO
> o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture - Finished waiting for
> partition release future [topVer=AffinityTopologyVersion [topVer=1,
> minorTopVer=279], waitTime=0ms, futInfo=NA, mode=LOCAL]
> 2020-12-07 17:32:19.037 [] [exchange-worker-#54%tradecore%] INFO
> o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture -
> finishExchangeOnCoordinator [topVer=AffinityTopologyVersion [topVer=1,
> minorTopVer=279], resVer=AffinityTopologyVersion [topVer=1, minorTopVer=
> 279]]
> 2020-12-07 17:32:19.438 [] [exchange-worker-#54%tradecore%] INFO
> o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture - Finish exchange
> future [startVer=AffinityTopologyVersion [topVer=1, minorTopVer=279],
> resVer=AffinityTopologyVersion [topVer=1, minorTopVer=279], err=null,
> rebalanced=true, wasRebalanced=true]
> 2020-12-07 17:32:20.870 [] [db-checkpoint-thread-#75%tradecore%] INFO
> o.a.i.i.p.c.p.GridCacheDatabaseSharedManager - Checkpoint started
> [checkpointId=f001018a-100e-4154-98c9-547dabf5015f,
> startPtr=FileWALPointer [idx=16, fileOff=1059360696, len=4770137],
> checkpointBeforeLockTime=549ms, checkpointLockWait=0ms,
> checkpointListenersExecuteTime=529ms, checkpointLockHoldTime=853ms,
> walCpRecordFsyncDuration=17ms, writeCheckpointEntryDuration=7ms,
> splitAndSortCpPagesDuration=4ms, pages=10775, reason='caches stop']
> 2020-12-07 17:32:21.255 [] [checkpoint-runner-#79%tradecore%] WARN
> o.a.i.i.p.c.p.GridCacheDatabaseSharedManager - 1 checkpoint pages were
> not written yet due to unsuccessful page write lock acquisition and will be
> retried
> 2020-12-07 17:32:21.261 [] [exchange-worker-#54%tradecore%] ERROR
> o.a.i.i.p.c.GridCacheProcessor - Failed to wait for checkpoint finish
> during cache stop.
> org.apache.ignite.IgniteCheckedException: Compound exception for
> CountDownFuture.
> at
> org.apache.ignite.internal.util.future.CountDownFuture.addError(CountDownFuture.java:72)
> ~[ignite-core-2.9.0.jar!/:2.9.0]
> at
> org.apache.ignite.internal.util.future.CountDownFuture.onDone(CountDownFuture.java:46)
> ~[ignite-core-2.9.0.jar!/:2.9.0]
> at
> org.apache.ignite.internal.util.future.CountDownFuture.onDone(CountDownFuture.java:28)
> ~[ignite-core-2.9.0.jar!/:2.9.0]
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:478)
> ~[ignite-core-2.9.0.jar!/:2.9.0]
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$WriteCheckpointPages.run(GridCacheDatabaseSharedManager.java:4546)
> ~[ignite-core-2.9.0.jar!/:2.9.0]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> ~[?:1.8.0_272]
> at
> java.

Re: How do we set statisticsEnabled for cache created thru JDBC SQL like create table

[Ilya Kasnacheev]

Hello!

You can define a cache template, use this template to create your tables.

https://ignite.apache.org/docs/latest/configuring-caches/configuration-overview#cache-templates

Regards,
-- 
Ilya Kasnacheev


пн, 14 дек. 2020 г. в 14:04, Naveen :

> HI
>
> We do have created cache with JDBC create table DDL and want to enable
> cache
> metrics for the same.
> I do not see any property for create table to enable cache metrics.
> If there any property to enable cache metrics for a cache created thru JDBC
> SQL DDL.
>
> Thanks
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Native persistence and upgrading

[Ilya Kasnacheev]

Hello!

All of 2.x are compatible, meaning you can upgrade from 2.x to 2.y, y > x,
while keeping your persistence files.

Yes, I think we should document this somewhere:
https://issues.apache.org/jira/browse/IGNITE-13851

Regards,
-- 
Ilya Kasnacheev


пн, 14 дек. 2020 г. в 16:09, xero :

> Thanks for the confirmation Stanislav. Is this compatibility kept between
> minors as a commitment from the team or is it just specific to the versions
> I mentioned?
> If this is a backward compatibility feature that you have intentions to
> maintain, I think it's worth mentioning that in the documentation because
> is
> a great feature.
>
> Thank you
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Native persistence and upgrading

[xero]

Thanks for the confirmation Stanislav. Is this compatibility kept between
minors as a commitment from the team or is it just specific to the versions
I mentioned?
If this is a backward compatibility feature that you have intentions to
maintain, I think it's worth mentioning that in the documentation because is
a great feature.

Thank you



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

Re: Why does TextQuery failed to find result

[Ilya Kasnacheev]

Hello!

I'm really suspicious of how you call GetOrCreateCache in
GetIConstructionCacheStore(string cacheName)

I would expect that it will create a cache without any indexing (i.e. with
no possibility of sql or text queries).

Make sure to always use GetOrCreateCache(cacheName, typeof(ValueType):
https://apacheignite-net.readme.io/docs/sql-queries#configuring-sql-indexes-using-attributes

I just don't see how your GetOrCreateCache will work given that the cache
will always be created, and that it's too late to add cache cfgs to client
config once it's already started.

Regards,
-- 
Ilya Kasnacheev


пн, 14 дек. 2020 г. в 12:34, siva :

> Hi,
> Please find the given below details.
>
>
>
> here is the complete code(CacheConfiguration,TexTquery method)  Github
> <
> https://github.com/CP-Ram/IgniteTextQueryDotNetTestApp/blob/81c7db2287064aa6eb40ed885a68e197face7430/IngiteTextQueryTestApp/IgniteThickClientTextQueryService.cs#L58>
>
> ThickClient TextQuery Test method.
>
> Thanks.
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

How do we set statisticsEnabled for cache created thru JDBC SQL like create table

[Naveen]

HI

We do have created cache with JDBC create table DDL and want to enable cache
metrics for the same.
I do not see any property for create table to enable cache metrics.
If there any property to enable cache metrics for a cache created thru JDBC
SQL DDL.

Thanks



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

Re: Regarding Partition Map exchange Triggers

[VeenaMithare]

>>Looking at your stack traces it seems that the cache you accessed in the
SQL query was stopped right before the new client node is joined.
>>All topology events are processed one-by-one, so the initial blocking time
was caused by cache stop PME rather than client node join.


What is the guidance regarding cleanly shutting down an client or server (
for deployment etc. )? Is it a good practice to call cache.close when a
client or a server node is being shutdown ? 

Cache closed but not destroyed means it can be still accessed by other nodes
by calling ignite.cache - what is the purpose of calling PME when
cache.close is invoked ?

Is there any difference in calling cache.close on the client( non baselined
node ) or server( baselined node ) node ?

regards,
Veena.





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

Re: Why does TextQuery failed to find result

[siva]

Hi,
Please find the given below details.



here is the complete code(CacheConfiguration,TexTquery method)  Github

 
ThickClient TextQuery Test method.

Thanks.




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

Re: Native persistence and upgrading

[Stanislav Lukyanov]

Yes, you can upgrade from an older version to a newer one and keep the data, it 
will just work.
You don't really need snapshots for that, although I assume snapshots would 
also work.

> On 10 Dec 2020, at 16:20, xero  wrote:
> 
> 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/