Re: Question in Continuous Query Remote Filter

[Evgenii Zhuravlev]

Hi,

You can just stop the CQ and then register it again if you don't want to
get notifications for some period of time.

Evgenii

пт, 31 июл. 2020 г. в 01:51, Devakumar J :

> Hi All,
>
> We have a setup of 2 servers and 1 client Node. Client node registers CQ on
> set of caches.
>
> I just want to temporarily pause and resume CQ notifications based on
> certain action at client node.
>
> I was trying to achieve this through remote filter and ignite messaging. I
> mean client publish message to all the server nodes to flip the boolean
> flag. And remote filter will return true or false based on the flag.
>
> The behavior was inconsistent. Sometime it works and some time i dont see
> even the CQ registered properly and when i query SYS.CONTINUOUS_QUERIES,
> getting some invalid state exception.
>
> Is there any other way of pausing and resuming CQ notification based on
> client side event?
>
> Thanks & Regards,
> Devakumar J
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Log file not found with Ignite 2.8.1

[Evgenii Zhuravlev]

Are you sure that this configuration file was applied? On the node start,
it prints info about log to the System.out, so, I would recommend checking
the console.

Best Regards,
Evgenii

чт, 30 июл. 2020 г. в 05:51, manueltg89 :

> Hi all!
>
> I have a Ignite app with version 2.8.1, I've followed this steps
> https://apacheignite.readme.io/docs/logging for Log4j, but my app is not
> created the log file. I attach my log4j.xml file.
>
> Any suggestion?
> Thanks in advance. log4j.xml
> 
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Effective Monitoring of Rebalancing

[Denis Magda]

John,

If it's still relevant for you, now you can monitor rebalancing progress
with a special widget of Control Center:
https://www.gridgain.com/docs/control-center/latest/monitoring/configuring-widgets#rebalance-widget

-
Denis


On Fri, Jan 17, 2020 at 12:33 AM John Gardner 
wrote:

> I've found a similar request from Evgenii Zhuravlev in December 2019, and
> some solutions, but I was hoping that these metrics were available via the
> REST API?
>
> John
>
> On Fri, 17 Jan 2020 at 08:19, John Gardner 
> wrote:
>
>> Hi everyone
>>
>> We've been using Ignite (actually GridGain) in AWS for a couple of years,
>> but in a very basic way.  Now we're in a position to use a lot more of the
>> functionality we need to start monitoring valid metrics more and
>> subsequently alert on issues.
>>
>> We're trying to automate our processes as much as possible using CI and
>> CodeDeploy, but we really need to understand when the entire cluster is
>> rebalanced successfully, because only then can we trigger further
>> autonomous operations.
>>
>> What tricks and techniques is everybody using for this?
>>
>> Thanks in advance.
>>
>> John
>>
>>
>
> --
>
> 
> John Gardner
> Infrastructure Manager
>
> W: www.salecycle.com 
> [image: Email Marketing in a Privacy Conscious World - Download Report]
> 
>

Re: Does user thread interruption impact Ignite?

[akurbanov]

Hello,

Does these exceptions impact the cluster in your use-case? I would say that
this should be generally safe to interrupt user threads running on a client
side, but it is hard to say if there is any corner case or a critical
operation that might lead to cluster being impacted with interrupt.

I recall that I mostly aware of cases where this kind of exception was a
consequence rather that a cause.

Interrupts are also used to timeout a compute task, so I would say that you
should be safe doing the same.

Please post logs if you will ever see issues with interrupts being the cause
of cluster issue.

Best regards,
Anton



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

Re: apache ignite compatibility with armhf(arm 32-bit)

[Ilya Kasnacheev]

Hello!

Try it and see :)

I don't see why it won't work. Maybe there will be some endianness issues,
but you never know in advance.

Regards,
-- 
Ilya Kasnacheev


чт, 23 июл. 2020 г. в 20:54, rakshita04 :

> I need to use apache ignite for my Debian linux 32-bit version.
> Is it compatible with armhf(32-bit arm linux)?
> can i use apache-ignite debian package for the same?
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

[Apache Ignite Virtual Meetup] Building a Blockchain Network with Apache Ignite

[Kseniya Romanova]

Hi Igniters!
Recently, we started Virtual Meetup[1]. One of our goals is to create a
space where app developers can share their experience of using Ignite. So,
I’m happy to invite you to a talk by Branimir Angelov on August 11[2].

Branimir will introduce a stream-based, horizontally scalable framework for
asynchronous data processing. The framework is built on top of Apache
Ignite and — Perper[3]. Join us live and ask and receive answers to your
questions about Ignite for blockchain or watch the video later.

If you have a story to share with the group, please contact me or fill out
the form at  https://bit.ly/2Bmq1WT.

Cheers, Kseniya

[1] https://www.meetup.com/Apache-Ignite-Virtual-Meetup/

[2] https://www.meetup.com/Apache-Ignite-Virtual-Meetup/events/271920068/

[3] https://github.com/obecto/perper

IgniteTxOptimisticCheckedException

[marble.zh...@coinflex.com]

Hi Guru, 

We met below two kinds of Optimistic exceptions when doing the transactions,
we use OPTIMISTIC and SERIALIZABLE isolation, do you have any suggestions,
or if we change to PESSIMISTIC, any risks on that, such as performance or
other exceptions? thanks.

{"log":"Caused by:
org.apache.ignite.internal.transactions.IgniteTxOptimisticCheckedException:
Failed to prepare transaction, read/write conflict [key=92-USD,
keyCls=java.lang.String, val=Balance(accountId=92, instrumentId=USD,
quantity=2307.812920282500, reserved=0, lastUpdated=2020-07-31
03:10:36.889, lastUpdatedEvent=TRANSFER, tradeType=null),
valCls=ignite.entity.Balance, cache=Balance, thread=IgniteThread
[compositeRwLockIdx=7, stripe=4, plc=-1, holdsTopLock=false,
forbiddenToRequestBinaryMetadata=false,
name=sys-stripe-4-#5]]\n","stream":"stderr","time":"2020-07-31T03:10:36.953698541Z"}


{"log":"Caused by:
org.apache.ignite.internal.transactions.IgniteTxOptimisticCheckedException:
Failed to prepare transaction (lock conflict): GridDhtTxLocal
[nearNodeId=7e3589a0-c829-42a2-8fb4-115c57ba64f5,
nearFutId=3077cc2a371-7364caca-357e-49f2-840e-a101e7c64fa8, nearMiniId=1,
nearFinFutId=null, nearFinMiniId=0, nearXidVer=GridCacheVersion
[topVer=207644034, order=1596164732765, nodeOrder=2], lb=null,
super=GridDhtTxLocalAdapter [nearOnOriginatingNode=false,
nearNodes=KeySetView [], dhtNodes=KeySetView [], explicitLock=false,
super=IgniteTxLocalAdapter [completedBase=null, sndTransformedVals=false,
depEnabled=false, txState=IgniteTxStateImpl [activeCacheIds=[1325467324],
recovery=false, mvccEnabled=false, mvccCachingCacheIds=[], txMap=ArrayList
[IgniteTxEntry [txKey=IgniteTxKey [key=KeyCacheObjectImpl [part=45,
val=92-USD, hasValBytes=true], cacheId=1325467324], val=[op=UPDATE,
val=ignite.entity.Balance [idHash=1055847466, hash=-1577210704,
accountId=92, lastUpdated=2020-07-31 03:10:36.943,
quantity=1204.259920282500, reserved=null, instrumentId=USD,
tradeType=null, lastUpdatedEvent=TRANSFER]], 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=false,
entry=GridDhtCacheEntry [rdrs=ReaderId[] [], part=45,
super=GridDistributedCacheEntry [super=GridCacheMapEntry
[key=KeyCacheObjectImpl [part=45, val=92-USD, hasValBytes=true],
val=null, ver=GridCacheVersion [topVer=207644034, order=1596164732830,
nodeOrder=1], hash=-148923086, extras=GridCacheObsoleteEntryExtras
[obsoleteVer=GridCacheVersion [topVer=2147483647, order=0, nodeOrder=0]],
flags=2]]], prepared=1, locked=false, nodeId=null, locMapped=false,
expiryPlc=null, transferExpiryPlc=false, flags=0, partUpdateCntr=0,
serReadVer=GridCacheVersion [topVer=207644034, order=1596164732670,
nodeOrder=1], xidVer=null], IgniteTxEntry [txKey=IgniteTxKey
[key=KeyCacheObjectImpl [part=504, val=1380978-USD, hasValBytes=true],
cacheId=1325467324], val=[op=UPDATE, val=ignite.entity.Balance
[idHash=577969755, hash=-2001853349, accountId=1380978,
lastUpdated=2020-07-31 03:10:36.95, quantity=13614077.57624000,
reserved=null, instrumentId=USD, tradeType=null,
lastUpdatedEvent=TRANSFER]], 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=false,
entry=GridDhtCacheEntry [rdrs=ReaderId[] [], part=504,
super=GridDistributedCacheEntry [super=GridCacheMapEntry
[key=KeyCacheObjectImpl [part=504, val=1380978-USD, hasValBytes=true],
val=null, ver=GridCacheVersion [topVer=0, order=0, nodeOrder=0],
hash=1004605465, extras=null, flags=0]]], prepared=0, locked=false,
nodeId=null, locMapped=false, expiryPlc=null, transferExpiryPlc=false,
flags=0, partUpdateCntr=0, serReadVer=GridCacheVersion [topVer=207644034,
order=1596164732670, nodeOrder=1], xidVer=null]]], super=IgniteTxAdapter
[xidVer=GridCacheVersion [topVer=207644034, order=1596164732835,
nodeOrder=1], writeVer=null, implicit=false, loc=true, threadId=146,
startTime=1596165036958, nodeId=990fbcf8-4105-4aee-b03f-bef9141f5533,
startVer=GridCacheVersion [topVer=207644034, order=1596164732835,
nodeOrder=1], endVer=null, isolation=SERIALIZABLE, concurrency=OPTIMISTIC,
timeout=0, sysInvalidate=false, sys=false, plc=2, commitVer=null,
finalizing=NONE, invalidParts=null, state=MARKED_ROLLBACK, timedOut=false,
topVer=AffinityTopologyVersion [topVer=4, minorTopVer=1], mvccSnapshot=null,
skipCompletedVers=false, parentTx=null, duration=0ms, onePhaseCommit=false],
size=2]]]\n","stream":"stderr","time":"2020-07-31T03:10:37.002484848Z"}



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

Question in Continuous Query Remote Filter

[Devakumar J]

Hi All,

We have a setup of 2 servers and 1 client Node. Client node registers CQ on
set of caches.

I just want to temporarily pause and resume CQ notifications based on
certain action at client node.

I was trying to achieve this through remote filter and ignite messaging. I
mean client publish message to all the server nodes to flip the boolean
flag. And remote filter will return true or false based on the flag.

The behavior was inconsistent. Sometime it works and some time i dont see
even the CQ registered properly and when i query SYS.CONTINUOUS_QUERIES,
getting some invalid state exception.

Is there any other way of pausing and resuming CQ notification based on
client side event?

Thanks & Regards,
Devakumar J



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