Re: Can we avoid the PME when restarts a node in cluster.

[Justin Ji]

2.7.5 may not include the feature~



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

Re: Can we avoid the PME when restarts a node in cluster.

[Justin Ji]

Thank for your replay!

Is there a scheduled release date of 2.8.0?



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

RE: Ignite on GCP / GKE

[Stéphane Gayet]

Thanks, Maxim. I will give it a try :)

 Stéphane Gayet
 Responsable Développement / Development Manager
[https://storage.letsignit.com/5b884a1a1e0a0f0007c51472/55370421467418375936059118036679301217_5b8eb5cb514093000719db66_8e82e6302fdca8989b5eec24209877fa.png]
   (+33) 1 70 38 70 74 +33 6 00 00 00 00
[https://storage.letsignit.com/5b884a1a1e0a0f0007c51472/317558219157559608341284032890064642484_5b8eb5cb514093000719db66_3c9ea4b29daa57047729e2a2e8dfc4a4.png]
  stephane.ga...@misterfly.com
[https://storage.letsignit.com/5b884a1a1e0a0f0007c51472/178007963808408740710245191003991062821_5b8eb5cb514093000719db66_7f052010d2044c090deb48e04aaa39af.png]
  25 Rue de Ponthieu Bâtiment C 75008 Paris
Vols, Hôtels, Séjours,... Et c'est pas fini !
misterfly.com
 | 
misterflypro.com
 | 
iziwifi.com
[https://storage.letsignit.com/icons/facebook...@2x.png]
[https://storage.letsignit.com/icons/twitter...@2x.png] 

[https://storage.letsignit.com/icons/instagram...@2x.png] 

  [https://storage.letsignit.com/icons/linkedin...@2x.png] 

[https://storage.letsignit.com/5b884a1a1e0a0f0007c51472/276623704557963397770479731125901207279_5b8eb5cb514093000719db66_3931b60112812fe1ed7aac46feb9b92d.png]
[https://storage.letsignit.com/5b884a1a1e0a0f0007c51472/124856704240080447357977399086155886407_5c6bc66ef6d4cf0008f0bac7_f8cdde50fea6f4b2c6d22c96c19f8910.jpg]


De : Maxim.Pudov 
Envoyé : jeudi 20 juin 2019 14:24
À : user@ignite.apache.org
Objet : Re: Ignite on GCP / GKE

Hi Stephane,

Since Ignite is basically just a java process, it's as reliable as any other
java application. You should probably set workDirectory, wal and storage to
a mounted disk in Ignite config if you use persistent data regions and want
your data to survive pod restarts. Those mounted disks are slower than bare
metal, but the difference is not that big.
As far as I know Google Cloud provides a free trial period, so you could try
it.



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

Re: Ignite Visor Cache command hangs indefinitely.

[John Smith]

Actually this hapenned when the WIFI node connected. But it never hapenned
before...

[14:51:46,660][INFO][exchange-worker-#43%xx%][GridDhtPartitionsExchangeFuture]
Completed partition exchange
[localNode=e9e9f4b9-b249-4a4d-87ee-fc97097ad9ee,
exchange=GridDhtPartitionsExchangeFuture [topVer=AffinityTopologyVersion
[topVer=59, minorTopVer=0], evt=NODE_JOINED, evtNode=TcpDiscoveryNode
[id=45516c37-5ee0-4046-a13a-9573607d25aa, addrs=[0:0:0:0:0:0:0:1,
127.0.0.1, MY_WIFI_IP, MY_WIFI_IP], sockAddrs=[/MY_WIFI_IP:0,
/0:0:0:0:0:0:0:1:0, /127.0.0.1:0, /MY_WIFI_IP:0], discPort=0, order=59,
intOrder=32, lastExchangeTime=1561042306599, loc=false,
ver=2.7.0#20181130-sha1:256ae401, isClient=true], done=true],
topVer=AffinityTopologyVersion [topVer=59, minorTopVer=0],
durationFromInit=0]
[14:51:46,660][INFO][exchange-worker-#43%xx%][time] Finished exchange
init [topVer=AffinityTopologyVersion [topVer=59, minorTopVer=0], crd=true]
[14:51:46,662][INFO][exchange-worker-#43%xx%][GridCachePartitionExchangeManager]
Skipping rebalancing (nothing scheduled) [top=AffinityTopologyVersion
[topVer=59, minorTopVer=0], force=false, evt=NODE_JOINED,
node=45516c37-5ee0-4046-a13a-9573607d25aa]
[14:51:47,123][INFO][grid-nio-worker-tcp-comm-2-#26%xx%][TcpCommunicationSpi]
Accepted incoming communication connection [locAddr=/xxx.xxx.xxx.69:47100,
rmtAddr=/MY_WIFI_IP:62249]
[14:51:59,428][INFO][db-checkpoint-thread-#1068%xx%][GridCacheDatabaseSharedManager]
Checkpoint started [checkpointId=56e2ea25-7273-49ab-81ac-0fdbc5945626,
startPtr=FileWALPointer [idx=137, fileOff=45790479, len=17995],
checkpointLockWait=0ms, checkpointLockHoldTime=12ms,
walCpRecordFsyncDuration=3ms, pages=242, reason='timeout']
[14:51:59,544][INFO][db-checkpoint-thread-#1068%xx%][GridCacheDatabaseSharedManager]
Checkpoint finished [cpId=56e2ea25-7273-49ab-81ac-0fdbc5945626, pages=242,
markPos=FileWALPointer [idx=137, fileOff=45790479, len=17995],
walSegmentsCleared=0, walSegmentsCovered=[], markDuration=23ms,
pagesWrite=14ms, fsync=101ms, total=138ms]
[14:52:45,827][INFO][tcp-disco-msg-worker-#2%xx%][TcpDiscoverySpi]
Local node seems to be disconnected from topology (failure detection
timeout is reached) [failureDetectionTimeout=1, connCheckInterval=500]
[14:52:45,847][SEVERE][ttl-cleanup-worker-#1652%xx%][G] Blocked
system-critical thread has been detected. This can lead to cluster-wide
undefined behaviour [threadName=tcp-disco-msg-worker, blockedFor=39s]
[14:52:45,859][INFO][tcp-disco-sock-reader-#36%xx%][TcpDiscoverySpi]
Finished serving remote node connection [rmtAddr=/xxx.xxx.xxx.76:56861,
rmtPort=56861
[14:52:45,864][WARNING][ttl-cleanup-worker-#1652%xx%][G] Thread
[name="tcp-disco-msg-worker-#2%xx%", id=83, state=RUNNABLE, blockCnt=6,
waitCnt=24621465]

[14:52:45,875][SEVERE][ttl-cleanup-worker-#1652%xx%][] Critical system
error detected. Will be handled accordingly to configured handler
[hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0,
super=AbstractFailureHandler
[ignoredFailureTypes=[SYSTEM_WORKER_BLOCKED]]], failureCtx=FailureContext
[type=SYSTEM_WORKER_BLOCKED, err=class o.a.i.IgniteException: GridWorker
[name=tcp-disco-msg-worker, igniteInstanceName=xx, finished=false,
heartbeatTs=1561042326687]]]
class org.apache.ignite.IgniteException: GridWorker
[name=tcp-disco-msg-worker, igniteInstanceName=xx, finished=false,
heartbeatTs=1561042326687]
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance$2.apply(IgnitionEx.java:1831)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance$2.apply(IgnitionEx.java:1826)
at
org.apache.ignite.internal.worker.WorkersRegistry.onIdle(WorkersRegistry.java:233)
at
org.apache.ignite.internal.util.worker.GridWorker.onIdle(GridWorker.java:297)
at
org.apache.ignite.internal.processors.cache.GridCacheSharedTtlCleanupManager$CleanupWorker.body(GridCacheSharedTtlCleanupManager.java:151)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at java.lang.Thread.run(Thread.java:748)


[14:52:47,974][WARNING][jvm-pause-detector-worker][IgniteKernal%xx]
Possible too long JVM pause: 2047 milliseconds.
[14:52:47,994][INFO][tcp-disco-srvr-#3%xx%][TcpDiscoverySpi]
TCP discovery accepted incoming connection [rmtAddr=/xxx.xxx.xxx.72,
rmtPort=37607]
[14:52:47,994][INFO][tcp-disco-srvr-#3%xx%][TcpDiscoverySpi]
TCP discovery spawning a new thread for connection
[rmtAddr=/xxx.xxx.xxx.72, rmtPort=37607]

[14:52:47,996][INFO][tcp-disco-sock-reader-#37%xx%][TcpDiscoverySpi]
Started serving remote node connection [rmtAddr=/xxx.xxx.xxx.72:37607,
rmtPort=37607]

[14:52:48,005][WARNING][ttl-cleanup-worker-#1652%xx%][FailureProcessor]
Thread dump at 2019/06/20 14:52:47 UTC
Thread [name="sys-#25624%xx%", id=33109, state=TIMED_WAITING,
blockCnt=0, waitCnt=1]
Lock
[object=java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@

Cache misses with complex cache keys that have fields not relevant for hashCode/equals

[Axel Faust]

Hello,

I have been working on integrating Apache Ignite as a distributed
caching layer in the open source edition of the Alfresco Content
Services product. As this would be an extension, I don't have full
control over the kinds of keys used in cache operations. One default
cache in particular is using - among others - a complex cache key object
where at least one instance field is not relevant for the purpose of
establishing equality. Only when a lookup key object is set to the exact
same internal state as the key used for the cache put operation,
including the field not relevant for equality, will a cache get
operation actually hit the existing entry and return the expected cached
value.

I have read in
https://apacheignite.readme.io/docs/binary-marshaller#binaryobject-and-cachestore
that the Ignite BinaryObject class provides automatic hash code / equals
implementation. But I have found no details for how these
implementations treat different types of fields, e.g. dependent on
modifiers, or how to change the default behaviour without modifying the
key class in question. My (maybe naiive) assumption was that, if a value
class actually provides a hashCode operation that overrides the Object
default, then that would be respected.

By looking through the source, I have found the interface
BinaryIdentityResolver which sounds like it could be helpful in my case.
Unfortunately, since I can never know in advance what types of objects
users of my extension will use as keys, I can hardly configure a custom
binary type configuration for all possible / potential classes. Is there
any other way to deal with this kind of situation?


For reference, the following GitHub Gist contains the simple unit test I
set up to verify this was an issue with Ignite handling of cache keys
and not something in my implementation on top of Ignite:
https://gist.github.com/AFaust/e52ca1008a71b3e386a34f0fa63274be


Regards

Axel Faust

Re: Ignite Visor Cache command hangs indefinitely.

[John Smith]

Ok, where do I look for the visor logs when it hangs? And it's not a no
caches issue the cluster works great. It when visor cannot reach a specific
client node.

On Thu., Jun. 20, 2019, 8:45 a.m. Vasiliy Sisko, 
wrote:

> Hello @javadevmtl
>
> I failed to reproduce your problem.
> In case of any error in cache command Visor CMD shows message "No caches
> found".
> Please provide logs of visor, server and client nodes after command hang.
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Can we avoid the PME when restarts a node in cluster.

[Ilya Kasnacheev]

Hello!

There is also this ticket: https://issues.apache.org/jira/browse/IGNITE-9420

It is done but not released yet, since 2.8 is not out.

Regards,
-- 
Ilya Kasnacheev


чт, 20 июн. 2019 г. в 15:13, Maxim.Pudov :

> Hi Justin.
> There is no such option. PME speed was significantly improved in recent
> releases though. Consider upgrading to 2.7.5 version.
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: updating a composite Key in Ignite SQL Table

[Maxim.Pudov]

Hi Mahesh,

It is not planned at the moment. I think you could simply replace this with
a DELETE and INSERT as a workaround.



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

Re: Random CorruptedTreeException from Apache Ignite

[Maxim.Pudov]

Hi,
>From the stacktrace I can tell that there is a problem with an index in your
cache. It's hard to tell more from the stacktrace itself. Could you share
the cache config as well?
In the next release (probably 2.8) such exceptions will be better explained
in the logs (https://issues.apache.org/jira/browse/IGNITE-11750).





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

Re: Ignite Visor Cache command hangs indefinitely.

[Vasiliy Sisko]

Hello @javadevmtl

I failed to reproduce your problem. 
In case of any error in cache command Visor CMD shows message "No caches
found".
Please provide logs of visor, server and client nodes after command hang.



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

Re: Ignite on GCP / GKE

[Maxim.Pudov]

Hi Stephane,

Since Ignite is basically just a java process, it's as reliable as any other
java application. You should probably set workDirectory, wal and storage to
a mounted disk in Ignite config if you use persistent data regions and want
your data to survive pod restarts. Those mounted disks are slower than bare
metal, but the difference is not that big.
As far as I know Google Cloud provides a free trial period, so you could try
it.



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

Re: Can we avoid the PME when restarts a node in cluster.

[Maxim.Pudov]

Hi Justin.
There is no such option. PME speed was significantly improved in recent
releases though. Consider upgrading to 2.7.5 version.




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

Re: Stop JVM on network Segmenation

[tarunk]

Thank you for the response Павлухин Иван.

We need this as ignite-nodes are running on aws-ec2 and would like
autoscaling to start new node if one got segmented due to some network
issue.
We are not starting service by commandline script so i think we cant use
RESTART_JVM Segmentation policy.



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

Ignite on GCP / GKE

[Stéphane Gayet]

Hi All,

Does someone have any experience about hosting Ignite on Google GCP / GKE ? I 
read the documentation on Kubernetes deployment on google cloud, but if someone 
can share its experience on:

  *   performances
  *   persistance,
  *   cost,
  *   ...

Thanks

 Stéphane Gayet
 Responsable Développement / Development Manager
[https://storage.letsignit.com/5b884a1a1e0a0f0007c51472/55370421467418375936059118036679301217_5b8eb5cb514093000719db66_8e82e6302fdca8989b5eec24209877fa.png]
   (+33) 1 70 38 70 74 +33 6 00 00 00 00
[https://storage.letsignit.com/5b884a1a1e0a0f0007c51472/317558219157559608341284032890064642484_5b8eb5cb514093000719db66_3c9ea4b29daa57047729e2a2e8dfc4a4.png]
  stephane.ga...@misterfly.com
[https://storage.letsignit.com/5b884a1a1e0a0f0007c51472/178007963808408740710245191003991062821_5b8eb5cb514093000719db66_7f052010d2044c090deb48e04aaa39af.png]
  25 Rue de Ponthieu Bâtiment C 75008 Paris
Vols, Hôtels, Séjours,... Et c'est pas fini !
misterfly.com
 | 
misterflypro.com
 | 
iziwifi.com
[https://storage.letsignit.com/icons/facebook...@2x.png]
[https://storage.letsignit.com/icons/twitter...@2x.png] 

[https://storage.letsignit.com/icons/instagram...@2x.png] 

  [https://storage.letsignit.com/icons/linkedin...@2x.png] 

[https://storage.letsignit.com/5b884a1a1e0a0f0007c51472/276623704557963397770479731125901207279_5b8eb5cb514093000719db66_3931b60112812fe1ed7aac46feb9b92d.png]
[https://storage.letsignit.com/5b884a1a1e0a0f0007c51472/124856704240080447357977399086155886407_5c6bc66ef6d4cf0008f0bac7_f8cdde50fea6f4b2c6d22c96c19f8910.jpg]

Unsubscribe

[Vadim Dedkov]

-- 
___ ___
Best regards,С уважением
Vadim Dedkov.  Вадим Дедков.

Can we avoid the PME when restarts a node in cluster.

[Justin Ji]

Hi Igniters - 

Since the PME may hang the cluster for a while when restarting, so can we
avoid it?



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

updating a composite Key in Ignite SQL Table

[mahesh76private]

Hi, 

We know, currently, a composite key cannot be updated in a SQL table. 

What would be useful is 
if an update to a composite key, does not cause a conflict with other keys,
then it should be allowed
however, if the update causes a duplicate, an exception should be thrown

Could this feature be supported in future?

regards






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