Re: Apache Ignite 2.8.0: Node Metrics System View doesn't exist

[Denis Magda]

Nikolay, could you please join the thread? Probably, that's a known
limitation that should be addressed soon.

-
Denis


On Tue, Apr 28, 2020 at 3:42 AM ivan.fedorenkov 
wrote:

> Hello!
>
> According to documentation
> https://apacheignite.readme.io/docs/system-views ignite should expose the
> Node Metrics System View. However there is no such view in the code (
> org.apache.ignite.spi.systemview.view package). Is it a peace of
> not-implemented-yet feature or is it a bug in the documentation?
>
> Reference to SO question:
>
> https://stackoverflow.com/questions/61410519/apache-ignite-2-8-0-node-metrics-system-view-doesnt-exist/61461243
>
>
> Best regards,
> Ivan Fedorenkov
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: unsubscribe

[Denis Magda]

Hi Gordon,

You need to send an email to user-unsubscr...@ignite.apache.org to
unsubscribe.

Btw, did Ignite work out for your use case or you found a better solution?
Just curios.

-
Denis


On Wed, Apr 29, 2020 at 3:29 PM Gordon Reid (Nine Mile) <
gordon.r...@ninemilefinancial.com> wrote:

> unsubscribe
>
>
> This email and any attachments are proprietary & confidential and are
> intended solely for the use of the individuals to whom it is addressed. Any
> views or opinions expressed are solely for those of the author and do not
> necessarily reflect those of Nine Mile Financial Pty. Limited. If you have
> received this email in error, please let us know immediately by reply email
> and delete from your system. Nine Mile Financial Pty. Limited. ABN: 346
> 1349 0252
>

unsubscribe

[Gordon Reid (Nine Mile)]

unsubscribe


This email and any attachments are proprietary & confidential and are intended 
solely for the use of the individuals to whom it is addressed. Any views or 
opinions expressed are solely for those of the author and do not necessarily 
reflect those of Nine Mile Financial Pty. Limited. If you have received this 
email in error, please let us know immediately by reply email and delete from 
your system. Nine Mile Financial Pty. Limited. ABN: 346 1349 0252

Re: Continuous query setPageSize and setTimeInterval question

[akorensh]

You are correct. Your local reciever will get an update every 100 entries.

setPageSize sets the number of entries to batch together before sending.
When the server has accumulated a number of entries larger than getPageSize
it sends a message to the receiver. 

Like I mentioned before, setIntervalSize() allows you to send a batch every
set interval irrespective of whether pageSize has been reached or not

from the doc:
https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/cache/query/ContinuousQuery.html

Continuous queries allow registering a remote filter and a local listener
for cache updates. 
If an update event passes the filter, it will be sent to the node that
executed the query, and local listener will be notified.



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

Re: Random2LruPageEvictionTracker causing hanging in our integration tests

[scottmf]

Hi Anton,Just to be clear, the stack trace is from a thread dump that I took
while the process was hanging indefinitely.

Although I can reproduce this easily in my service, I can't share the code
with you.  I'll attempt to get a generic use case to hang in this manner and
post it to github.

The full stack is below.

No use-case in this particular scenario for eviction.  Like I said, it is
just for integration testing.  My only concern is to ensure that there is no
bug that would hit us in production.

It is eviction for an in-memory cluster, no persistence, on-heap or near
cache.

"Test worker" #22 prio=5 os_prio=31 cpu=299703.41ms elapsed=317.18s
tid=0x7ff3cfc8c800 nid=0x7203 runnable  [0x75b38000]  
java.lang.Thread.State: RUNNABLEat
org.apache.ignite.internal.processors.cache.persistence.evict.Random2LruPageEvictionTracker.evictDataPage(Random2LruPageEvictionTracker.java:152)
at
org.apache.ignite.internal.processors.cache.persistence.IgniteCacheDatabaseSharedManager.ensureFreeSpace(IgniteCacheDatabaseSharedManager.java:1086)
at
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.ensureFreeSpace(GridCacheMapEntry.java:4513)
at
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.innerSet(GridCacheMapEntry.java:1461)
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxLocalAdapter.userCommit(IgniteTxLocalAdapter.java:745)
at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.localFinish(GridNearTxLocal.java:3850)
at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxFinishFuture.doFinish(GridNearTxFinishFuture.java:440)
at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxFinishFuture.finish(GridNearTxFinishFuture.java:390)
at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal$25.apply(GridNearTxLocal.java:4129)
at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal$25.apply(GridNearTxLocal.java:4118)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:399)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:354)
at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.commitNearTxLocalAsync(GridNearTxLocal.java:4118)
at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.commit(GridNearTxLocal.java:4086)
at
org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor$4.applyx(DataStructuresProcessor.java:587)
at
org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor$4.applyx(DataStructuresProcessor.java:556)
at
org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor.retryTopologySafe(DataStructuresProcessor.java:1664)
at
org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor.getAtomic(DataStructuresProcessor.java:556)
at
org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor.reentrantLock(DataStructuresProcessor.java:1361)
at
org.apache.ignite.internal.IgniteKernal.reentrantLock(IgniteKernal.java:4136)
at jdk.internal.reflect.GeneratedMethodAccessor713.invoke(Unknown Source)   
at
jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(java.base@11.0.5/DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(java.base@11.0.5/Method.java:566)at
com.example.symphony.cmf.ignite.IgniteInitializer$1.invoke(IgniteInitializer.java:158)
at com.sun.proxy.$Proxy205.reentrantLock(Unknown Source)at
com.example.data.store.jdbc.cache.CacheService.getCount(CacheService.java:47)
at
com.example.data.store.jdbc.cache.CacheService$$FastClassBySpringCGLIB$$7efa9131.invoke()
at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:218)
at
org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:771)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
at
org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:749)
at
org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:88)
at io.micrometer.core.aop.TimedAspect.processWithTimer(TimedAspect.java:105)
at io.micrometer.core.aop.TimedAspect.timedMethod(TimedAspect.java:94)  at
jdk.internal.reflect.GeneratedMethodAccessor712.invoke(Unknown Source)  at
jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(java.base@11.0.5/DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(java.base@11.0.5/Method.java:566)at
org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:644)
at
org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:633)
at

Re: Ignite Data loss

[Evgenii Zhuravlev]

Hi,

Please attach full logs from all nodes for investigation.

ср, 29 апр. 2020 г. в 06:48, krkumar24061...@gmail.com <
krkumar24061...@gmail.com>:

> Checked the logs and nothing like that happened where went down.
>
> Thanx and Regards,
> KR Kumar
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Ignite Data loss

[krkumar24061...@gmail.com]

Checked the logs and nothing like that happened where went down.

Thanx and Regards,
KR Kumar



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

Re: There is a bug in the ValidationOnNodeJoinUtils class

[Stephen Darlington]

Can you open a ticket? You’ve clearly done a lot of work here already. Do you 
have a reproducer, or a patch even?

> On 29 Apr 2020, at 09:52, hulitao198758  wrote:
> 
> The validation class ValidationOnNodeJoinUtils has been added. It does not
> matter if the write cache is not configured. After the cache is configured
> in the cache, it will verify ctx.discovery (). CacheAffinityNode
> (ctx.discovery (). LocalNode (), cc. getName () this method, ctx.discovery
> (). localNode () this method returns null and then reports an error
> 
> 
> 
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/

There is a bug in the ValidationOnNodeJoinUtils class

[hulitao198758]

The validation class ValidationOnNodeJoinUtils has been added. It does not
matter if the write cache is not configured. After the cache is configured
in the cache, it will verify ctx.discovery (). CacheAffinityNode
(ctx.discovery (). LocalNode (), cc. getName () this method, ctx.discovery
(). localNode () this method returns null and then reports an error



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

Re: Regarding EVT_NODE_SEGMENTED event

[VeenaMithare]

Thanks Ilya, 

Let me try.

regards
Veena.



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