date:20201119

Re: Query on CVE-2020-5421

2020-11-19 Thread Vladimir Pligin

This issue is definitely web-oriented. It's about the 'Content-Disposition'
custom HTTP header which raised a big deal of concerns about security itself
over time. As far as I currently understand it affects only web part(s) of
Spring, more particularly spring-webmvc. It's not being used by Ignite. So I
suppose it's safe to think that Ignite is not affected by that one.



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

Re: Ignite 2.8.1: Database Closed error

2020-11-19 Thread Evgenii Zhuravlev

Hi,

I don't think it's related to the discovery. In the log, before OOM you can
see the long JVM pause:
 Possible too long JVM pause: 2323 milliseconds.

So, probably you used more heap memory than you had.

What version do you use? How much heap memory do you have? What do you do
with a cluster(SQL, key value operations, etc.)? Also, can you share full
logs?

I would recommend collecting heap dump and checking objects that use memory
there.

Evgenii

чт, 19 нояб. 2020 г. в 09:16, Mahesh Renduchintala <
mahesh.renduchint...@aline-consulting.com>:

> Hi,
>
>
> Any pointers on what the below error means.
> There seems to be an out of memory on discoverySPI.  what can cause this?
>
>
>
>
> ^--   TxLog region [used=0MB, free=100%, comm=100MB]
> ^-- Ignite persistence [used=50071MB]
> ^--   sysMemPlc region [used=0MB]
> ^--   default region [used=50071MB]
> ^--   metastoreMemPlc region [used=0MB]
> ^--   TxLog region [used=0MB]
> ^-- Outbound messages queue [size=0]
> ^-- Public thread pool [active=0, idle=0, qSize=0]
> ^-- System thread pool [active=0, idle=1, qSize=0]
> [16:29:45,630][INFO][exchange-worker-#85][GridCachePartitionExchangeManager]
> Skipping rebalancing (nothing scheduled) [top=AffinityTopologyVersion
> [topVer=2016, minorTopVer=0], force=true, evt=DISCOVERY>
> [16:30:12,877][WARNING][jvm-pause-detector-worker][IgniteKernal] Possible
> too long JVM pause: 2323 milliseconds.
> [16:30:12,877][INFO][tcp-disco-srvr-[:47500]-#3][TcpDiscoverySpi] TCP
> discovery accepted incoming connection [rmtAddr=/192.168.10.137,
> rmtPort=39599]
> [16:30:12,882][SEVERE][tcp-disco-client-message-worker-[9a0c020b
> 192.168.1.9:61059]-#1560][TcpDiscoverySpi] Runtime error caught during
> grid runnable execution: GridWorker [name=tcp-disco-client-message>
> java.lang.OutOfMemoryError: Java heap space
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.addConditionWaiter(AbstractQueuedSynchronizer.java:1855)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2068)
> at
> java.util.concurrent.LinkedBlockingDeque.pollFirst(LinkedBlockingDeque.java:522)
> at
> java.util.concurrent.LinkedBlockingDeque.poll(LinkedBlockingDeque.java:684)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorker.body(ServerImpl.java:7761)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerThread.body(ServerImpl.java:7697)
> at
> org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:61)
> [16:30:12,883][INFO][tcp-disco-srvr-[:47500]-#3][TcpDiscoverySpi] TCP
> discovery spawning a new thread for connection [rmtAddr=/192.168.10.137,
> rmtPort=39599]
> [16:30:12,883][SEVERE][query-#218652][GridMapQueryExecutor] Failed to
> execute local query.
> class org.apache.ignite.IgniteCheckedException: Failed to execute SQL
> query. The database has been closed [90098-197]
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQuery(IgniteH2Indexing.java:874)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQueryWithTimer(IgniteH2Indexing.java:955)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor.onQueryRequest0(GridMapQueryExecutor.java:412)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor.onQueryRequest(GridMapQueryExecutor.java:241)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.onMessage(IgniteH2Indexing.java:2186)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.lambda$start$17(IgniteH2Indexing.java:2139)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$ArrayListener.onMessage(GridIoManager.java:3386)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1847)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1472)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$5200(GridIoManager.java:229)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1367)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.h2.jdbc.JdbcSQLException: The database has been closed
> [90098-197]
> at
> org.h2.message.DbException.getJdbcSQLException(DbException.java:357)
> at org.h2.message.DbException.get(DbException.java:179)
> at org.h2.message.DbException.get(DbException.java:155)
>

Ignite 2.8.1: Database Closed error

2020-11-19 Thread Mahesh Renduchintala

Hi,


Any pointers on what the below error means.
There seems to be an out of memory on discoverySPI.  what can cause this?




^--   TxLog region [used=0MB, free=100%, comm=100MB]
^-- Ignite persistence [used=50071MB]
^--   sysMemPlc region [used=0MB]
^--   default region [used=50071MB]
^--   metastoreMemPlc region [used=0MB]
^--   TxLog region [used=0MB]
^-- Outbound messages queue [size=0]
^-- Public thread pool [active=0, idle=0, qSize=0]
^-- System thread pool [active=0, idle=1, qSize=0]
[16:29:45,630][INFO][exchange-worker-#85][GridCachePartitionExchangeManager] 
Skipping rebalancing (nothing scheduled) [top=AffinityTopologyVersion 
[topVer=2016, minorTopVer=0], force=true, evt=DISCOVERY>
[16:30:12,877][WARNING][jvm-pause-detector-worker][IgniteKernal] Possible too 
long JVM pause: 2323 milliseconds.
[16:30:12,877][INFO][tcp-disco-srvr-[:47500]-#3][TcpDiscoverySpi] TCP discovery 
accepted incoming connection [rmtAddr=/192.168.10.137, rmtPort=39599]
[16:30:12,882][SEVERE][tcp-disco-client-message-worker-[9a0c020b 
192.168.1.9:61059]-#1560][TcpDiscoverySpi] Runtime error caught during grid 
runnable execution: GridWorker [name=tcp-disco-client-message>
java.lang.OutOfMemoryError: Java heap space
at 
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.addConditionWaiter(AbstractQueuedSynchronizer.java:1855)
at 
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2068)
at 
java.util.concurrent.LinkedBlockingDeque.pollFirst(LinkedBlockingDeque.java:522)
at 
java.util.concurrent.LinkedBlockingDeque.poll(LinkedBlockingDeque.java:684)
at 
org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorker.body(ServerImpl.java:7761)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at 
org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerThread.body(ServerImpl.java:7697)
at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:61)
[16:30:12,883][INFO][tcp-disco-srvr-[:47500]-#3][TcpDiscoverySpi] TCP discovery 
spawning a new thread for connection [rmtAddr=/192.168.10.137, rmtPort=39599]
[16:30:12,883][SEVERE][query-#218652][GridMapQueryExecutor] Failed to execute 
local query.
class org.apache.ignite.IgniteCheckedException: Failed to execute SQL query. 
The database has been closed [90098-197]
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQuery(IgniteH2Indexing.java:874)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQueryWithTimer(IgniteH2Indexing.java:955)
at 
org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor.onQueryRequest0(GridMapQueryExecutor.java:412)
at 
org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor.onQueryRequest(GridMapQueryExecutor.java:241)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.onMessage(IgniteH2Indexing.java:2186)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.lambda$start$17(IgniteH2Indexing.java:2139)
at 
org.apache.ignite.internal.managers.communication.GridIoManager$ArrayListener.onMessage(GridIoManager.java:3386)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1847)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1472)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.access$5200(GridIoManager.java:229)
at 
org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1367)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.h2.jdbc.JdbcSQLException: The database has been closed 
[90098-197]
at org.h2.message.DbException.getJdbcSQLException(DbException.java:357)
at org.h2.message.DbException.get(DbException.java:179)
at org.h2.message.DbException.get(DbException.java:155)
at org.h2.message.DbException.get(DbException.java:144)
at org.h2.engine.Database.checkPowerOff(Database.java:536)
at org.h2.command.Command.executeQuery(Command.java:228)

[2.8.1]Checking optimistic transaction state on remote nodes

2020-11-19 Thread 38797715


Hi community,

Although there is a transactional cache, no transaction operation is 
performed, but there is a lot of output below in the log. Why?


[2020-11-16 14:01:44,947][INFO ][sys-stripe-8-#9][IgniteTxManager] 
Checking optimistic transaction state on remote nodes [tx=GridDhtTxLocal 
[nearNodeId=a7eded9b-4078-4ee5-a1dd-426b8debc203, 
nearFutId=e0576afd571-dbd82c53-1772-4c53-a4ea-38e601002379, 
nearMiniId=1, nearFinFutId=null, nearFinMiniId=0, 
nearXidVer=GridCacheVersion [topVer=216485010, order=1607062821327, 
nodeOrder=30], lb=null, super=GridDhtTxLocalAdapter 
[nearOnOriginatingNode=false, nearNodes=KeySetView [], 
dhtNodes=KeySetView [e4d4fc27-d2d9-47f9-8d21-dfac2c003b55, 
3060fc02-e94a-4b6d-851a-05d75ea751e0], explicitLock=false, 
super=IgniteTxLocalAdapter [completedBase=null, 
sndTransformedVals=false, depEnabled=false, 
txState=IgniteTxImplicitSingleStateImpl [init=true, recovery=false, 
useMvccCaching=false], super=IgniteTxAdapter [xidVer=GridCacheVersion 
[topVer=216485010, order=1607062856849, nodeOrder=1], 
writeVer=GridCacheVersion [topVer=216485023, order=1607062856850, 
nodeOrder=1], implicit=true, loc=true, threadId=24070, 
startTime=1605506134277, nodeId=2b0db4f4-86d1-42c2-babf-f6318bd932e5, 
startVer=GridCacheVersion [topVer=216485010, order=1607062856849, 
nodeOrder=1], endVer=null, isolation=READ_COMMITTED, 
concurrency=OPTIMISTIC, timeout=0, sysInvalidate=false, sys=false, 
plc=2, commitVer=null, finalizing=RECOVERY_FINISH, invalidParts=null, 
state=PREPARED, timedOut=false, topVer=AffinityTopologyVersion 
[topVer=117, minorTopVer=0], mvccSnapshot=null, skipCompletedVers=false, 
parentTx=null, duration=370668ms, onePhaseCommit=false], size=1]]], 
fut=GridCacheTxRecoveryFuture [trackable=true, 
futId=81c3b7af571-1093b7fe-20ae-4c3f-9adb-4ecac23c136e, 
tx=GridDhtTxLocal [nearNodeId=a7eded9b-4078-4ee5-a1dd-426b8debc203, 
nearFutId=e0576afd571-dbd82c53-1772-4c53-a4ea-38e601002379, 
nearMiniId=1, nearFinFutId=null, nearFinMiniId=0, 
nearXidVer=GridCacheVersion [topVer=216485010, order=1607062821327, 
nodeOrder=30], lb=null, super=GridDhtTxLocalAdapter 
[nearOnOriginatingNode=false, nearNodes=KeySetView [], 
dhtNodes=KeySetView [e4d4fc27-d2d9-47f9-8d21-dfac2c003b55, 
3060fc02-e94a-4b6d-851a-05d75ea751e0], explicitLock=false, 
super=IgniteTxLocalAdapter [completedBase=null, 
sndTransformedVals=false, depEnabled=false, 
txState=IgniteTxImplicitSingleStateImpl [init=true, recovery=false, 
useMvccCaching=false], super=IgniteTxAdapter [xidVer=GridCacheVersion 
[topVer=216485010, order=1607062856849, nodeOrder=1], 
writeVer=GridCacheVersion [topVer=216485023, order=1607062856850, 
nodeOrder=1], implicit=true, loc=true, threadId=24070, 
startTime=1605506134277, nodeId=2b0db4f4-86d1-42c2-babf-f6318bd932e5, 
startVer=GridCacheVersion [topVer=216485010, order=1607062856849, 
nodeOrder=1], endVer=null, isolation=READ_COMMITTED, 
concurrency=OPTIMISTIC, timeout=0, sysInvalidate=false, sys=false, 
plc=2, commitVer=null, finalizing=RECOVERY_FINISH, invalidParts=null, 
state=PREPARED, timedOut=false, topVer=AffinityTopologyVersion 
[topVer=117, minorTopVer=0], mvccSnapshot=null, skipCompletedVers=false, 
parentTx=null, duration=370668ms, onePhaseCommit=false], size=1]]], 
failedNodeIds=SingletonSet [a7eded9b-4078-4ee5-a1dd-426b8debc203], 
nearTxCheck=false, innerFuts=EmptyList [], 
super=GridCompoundIdentityFuture [super=GridCompoundFuture [rdc=Bool 
reducer: true, initFlag=0, lsnrCalls=0, done=false, cancelled=false, 
err=null, futs=EmptyList []
[2020-11-16 14:01:44,947][INFO ][sys-stripe-8-#9][IgniteTxManager] 
Finishing prepared transaction [commit=true, tx=GridDhtTxLocal 
[nearNodeId=a7eded9b-4078-4ee5-a1dd-426b8debc203, 
nearFutId=e0576afd571-dbd82c53-1772-4c53-a4ea-38e601002379, 
nearMiniId=1, nearFinFutId=null, nearFinMiniId=0, 
nearXidVer=GridCacheVersion [topVer=216485010, order=1607062821327, 
nodeOrder=30], lb=null, super=GridDhtTxLocalAdapter 
[nearOnOriginatingNode=false, nearNodes=KeySetView [], 
dhtNodes=KeySetView [e4d4fc27-d2d9-47f9-8d21-dfac2c003b55, 
3060fc02-e94a-4b6d-851a-05d75ea751e0], explicitLock=false, 
super=IgniteTxLocalAdapter [completedBase=null, 
sndTransformedVals=false, depEnabled=false, 
txState=IgniteTxImplicitSingleStateImpl [init=true, recovery=false, 
useMvccCaching=false], super=IgniteTxAdapter [xidVer=GridCacheVersion 
[topVer=216485010, order=1607062856849, nodeOrder=1], 
writeVer=GridCacheVersion [topVer=216485023, order=1607062856850, 
nodeOrder=1], implicit=true, loc=true, threadId=24070, 
startTime=1605506134277, nodeId=2b0db4f4-86d1-42c2-babf-f6318bd932e5, 
startVer=GridCacheVersion [topVer=216485010, order=1607062856849, 
nodeOrder=1], endVer=null, isolation=READ_COMMITTED, 
concurrency=OPTIMISTIC, timeout=0, sysInvalidate=false, sys=false, 
plc=2, commitVer=null, finalizing=RECOVERY_FINISH, invalidParts=null, 
state=PREPARED, timedOut=false, topVer=AffinityTopologyVersion 
[topVer=117, minorTopVer=0], mvccSnapshot=null, skipCompletedVers=false,

Re: Caches, Regions, Expiry, Eviction

2020-11-19 Thread narges saleh

Thanks Ilya, for the explanation.

So, to recap,
data always resides in off heap, but it can be configured to reside to on
heap as well.
You define eviction policy on regions to evict the data from on heap, but
it won't affect the off heap.
You define expiry policy at cache level to remove data from off heap.

On Mon, Nov 16, 2020 at 7:04 AM Ilya Kasnacheev 
wrote:

> Hello!
>
> 1. There's no such thing as pure on-heap cache. On-heap is an extra option
> for a cache, which is always off-heap. So you need to set both.
> 2. Eviction policy is applicable to on-heap part of a cache only. Expiry
> policy will remove data from both off-heap and PDS. There's also page
> eviction which changes its meaning when you add persistence.
> 3. Yes, but it will not remove data from off-heap so it will still be in
> the cache.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> пн, 16 нояб. 2020 г. в 15:55, narges saleh :
>
>> Hi All,
>>
>> I need confirmation for my understanding of some basic concepts.
>> These are my understanding. Please confirm.
>> 1) Regions are not applicable to on heap caches. I'd use JVM -Xms and
>> -Xmx to set the limits, while with off heap caches, I'd use regions  with
>> initial/max size set.
>> 2) When I define regions with persistence enabled, I'd define
>> expiryPolicy, not evictionPolicy.
>> 3) With on heap caches, I'd define the evictionPolicy directly applied to
>> the cache.
>>
>> thanks
>>
>>
>>

Re: Apache Ignite Clientside NearCache and Serverside Eviction blocking cluster

2020-11-19 Thread pvprsd

Hi,

I have created a sample reproducer using examples files. I am using ignite
2.8.0 version.

Here I have updated server configurations in ExampleNodeStartup.java, and
client configurations in CacheClientBinaryPutGetExample.java files.

Server is configured with eviction-enabled, and client is configured with
near-cache. Client keeps adding more entries to the cache. Server stores all
the entries, and when memory utilization reached 90%, it should evict the
LRU entries from server cache in this use-case. 

In 7-8 minutes, the server is not able to evict the data and showing the
warning "Too many failed attempts to evict page: 30".

I am attaching the updated files for your reference. Can you please review
and provide your recommendations.

Ignite_Blocker_Issue.zip

  

Thanks,
Prasad




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

Re: Query on CVE-2020-5421

Re: Ignite 2.8.1: Database Closed error

Ignite 2.8.1: Database Closed error

[2.8.1]Checking optimistic transaction state on remote nodes

Re: Caches, Regions, Expiry, Eviction

Re: Apache Ignite Clientside NearCache and Serverside Eviction blocking cluster

6 matches

Site Navigation

Mail list logo

Footer information