Re: How data region is propagated to other nodes

[dhiman_nikhil]

As per documentation, I can do persistence in data region only. If I wanted a
cache key to be persisted then I have to make sure that data region to be
replicated across all nodes. 

Basically, my requirement is to give multi-tenancy support[Multiple
Applications can communicate to Ignite Cluster]. To prevent conflict of
CacheKey, I will be writing an Ignite Client[Wrapper over IgniteClient
library] and passing on the limiting functionality to Services[Like they can
get CacheKey, but not been able to create it]. 

If a new Application comes and demands a CacheKey with persistence ON, we
should be able to provide it without reloading the whole nodes of Ignite
cluster.



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

Two DataStreamer pods for load balancing on Kubernetes

[sheshananda]

HI,

I am using DataStreamer to load data from KAFKA to IGNITE.

When we inject data with one DataStreamer pod we are able to see logs on
DataStreamer pod.

Similarly, when we try with with two DataStreamer  pods  logs are coming
only on 1st pod. we are not getting any logs for the 2nd pod.

Both DataStreamer pods are in same consumerGroup.

Please let me know the configurations to use multiple DataStreamer for load
balancing.

Thanks and Regards
Sheshananda



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

Re: Issues with Clients joining cluster on Kubernetes (EKS)

[aes]

Sure, set preferIPv4 on the client, and set IGNITE_QUIET to false. logs
attached. Thank you!!

serverLogs.serverLogs

  
clientLogs.clientLogs

  



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

Creating off-heap REPLICATED cache with Eviction policies borks the cluster.

[John Smith]

Hi running 2.7.0,

I have a 4 node cluster running with off-heap persistence works great!

I then by mistake tried to create a REPLICATED cache with
LruEvictionPolicy. So we know if the cache is off-heap mode it cannot be
created.

But this seems to have borked the cluster, it shut down and now it will no
longer start... THE ONLY WAY TO RECOVER IS TO DELETE THE WORK folder.

[19:47:01,758][SEVERE][exchange-worker-#43%xx%][CacheAffinitySharedManager]
Failed to initialize cache. Will try to rollback cache start routine.
[cacheName=xx]
class org.apache.ignite.IgniteCheckedException: Onheap cache must be
enabled if eviction policy is configured [cacheName=xx]
...
[19:47:01,759][INFO][exchange-worker-#43%xx%][GridCacheProcessor] Can
not finish proxy initialization because proxy does not exist,
cacheName=xx, localNodeId=a45103eb-4fe1-4b10-8d2a-3e46b5186068
...
[19:47:01,972][INFO][exchange-worker-#43%xx%][GridCacheDatabaseSharedManager]
Finished applying WAL changes [updatesApplied=0, time=178ms]
[19:47:01,972][INFO][exchange-worker-#43%xx%][GridCacheDatabaseSharedManager]
Logical recovery performed in 173 ms.
...
[19:47:01,978][SEVERE][exchange-worker-#43%xx%][GridDhtPartitionsExchangeFuture]
Failed to reinitialize local partitions (rebalancing will be stopped):
GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=4,
minorTopVer=1], discoEvt=DiscoveryCustomEvent
[customMsg=ChangeGlobalStateMessage
[id=994851a7a61-2637d9af-479a-455f-8408-c3f6e4a28782,
reqId=746a7c79-2921-4e3f-8b2c-22d43c0c0c6d,
initiatingNodeId=cda68e29-5639-4c41-bd50-a9d398f8d7f2, activate=true,
baselineTopology=BaselineTopology [id=0, branchingHash=-999309033,
branchingType='Cluster activation',
baselineNodes=[01a3df31-6d32-4386-bb46-847a16b1dea3,
a532b052-9d42-4342-a007-26437525f209, 5369a6f5-edc6-4895-affb-d43b04e2e914,
5b205b68-c665-43ef-937d-90082e22f15e]], forceChangeBaselineTopology=false,
timestamp=1556826421083], affTopVer=AffinityTopologyVersion [topVer=4,
minorTopVer=1], super=DiscoveryEvent [evtNode=TcpDiscoveryNode
[id=cda68e29-5639-4c41-bd50-a9d398f8d7f2, addrs=[0:0:0:0:0:0:0:1%lo,
127.0.0.1, 172.17.17.65], sockAddrs=[ignite-dev-v-0003/172.17.17.65:47500,
/0:0:0:0:0:0:0:1%lo:47500, /127.0.0.1:47500], discPort=47500, order=4,
intOrder=4, lastExchangeTime=1556826394021, loc=false,
ver=2.7.0#20181130-sha1:256ae401, isClient=false], topVer=4,
nodeId8=a45103eb, msg=null, type=DISCOVERY_CUSTOM_EVT,
tstamp=1556826421114]], nodeId=cda68e29, evt=DISCOVERY_CUSTOM_EVT]
java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
...
[19:47:02,081][WARNING][exchange-worker-#43%xx%][FailureProcessor]
Thread dump at 2019/05/02 19:47:02 UTC
Thread [name="ttl-cleanup-worker-#72%xx%", id=125, state=TIMED_WAITING,
blockCnt=0, waitCnt=1]
at java.lang.Thread.sleep(Native Method)
at o.a.i.i.util.IgniteUtils.sleep(IgniteUtils.java:7774)
at
o.a.i.i.processors.cache.GridCacheSharedTtlCleanupManager$CleanupWorker.body(GridCacheSharedTtlCleanupManager.java:149)
at o.a.i.i.util.worker.GridWorker.run(GridWorker.java:120)
at java.lang.Thread.run(Thread.java:748)

Thread [name="sys-#71%xx%", id=124, state=TIMED_WAITING, blockCnt=0,
waitCnt=1]
Lock
[object=java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@15dc7079,
ownerName=null, ownerId=-1]
at sun.misc.Unsafe.park(Native Method)
at
java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
at
java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:467)
at
java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1073)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
...
[19:47:02,086][SEVERE][exchange-worker-#43%xx%][] JVM will be halted
immediately due to the failure: [failureCtx=FailureContext
[type=SYSTEM_WORKER_TERMINATION, err=class o.a.i.IgniteCheckedException:
Index: 0, Size: 0]]

Re: Transactions from Python

[Stéphane Thibaud]

Hello Evgenii,

Thank you for the quick answer. I will follow this feature attentively.


Kind regards,

Stéphane Thibaud

2019年5月2日(木) 17:38 Evgenii Zhuravlev :

> Hi Stéphane
>
> Community is working on this functionality at the moment, here you can
> find design document and discussion regarding this feature:
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-34+Thin+client%3A+transactions+support
>
> Alternatively, you can start to use ODBC from python, now SQL has support
> for Transactions, but it's in beta now, GA release will be available later
> this year I believe.
>
> Best Regards,
> Evgeniii
>
>
>
> чт, 2 мая 2019 г. в 07:15, Stéphane Thibaud :
>
>> Hello Apache Ignite users,
>>
>> I recently started writing my web service using the thin client of Apache
>> Ignite, but was shocked to discover that transactions seem absent in the
>> Python thin client API. Any recommendations?
>>
>>
>> Kind regards,
>>
>> Stéphane Thibaud
>>
>

Ignite 2.7.5

[Loredana Radulescu Ivanoff]

Hello,

Would you happen to have any news about the 2.7.5 release date?

Thank you,
Loredana

Re: How data region is propagated to other nodes

[Evgenii Zhuravlev]

Hi,

No, Data region configuration won't be propagated to other nodes in the
cluster. DataRegion is only a local configuration, so, you have to
configure it on each node. Moreover, these the same data region on
different nodes can have different maxSize, which could be useful in case
of using NodeFilter for caches.

Best Regards,
Evgenii

чт, 2 мая 2019 г. в 14:01, dhiman_nikhil :

> Server level config:
> Server: Node 1
> CacheKey: "location"
> DataRegion: "location"
> persistence: true
>
> Server: Node 2
> CacheKey: "category"
> DataRegion: "category"
> persistence : false
>
> Both belong to same cluster.
> Since Data is partitioned across nodes when I start Node 1 and then Node 2,
> will "location" region is also created in Node 2 since data will be
> partitioned for CacheKey: "location"  ??
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Trouble with continuous queries

[Mike Needham]

I have seen that example, what I do not understand is I have two SQL tables
in a cache that has n number of nodes.  it is loaded ahead of time and a
client wants to be notified when the contents of the cache are changed.  Do
you have to have the continuous query in a never ending loop to not have it
end?  All the examples are simply using ContinuousQuery. my
example uses  which is a java class defining the
structure.  do I just set-up a   ContinuousQuery

On Thu, May 2, 2019 at 3:59 AM aealexsandrov 
wrote:

> Hi,
>
> The good example of how it can be done you can see here:
>
>
> https://github.com/gridgain/gridgain-advanced-examples/blob/master/src/main/java/org/gridgain/examples/datagrid/query/ContinuousQueryExample.java
>
> You can set remote listener to handle changes on remote nodes and local
> listers for current.
>
> Note that you will get the updates only until ContinuousQuery will not be
> closed or until the node that starts it will not left the cluster.
>
> Also, you can try to use CacheEvents like in example here:
>
> https://apacheignite.readme.io/docs/events#section-remote-events
>
> Note that events can affect your performance.
>
> BR,
> Andrei
>
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>


-- 
*Don't be afraid to be wrong. Don't be afraid to admit you don't have all
the answers. Don't be afraid to say "I think" instead of "I know."*

How data region is propagated to other nodes

[dhiman_nikhil]

Server level config:
Server: Node 1  
CacheKey: "location"
DataRegion: "location"
persistence: true

Server: Node 2
CacheKey: "category"
DataRegion: "category"
persistence : false

Both belong to same cluster.
Since Data is partitioned across nodes when I start Node 1 and then Node 2,
will "location" region is also created in Node 2 since data will be
partitioned for CacheKey: "location"  ??



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

Re: Trouble with continuous queries

[aealexsandrov]

Hi,

The good example of how it can be done you can see here:

https://github.com/gridgain/gridgain-advanced-examples/blob/master/src/main/java/org/gridgain/examples/datagrid/query/ContinuousQueryExample.java

You can set remote listener to handle changes on remote nodes and local
listers for current.

Note that you will get the updates only until ContinuousQuery will not be
closed or until the node that starts it will not left the cluster.

Also, you can try to use CacheEvents like in example here:

https://apacheignite.readme.io/docs/events#section-remote-events

Note that events can affect your performance.

BR,
Andrei





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

Re: Transactions from Python

[Evgenii Zhuravlev]

Hi Stéphane

Community is working on this functionality at the moment, here you can find
design document and discussion regarding this feature:
https://cwiki.apache.org/confluence/display/IGNITE/IEP-34+Thin+client%3A+transactions+support

Alternatively, you can start to use ODBC from python, now SQL has support
for Transactions, but it's in beta now, GA release will be available later
this year I believe.

Best Regards,
Evgeniii



чт, 2 мая 2019 г. в 07:15, Stéphane Thibaud :

> Hello Apache Ignite users,
>
> I recently started writing my web service using the thin client of Apache
> Ignite, but was shocked to discover that transactions seem absent in the
> Python thin client API. Any recommendations?
>
>
> Kind regards,
>
> Stéphane Thibaud
>

Re: [EXTERNAL] Re: Replace or Put after PutAsync causes Ignite to hang

[Barney Pippin]

Thanks for the response Ilya. Did you get a chance to look at this Pavel?
Thanks.



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