Re: Using @SpringResource & @SpringApplicationContextResource in IgniteCallable

2020-10-15 Thread ashishb888
Please help



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


Re: ApacheCon talk available

2020-10-15 Thread Andrey Gura
Saikat,

thanks a lot! *applause*

On Fri, Oct 16, 2020 at 12:11 AM Saikat Maitra  wrote:
>
> Hi,
>
> My talk about Data Streaming using Apache Flink and Apache Ignite in
> ApacheCon is available now
>
> https://www.youtube.com/watch?v=n74HMmTz5i0
>
> Regards,
> Saikat


ApacheCon talk available

2020-10-15 Thread Saikat Maitra
Hi,

My talk about Data Streaming using Apache Flink and Apache Ignite in
ApacheCon is available now

https://www.youtube.com/watch?v=n74HMmTz5i0

Regards,
Saikat


Re: 3.0 and messaging

2020-10-15 Thread Pavel Tupitsyn
Hi Mikael,

Please check the discussion on the dev list [1]

In short:
- Messaging can be simulated with Services and/or Compute to some extent
- Some people have the same concern as you,
  so it is not clear yet whether we are going to remove messaging or not

[1]
http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-3-0-td48671i20.html

On Thu, Oct 15, 2020 at 8:28 PM Mikael  wrote:

> Hi!
>
> It sounds like the messaging API will be removed from 3.0, is that
> correct ? I use the messaging a lot so in that case I guess I have to
> work out some other solution for sending messages between nodes, any
> idea on the best solution for this ?
>
>
>


Continuous query not transactional ?

2020-10-15 Thread VeenaMithare
Hi ,

This is in continuation of the below statement on this post : 
http://apache-ignite-users.70518.x6.nabble.com/Lag-before-records-are-visible-after-transaction-commit-tp33787p33861.html

>>Continuous Query itself is not transactional and it looks like it can't be
used for this at the moment. So, it gets notification before other entries
were committed.

Does this mean we could get dirty reads as updates in continuous query ?
i.e. for eg if the code is as below:
1. Start transaction  
2. update records of cache a
3. update records of cache b
4. update records for cache c
5. commit

if update of cache a succeeds , but update of cache b fails, will the local
listener for continuous query for 'cache a' get an update ?

regards,
Veena.


regards
Veena.



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


Re: Lag before records are visible after transaction commit

2020-10-15 Thread VeenaMithare
Hi , 

>>Continuous Query itself is not transactional and it looks like it can't be
used for this at the moment. So, it gets notification before other entries
were committed.

Does this mean we could get dirty reads as updates in continuous query ?
i.e. for eg if the code is as below:
1. Start transaction  
2. update records of cache a
3. update records of cache b 
4. update records for cache c
5. commit

if update of cache a succeeds , but update of cache b fails, will the local
listener for continuous query for 'cache a' get an update ?

regards,
Veena.


regards
Veena.



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


3.0 and messaging

2020-10-15 Thread Mikael

Hi!

It sounds like the messaging API will be removed from 3.0, is that 
correct ? I use the messaging a lot so in that case I guess I have to 
work out some other solution for sending messages between nodes, any 
idea on the best solution for this ?





Re: Different cache expiry policy each node..

2020-10-15 Thread Ilya Kasnacheev
Hello!

You can also use cache.withExpiryPolicy() to adjust that on the fly since
it's really a property of data.

Regards,
-- 
Ilya Kasnacheev


ср, 14 окт. 2020 г. в 05:19, kay :

> Hello, I have 4 server nodes.
>
> and each node have a cache with 4minutes Modified expirypolicy..
>
> I restarted 1 node for change expirypolicy to 10minutes..
>
> Is it apply to expiryPolicy for other node?? or I have to start other 3
> nodes also??
>
> Thank you so much
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>


Re: Ignite instance fails. Unsure as to root cause

2020-10-15 Thread Ilya Kasnacheev
Hello!

Oct 12 17:49:41 nalrcsvridbq02 kernel: watchdog: BUG: soft lockup - CPU#0
stuck for 38s! [kworker/u256:0:3703404]

This is bad. Your system kernel says your CPU#0 was hanging for 38 seconds.

This is enough to trigger failure detection timeout and kill and instance,
or at least for the node to be segmented from cluster by the other nodes.

Regards,
-- 
Ilya Kasnacheev


ср, 14 окт. 2020 г. в 16:00, bbellrose :

> Oct 12 17:47:39 nalrcsvridbq02 Ignite[2031634]: [17:47:39] Possible failure
> suppressed accordingly to a configured handler
> [hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0,
> super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet
> [SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]],
> failureCtx=FailureContext [type=SYSTEM_WORKER_BLOCKED, err=class
> o.a.i.IgniteException: GridWorker [name=nio-acceptor-tcp-comm,
> igniteInstanceName=RailConnect Ignite QA Grid, finished=false,
> heartbeatTs=1602539219763]]]
> Oct 12 17:48:20 nalrcsvridbq02 Ignite[2031634]: [17:48:20] Possible failure
> suppressed accordingly to a configured handler
> [hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0,
> super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet
> [SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]],
> failureCtx=FailureContext [type=SYSTEM_WORKER_BLOCKED, err=class
> o.a.i.IgniteException: GridWorker [name=grid-nio-worker-tcp-comm-1,
> igniteInstanceName=RailConnect Ignite QA Grid, finished=false,
> heartbeatTs=1602539260020]]]
> Oct 12 17:48:20 nalrcsvridbq02 Ignite[2031634]: [17:48:20] Possible failure
> suppressed accordingly to a configured handler
> [hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0,
> super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet
> [SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]],
> failureCtx=FailureContext [type=SYSTEM_WORKER_BLOCKED, err=class
> o.a.i.IgniteException: GridWorker [name=ttl-cleanup-worker,
> igniteInstanceName=RailConnect Ignite QA Grid, finished=false,
> heartbeatTs=1602539260020]]]
> Oct 12 17:48:20 nalrcsvridbq02 Ignite[2031634]: [17:48:20] Possible failure
> suppressed accordingly to a configured handler
> [hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0,
> super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet
> [SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]],
> failureCtx=FailureContext [type=SYSTEM_WORKER_BLOCKED, err=class
> o.a.i.IgniteException: GridWorker [name=db-checkpoint-thread,
> igniteInstanceName=RailConnect Ignite QA Grid, finished=false,
> heartbeatTs=1602539260006]]]
> Oct 12 17:49:00 nalrcsvridbq02 chronyd[1216]: Forward time jump detected!
> Oct 12 17:49:00 nalrcsvridbq02 chronyd[1216]: Can't synchronise: no
> selectable sources
> Oct 12 17:49:00 nalrcsvridbq02 process-agent[2039258]: 2020-10-12 17:49:00
> EDT | PROCESS | INFO | (collector.go:209 in func1) | Delivery queues:
> process[size=0, weight=0], pod[size=0, weight=0]
> Oct 12 17:49:00 nalrcsvridbq02 agent[2039257]: 2020-10-12 17:49:00 EDT |
> CORE | ERROR | (pkg/forwarder/worker.go:178 in process) | Error while
> processing transaction: error while sending transaction, rescheduling it:
> Post
>
> https://7-22-1-app.agent.datadoghq.com/api/v1/series?api_key=*44602
> :
> net/http: request canceled (Client.Timeout exceeded while awaiting headers)
> Oct 12 17:49:00 nalrcsvridbq02 trace-agent[2039259]: 2020-10-12 17:49:00
> EDT
> | TRACE | INFO | (pkg/trace/info/stats.go:101 in LogStats) | No data
> received
> Oct 12 17:49:00 nalrcsvridbq02 Ignite[2031634]: [17:49:00] Topology
> snapshot
> [ver=21, locNode=2eca41b3, servers=1, clients=0, state=ACTIVE, CPUs=2,
> offheap=2.0GB, heap=0.25GB]
> Oct 12 17:49:00 nalrcsvridbq02 Ignite[2031634]: [17:49:00]   ^-- Baseline
> [id=0, size=2, online=1, offline=1]
> Oct 12 17:49:00 nalrcsvridbq02 Ignite[2031634]: [17:49:00] (err) Failed to
> execute compound future reducer: GridNearTxFinishFuture
> [futId=7a28b630571-b3eac955-0171-4b45-b048-84653e88427e, tx=GridNearTxLocal
> [mappings=IgniteTxMappingsSingleImpl [mapping=GridDistributedTxMapping
> [entries=LinkedHashSet [IgniteTxEntry [txKey=IgniteTxKey
> [key=KeyCacheObject
> [hasValBytes=true], cacheId=-27866919], val=BinaryObject
> [idHash=1523169004,
> hash=1743117496][op=CREATE, val=], prevVal=[op=NOOP, val=null],
> oldVal=[op=NOOP, val=null], entryProcessorsCol=null, ttl=-1,
> conflictExpireTime=-1, conflictVer=null, explicitVer=null, dhtVer=null,
> filters=CacheEntryPredicate[] [], filtersPassed=false, filtersSet=true,
> entry=GridDhtDetachedCacheEntry [super=GridDistributedCacheEntry
> [super=GridCacheMapEntry [key=KeyCacheObject [hasValBytes=true], val=null,
> ver=GridCacheVersion [topVer=0, order=0, nodeOrder=0], hash=684422756,
> extras=null, flags=0]]], prepared=0, locked=false,
> nodeId=3f8b7981-ee81-4ca4-9f52-5c6f03cb8cee, locMapped=false,
> expiryPlc=null, transferExpiryPlc=false, flags=2, partUpdateCntr=0,
> 

Re: java.lang.IllegalStateException: Getting affinity for too old topology version that is already out of history

2020-10-15 Thread Ilya Kasnacheev
Hello!

Why not, if it fixes the issue for you. Then you can try 2.9.0 once it is
out.

Unfortunately, a small snippet of server log is not sufficient, complete
log is needed. I can already spot some communication problems, though.

Regards,
-- 
Ilya Kasnacheev


чт, 15 окт. 2020 г. в 09:50, swara :

> Hello
>
> We are using this type of cache design from last 3 years with 2.5.6
> version.
> we never got any issue.
> When we upgraded to 2.8.1 we are getting this type of errors.
> Should we downgrade to 2.8.0 or 2.5.6. Please suggest?
>
> Thank You
> Swara
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>


Re: java.lang.IllegalStateException: Getting affinity for too old topology version that is already out of history

2020-10-15 Thread swara
Hello

We are using this type of cache design from last 3 years with 2.5.6 version.
we never got any issue. 
When we upgraded to 2.8.1 we are getting this type of errors.
Should we downgrade to 2.8.0 or 2.5.6. Please suggest?

Thank You
Swara



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