[jira] [Created] (IGNITE-8378) Java crash upon node start after some restarts during failover test with 500 logical and 26 physical caches
Ksenia Rybakova created IGNITE-8378: --- Summary: Java crash upon node start after some restarts during failover test with 500 logical and 26 physical caches Key: IGNITE-8378 URL: https://issues.apache.org/jira/browse/IGNITE-8378 Project: Ignite Issue Type: Bug Affects Versions: 2.4 Reporter: Ksenia Rybakova Load config: - Yardstick benchmark: CacheRandomOperationBenchmark - 10 client nodes, 20 server nodes - 10K perloading, 20K key range - 26 physical caches - 500 logical caches - 2 backups - 1 server node is being restarted periodically Complete configs are attached. After several successfull restarts the node being restarted crashes (Java crash). Node log and error file are attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8373) BinaryObjectException: Cannot find schema for object with compact footer during load test
Ksenia Rybakova created IGNITE-8373: --- Summary: BinaryObjectException: Cannot find schema for object with compact footer during load test Key: IGNITE-8373 URL: https://issues.apache.org/jira/browse/IGNITE-8373 Project: Ignite Issue Type: Bug Affects Versions: 2.4 Reporter: Ksenia Rybakova -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8308) Sporadic NPE in IgniteAtomicSequenceExample at GridDhtTxPrepareFuture.map
Ksenia Rybakova created IGNITE-8308:
---
Summary: Sporadic NPE in IgniteAtomicSequenceExample at
GridDhtTxPrepareFuture.map
Key: IGNITE-8308
URL: https://issues.apache.org/jira/browse/IGNITE-8308
Project: Ignite
Issue Type: Bug
Affects Versions: 1.8
Reporter: Ksenia Rybakova
Sporadic NPE occures in IgniteAtomicSequenceExample at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.map
{noformat}
java.lang.NullPointerException
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.map(GridDhtTxPrepareFuture.java:1513)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.map(GridDhtTxPrepareFuture.java:1462)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.prepare0(GridDhtTxPrepareFuture.java:1194)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.mapIfLocked(GridDhtTxPrepareFuture.java:667)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.prepare(GridDhtTxPrepareFuture.java:1040)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.prepareAsync(GridDhtTxLocal.java:481)
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.prepareNearTx(IgniteTxHandler.java:465)
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.prepareTx(IgniteTxHandler.java:237)
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processNearTxPrepareRequest(IgniteTxHandler.java:123)
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$1.apply(IgniteTxHandler.java:145)
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$1.apply(IgniteTxHandler.java:143)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:836)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:378)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:302)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$000(GridCacheIoManager.java:96)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:247)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1512)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1140)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:119)
at
org.apache.ignite.internal.managers.communication.GridIoManager$8.run(GridIoManager.java:1080)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
{noformat}
For instance with 2 nodes:
Node1:
{noformat}
[17:17:56] Ignite node started OK (id=ac7dda5e) [17:17:56] Topology snapshot
[ver=2, servers=2, clients=0, CPUs=32, heap=3.0GB] >>> Cache atomic sequence
example started. Sequence initial value on local node: 0 Sequence
[currentValue=0, afterIncrement=1] Sequence [currentValue=1, afterIncrement=2]
Sequence [currentValue=2, afterIncrement=3] Sequence [currentValue=3,
afterIncrement=4] Sequence [currentValue=4, afterIncrement=5] Sequence
[currentValue=5, afterIncrement=6] Sequence [currentValue=6, afterIncrement=7]
Sequence [currentValue=7, afterIncrement=8] Sequence [currentValue=8,
afterIncrement=9] Sequence [currentValue=9, afterIncrement=10] Sequence
[currentValue=10, afterIncrement=11] Sequence [currentValue=11,
afterIncrement=12] Sequence [currentValue=12, afterIncrement=13] Sequence
[currentValue=13, afterIncrement=14] Sequence [currentValue=14,
afterIncrement=15] Sequence [currentValue=15, afterIncrement=16] Sequence
[currentValue=16, afterIncrement=17] Sequence [currentValue=17,
afterIncrement=18] Sequence [currentValue=18, afterIncrement=19] Sequence
[currentValue=19, afterIncrement=20] Sequence after incrementing [expected=20,
actual=20] Finished atomic sequence example... Check all nodes for output (this
node is also part of the cluster).
{noformat}
Node2:
{noformat}
[17:17:42] Ignite node started OK (id=734c312e) [17:17:42] Topology snapshot
[ver=1, servers=1, clients=0, CPUs=32, heap=2.0GB] [17:17:55] Topology snapshot
[ver=2, servers=2, clients=0, CPUs=32, heap=3.0GB]
[17:17:56,719][SEVERE][utility-#87%null%][GridCacheIoManager] Failed processing
message [senderId=ac7dda5e-491b-43ce-aa22-d5442fb4db8c,
msg=GridNearTxPrepareRequest
[futId=14f91dec261-f8b65720-5df3-4f06-b1d5-f74b356049cf,
[jira] [Created] (IGNITE-8022) Need to add README.txt for ignite-direct-io
Ksenia Rybakova created IGNITE-8022: --- Summary: Need to add README.txt for ignite-direct-io Key: IGNITE-8022 URL: https://issues.apache.org/jira/browse/IGNITE-8022 Project: Ignite Issue Type: Bug Affects Versions: 2.4 Reporter: Ksenia Rybakova Fix For: 2.5 Need to add README.txt for ignite-direct-io -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-7841) "Failed to send one phase commit ack to backup node" at some Java8 examples with 2 nodes
Ksenia Rybakova created IGNITE-7841:
---
Summary: "Failed to send one phase commit ack to backup node" at
some Java8 examples with 2 nodes
Key: IGNITE-7841
URL: https://issues.apache.org/jira/browse/IGNITE-7841
Project: Ignite
Issue Type: Bug
Affects Versions: 1.7
Reporter: Ksenia Rybakova
- Open Ignite examples.
- Start 1 server ignite node, use Java8.
- Start one of the Java8 examples ().
For instance, ComputeCallableExample.
Example competed successfully
{noformat}
[13:45:49] Topology snapshot [ver=2, servers=2, clients=0, CPUs=4, heap=7.1GB]
>>> Compute callable example started.
>>> Printing 'using' on this node from ignite job.
>>> Printing 'Count' on this node from ignite job.
>>> Total number of characters in the phrase is '28'.
>>> Check all nodes for output (this node is also part of the cluster).
[13:45:50] Ignite node stopped OK [uptime=00:00:00:483]
{noformat}
But server node failed to send one phase commit ack:
{noformat}
[13:45:49] Topology snapshot [ver=2, servers=2, clients=0, CPUs=4, heap=7.1GB]
>>> Printing 'characters' on this node from ignite job.
>>> Printing 'callable' on this node from ignite job.
[13:45:49] Topology snapshot [ver=3, servers=1, clients=0, CPUs=4, heap=3.5GB]
[13:45:50,502][ERROR][sys-#51%null%][IgniteTxManager] Failed to send one phase
commit ack to backup node [backup=f951ad58-414d-4091-b784-634a2675c830]
class org.apache.ignite.internal.cluster.ClusterTopologyCheckedException:
Failed to send message because node left grid
[nodeId=f951ad58-414d-4091-b784-634a2675c830,
msg=GridDhtTxOnePhaseCommitAckRequest [vers=[GridCacheVersion
[topVer=131294740, time=1519814749915, order=1519814744287, nodeOrder=1],
GridCacheVersion [topVer=131294740, time=1519814749915, order=1519814744286,
nodeOrder=1]], super=GridCacheMessage [msgId=-1, depInfo=null, err=null,
skipPrepare=false, cacheId=0, cacheId=0]]]
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1065)
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager$2.finish(IgniteTxManager.java:283)
at
org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer.finish0(GridDeferredAckMessageSender.java:214)
at
org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer.access$000(GridDeferredAckMessageSender.java:111)
at
org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer$1.run(GridDeferredAckMessageSender.java:159)
at
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6640)
at
org.apache.ignite.internal.processors.closure.GridClosureProcessor$1.body(GridClosureProcessor.java:788)
at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
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)
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-7731) Restarted node can
Ksenia Rybakova created IGNITE-7731: --- Summary: Restarted node can Key: IGNITE-7731 URL: https://issues.apache.org/jira/browse/IGNITE-7731 Project: Ignite Issue Type: Bug Reporter: Ksenia Rybakova -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-7589) Grid hangs on partition map exhcange during failover test with 34 physical caches (PDS + in memory)
Ksenia Rybakova created IGNITE-7589: --- Summary: Grid hangs on partition map exhcange during failover test with 34 physical caches (PDS + in memory) Key: IGNITE-7589 URL: https://issues.apache.org/jira/browse/IGNITE-7589 Project: Ignite Issue Type: Bug Affects Versions: 2.4 Reporter: Ksenia Rybakova Grid hangs on partition map exhcange during failover test with 34 physical caches (PDS + in memory) during preloading (streaming) phase. Several restarts completed successfully, but then grid hung after node joined. Load config: CacheRandomOperationBenchmark 11 client nodes, 22 server nodes 250K perloading, 500K key range 34 physical caches of different types (onheap/offheap, tx/atomic, partitioned/replicated, with/without eviction, pds/in memory) 2 backups 2 server nodes are being restarted periodically Complete configs are attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-7570) Client nodes failed with "Failed to process invalid partitions response" during failover
Ksenia Rybakova created IGNITE-7570:
---
Summary: Client nodes failed with "Failed to process invalid
partitions response" during failover
Key: IGNITE-7570
URL: https://issues.apache.org/jira/browse/IGNITE-7570
Project: Ignite
Issue Type: Bug
Affects Versions: 2.4
Reporter: Ksenia Rybakova
Some client nodes fail with "Failed to process invalid partitions response"
during failover test:
{noformat}
[2018-01-30 16:27:58,610][INFO ][sys-#190][GridDhtPartitionsExchangeFuture]
Received full message, will finish exchange
[node=80ebd2ac-1432-4bfc-bab7-d9dbf56cdeb4, resVer=AffinityTopologyVersion
[topVer=37, minorTopVer=0]]
[2018-01-30 16:27:58,688][INFO ][sys-#190][GridDhtPartitionsExchangeFuture]
Finish exchange future [startVer=AffinityTopologyVersion [topVer=37,
minorTopVer=0], resVer=AffinityTopologyVersion [topVer=37, minorTopVer=0],
err=null]
<16:27:58> The benchmark of random operation
failed.
javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException:
Failed to process invalid partitions response (remote node reported invalid
partitions but remote topology version does not differ from local)
[topVer=AffinityTopologyVersion [topVer=37, minorTopVer=0],
rmtTopVer=AffinityTopologyVersion [topVer=37, minorTopVer=0], part=204,
nodeId=80ebd2ac-1432-4bfc-bab7-d9dbf56cdeb4]
at
org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1294)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cacheException(IgniteCacheProxyImpl.java:1673)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.get(IgniteCacheProxyImpl.java:852)
at
org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.get(GatewayProtectedCacheProxy.java:676)
at
org.apache.ignite.yardstick.cache.load.IgniteCacheRandomOperationBenchmark.doGet(IgniteCacheRandomOperationBenchmark.java:776)
at
org.apache.ignite.yardstick.cache.load.IgniteCacheRandomOperationBenchmark.executeRandomOperation(IgniteCacheRandomOperationBenchmark.java:624)
at
org.apache.ignite.yardstick.cache.load.IgniteCacheRandomOperationBenchmark.executeOutOfTx(IgniteCacheRandomOperationBenchmark.java:602)
at
org.apache.ignite.yardstick.cache.load.IgniteCacheRandomOperationBenchmark.test(IgniteCacheRandomOperationBenchmark.java:207)
at org.yardstickframework.impl.BenchmarkRunner$2.run(BenchmarkRunner.java:178)
at java.lang.Thread.run(Thread.java:748)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to process
invalid partitions response (remote node reported invalid partitions but remote
topology version does not differ from local) [topVer=AffinityTopologyVersion
[topVer=37, minorTopVer=0], rmtTopVer=AffinityTopologyVersion [topVer=37,
minorTopVer=0], part=204, nodeId=80ebd2ac-1432-4bfc-bab7-d9dbf56cdeb4]
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.checkError(GridPartitionedSingleGetFuture.java:596)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.onResult(GridPartitionedSingleGetFuture.java:505)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter.processNearSingleGetResponse(GridDhtCacheAdapter.java:349)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$1400(GridDhtAtomicCache.java:130)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$15.apply(GridDhtAtomicCache.java:422)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$15.apply(GridDhtAtomicCache.java:417)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1060)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:579)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:378)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:304)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:99)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:293)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1555)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1183)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:126)
at
org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1090)
at
org.apache.ignite.internal.util.StripedExecutor$Stripe.run(StripedExecutor.java:499)
... 1 more
Finishing main test
[jira] [Created] (IGNITE-7406) Transactions hang forever during load test
Ksenia Rybakova created IGNITE-7406:
---
Summary: Transactions hang forever during load test
Key: IGNITE-7406
URL: https://issues.apache.org/jira/browse/IGNITE-7406
Project: Ignite
Issue Type: Bug
Affects Versions: 2.3
Reporter: Ksenia Rybakova
Load test config:
- CacheRandomOperationBenchmark
- 13 client nodes (1 per host), 62 server nodes (4 per host)
- 30 caches with different configs
- data store config: 6Gb default region, two 100M regions, two 1Gb regions
- operations: PUT PUT_ALL GET GET_ALL INVOKE INVOKE_ALL REMOVE REMOVE_ALL
PUT_IF_ABSENT REPLACE
- preload amount 200K entries, key range 400K
- Persistent store is disabled
Preloading phase completed successfully, but during main test transactions
completely hang ("long running tx/cache future" logs show duration more than
48h) after some time.
Yardstick configs are attached, "long running tx/cache future" messages from
one of the server are attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-7262) Most of clients get stuck with "Failed to wait for partition map ..." during load test with 500 logical caches
Ksenia Rybakova created IGNITE-7262: --- Summary: Most of clients get stuck with "Failed to wait for partition map ..." during load test with 500 logical caches Key: IGNITE-7262 URL: https://issues.apache.org/jira/browse/IGNITE-7262 Project: Ignite Issue Type: Bug Reporter: Ksenia Rybakova Load config: -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-6829) NPE at org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager#exchangeFuture
Ksenia Rybakova created IGNITE-6829:
---
Summary: NPE at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager#exchangeFuture
Key: IGNITE-6829
URL: https://issues.apache.org/jira/browse/IGNITE-6829
Project: Ignite
Issue Type: Bug
Security Level: Public (Viewable by anyone)
Components: general
Affects Versions: 1.8
Reporter: Ksenia Rybakova
Priority: Normal
NPE at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager#exchangeFuture
when client node is dropped from cluster:
{noformat}
[15:17:45,677][INFO ][main][IgniteKernal]
>>>__
>>> / _/ ___/ |/ / _/_ __/ __/
>>> _/ // (7 7// / / / / _/
>>> /___/\___/_/|_/___/ /_/ /___/
>>>
>>> ver. 1.9.0-SNAPSHOT#20171101-sha1:8b6b126a
>>> 2017 Copyright(C) Apache Software Foundation
>>>
>>> Ignite documentation: http://ignite.apache.org
[15:17:45,677][INFO ][main][IgniteKernal] Config URL: n/a
[15:17:45,677][INFO ][main][IgniteKernal] Daemon mode: off
[15:17:45,677][INFO ][main][IgniteKernal] OS: Linux 3.10.0-693.2.2.el7.x86_64
amd64
[15:17:45,677][INFO ][main][IgniteKernal] OS user: krybakova
[15:17:45,679][INFO ][main][IgniteKernal] PID: 21415
[15:17:45,679][INFO ][main][IgniteKernal] Language runtime: Java Platform API
Specification ver. 1.8
[15:17:45,679][INFO ][main][IgniteKernal] VM information: Java(TM) SE Runtime
Environment 1.8.0_141-b15 Oracle Corporation Java HotSpot(TM) 64-Bit Server VM
25.141-b15
[15:17:45,680][INFO ][main][IgniteKernal] VM total memory: 4.0GB
[15:17:45,681][INFO ][main][IgniteKernal] Remote Management [restart: off,
REST: off, JMX (remote: off)]
[15:17:45,681][INFO ][main][IgniteKernal]
IGNITE_HOME=/storage/ssd/krybakova/opts-set-b-2-d-3600-m-client-rev-8b6b126a-date-0311-151639/yardstick
[15:17:45,681][INFO ][main][IgniteKernal] VM arguments: [-Xms2g, -Xmx2g,
-Djava.net.preferIPv4Stack=true, -DIGNITE_QUIET=false, -XX:+UseTLAB,
-XX:NewSize=512m, -XX:MaxNewSize=512m, -XX:SurvivorRatio=6,
-XX:+AlwaysPreTouch, -XX:+UseG1GC, -XX:MaxGCPauseMillis=2000,
-XX:GCTimeRatio=4, -XX:InitiatingHeapOccupancyPercent=30,
-XX:G1HeapRegionSize=8M, -XX:ConcGCThreads=16, -XX:ParallelGCThreads=16,
-XX:G1HeapWastePercent=10, -XX:+ScavengeBeforeFullGC, -XX:+DisableExplicitGC,
-XX:+PrintGCDetails, -XX:+PrintGCDateStamps, -verbose:gc,
-DIGNITE_THREAD_DUMP_ON_EXCHANGE_TIMEOUT=true, -Xms4g, -Xmx4g,
-Xloggc:./gc-driver0.log, -Dyardstick.driver0]
[15:17:45,681][INFO ][main][IgniteKernal] Configured caches
['ignite-marshaller-sys-cache', 'ignite-sys-cache', 'ignite-atomics-sys-cache',
'atomic', 'atomic-evict', 'atomic-offheap', 'atomic-offheap-values', 'tx',
'tx-evict', 'compute', 'tx-offheap', 'tx-offheap-values', 'atomic-index',
'query', 'orgCache']
[15:17:45,685][INFO ][main][IgniteKernal] 3-rd party licenses can be found at:
/storage/ssd/krybakova/opts-set-b-2-d-3600-m-client-rev-8b6b126a-date-0311-151639/yardstick/libs/licenses
[15:17:45,764][INFO ][main][IgnitePluginProcessor] Configured plugins:
[15:17:45,764][INFO ][main][IgnitePluginProcessor] ^-- None
[15:17:45,765][INFO ][main][IgnitePluginProcessor]
[15:17:45,831][INFO ][main][TcpCommunicationSpi] Successfully bound
communication NIO server to TCP port [port=47103, locHost=0.0.0.0/0.0.0.0,
selectorsCnt=8, selectorSpins=0, pairedConn=false]
[15:17:45,838][WARN ][main][TcpCommunicationSpi] Message queue limit is set to
0 which may lead to potential OOMEs when running cache operations in FULL_ASYNC
or PRIMARY_SYNC modes due to message queues growth on sender and receiver sides.
[15:17:45,865][WARN ][main][NoopCheckpointSpi] Checkpoints are disabled (to
enable configure any GridCheckpointSpi implementation)
[15:17:45,897][WARN ][main][GridCollisionManager] Collision resolution is
disabled (all jobs will be activated upon arrival).
[15:17:45,899][WARN ][main][NoopSwapSpaceSpi] Swap space is disabled. To enable
use FileSwapSpaceSpi.
[15:17:45,900][INFO ][main][IgniteKernal] Security status [authentication=off,
tls/ssl=off]
[15:17:46,350][INFO ][main][GridRestProcessor] REST protocols do not start on
client node. To start the protocols on client node set
'-DIGNITE_REST_START_ON_CLIENT=true' system property.
[15:17:46,397][INFO ][main][IgniteKernal] Non-loopback local IPs: 172.17.0.1,
172.25.1.11
[15:17:46,398][INFO ][main][IgniteKernal] Enabled local MACs: 02429159579F,
2C55D3F375DE
[15:17:46,405][WARN ][main][TcpDiscoverySpi] Failure detection timeout will be
ignored (one of SPI parameters has been set explicitly)
[15:18:21,121][WARN ][tcp-client-disco-msg-worker-#4%null%][TcpDiscoverySpi]
Local node was dropped from cluster due to network problems, will try to
reconnect with new id after 1ms (reconnect delay can be changed using
IGNITE_DISCO_
FAILED_CLIENT_RECONNECT_DELAY system property)
[jira] [Created] (IGNITE-6823) Sporadic Redis python and php examples failures
Ksenia Rybakova created IGNITE-6823:
---
Summary: Sporadic Redis python and php examples failures
Key: IGNITE-6823
URL: https://issues.apache.org/jira/browse/IGNITE-6823
Project: Ignite
Issue Type: Bug
Security Level: Public (Viewable by anyone)
Affects Versions: 2.1
Reporter: Ksenia Rybakova
Priority: Normal
Sporadic Redis python examples failure
{noformat}
['python3', 'examples/redis/redis-example.py']
Traceback (most recent call last):
File "examples/redis/redis-example.py", line 30, in
r.set('k1', 1)
File "c:\program files\python34\lib\site-packages\redis\client.py", line
1171, in set
return self.execute_command('SET', *pieces)
File "c:\program files\python34\lib\site-packages\redis\client.py", line 668,
in execute_command
return self.parse_response(connection, command_name, **options)
File "c:\program files\python34\lib\site-packages\redis\client.py", line 680,
in parse_response
response = connection.read_response()
File "c:\program files\python34\lib\site-packages\redis\connection.py", line
624, in read_response
response = self._parser.read_response()
File "c:\program files\python34\lib\site-packages\redis\connection.py", line
292, in read_response
(str(byte), str(response)))
redis.exceptions.InvalidResponse: Protocol Error: E, b'RROR'
Command '['python3', 'examples/redis/redis-example.py']' returned non-zero exit
status 1
{noformat}
and Redis php
{noformat}
['php', 'examples/redis/redis-example.php']
>>> Successfully connected to Redis.
>>> Couldn't connected to Redis.Unknown response prefix: 'E'.
>>> [tcp://localhost:11211]
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (IGNITE-6774) Java doc is broken: "LUDecomposition.java:40: warning - Tag @see: missing final '>'"
Ksenia Rybakova created IGNITE-6774:
---
Summary: Java doc is broken: "LUDecomposition.java:40: warning -
Tag @see: missing final '>'"
Key: IGNITE-6774
URL: https://issues.apache.org/jira/browse/IGNITE-6774
Project: Ignite
Issue Type: Bug
Security Level: Public (Viewable by anyone)
Components: ml
Affects Versions: 2.1
Reporter: Ksenia Rybakova
Java doc is broken in the build
{noformat}
[WARNING] Javadoc Warnings
[WARNING]
/var/lib/teamcity/data/work/6ae9d4bd0822354f/incubator-ignite/modules/ml/src/main/java/org/apache/ignite/ml/math/decompositions/LUDecomposition.java:40:
warning - Tag @see: missing final '>': "http://en.wikipedia.org/wiki/LU_decomposition;>Wikipedia
[WARNING] TODO: Maybe we should make this class (and other decompositions)
Externalizable."
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (IGNITE-6436) ransactions slow down
Ksenia Rybakova created IGNITE-6436: --- Summary: ransactions slow down Key: IGNITE-6436 URL: https://issues.apache.org/jira/browse/IGNITE-6436 Project: Ignite Issue Type: Bug Reporter: Ksenia Rybakova -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-6402) Make yardstick delete config-db from and not copy logs to remotes
Ksenia Rybakova created IGNITE-6402: --- Summary: Make yardstick delete config-db from and not copy logs to remotes Key: IGNITE-6402 URL: https://issues.apache.org/jira/browse/IGNITE-6402 Project: Ignite Issue Type: Improvement Components: yardstick Affects Versions: 2.1 Reporter: Ksenia Rybakova 1) Currently if we run yardstick from folder that contains output/logs-, this logs- will be also copied to remotes during yardstick deployment. This is not needed. 2) During clean up process folder config-db is not removed from remotes along with others (config, bin, etc.) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-6401) Change size to maxSize for memory config in ignite-base-load-config.xml
Ksenia Rybakova created IGNITE-6401: --- Summary: Change size to maxSize for memory config in ignite-base-load-config.xml Key: IGNITE-6401 URL: https://issues.apache.org/jira/browse/IGNITE-6401 Project: Ignite Issue Type: Bug Components: yardstick Affects Versions: 2.1 Reporter: Ksenia Rybakova Typo in ignite-base-load-config.xml: 'size' need to be changed to 'maxSize' for memory config since there is no 'size' property. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-6302) Client heap starts constantly growing when server offheap memory gets full
Ksenia Rybakova created IGNITE-6302: --- Summary: Client heap starts constantly growing when server offheap memory gets full Key: IGNITE-6302 URL: https://issues.apache.org/jira/browse/IGNITE-6302 Project: Ignite Issue Type: Bug Components: general, streaming Affects Versions: 2.1 Reporter: Ksenia Rybakova Load benchmark is streaming data to grid. Page memory maxSize is set. Sometimes IgniteOutOfMemoryException is not thrown at servers when maxSize is reached. This is the first problem. The second one - client's heap starts to grow constantly after server's offheap memory gets full. Load config: - org.apache.ignite.yardstick.cache.load.IgniteCacheRandomOperationBenchmark is used to stream data - 1 client, 4 server nodes - client heap: -Xms20g -Xmx20g, server heap: -Xms4g -Xmx4g - memory policy maxSize: 5Gb - page size: 2Kb - number of entries to preload: 35M At some point servers reach max offheap size (number of pages in log doesn't change and this number matches 5Gb maxSize). IgniteOutOfMemoryException is not thrown and client starts to utilize more and more heap capacity. All configs are attached. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-6150) ignite-osgi-karaf-licenses.txt is absent in a build
Ksenia Rybakova created IGNITE-6150:
---
Summary: ignite-osgi-karaf-licenses.txt is absent in a build
Key: IGNITE-6150
URL: https://issues.apache.org/jira/browse/IGNITE-6150
Project: Ignite
Issue Type: Bug
Affects Versions: 1.9
Reporter: Ksenia Rybakova
optional/ignite-osgi-karaf/licenses/ignite-osgi-karaf-licenses.txt file is
absent in a build.
While building there is a warning:
{noformat}
[23:57:23][Step 30/31] [INFO] An Ant BuildException has occured: Warning: Could
not find file
/var/lib/teamcity/data/work/374178e7af8a6b6/incubator-ignite/modules/osgi-karaf/target/classes/META-INF/licenses.txt
to copy.
[23:57:23][Step 30/31] around Ant part ..
@ 4:270 in
/var/lib/teamcity/data/work/374178e7af8a6b6/incubator-ignite/modules/osgi-karaf/target/antrun/build-main.xml
[23:57:23][Step 30/31]
/var/lib/teamcity/data/work/374178e7af8a6b6/incubator-ignite/modules/osgi-karaf/target/antrun/build-main.xml:4:
Warning: Could not find file
/var/lib/teamcity/data/work/374178e7af8a6b6/incubator-ignite/modules/osgi-karaf/target/classes/META-INF/licenses.txt
to copy.
[23:57:23][Step 30/31] at
org.apache.tools.ant.taskdefs.Copy.copySingleFile(Copy.java:619)
[23:57:23][Step 30/31] at
org.apache.tools.ant.taskdefs.Copy.execute(Copy.java:444)
[23:57:23][Step 30/31] at
org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
[23:57:23][Step 30/31] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
[23:57:23][Step 30/31] at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
[23:57:23][Step 30/31] at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[23:57:23][Step 30/31] at java.lang.reflect.Method.invoke(Method.java:606)
[23:57:23][Step 30/31] at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
[23:57:23][Step 30/31] at org.apache.tools.ant.Task.perform(Task.java:348)
[23:57:23][Step 30/31] at org.apache.tools.ant.Target.execute(Target.java:390)
[23:57:23][Step 30/31] at
org.apache.tools.ant.Target.performTasks(Target.java:411)
[23:57:23][Step 30/31] at
org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
[23:57:23][Step 30/31] at
org.apache.tools.ant.Project.executeTarget(Project.java:1368)
[23:57:23][Step 30/31] at
org.apache.maven.plugin.antrun.AntRunMojo.execute(AntRunMojo.java:327)
[23:57:23][Step 30/31] at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
[23:57:23][Step 30/31] at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
[23:57:23][Step 30/31] at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
[23:57:23][Step 30/31] at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
[23:57:23][Step 30/31] at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
[23:57:23][Step 30/31] at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
[23:57:23][Step 30/31] at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
[23:57:23][Step 30/31] at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
[23:57:23][Step 30/31] at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
[23:57:23][Step 30/31] at
org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
[23:57:23][Step 30/31] at
org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
[23:57:23][Step 30/31] at
org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
[23:57:23][Step 30/31] at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
[23:57:23][Step 30/31] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
[23:57:23][Step 30/31] at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
[23:57:23][Step 30/31] at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[23:57:23][Step 30/31] at java.lang.reflect.Method.invoke(Method.java:606)
[23:57:23][Step 30/31] at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
[23:57:23][Step 30/31] at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
[23:57:23][Step 30/31] at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
[23:57:23][Step 30/31] at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (IGNITE-6066) Grid hangs on partition map exhcange during failover test with 30 physical caches and PDS
Ksenia Rybakova created IGNITE-6066: --- Summary: Grid hangs on partition map exhcange during failover test with 30 physical caches and PDS Key: IGNITE-6066 URL: https://issues.apache.org/jira/browse/IGNITE-6066 Project: Ignite Issue Type: Bug Affects Versions: 2.1 Reporter: Ksenia Rybakova -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-6056) Grid hangs on partition map exhcange during failover test with 500 logical and 26 physical caches
Ksenia Rybakova created IGNITE-6056: --- Summary: Grid hangs on partition map exhcange during failover test with 500 logical and 26 physical caches Key: IGNITE-6056 URL: https://issues.apache.org/jira/browse/IGNITE-6056 Project: Ignite Issue Type: Bug Affects Versions: 2.1 Reporter: Ksenia Rybakova Grid hangs on partition map exhcange during failover test with 500 logical and 26 physical caches. Load config: - CacheRandomOperationBenchmark - 8 client nodes, 40 server nodes - 40K perloading, 60K key range - 26 physical caches - 500 logical caches - 2 backups - 1 server node is being restarted periodically Complete configs are attached. Preloading phase is ok, then main test starts and after some time grid hangs. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-5996) Load test with >100 servers: slow topology setup and hanging during preloading
Ksenia Rybakova created IGNITE-5996: --- Summary: Load test with >100 servers: slow topology setup and hanging during preloading Key: IGNITE-5996 URL: https://issues.apache.org/jira/browse/IGNITE-5996 Project: Ignite Issue Type: Bug Affects Versions: 2.1 Reporter: Ksenia Rybakova Load test config: - CacheRandomOperationBenchmark - 30 caches: 2 atomic partitioned 2 atomic partitioned with offheap eviction atomic replicated 2 atomic replicated with offheap eviction 3 atomic partitioned onheap 3 atomic replicated onheap 4 atomic partitioned indexed 2 transactional partitioned 2 transactional partitioned with offheap eviction transactional replicated 2 transactional replicated with offheap eviction 3 transactional partitioned onheap 3 transactional replicated onheap - Preload amount: 100K-500K - Key range: 200K - 7 client nodes, 119 server nodes - Persistent store is disabled -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-5930) Long running transactions while load test with 1 memory policy, 14 caches and >=24 servers
Ksenia Rybakova created IGNITE-5930: --- Summary: Long running transactions while load test with 1 memory policy, 14 caches and >=24 servers Key: IGNITE-5930 URL: https://issues.apache.org/jira/browse/IGNITE-5930 Project: Ignite Issue Type: Bug Affects Versions: 1.9 Reporter: Ksenia Rybakova Load config: - CacheRandomOperation benchmark - Caches: atomic partitioned cache 2 tx partitioned caches 2 atomic partitioned onheap caches 2 atomic replicated onheap caches 2 tx partitioned onheap caches 2 tx replicated onheap caches 3 partitioned atomic indexed caches - Preload amount: 500K-2.5M entries per cache - Key range: 1M - Persistent store is disabled - 24 server nodes or more (3 nodes per physical host), 16 client nodes Long running transactions occur after preloading and throughput dropps to 0. Note, that with 16 server nodes transactions are ok. Complete configs are attached. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-5707) Client can't resume streaming even after topology got stable during load test
Ksenia Rybakova created IGNITE-5707:
---
Summary: Client can't resume streaming even after topology got
stable during load test
Key: IGNITE-5707
URL: https://issues.apache.org/jira/browse/IGNITE-5707
Project: Ignite
Issue Type: Bug
Affects Versions: 2.1
Reporter: Ksenia Rybakova
Load test config:
- CacheRandomOperationBenchmark
- 8 clients, 48 servers at 8 hosts
- 26 physical caches of different types with different memory policies + 30
groups with 10 partitioned caches each + 20 groups with 10 replicated caches
each. Total 526 caches.
- Preloading amount: 50K, key range: 60K
Complete configs are attached.
3 of 8 clients have following messages during preloading:
{noformat}
[12:17:56] (err) Failed to execute compound future reducer: GridCompoundFuture
[rdc=null, initFlag=1, lsnrCalls=0, done=false, cancelled=false, err=null,
futs=[true, false, false]][12:17:56] (err) Failed to
execute compound future reducer: GridCompoundFuture [rdc=null, initFlag=1,
lsnrCalls=0, done=false, cancelled=false, err=null, futs=[true, true, false,
false, false, false, false, false, false, false, false,
false, false, false, false, false, false, false, false, false, false, false,
false, false, false, false, false, false, false, false, false, false, false,
false, false, false, false]][12:17:56] (err) Failed
to execute compound future reducer: GridCompoundFuture [rdc=null, initFlag=1,
lsnrCalls=0, done=false, cancelled=false, err=null, futs=[true, true, false,
false, false, false, false, false, false, false, fal
se, false, false, false, false, false, false, false, false, false, false,
false, false, false, false, false, false, false, false, false, false, false,
false, false, false, false, false]]class org.apache.igni
te.IgniteCheckedException: DataStreamer request failed
[node=16a20d0c-4009-4bfa-ad6e-0261d9e3b2a3]
at
org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$Buffer.onResponse(DataStreamerImpl.java:1785)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$3.onMessage(DataStreamerImpl.java:333)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1556)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1184)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:126)
at
org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1097)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: class org.apache.ignite.IgniteCheckedException: DataStreamer will
retry data transfer at stable topology [reqTop=AffinityTopologyVersion
[topVer=56, minorTopVer=0], topVer=AffinityTopologyVersion
[topVer=56, minorTopVer=1], node=remote]
at
org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.localUpdate(DataStreamProcessor.java:343)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.processRequest(DataStreamProcessor.java:301)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.access$000(DataStreamProcessor.java:58)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor$1.onMessage(DataStreamProcessor.java:88)
... 7 more
{noformat}
2 drivers were able to resume streaming after some time, but 1 didn't (error
messages continued to be printed). This driver had high heap utilization, that
resulted in long GC pause. Finally it was considered failed by other nodes.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (IGNITE-5590) Physical and logical caches wtih the same amount of data have different storage size
Ksenia Rybakova created IGNITE-5590: --- Summary: Physical and logical caches wtih the same amount of data have different storage size Key: IGNITE-5590 URL: https://issues.apache.org/jira/browse/IGNITE-5590 Project: Ignite Issue Type: Bug Affects Versions: 2.1 Reporter: Ksenia Rybakova Priority: Minor The following experiment was done to compare logical vs physical caches witn PDS: - CacheRandomOperation benchmark was used to load data into caches - Number of loaded entries 10M per cache - All caches are atomic: 10 logical caches in 1 group vs 10 physical caches - walHistorySize =2 - One default memory policy, memory config is default as well Configs are attached. ||10 logical caches in 1 group|| 10 physical caches ||Comments|| ||Total size of work/db/127_0_0_1*| |Among all hosts| |23.6G|28.6G|Mainly because total size of partitions files (part-.bin) in "physical" case is bigger. In "phisical" case index.bin is one per cache while in "logical" case is one per group, but it's size is 16Kb so it doesn't make any difference.| ||Total size of work/db/wal/archive| |Among all hosts| |86.7G|63.6G|In "physical" case archive has more files.| ||Total size of work/db/wal/127_0_0_1*| |Among all hosts| |7.6G|7.6G| | The size difference should be investigated, currently reason is unclear. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-5585) NPE at CacheContinuousQueryManager.skipUpdateEvent during load test
Ksenia Rybakova created IGNITE-5585:
---
Summary: NPE at CacheContinuousQueryManager.skipUpdateEvent during
load test
Key: IGNITE-5585
URL: https://issues.apache.org/jira/browse/IGNITE-5585
Project: Ignite
Issue Type: Bug
Affects Versions: 1.8
Reporter: Ksenia Rybakova
Load test config:
- CacheRandomOperation benchmark
- Operations: put, put_all, get, get_all, invoke, invoke_all, remove,
remove_all, put_if_absent, replace
- Heap: 8Gb for servers, 4Gb for clients
- 5 clients, 20 servers
- 12 caches od different types (refer to config)
- Backups count: 1
NPE occurs at different server nodes:
{noformat}
[11:02:40,210][ERROR][sys-stripe-3-#4%null%][GridCacheIoManager] Failed
processing message [senderId=4563d4fe-26a7-4b51-8bee-27159c9595d9,
msg=GridDhtAtomicUpdateRequest [futVer=GridCacheVersion [topVer=109944018,
time=1498464160167, ord
er=1498486560554, nodeOrder=12], writeVer=GridCacheVersion [topVer=109944018,
time=1498464160167, order=1498486560553, nodeOrder=12],
topVer=AffinityTopologyVersion [topVer=25, minorTopVer=0],
keys=[KeyCacheObjectImpl [val=1047562, hasVa
lBytes=true], KeyCacheObjectImpl [val=106245, hasValBytes=true],
KeyCacheObjectImpl [val=1246917, hasValBytes=true], KeyCacheObjectImpl
[val=127624, hasValBytes=true], KeyCacheObjectImpl [val=166631,
hasValBytes=true], KeyCacheObjectImpl
[val=31560, hasValBytes=true], KeyCacheObjectImpl [val=446054,
hasValBytes=true]], vals=[o.a.i.yardstick.cache.model.Account
[idHash=2028849570, hash=1858002766, balance=1047562],
o.a.i.yardstick.cache.model.Person1 [idHash=53911759, ha
sh=106245, val1=106245], o.a.i.yardstick.cache.model.Person1
[idHash=2004318126, hash=1246917, val1=1246917],
o.a.i.yardstick.cache.model.Account [idHash=1146256840, hash=1589210217,
balance=127624], o.a.i.yardstick.cache.model.Account [
idHash=62912643, hash=39960152, balance=166631],
o.a.i.yardstick.cache.model.Account [idHash=810836577, hash=1131557455,
balance=31560], o.a.i.yardstick.cache.model.Account [idHash=1946609424,
hash=1691380387, balance=446054]], prevVals=
null, ttls=null, conflictExpireTimes=null, nearTtls=null, nearExpireTimes=null,
syncMode=PRIMARY_SYNC, nearKeys=null, nearVals=null,
forceTransformBackups=false, subjId=fb6f99ad-09fb-471f-8e8a-280049758dcd,
taskNameHash=0, updateCntrs=Gr
idLongList [idx=7, arr=[5235,6992,6993,7223,7169,5376,6439]], keepBinary=false,
flags=0, super=GridCacheMessage [msgId=15154, depInfo=null, err=null,
skipPrepare=false, cacheId=1489451830, cacheId=1489451830]]]
java.lang.NullPointerException
at
org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryManager.skipUpdateEvent(CacheContinuousQueryManager.java:186)
at
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.innerUpdate(GridCacheMapEntry.java:2283)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.processDhtAtomicUpdateRequest(GridDhtAtomicCache.java:3276)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$1800(GridDhtAtomicCache.java:130)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$8.apply(GridDhtAtomicCache.java:379)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$8.apply(GridDhtAtomicCache.java:374)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:827)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:369)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:293)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$000(GridCacheIoManager.java:95)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:238)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1512)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1140)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:119)
at
org.apache.ignite.internal.managers.communication.GridIoManager$8.run(GridIoManager.java:1080)
at
org.apache.ignite.internal.util.StripedExecutor$Stripe.run(StripedExecutor.java:428)
at java.lang.Thread.run(Thread.java:745)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (IGNITE-5573) Yardstick: Incorrect actual warmup and duration when test with pds and many caches
Ksenia Rybakova created IGNITE-5573:
---
Summary: Yardstick: Incorrect actual warmup and duration when test
with pds and many caches
Key: IGNITE-5573
URL: https://issues.apache.org/jira/browse/IGNITE-5573
Project: Ignite
Issue Type: Bug
Components: yardstick
Affects Versions: 2.1
Reporter: Ksenia Rybakova
Load config:
- CacheRandomOperation benchmak
- 5 driver nodes
- 12 server nodes (1 per host)
- 14 phisical caches + 50 groups with 500 logical caches (10 per group)
- preloading amount 10K, key range 20K
- warmup time 300s
- duration 1800s
But according to driver logs actual warmup time and duration are incorrect (or
it's just logging problem)
{noformat}
<16:15:35> Preload logger was started.
...
<16:27:19> Preload logger was stopped.
<16:27:19> Probe writer is not configured (using default CSV
writer)
<16:27:19> ThroughputLatencyProbe is started.
<16:27:19> DStatProbe is started. Command: 'dstat -m --all
--noheaders --noupdate 1'
<16:27:19> PercentileProbe is started.
<16:27:19> Starting warmup.
...
<17:02:09> Starting main test (warmup finished).
<17:02:09> Starting iteration: 18
<17:02:09> Starting iteration: 10
<17:02:09> Starting iteration: 9
<17:02:09> Starting iteration: 25
<17:02:09> Starting iteration: 27
<17:02:09> Starting iteration: 23
<17:02:09> Starting iteration: 34
<17:02:09> Starting iteration: 36
<17:02:09> Starting iteration: 41
<17:02:09> Starting iteration: 1
<17:02:09> Starting iteration: 44
<17:02:09> Starting iteration: 46
<17:02:09> Starting iteration: 47
<17:02:09> Starting iteration: 48
<17:02:09> Starting iteration: 39
<17:02:09> Starting iteration: 52
<17:02:09> Starting iteration: 54
<17:02:09> Starting iteration: 56
<17:02:09> Starting iteration: 57
<17:02:09> Starting iteration: 58
<17:02:09> Starting iteration: 20
<17:02:09> Starting iteration: 24
<17:02:09> Starting iteration: 59
<17:02:09> Starting iteration: 60
<17:02:09> Starting iteration: 61
<17:02:09> Starting iteration: 62
<17:02:09> Starting iteration: 63
<17:02:09> Starting iteration: 21
<17:02:09> Starting iteration: 22
<17:02:09> Starting iteration: 7
<17:02:09> Starting iteration: 8
<17:02:09> Starting iteration: 5
<17:02:09> Starting iteration: 3
<17:02:09> Starting iteration: 15
<17:02:09> Starting iteration: 2
<17:02:09> Starting iteration: 11
<17:02:09> Starting iteration: 12
<17:02:09> Starting iteration: 4
<17:02:09> Starting iteration: 16
<17:02:09> Starting iteration: 19
<17:02:09> Starting iteration: 6
<17:02:09> Starting iteration: 17
<17:02:09> Starting iteration: 13
<17:02:09> Starting iteration: 14
<17:02:09> Starting iteration: 64
<17:02:09> Starting iteration: 37
<17:02:09> Starting iteration: 55
<17:02:09> Starting iteration: 53
<17:02:09> Starting iteration: 51
<17:02:09> Starting iteration: 50
<17:02:09> Starting iteration: 49
<17:02:09> Starting iteration: 45
<17:02:09> Starting iteration: 38
<17:02:09> Starting iteration: 42
<17:02:09> Starting iteration: 43
<17:02:09> Starting iteration: 40
<17:02:09> Starting iteration: 35
<17:02:09> Starting iteration: 31
<17:02:09> Starting iteration: 32
<17:02:09> Starting iteration: 33
<17:02:09> Starting iteration: 29
<17:02:09> Starting iteration: 30
<17:02:09> Starting iteration: 28
<17:02:09> Starting iteration: 26
<17:02:10> ThroughputLatencyProbe results will be
saved to: results-20170621-161454/0-172.25.1.31
<17:02:10> DStatProbe results will be saved to:
results-20170621-161454/0-172.25.1.31
...
Finishing main test [ts=1498054591988, date=Wed Jun 21 17:16:31 MSK 2017]
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (IGNITE-5556) Integer to Long cast exception during load test when print cache size
Ksenia Rybakova created IGNITE-5556:
---
Summary: Integer to Long cast exception during load test when
print cache size
Key: IGNITE-5556
URL: https://issues.apache.org/jira/browse/IGNITE-5556
Project: Ignite
Issue Type: Bug
Affects Versions: 2.1
Reporter: Ksenia Rybakova
"java.lang.Integer cannot be cast to java.lang.Long" occurs during preloading
phase of load test.
{noformat}
<13:13:02> Failed to print cache size
[cache=orgCache, msg=class org.apache.ignite.IgniteCheckedException:
java.lang.Integer cannot be cast to java.lang.Long]
[2017-06-20 13:13:02,845][ERROR][pool-4-thread-1][GridTaskWorker] Failed to
reduce job results due to undeclared user exception
[task=o.a.i.i.processors.cache.GridCacheAdapter$SizeLongTask@2d899933,
err=java.lang.ClassCastException: java.lang.Integer cannot be cast to
java.lang.Long]
java.lang.ClassCastException: java.lang.Integer cannot be cast to java.lang.Long
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter$SizeLongTask.reduce(GridCacheAdapter.java:6266)
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter$SizeLongTask.reduce(GridCacheAdapter.java:6210)
at
org.apache.ignite.internal.processors.task.GridTaskWorker$6.call(GridTaskWorker.java:1113)
at
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6608)
at
org.apache.ignite.internal.processors.task.GridTaskWorker.reduce(GridTaskWorker.java:)
at
org.apache.ignite.internal.processors.task.GridTaskWorker.onResponse(GridTaskWorker.java:938)
at
org.apache.ignite.internal.processors.task.GridTaskWorker.processDelayedResponses(GridTaskWorker.java:687)
at
org.apache.ignite.internal.processors.task.GridTaskWorker.body(GridTaskWorker.java:538)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at
org.apache.ignite.internal.processors.task.GridTaskProcessor.startTask(GridTaskProcessor.java:744)
at
org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:443)
at
org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:399)
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter.sizeLongAsync(GridCacheAdapter.java:3742)
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter.sizeLong(GridCacheAdapter.java:3688)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.sizeLong(IgniteCacheProxy.java:1054)
at
org.apache.ignite.yardstick.PreloadLogger.printCacheStatistics(PreloadLogger.java:89)
at
org.apache.ignite.yardstick.PreloadLogger.printCachesStatistics(PreloadLogger.java:72)
at org.apache.ignite.yardstick.PreloadLogger.run(PreloadLogger.java:63)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (IGNITE-5547) Slow streaming and long running transactions while load test with 500 logical caches and PDS
Ksenia Rybakova created IGNITE-5547: --- Summary: Slow streaming and long running transactions while load test with 500 logical caches and PDS Key: IGNITE-5547 URL: https://issues.apache.org/jira/browse/IGNITE-5547 Project: Ignite Issue Type: Bug Affects Versions: 2.1 Reporter: Ksenia Rybakova Load config: - CacheRandomOperation benchmark - Caches: atomic partitioned cache 2 tx partitioned caches 2 atomic partitioned onheap caches 2 atomic replicated onheap caches 2 tx partitioned onheap caches 2 tx replicated onheap caches 3 partitioned atomic indexed caches 30 groups with 10 partitioned caches each (atomic and tx? total 300 logical caches) 20 groups with 10 replicated caches each (atomic and tx, total 200 logical caches) - Preload amount: 10K-30K entries per cache - Key range: 20K - Persistent store is enabled - 32 server nodes (4 nodes per phisical host), 5 client nodes (2 of 5 failed due to benchmark problems) Preloading took 50 minutes that is too long for configured preloading amount. Warmup took an hour instead of configured 5 minutes (possibly because of long running transaction), and operations are also slowed down. Complete configs are attached. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-5534) Enable yardstick to activate grid
Ksenia Rybakova created IGNITE-5534:
---
Summary: Enable yardstick to activate grid
Key: IGNITE-5534
URL: https://issues.apache.org/jira/browse/IGNITE-5534
Project: Ignite
Issue Type: Wish
Components: yardstick
Affects Versions: 2.1
Reporter: Ksenia Rybakova
If we run benchmarks with pds enabled grid starts inactive, that causes an
error:
{noformat}
[2017-06-19 10:56:36,917][INFO ][main][root] Benchmark arguments:
IgniteBenchmarkArguments [nodes=37, backups=1,
cfg=/storage/ssd/krybakova/opts-set-w-300-d-1800-m-client-rev-8b66f3b2-date-1906-105549/yardstick/bin/../config/run-load.xml,
loadTestQueriesFile=/storage/ssd/krybakova/opts-set-w-300-d-1800-m-client-rev-8b66f3b2-date-1906-105549/yardstick/bin/../config/queries.sql,
syncMode=PRIMARY_SYNC, clientOnly=true, nearCacheFlag=false, nearCacheSize=0,
txConcurrency=PESSIMISTIC, txIsolation=REPEATABLE_READ, restTcpPort=0,
restTcpHost=null, range=6, scaleFactor=1, ntv=false, preloadAmount=5,
preloadLogsInterval=3, jobs=10, storeEnabled=false,
cleanWorkDirectory=false, writeBehind=false, batch=50, collocated=false,
singleStripe=false, jdbcUrl=null, schemaDefinition=null, jdbcDriver=null,
createTempDatabase=false, dbn=null, restartDelay=20, restartSleep=2,
cacheConsistencyCheckingPeriod=120, keysCnt=5, cacheOpTimeout=30,
keysPerThread=false, partitionedCachesNumber=1, replicatedCachesNumber=1,
additionalCachesNum=0, additionalCachesName=null, printPartStats=false,
pageSize=2048, partitions=10, cacheGrp=null, cachesCnt=1,
persistentStoreEnabled=false]
<10:56:36> Failed to set up benchmark drivers (will shutdown
and exit).
[2017-06-19 10:56:36,917][INFO ][exchange-worker-#41%null%][time] Started
exchange init [topVer=AffinityTopologyVersion [topVer=37, minorTopVer=0],
crd=false, evt=10, node=TcpDiscoveryNode
[id=adf2cf44-283b-4dfb-97d0-08ced87e9dde, addrs=[127.0.0.1, 172.25.1.31],
sockAddrs=[testagent01.gridgain.local/172.25.1.31:0, /127.0.0.1:0], discPort=0,
order=33, intOrder=0, lastExchangeTime=1497858993142, loc=true,
ver=2.1.0#20170616-sha1:8b66f3b2, isClient=true], evtNode=TcpDiscoveryNode
[id=adf2cf44-283b-4dfb-97d0-08ced87e9dde, addrs=[127.0.0.1, 172.25.1.31],
sockAddrs=[testagent01.gridgain.local/172.25.1.31:0, /127.0.0.1:0], discPort=0,
order=33, intOrder=0, lastExchangeTime=1497858993142, loc=true,
ver=2.1.0#20170616-sha1:8b66f3b2, isClient=true], customEvt=null]
class org.apache.ignite.IgniteException: Can not perform the operation because
the cluster is inactive. Note, that the cluster is considered inactive by
default if Ignite Persistent Store is used to let all the nodes join the
cluster. To activate the cluster call Ignite.activate(true).
at
org.apache.ignite.internal.IgniteKernal.checkClusterState(IgniteKernal.java:3666)[2017-06-19
10:56:36,917][INFO ][exchange-worker-#41%null%][time] Finished exchange init
[topVer=AffinityTopologyVersion [topVer=37, minorTopVer=0], crd=false]
at
org.apache.ignite.internal.IgniteKernal.cacheNames(IgniteKernal.java:3188)
at
org.apache.ignite.yardstick.cache.load.IgniteCacheRandomOperationBenchmark.searchCache(IgniteCacheRandomOperationBenchmark.java:235)
at
org.apache.ignite.yardstick.cache.load.IgniteCacheRandomOperationBenchmark.setUp(IgniteCacheRandomOperationBenchmark.java:145)
at
org.yardstickframework.BenchmarkDriverStartUp.main(BenchmarkDriverStartUp.java:130)
{noformat}
Please add some option that whould control if driver should activate a grid or
not.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (IGNITE-5433) Incorrect warning when "default" memory policy is used
Ksenia Rybakova created IGNITE-5433:
---
Summary: Incorrect warning when "default" memory policy is used
Key: IGNITE-5433
URL: https://issues.apache.org/jira/browse/IGNITE-5433
Project: Ignite
Issue Type: Bug
Affects Versions: 2.1
Reporter: Ksenia Rybakova
Priority: Minor
Fix For: 2.1
The following memory config is used:
{noformat}
{noformat}
No any additional memory policies are configured.
Server RAM is 98Gb (at least 50Gb is free). Default memory policy should use
80% of it.
But warning in log is:
{noformat}
[WARN ][main][IgniteCacheDatabaseSharedManager] No user-defined default
MemoryPolicy found; system default of 1GB size will be used.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (IGNITE-5209) "IllegalStateException: Already swapped" error with offheap_tired indexed cache
Ksenia Rybakova created IGNITE-5209:
---
Summary: "IllegalStateException: Already swapped" error with
offheap_tired indexed cache
Key: IGNITE-5209
URL: https://issues.apache.org/jira/browse/IGNITE-5209
Project: Ignite
Issue Type: Bug
Affects Versions: 1.9
Reporter: Ksenia Rybakova
The following error occurs during load test and causes client fail:
{noformat}
<12:33:26> The benchmark of random operation
failed.
javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException:
Failed to update keys on primary node.
at
org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1443)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.cacheException(IgniteCacheProxy.java:2182)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.putAll(IgniteCacheProxy.java:1429)
at
org.apache.ignite.yardstick.cache.load.IgniteCacheRandomOperationBenchmark.doPutAll(IgniteCacheRandomOperationBenchmark.java:712)
at
org.apache.ignite.yardstick.cache.load.IgniteCacheRandomOperationBenchmark.executeRandomOperation(IgniteCacheRandomOperationBenchmark.java:566)
at
org.apache.ignite.yardstick.cache.load.IgniteCacheRandomOperationBenchmark.executeOutOfTx(IgniteCacheRandomOperationBenchmark.java:548)
at
org.apache.ignite.yardstick.cache.load.IgniteCacheRandomOperationBenchmark.test(IgniteCacheRandomOperationBenchmark.java:157)
at
org.yardstickframework.impl.BenchmarkRunner$2.run(BenchmarkRunner.java:178)
at java.lang.Thread.run(Thread.java:745)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to update
keys on primary node.
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateResponse.addFailedKeys(GridNearAtomicUpdateResponse.java:370)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:2023)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1776)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.processNearAtomicUpdateRequest(GridDhtAtomicCache.java:3254)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$1600(GridDhtAtomicCache.java:131)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$6.apply(GridDhtAtomicCache.java:342)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$6.apply(GridDhtAtomicCache.java:337)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:827)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:369)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:293)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$000(GridCacheIoManager.java:95)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:238)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1224)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:852)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$2100(GridIoManager.java:109)
at
org.apache.ignite.internal.managers.communication.GridIoManager$7.run(GridIoManager.java:792)
at
org.apache.ignite.internal.util.StripedExecutor$Stripe.run(StripedExecutor.java:428)
... 1 more
Suppressed: java.lang.IllegalStateException: Already swapped:
140510727619712
at
org.apache.ignite.internal.processors.query.h2.opt.GridH2KeyValueRowOffheap.onSwap(GridH2KeyValueRowOffheap.java:201)
at
org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.onSwapUnswap(GridH2Table.java:230)
at
org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.onSwap(GridH2Table.java:181)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.onSwap(IgniteH2Indexing.java:736)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.onSwap(GridQueryProcessor.java:1183)
at
org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.onSwap(GridCacheQueryManager.java:398)
at
org.apache.ignite.internal.processors.cache.GridCacheSwapManager.write(GridCacheSwapManager.java:1381)
at
[jira] [Created] (IGNITE-5202) Default mem policy name is not changed after setting defaultMemoryPolicyName property
Ksenia Rybakova created IGNITE-5202:
---
Summary: Default mem policy name is not changed after setting
defaultMemoryPolicyName property
Key: IGNITE-5202
URL: https://issues.apache.org/jira/browse/IGNITE-5202
Project: Ignite
Issue Type: Bug
Affects Versions: 2.0
Reporter: Ksenia Rybakova
Fix For: 2.1
Default mem policy name is not changed after setting defaultMemoryPolicyName
property.
Config:
{noformat}
http://www.springframework.org/schema/beans;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans-2.5.xsd;>
...
{noformat}
{noformat}
http://www.springframework.org/schema/beans;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans-2.5.xsd;>
...
...
...
...
{noformat}
According to this config default memory policy should be "default2", but it
remains "default" (while SystemCacheInitialSize was changed successfully to
50Mb as it's set in config).
{noformat}
[12:48:12,226][INFO ][main][IgniteKernal] System cache's MemoryPolicy size is
configured to 50 MB. Use MemoryConfiguration.systemCacheMemorySize property to
change the setting.
[12:48:12,226][INFO ][main][IgniteKernal] Configured caches [in 'default'
memoryPolicy: ['ignite-sys-cache', 'ignite-atomics-sys-cache', 'atomic-part',
'atomic-rplc', 'atomic-part-fat-values', 'atomic-part-onheap-evict-fifo',
'atomic-rplc-onheap-evict-lru', 'tx-part', 'tx-rplc', 'tx-part-fat-values',
'compute', 'tx-part-onheap-evict-lru', 'tx-rplc-onheap-evict-fifo',
'atomic-index', 'query', 'orgCache']]
{noformat}
Also it would be nice to have default policy name instead of "null" in logs
when printing caches info:
{noformat}
<12:48:12> Cache configured with the following parameters:
CacheConfiguration [name=atomic-part, memPlcName=null,
storeConcurrentLoadAllThreshold=5, ...
{noformat}
{noformat}
[12:48:13,239][INFO ][main][GridCacheProcessor] Started cache
[name=atomic-part, memoryPolicyName=null, mode=PARTITIONED]
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (IGNITE-5192) NPE at CacheDataStoreImpl.canUpdateOldRow during load test
Ksenia Rybakova created IGNITE-5192:
---
Summary: NPE at CacheDataStoreImpl.canUpdateOldRow during load test
Key: IGNITE-5192
URL: https://issues.apache.org/jira/browse/IGNITE-5192
Project: Ignite
Issue Type: Bug
Affects Versions: 2.0
Reporter: Ksenia Rybakova
NPE occurs during load test:
{noformat}
[14:05:37,145][ERROR][sys-stripe-5-#6%null%][GridDhtTxLocal] Heuristic
transaction failure.
class
org.apache.ignite.internal.transactions.IgniteTxHeuristicCheckedException:
Failed to locally write to cache (all transaction entries will be invalidated,
however there was a window when entries for this transaction were visible to
others) ...
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxLocalAdapter.userCommit(IgniteTxLocalAdapter.java:829)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocalAdapter.localFinish(GridDhtTxLocalAdapter.java:772)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.localFinish(GridDhtTxLocal.java:580)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.finishTx(GridDhtTxLocal.java:466)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.commitDhtLocalAsync(GridDhtTxLocal.java:514)
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.finishDhtLocal(IgniteTxHandler.java:841)
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.finish(IgniteTxHandler.java:720)
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processNearTxFinishRequest(IgniteTxHandler.java:676)
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.access$200(IgniteTxHandler.java:95)
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$3.apply(IgniteTxHandler.java:153)
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$3.apply(IgniteTxHandler.java:151)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:863)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:386)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:308)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$000(GridCacheIoManager.java:100)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:253)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1257)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:885)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$2100(GridIoManager.java:114)
at
org.apache.ignite.internal.managers.communication.GridIoManager$7.run(GridIoManager.java:802)
at
org.apache.ignite.internal.util.StripedExecutor$Stripe.run(StripedExecutor.java:483)
at java.lang.Thread.run(Thread.java:745)
Caused by: class org.apache.ignite.IgniteException: Runtime failure on search
row:
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$SearchRow@55f39849
at
org.apache.ignite.internal.processors.cache.database.tree.BPlusTree.invoke(BPlusTree.java:1615)
at
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke(IgniteCacheOffheapManagerImpl.java:925)
at
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.invoke(IgniteCacheOffheapManagerImpl.java:326)
at
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.storeValue(GridCacheMapEntry.java:3241)
at
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.innerSet(GridCacheMapEntry.java:992)
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxLocalAdapter.userCommit(IgniteTxLocalAdapter.java:663)
... 21 more
Caused by: java.lang.NullPointerException
at
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.canUpdateOldRow(IgniteCacheOffheapManagerImpl.java:913)
at
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.createRow(IgniteCacheOffheapManagerImpl.java:970)
at
org.apache.ignite.internal.processors.cache.GridCacheMapEntry$UpdateClosure.call(GridCacheMapEntry.java:3937)
at
org.apache.ignite.internal.processors.cache.GridCacheMapEntry$UpdateClosure.call(GridCacheMapEntry.java:3895)
at
[jira] [Created] (IGNITE-5151) Add some warning when offheap eviction occurs
Ksenia Rybakova created IGNITE-5151: --- Summary: Add some warning when offheap eviction occurs Key: IGNITE-5151 URL: https://issues.apache.org/jira/browse/IGNITE-5151 Project: Ignite Issue Type: Improvement Affects Versions: 2.0 Reporter: Ksenia Rybakova Currently if offheap eviction occurs we are silently losing data. It whould be helpful to have some warning in log as it's done for onheap eviction. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-5150) Allocated memory pages count is incorrect during load test
Ksenia Rybakova created IGNITE-5150:
---
Summary: Allocated memory pages count is incorrect during load test
Key: IGNITE-5150
URL: https://issues.apache.org/jira/browse/IGNITE-5150
Project: Ignite
Issue Type: Bug
Affects Versions: 2.0
Reporter: Ksenia Rybakova
Load test config:
- CacheRandomOpearion benchmark
- 1 server (-Xms4g -Xmx4g)
- 1 client (-Xms4g -Xmx4g)
- 1 cache with following config
{noformat}
{noformat}
- preloaded data: 40M entries
- backup count: 0
- memory config:
{noformat}
{noformat}
40M entries consume about 4Gb offheap memory. It might be proved by [[top]]
command (RES value - JVM memory = 8Gb - 4Gb) or by summing all "Allocated next
memory segment" printed in server log.
After all data preloaded metrics show the following:
{noformat}
[18:37:18,152][INFO ][grid-timeout-worker-#23%null%][IgniteKernal]
Metrics for local node (to disable set 'metricsLogFrequency' to 0)
^-- Node [id=dc009e3c, name=null, uptime=00:02:10:102]
^-- H/N/C [hosts=2, nodes=2, CPUs=32]
^-- CPU [cur=19.53%, avg=11.99%, GC=0.03%]
^-- PageMemory [pages=22527667]
^-- Heap [used=238MB, free=94.17%, comm=4096MB]
^-- Non heap [used=40MB, free=68.18%, comm=45MB]
^-- Public thread pool [active=0, idle=0, qSize=0]
^-- System thread pool [active=0, idle=10, qSize=0]
^-- Outbound messages queue [size=0]
{noformat}
pages=22527667 seems to be wrong, otherwise offheap memory size would be
22527667 * 2KB = about 43Gb.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (IGNITE-4734) Sporadic GridServiceNotFoundException in ServiceExample
Ksenia Rybakova created IGNITE-4734:
---
Summary: Sporadic GridServiceNotFoundException in ServiceExample
Key: IGNITE-4734
URL: https://issues.apache.org/jira/browse/IGNITE-4734
Project: Ignite
Issue Type: Bug
Components: general
Affects Versions: 1.7
Reporter: Ksenia Rybakova
Sometimes ServiceExample thows GridServiceNotFoundException
Configs might be different - 1 node/3 nodes, linux/windows
Driver node log:
{noformat}
[10:50:31,428][INFO][main][GridDiscoveryManager] Topology snapshot [ver=2,
servers=1, clients=1, CPUs=4, heap=2.0GB]
>>>
>>> Starting service proxy example.
>>>
[10:50:31,768][SEVERE][sys-#32%null%][GridTaskWorker] Failed to obtain remote
job result policy for result from ComputeTask.result(..) method (will fail the
whole task): GridJobResultImpl [job=C2V2 [c=ServiceProxyCallable [mtdName=put,
svcName=myNodeSingletonService, ignite=null]], sib=GridJobSiblingImpl
[sesId=b2c66af5a51-87f5f92a-d9ee-4119-90a5-35659bd7e50d,
jobId=d2c66af5a51-87f5f92a-d9ee-4119-90a5-35659bd7e50d,
nodeId=01aea3a3-0981-4760-a26b-732afc4a8a27, isJobDone=false],
jobCtx=GridJobContextImpl
[jobId=d2c66af5a51-87f5f92a-d9ee-4119-90a5-35659bd7e50d, timeoutObj=null,
attrs={}], node=TcpDiscoveryNode [id=01aea3a3-0981-4760-a26b-732afc4a8a27,
addrs=[127.0.0.1, 172.25.2.17], sockAddrs=[/172.25.2.17:47500,
/127.0.0.1:47500], discPort=47500, order=1, intOrder=1,
lastExchangeTime=1487663430926, loc=false, ver=1.7.8#20170220-sha1:6112bce9,
isClient=false], ex=class o.a.i.IgniteException: Service not found:
myNodeSingletonService, hasRes=true, isCancelled=false, isOccupied=true]
class org.apache.ignite.IgniteException: Remote job threw user exception
(override or implement ComputeTask.result(..) method if you would like to have
automatic failover for this exception).
at
org.apache.ignite.compute.ComputeTaskAdapter.result(ComputeTaskAdapter.java:101)
at
org.apache.ignite.internal.processors.task.GridTaskWorker$5.apply(GridTaskWorker.java:1031)
at
org.apache.ignite.internal.processors.task.GridTaskWorker$5.apply(GridTaskWorker.java:1024)
at
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6596)
at
org.apache.ignite.internal.processors.task.GridTaskWorker.result(GridTaskWorker.java:1024)
at
org.apache.ignite.internal.processors.task.GridTaskWorker.onResponse(GridTaskWorker.java:842)
at
org.apache.ignite.internal.processors.task.GridTaskProcessor.processJobExecuteResponse(GridTaskProcessor.java:996)
at
org.apache.ignite.internal.processors.task.GridTaskProcessor$JobMessageListener.onMessage(GridTaskProcessor.java:1221)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1082)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:710)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:102)
at
org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:673)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: class org.apache.ignite.IgniteException: Service not found:
myNodeSingletonService
at
org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2V2.execute(GridClosureProcessor.java:2059)
at
org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:560)
at
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6564)
at
org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:554)
at
org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:483)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at
org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1180)
at
org.apache.ignite.internal.processors.job.GridJobProcessor$JobExecutionListener.onMessage(GridJobProcessor.java:1894)
... 7 more
Caused by: class
org.apache.ignite.internal.processors.service.GridServiceNotFoundException:
Service not found: myNodeSingletonService
at
org.apache.ignite.internal.processors.service.GridServiceProxy$ServiceProxyCallable.call(GridServiceProxy.java:397)
at
org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2V2.execute(GridClosureProcessor.java:2056)
... 14 more
Map service size: 10
>>>
>>> Starting service injection example.
>>>
[10:50:31,905][INFO][main][GridDeploymentLocalStore] Class locally
[jira] [Created] (IGNITE-4722) CacheRandomOperation benchmark: preloading as separate benchmarl with ability to load in a loop
Ksenia Rybakova created IGNITE-4722: --- Summary: CacheRandomOperation benchmark: preloading as separate benchmarl with ability to load in a loop Key: IGNITE-4722 URL: https://issues.apache.org/jira/browse/IGNITE-4722 Project: Ignite Issue Type: Improvement Components: yardstick Reporter: Ksenia Rybakova Fix For: 1.8 We need an ability to perform preloading (streaming) test for quite long time (2 hours or even more). Currently this might be done only by setting preloading amount parameter to some really big value. This requires lot of memory and many nodes in the cluster. This is not always possible due to hardware limits. Suggest moving preloading from CacheRandomOperation benchmark to a separate one and add ability to perform it in a loop during predefined time. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-4616) Yardstick makes wrong restarts when several servers are at the same host
Ksenia Rybakova created IGNITE-4616:
---
Summary: Yardstick makes wrong restarts when several servers are
at the same host
Key: IGNITE-4616
URL: https://issues.apache.org/jira/browse/IGNITE-4616
Project: Ignite
Issue Type: Bug
Components: yardstick
Affects Versions: 1.8
Reporter: Ksenia Rybakova
During failover test yardstick makes wrong restarts when several servers are at
the same host and first digits of their ids match (1 and 12,13,etc.; 2 and
27,22,etc.; 7 and 70,74,etc.)
For instance, we have the following RESTART_SERVERS option:
{noformat}
hostA:1:600:1200:6000,hostB:2:900:1200:6000,hostA:11:1200:1200:6000,hostB:12:1500:1200:6000,hostA:20:1800:1200:6000,hostB:21:2100:1200:6000
{noformat}
During server id1 restart at hostA server id11 also will be restarted, server
id12 won't be restarted since it's at another host.
During server id2 restart at hostB server id21 will be restarted as well while
server id20 won't.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-4502) JVM driver crash during load test
Ksenia Rybakova created IGNITE-4502:
---
Summary: JVM driver crash during load test
Key: IGNITE-4502
URL: https://issues.apache.org/jira/browse/IGNITE-4502
Project: Ignite
Issue Type: Bug
Affects Versions: 1.7
Reporter: Ksenia Rybakova
During load test one of the driver JVMs failed with the following
{noformat}
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x7f781306426d, pid=9061, tid=140153654769408
#
# JRE version: Java(TM) SE Runtime Environment (7.0_79-b15) (build 1.7.0_79-b15)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (24.79-b02 mixed mode linux-amd64
compressed oops)
# Problematic frame:
# C [libc.so.6+0x8a26d][thread 140153650558720 also had an error]
__memset_sse2+0x95d
{noformat}
Error report file is attached.
Revision:
5494dfb8 (but ignite-yardstick lib was replaced with newer version,
corresponding jar is attached)
This issue is of one time occurrence.
Load config:
- Operations: put, put_all, get, get_all, invoke, invoke_all, remove,
remove_all, put_if_absent, replace
- Heap: 8Gb for servers, 4Gb for clients
- 5 clients, 20 servers
- 12 caches
- Types of caches (atomicity mode) : different (atomic, transactional)
- Types of caches (tiered storage mode) : different (onheap without eviction,
onheap with eviction, offheap_tired, offheap_values)
- Types of caches (indexing): different (with and without indexes)
- Types of caches (cache mode): different (partitioned, replicated)
- Backups count: 1
- TLSv1.2 is enabled
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-4456) ODBC DML: add to doc some info on how to deal with complex affinity key and partitioned cache
Ksenia Rybakova created IGNITE-4456:
---
Summary: ODBC DML: add to doc some info on how to deal with
complex affinity key and partitioned cache
Key: IGNITE-4456
URL: https://issues.apache.org/jira/browse/IGNITE-4456
Project: Ignite
Issue Type: Improvement
Affects Versions: 1.8
Reporter: Ksenia Rybakova
Example:
{code}
CacheConfiguration personCacheCfg = new
CacheConfiguration<>("Persons");
...
public AffinityKey key() {
if (key == null)
key = new AffinityKey<>(id, orgId);
return key;
}
{code}
Currently it's not obvious that in such a case we should:
1) Use QueryEntity to specify {{key}} and {{affKey}} as key fields as it's
described in https://apacheignite.readme.io/docs/dml#section-custom-keys
2) Use {{key}} and {{affKey}} in statements directly instead of {{_key}}:
{code}
"INSERT INTO Person(key, affKey, firstName, lastName, resume, salary, orgId)
VALUES (42, 2, 'Ivan', 'Ivanov', 'Ivan Ivanov has no
degree', CAST(300 AS DOUBLE), 2)"
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-4443) .NET: doc for 1.7: there is no TransactionDeadlockException class
Ksenia Rybakova created IGNITE-4443: --- Summary: .NET: doc for 1.7: there is no TransactionDeadlockException class Key: IGNITE-4443 URL: https://issues.apache.org/jira/browse/IGNITE-4443 Project: Ignite Issue Type: Bug Components: documentation Affects Versions: 1.7 Reporter: Ksenia Rybakova Priority: Minor https://apacheignite-net.readme.io/v1.7/docs/transactions#deadlock-detection-in-pessimistic-transactions mentions TransactionDeadlockException class, but this class is absent in 1.7 version. Please, make corresponding corrections. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-4430) .NET: Cannot convert the "Name" value of type "System.String" to type "System.Management.Automation.Scr iptBlock"
Ksenia Rybakova created IGNITE-4430:
---
Summary: .NET: Cannot convert the "Name" value of type
"System.String" to type "System.Management.Automation.Scr iptBlock"
Key: IGNITE-4430
URL: https://issues.apache.org/jira/browse/IGNITE-4430
Project: Ignite
Issue Type: Bug
Components: platforms
Affects Versions: 1.8
Reporter: Ksenia Rybakova
Priority: Minor
Environment:
- Windows7
- VS 2015
- NuGet Package Manager 3.4.4
- Powershell version
{noformat}
PS C:\Users\San> $PSVersionTable.PSVersion
Major Minor Build Revision
- - -
2 0 -1 -1
{noformat}
While installing/uninstalling Apache.Ignite package the following exception
occurs
{noformat}
PM> Install-Package Apache.Ignite -Source
https://www.myget.org/F/apache-ignite-staging/api/v2 -Version 1.8.1
Attempting to gather dependency information for package 'Apache.Ignite.1.8.1'
with respect to project 'WebApplication1', targeting
'.NETFramework,Version=v4.5.2'
Attempting to resolve dependencies for package 'Apache.Ignite.1.8.1' with
DependencyBehavior 'Lowest'
Resolving actions to install package 'Apache.Ignite.1.8.1'
Resolved actions to install package 'Apache.Ignite.1.8.1'
Adding package 'Apache.Ignite.1.8.1' to folder
'D:\Work_Ksu\Platform_tests\WebApplication1\packages'
Added package 'Apache.Ignite.1.8.1' to folder
'D:\Work_Ksu\Platform_tests\WebApplication1\packages'
Added package 'Apache.Ignite.1.8.1' to 'packages.config'
Executing script file
'D:\Work_Ksu\Platform_tests\WebApplication1\packages\Apache.Ignite.1.8.1\tools\Install.ps1'
Updating project properties...
Where-Object : Cannot bind parameter 'FilterScript'. Cannot convert the "Name"
value of type "System.String" to type "System.Management.Automation.Scr
iptBlock".
At
D:\Work_Ksu\Platform_tests\WebApplication1\packages\Apache.Ignite.1.8.1\tools\Install.ps1:33
char:37
+ $binDir = ($_.Properties | Where Name -match OutputPath).Value
+ CategoryInfo : InvalidArgument: (:) [Where-Object],
ParameterBindingException
+ FullyQualifiedErrorId :
CannotConvertArgumentNoMessage,Microsoft.PowerShell.Commands.WhereObjectCommand
Where-Object : Cannot bind parameter 'FilterScript'. Cannot convert the "Name"
value of type "System.String" to type "System.Management.Automation.Scr
iptBlock".
At
D:\Work_Ksu\Platform_tests\WebApplication1\packages\Apache.Ignite.1.8.1\tools\Install.ps1:33
char:37
+ $binDir = ($_.Properties | Where Name -match OutputPath).Value
+ CategoryInfo : InvalidArgument: (:) [Where-Object],
ParameterBindingException
+ FullyQualifiedErrorId :
CannotConvertArgumentNoMessage,Microsoft.PowerShell.Commands.WhereObjectCommand
Welcome to Apache Ignite.NET!
Successfully installed 'Apache.Ignite 1.8.1' to WebApplication1
PM>
PM> Uninstall-Package Apache.Ignite
Attempting to gather dependency information for package 'Apache.Ignite.1.8.1'
with respect to project 'WebApplication1', targeting
'.NETFramework,Version=v4.5.2'
Resolving actions to uninstall package 'Apache.Ignite.1.8.1'
Resolved actions to uninstall package 'Apache.Ignite.1.8.1'
Executing script file
'D:\Work_Ksu\Platform_tests\WebApplication1\packages\Apache.Ignite.1.8.1\tools\Uninstall.ps1'
Where-Object : Cannot bind parameter 'FilterScript'. Cannot convert the "Name"
value of type "System.String" to type "System.Management.Automation.Scr
iptBlock".
At
D:\Work_Ksu\Platform_tests\WebApplication1\packages\Apache.Ignite.1.8.1\tools\Uninstall.ps1:29
char:37
+ $binDir = ($_.Properties | Where Name -match OutputPath).Value
+ CategoryInfo : InvalidArgument: (:) [Where-Object],
ParameterBindingException
+ FullyQualifiedErrorId :
CannotConvertArgumentNoMessage,Microsoft.PowerShell.Commands.WhereObjectCommand
Where-Object : Cannot bind parameter 'FilterScript'. Cannot convert the "Name"
value of type "System.String" to type "System.Management.Automation.Scr
iptBlock".
At
D:\Work_Ksu\Platform_tests\WebApplication1\packages\Apache.Ignite.1.8.1\tools\Uninstall.ps1:29
char:37
+ $binDir = ($_.Properties | Where Name -match OutputPath).Value
+ CategoryInfo : InvalidArgument: (:) [Where-Object],
ParameterBindingException
+ FullyQualifiedErrorId :
CannotConvertArgumentNoMessage,Microsoft.PowerShell.Commands.WhereObjectCommand
Removed package 'Apache.Ignite.1.8.1' from 'packages.config'
Successfully uninstalled 'Apache.Ignite.1.8.1' from WebApplication1
Removing package 'Apache.Ignite.1.8.1' from folder
'D:\Work_Ksu\Platform_tests\WebApplication1\packages'
Removed package 'Apache.Ignite.1.8.1' from folder
'D:\Work_Ksu\Platform_tests\WebApplication1\packages'
PM>
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-4372) Set up code coverage reports
Ksenia Rybakova created IGNITE-4372: --- Summary: Set up code coverage reports Key: IGNITE-4372 URL: https://issues.apache.org/jira/browse/IGNITE-4372 Project: Ignite Issue Type: Improvement Reporter: Ksenia Rybakova Assignee: Ksenia Rybakova -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-4322) .NET: ClientReconnectExample is not clear enough
Ksenia Rybakova created IGNITE-4322:
---
Summary: .NET: ClientReconnectExample is not clear enough
Key: IGNITE-4322
URL: https://issues.apache.org/jira/browse/IGNITE-4322
Project: Ignite
Issue Type: Bug
Components: platforms
Affects Versions: 1.8
Reporter: Ksenia Rybakova
ClientReconnectExample has the following output
{noformat}
>>> Client reconnect example started.
[13:19:53]__
[13:19:53] / _/ ___/ |/ / _/_ __/ __/
[13:19:53] _/ // (7 7// / / / / _/
[13:19:53] /___/\___/_/|_/___/ /_/ /___/
[13:19:53]
[13:19:53] ver. 1.8.0-QASK2501#20161125-sha1:ccbe6007
[13:19:53] 2016 Copyright(C) Apache Software Foundation
[13:19:53]
[13:19:53] Ignite documentation: http://ignite.apache.org
[13:19:53]
[13:19:53] Quiet mode.
[13:19:53] ^-- Logging to file
'C:\WORK\Releases\apache-ignite-fabric-1.8.0-QASK2501-bin\work\log\ignite-a18708d8.0.log'
[13:19:53] ^-- To see **FULL** console log here add -DIGNITE_QUIET=false or
"-v" to ignite.{sh|bat}
[13:19:53]
[13:19:53] OS: Windows 10 10.0 amd64
[13:19:53] VM information: Java(TM) SE Runtime Environment 1.8.0_91-b14 Oracle
Corporation Java HotSpot(TM) 64-Bit Server VM 25.91-b14
[13:19:53] Initial heap size is 256MB (should be no less than 512MB, use
-Xms512m -Xmx512m).
[13:19:53] Configured plugins:
[13:19:53] ^-- None
[13:19:53]
[13:19:58] Security status [authentication=off, tls/ssl=off]
[13:19:59] Performance suggestions for grid 'serverNode' (fix if possible)
[13:19:59] To disable, set -DIGNITE_PERFORMANCE_SUGGESTIONS_DISABLED=true
[13:19:59] ^-- Disable grid events (remove 'includeEventTypes' from
configuration)
[13:19:59] ^-- Disable fully synchronous writes (set
'writeSynchronizationMode' to PRIMARY_SYNC or FULL_ASYNC)
[13:19:59]
[13:19:59] To start Console Management & Monitoring run ignitevisorcmd.{sh|bat}
[13:19:59]
[13:19:59] Ignite node started OK (id=a18708d8, grid=serverNode)
[13:19:59] Topology snapshot [ver=1, servers=1, clients=0, CPUs=4, heap=3.5GB]
>>> Server node started.
[13:20:00]__
[13:20:00] / _/ ___/ |/ / _/_ __/ __/
[13:20:00] _/ // (7 7// / / / / _/
[13:20:00] /___/\___/_/|_/___/ /_/ /___/
[13:20:00]
[13:20:00] ver. 1.8.0-QASK2501#20161125-sha1:ccbe6007
[13:20:00] 2016 Copyright(C) Apache Software Foundation
[13:20:00]
[13:20:00] Ignite documentation: http://ignite.apache.org
[13:20:00]
[13:20:00] Quiet mode.
[13:20:00] ^-- Logging to file
'C:\WORK\Releases\apache-ignite-fabric-1.8.0-QASK2501-bin\work\log\ignite-a18708d8.0.log'
[13:20:00] ^-- To see **FULL** console log here add -DIGNITE_QUIET=false or
"-v" to ignite.{sh|bat}
[13:20:00]
[13:20:00] OS: Windows 10 10.0 amd64
[13:20:00] VM information: Java(TM) SE Runtime Environment 1.8.0_91-b14 Oracle
Corporation Java HotSpot(TM) 64-Bit Server VM 25.91-b14
[13:20:00] Initial heap size is 256MB (should be no less than 512MB, use
-Xms512m -Xmx512m).
[13:20:00] Configured plugins:
[13:20:00] ^-- None
[13:20:00]
[13:20:00] Security status [authentication=off, tls/ssl=off]
[13:20:02] Topology snapshot [ver=2, servers=1, clients=1, CPUs=4, heap=3.5GB]
[13:20:02] To start Console Management & Monitoring run ignitevisorcmd.{sh|bat}
[13:20:02]
[13:20:02] Ignite node started OK (id=2f5922f5)
[13:20:02] Topology snapshot [ver=2, servers=1, clients=1, CPUs=4, heap=3.5GB]
>>> Client node connected to the cluster.
>>> Put value with key:0
>>> Put value with key:1
>>> Put value with key:2
[13:20:04,824][SEVERE][tcp-client-disco-sock-writer-#5%null%][TcpDiscoverySpi]
Failed to send message: TcpDiscoveryClientPingRequest
[nodeToPing=a18708d8-e489-4b47-a8e9-e16efc6b814e,
super=TcpDiscoveryAbstractMessage [sndNodeId=null,
id=a9fa27aa851-2f5922f5-d38b-4b4f-80cf-feec8bf52013, verifierNodeId=null,
topVer=0, pendingIdx=0, failedNodes=null, isClient=false]]
java.net.SocketException: Socket is closed
at java.net.Socket.getOutputStream(Socket.java:943)
at
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.writeToSocket(TcpDiscoverySpi.java:1354)
at
org.apache.ignite.spi.discovery.tcp.ClientImpl$SocketWriter.body(ClientImpl.java:1088)
at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
[13:20:04] Ignite node stopped OK [name=serverNode, uptime=00:00:04:899]
>>> Put value with key:3
[13:20:09] New version is available at ignite.apache.org: 1.7.0
>>> Restarting server node...
[13:20:09]__
[13:20:09] / _/ ___/ |/ / _/_ __/ __/
[13:20:09] _/ // (7 7// / / / / _/
[13:20:09] /___/\___/_/|_/___/ /_/ /___/
[13:20:09]
[13:20:09] ver. 1.8.0-QASK2501#20161125-sha1:ccbe6007
[13:20:09] 2016 Copyright(C) Apache Software Foundation
[13:20:09]
[13:20:09] Ignite documentation: http://ignite.apache.org
[13:20:09]
[13:20:09] Quiet mode.
[13:20:09] ^-- Logging to file
[jira] [Created] (IGNITE-4311) .NET: MultiTieredCacheExample has some issues
Ksenia Rybakova created IGNITE-4311:
---
Summary: .NET: MultiTieredCacheExample has some issues
Key: IGNITE-4311
URL: https://issues.apache.org/jira/browse/IGNITE-4311
Project: Ignite
Issue Type: Bug
Components: platforms
Affects Versions: 1.8
Reporter: Ksenia Rybakova
Apache.Ignite.Examples.Datagrid.MultiTieredCacheExample has some issues:
1) Typo
{noformat}
Console.WriteLine(">>> Lifecycle example started.");
{noformat}
2)
{noformat}
OffHeapMaxMemory = EntrySize * 10, // Limit off-heap to 10 entries.
{noformat}
This size is not enough to store 10 entries, overhead is not taked into
account. In my case some experiments showed that (EntrySize * 10) + 810 is
minimum.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-4299) Remove useless cin.get() in query_example.cpp
Ksenia Rybakova created IGNITE-4299:
---
Summary: Remove useless cin.get() in query_example.cpp
Key: IGNITE-4299
URL: https://issues.apache.org/jira/browse/IGNITE-4299
Project: Ignite
Issue Type: Bug
Components: platforms
Reporter: Ksenia Rybakova
Priority: Minor
Remove useless cin.get() in query_example.cpp:
{noformat}
std::cout << ">>> Ready" << std::endl;
std::cout << std::endl;
std::cin.get();
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-4232) "IllegalArgumentException: Cache is not configured: ignite-marshaller-sys-cache" while starting grid
Ksenia Rybakova created IGNITE-4232:
---
Summary: "IllegalArgumentException: Cache is not configured:
ignite-marshaller-sys-cache" while starting grid
Key: IGNITE-4232
URL: https://issues.apache.org/jira/browse/IGNITE-4232
Project: Ignite
Issue Type: Bug
Affects Versions: 1.6
Reporter: Ksenia Rybakova
While starting a grid with 20 servers and 5 clients the follwing errors occur
at some drivers:
{noformat}
[12:16:55,985][INFO ][main][IgniteKernal] Language runtime: Java Platform API
Specification ver. 1.7
[12:16:55,985][INFO ][main][IgniteKernal] VM information: Java(TM) SE Runtime
Environment 1.7.0_79-b15 Oracle Corporation Java HotSpot(TM) 64-Bit Server VM
24.79-b02
[12:16:55,986][INFO ][main][IgniteKernal] VM total memory: 4.0GB
[12:16:55,986][INFO ][main][IgniteKernal] Remote Management [restart: off,
REST: on, JMX (remote: off)]
[12:16:55,986][INFO ][main][IgniteKernal]
IGNITE_HOME=/home/krybakova/opts-set-w-300-d-3600-m-client-rev-6e36a795-date-1611-121630/yardstick
[12:16:55,986][INFO ][main][IgniteKernal] VM arguments: [-Xms2g, -Xmx2g,
-Djava.net.preferIPv4Stack=true, -DIGNITE_QUIET=false, -XX:+UseTLAB,
-XX:NewSize=512m, -XX:MaxNewSize=512m, -XX:SurvivorRatio=6,
-XX:+AlwaysPreTouch, -XX:+UseG1GC,
[12:16:55,986][INFO ][main][IgniteKernal] Configured caches
['ignite-marshaller-sys-cache', 'ignite-sys-cache', 'ignite-atomics-sys-cache',
'atomic']
[12:16:55,990][INFO ][main][IgniteKernal] 3-rd party licenses can be found at:
/home/krybakova/opts-set-w-300-d-3600-m-client-rev-6e36a795-date-1611-121630/yardstick/libs/licenses
[12:16:56,061][INFO ][main][IgnitePluginProcessor] Configured plugins:
[12:16:56,061][INFO ][main][IgnitePluginProcessor] ^-- None
[12:16:56,062][INFO ][main][IgnitePluginProcessor]
[12:16:56,108][INFO ][main][TcpCommunicationSpi] Successfully bound to TCP port
[port=47104, locHost=0.0.0.0/0.0.0.0]
[12:16:56,124][WARN ][main][NoopCheckpointSpi] Checkpoints are disabled (to
enable configure any GridCheckpointSpi implementation)
[12:16:56,152][WARN ][main][GridCollisionManager] Collision resolution is
disabled (all jobs will be activated upon arrival).
[12:16:56,155][WARN ][main][NoopSwapSpaceSpi] Swap space is disabled. To enable
use FileSwapSpaceSpi.
[12:16:56,157][INFO ][main][IgniteKernal] Security status [authentication=off,
tls/ssl=off]
[12:16:56,408][INFO ][main][GridTcpRestProtocol] Command protocol successfully
started [name=TCP binary, host=0.0.0.0/0.0.0.0, port=11215]
[12:16:56,449][INFO ][main][IgniteKernal] Non-loopback local IPs: 172.25.1.34
[12:16:56,449][INFO ][main][IgniteKernal] Enabled local MACs: 001B21D4F1B8
Exception in thread "sys-#34%null%" java.lang.IllegalArgumentException: Cache
is not configured: ignite-marshaller-sys-cache
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.jcache(GridCacheProcessor.java:3320)
at
org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.handleEvent(CacheContinuousQueryHandler.java:711)
at
org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.notifyCallback0(CacheContinuousQueryHandler.java:683)
at
org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.notifyCallback(CacheContinuousQueryHandler.java:642)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.processNotification(GridContinuousProcessor.java:1086)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.access$2000(GridContinuousProcessor.java:97)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$8.onMessage(GridContinuousProcessor.java:741)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1080)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$1600(GridIoManager.java:101)
at
org.apache.ignite.internal.managers.communication.GridIoManager$GridCommunicationMessageSet.unwind(GridIoManager.java:2317)
at
org.apache.ignite.internal.managers.communication.GridIoManager.unwindMessageSet(GridIoManager.java:1040)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$1900(GridIoManager.java:101)
at
org.apache.ignite.internal.managers.communication.GridIoManager$6.run(GridIoManager.java:1009)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Exception in thread "sys-#36%null%" java.lang.IllegalArgumentException: Cache
is not configured: ignite-marshaller-sys-cache
at
[jira] [Created] (IGNITE-4214) "Failed to wait for partition map exchange" warnings during different load tests
Ksenia Rybakova created IGNITE-4214: --- Summary: "Failed to wait for partition map exchange" warnings during different load tests Key: IGNITE-4214 URL: https://issues.apache.org/jira/browse/IGNITE-4214 Project: Ignite Issue Type: Bug Reporter: Ksenia Rybakova "Failed to wait for partition map exchange" warnings appears during different load tests. Grid doesn't hang though and operations are performed successfully. Example of load test config: - Benchmark: CacheRandomOperation - Operations: put, put_all, get, get_all, invoke, invoke_all, remove, remove_all, put_if_absent, replace - Heap: 8Gb for servers, 4Gb for clients - 5 clients, 20 servers - Number of caches: 12 - Types of caches (atomicity mode): different (atomic, transactional) - Types of caches (tiered storage mode): different (onheap without eviction, onheap with eviction, offheap_tired, offheap_values) - Types of caches (indexing): different (with and without indexes) - Types of caches (cache mode): different (partitioned, replicated) - Backups count: 12 Yardstick configs and property file are attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-4213) One of the node fails unexpectedly during failover test with TLS enabled
Ksenia Rybakova created IGNITE-4213:
---
Summary: One of the node fails unexpectedly during failover test
with TLS enabled
Key: IGNITE-4213
URL: https://issues.apache.org/jira/browse/IGNITE-4213
Project: Ignite
Issue Type: Bug
Affects Versions: 1.7
Reporter: Ksenia Rybakova
Load configuration
- Benchmark: CacheRandomOperation
- Operations: put, put_all, get, get_all, invoke, invoke_all, remove,
remove_all, put_if_absent, replace, scan_query, sql_query, continuous_query
- Heap: 8Gb for servers, 4Gb for clients
- 5 clients, 20 servers
- Number of caches: 12
- Types of caches (atomicity mode): different (atomic, transactional)
- Types of caches (tiered storage mode): different (onheap without eviction,
onheap with eviction, offheap_tired, offheap_values)
- Types of caches (indexing): different (with and without indexes)
- Types of caches (cache mode): different (partitioned, replicated)
- Backups count: 1
- Failover: 1 server are being restarted every 15 minutes
- Duration: 12h
- TLSv1.2 enabled
After one of the servers was restarted (killed and started again) on purpose
another one failed unexpectedly with the following errors:
{noformat}
[23:12:24,599][ERROR][tcp-disco-sock-reader-#72%null%][TcpDiscoverySpi] Failed
to initialize connection (this can happen due to short time network problems
and can be ignored if does not affect node discovery)
[sock=20a0[SSL_NULL_WIT
H_NULL_NULL: Socket[addr=/172.25.1.35,port=34762,localport=47500]]]
java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:152)
at java.net.SocketInputStream.read(SocketInputStream.java:122)
at sun.security.ssl.InputRecord.readFully(InputRecord.java:442)
at sun.security.ssl.InputRecord.read(InputRecord.java:480)
at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:934)
at
sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1332)
at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:889)
at sun.security.ssl.AppInputStream.read(AppInputStream.java:102)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:235)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:275)
at java.io.BufferedInputStream.read(BufferedInputStream.java:334)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl$SocketReader.body(ServerImpl.java:5260)
at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
[23:12:25,340][WARN ][grid-nio-worker-1-#10%null%][TcpCommunicationSpi] Failed
to process selector key (will close): GridSelectorNioSessionImpl
[selectorIdx=1, queueSize=5, writeBuf=java.nio.DirectByteBuffer[pos=0 lim=32530
cap=32768], r
eadBuf=java.nio.DirectByteBuffer[pos=0 lim=32768 cap=32768],
recovery=GridNioRecoveryDescriptor [acked=1508080, resendCnt=0, rcvCnt=1812199,
sentCnt=1508107, reserved=true, lastAck=1812192, nodeLeft=false,
node=TcpDiscoveryNode [id=2f7d3
673-2ca6-4d68-8b73-0c6a209df16f, addrs=[127.0.0.1, 172.25.1.36],
sockAddrs=[/127.0.0.1:47500, /172.25.1.36:47500], discPort=47500, order=7,
intOrder=7, lastExchangeTime=1478801828352, loc=false,
ver=1.8.0#20161110-sha1:baa75266, isClient
=false], connected=true, connectCnt=1, queueLimit=5120, reserveCnt=1],
super=GridNioSessionImpl [locAddr=/172.25.1.31:39392,
rmtAddr=/172.25.1.36:47100, createTime=1478801829611, closeTime=0,
bytesSent=2559699127, bytesRcvd=2820406363, s
ndSchedTime=1478808745318, lastSndTime=1478808745334,
lastRcvTime=1478808745334, readsPaused=false,
filterChain=FilterChain[filters=[GridNioCodecFilter
[parser=o.a.i.i.util.nio.GridDirectParser@61d3d493, directMode=true],
GridConnectionB
ytesVerifyFilter, SSL filter], accepted=false]]
[23:12:25,341][WARN ][grid-nio-worker-1-#10%null%][TcpCommunicationSpi] Closing
NIO session because of unhandled exception [cls=class
o.a.i.i.util.nio.GridNioException, msg=Connection reset by peer]
[23:12:26,331][WARN ][tcp-disco-msg-worker-#2%null%][TcpDiscoverySpi] Node is
out of topology (probably, due to short-time network problems).
[23:12:26,332][WARN ][disco-event-worker-#20%null%][GridDiscoveryManager] Local
node SEGMENTED: TcpDiscoveryNode [id=5fec5215-bbcb-48b3-bcdf-480243950218,
addrs=[127.0.0.1, 172.25.1.31], sockAddrs=[/127.0.0.1:47500,
testagent01.gridgain.
local/172.25.1.31:47500], discPort=47500, order=1, intOrder=1,
lastExchangeTime=1478808746325, loc=true, ver=1.8.0#20161110-sha1:baa75266,
isClient=false]
[23:12:26,393][WARN ][disco-event-worker-#20%null%][GridDiscoveryManager]
Stopping local node according to configured segmentation policy.
[23:12:26,393][WARN ][disco-event-worker-#20%null%][GridDiscoveryManager] Node
FAILED: TcpDiscoveryNode [id=6413da0d-fa60-42d1-8f44-dcbd88055cc6,
[jira] [Created] (IGNITE-4201) CPP: fix versioning of C++ libs
Ksenia Rybakova created IGNITE-4201: --- Summary: CPP: fix versioning of C++ libs Key: IGNITE-4201 URL: https://issues.apache.org/jira/browse/IGNITE-4201 Project: Ignite Issue Type: Bug Components: platforms Affects Versions: 1.7 Reporter: Ksenia Rybakova Currently versions are not set properly in Ignite C++ core libraries names if we build the libs on Linux according to $IGNITE_HOME/platforms/cpp/DEVNOTES.txt. For instance, for version 1.7.3 names are libignite*-1.6.0.8653 instead of libignite*-1.7.3 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-4187) "Remote node ID is not as expected" when client SSL certificate is signed by untrusted CA
Ksenia Rybakova created IGNITE-4187:
---
Summary: "Remote node ID is not as expected" when client SSL
certificate is signed by untrusted CA
Key: IGNITE-4187
URL: https://issues.apache.org/jira/browse/IGNITE-4187
Project: Ignite
Issue Type: Bug
Affects Versions: 1.6
Reporter: Ksenia Rybakova
Test config:
- 1 client node, 1 server node
- SSL is enabled
{noformat}
{noformat}
trust.jks on server side has one CA certificate and this is NOT the one that
was used to sign the client certificate (so the server doesn't trust to the
client)
trust.jks on client side has one CA certificate and this is the one that was
used to sign the server certificate (so the client does trust to the server)
- Yardstick is used to run simple load test (configs and property file are
attached)
Result:
client connects to server, but there are errors in log:
client:
{noformat}
[16:05:21,751][ERROR][exchange-worker-#22%null%][GridDhtAssignmentFetchFuture]
Failed to request affinity assignment from remote node (will continue to
another node): TcpDiscoveryNode [id=c02cdaa3-80de-4b81-884f-ca9ba830dba5,
addrs=[127.0.0.1, 172.25.1.32], sockAddrs=[/172.25.1.32:47500,
/127.0.0.1:47500], discPort=47500, order=1, intOrder=1,
lastExchangeTime=1478178315859, loc=false, ver=1.7.0#20161031-sha1:6b78ad0c,
isClient=false]
class org.apache.ignite.IgniteCheckedException: Failed to send message (node
may have left the grid or TCP connection cannot be established due to firewall
issues) [node=TcpDiscoveryNode [id=c02cdaa3-80de-4b81-884f-ca9ba830dba5,
addrs=[127.0.0.1, 172.25.1.32], sockAddrs=[/172.25.1.32:47500,
/127.0.0.1:47500], discPort=47500, order=1, intOrder=1,
lastExchangeTime=1478178315859, loc=false, ver=1.7.0#20161031-sha1:6b78ad0c,
isClient=false], topic=TOPIC_CACHE, msg=GridDhtAffinityAssignmentRequest
[topVer=AffinityTopologyVersion [topVer=2, minorTopVer=0],
super=GridCacheMessage [msgId=2, depInfo=null, err=null, skipPrepare=false,
cacheId=1489451830, cacheId=1489451830]], policy=4]
at
org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1151)
at
org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1215)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:836)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtAssignmentFetchFuture.requestFromNextNode(GridDhtAssignmentFetchFuture.java:185)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtAssignmentFetchFuture.init(GridDhtAssignmentFetchFuture.java:107)
at
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.fetchAffinityOnJoin(CacheAffinitySharedManager.java:953)
at
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.onClientEvent(CacheAffinitySharedManager.java:639)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onClientNodeEvent(GridDhtPartitionsExchangeFuture.java:619)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:464)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:1453)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:745)
Caused by: class org.apache.ignite.spi.IgniteSpiException: Failed to send
message to remote node: TcpDiscoveryNode
[id=c02cdaa3-80de-4b81-884f-ca9ba830dba5, addrs=[127.0.0.1, 172.25.1.32],
sockAddrs=[/172.25.1.32:47500, /127.0.0.1:47500], discPort=47500, order=1,
intOrder=1, lastExchangeTime=1478178315859, loc=false,
ver=1.7.0#20161031-sha1:6b78ad0c, isClient=false]
at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage0(TcpCommunicationSpi.java:2017)
at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage(TcpCommunicationSpi.java:1955)
at
org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1146)
... 11 more
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to connect to
node (is node still alive?). Make sure that each ComputeTask and
GridCacheTransaction has a timeout set in order to prevent parties from waiting
forever in case of network issues [nodeId=c02cdaa3-80de-4b81-884f-ca9ba830dba5,
addrs=[/172.25.1.32:47100, /127.0.0.1:47100]]
at
[jira] [Created] (IGNITE-4186) .NET: "Invalid session release request" exception in IgniteSessionStateStoreProvider.SetAndReleaseItemExclusive
Ksenia Rybakova created IGNITE-4186:
---
Summary: .NET: "Invalid session release request" exception in
IgniteSessionStateStoreProvider.SetAndReleaseItemExclusive
Key: IGNITE-4186
URL: https://issues.apache.org/jira/browse/IGNITE-4186
Project: Ignite
Issue Type: Bug
Components: platforms
Affects Versions: 1.7
Environment: Windows 10
MS VS 2015
.NET Framework 4.0.30319
ASP.NET 4.6.1586.0
Reporter: Ksenia Rybakova
Fix For: 1.8
Steps:
- Create a new C# Web application in the MS Visual Studio
- Install Apache.Ignite.AspNet package via Tools->NuGet Package ManagerPackage
Manager Console:
- Open Web.config file, remove default sessionState section in and
add the following instead:
{noformat}
{noformat}
- Open Default.aspx.cs file and add the following to Page_Load method
{noformat}
Session["test"] = "abc";
{noformat}
- Run project
Result:
{noformat}
[IgniteException: Invalid session release request, expected lockId: 0, actual: ]
Apache.Ignite.AspNet.IgniteSessionStateStoreProvider.SetAndReleaseItemExclusive(HttpContext
context, String id, SessionStateStoreData item, Object lockId, Boolean
newItem) +298
System.Web.SessionState.SessionStateModule.OnReleaseState(Object source,
EventArgs eventArgs) +573
System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
+141
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean&
completedSynchronously) +69
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-4185) Apache.Ignite.AspNet.IgniteOutputCacheProvider: System.NullReferenceException when igniteConfiguration is missed
Ksenia Rybakova created IGNITE-4185:
---
Summary: Apache.Ignite.AspNet.IgniteOutputCacheProvider:
System.NullReferenceException when igniteConfiguration is missed
Key: IGNITE-4185
URL: https://issues.apache.org/jira/browse/IGNITE-4185
Project: Ignite
Issue Type: Bug
Components: platforms
Affects Versions: 1.7
Environment: Windows 10
MS VS 2015
Reporter: Ksenia Rybakova
Steps:
- Create a new C# Web application in the MS Visual Studio
- Install Apache.Ignite.AspNet package via Tools->NuGet Package ManagerPackage
Manager Console:
- Open Web.config file and do the following changes:
Add to :
{noformat}
{noformat}
Remove default sessionState section in and add the following
instead:
{noformat}
{noformat}
Add to :
{noformat}
{noformat}
- Run project
Result:
{noformat}
Failed to initialize Apache.Ignite.AspNet.IgniteOutputCacheProvider:
System.NullReferenceException:
in
Apache.Ignite.AspNet.Impl.ConfigUtil.StartFromApplicationConfiguration(String
sectionName, String gridName)
в
Apache.Ignite.AspNet.Impl.ConfigUtil.InitializeCache[TK,TV](NameValueCollection
config, Type callerType, String defaultCacheName)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-4144) Ignite ODBC with php PDO: data of Time type cannot be retrieved correctly
Ksenia Rybakova created IGNITE-4144:
---
Summary: Ignite ODBC with php PDO: data of Time type cannot be
retrieved correctly
Key: IGNITE-4144
URL: https://issues.apache.org/jira/browse/IGNITE-4144
Project: Ignite
Issue Type: Bug
Components: odbc
Affects Versions: 1.6
Reporter: Ksenia Rybakova
Setup:
Windows 10
php7.0 + php PDO
Ignite ODBC drivers is installed and DSN is configured
Cache stores {{AllTypes}} objects, one of the field of this object is {{Time
timeCol}} that stores current time. When we retrieve this field using php pdo
{noformat}
$dbh = new PDO('odbc:Apache Ignite DSN');
$result = $dbh->query('SELECT timeCol from "AllTypes".AllTypes');
print_r($result->fetch(PDO::FETCH_ASSOC));
{noformat}
we get
{noformat}
Array
(
[TIME] => 1970-01-01
)
{noformat}
instead of correct hh:mm:ss value
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-4113) php PDO: CLI crash when execute query using scrollable cursor and FETCH_ORI_LAST, FETCH_ORI_PRIOR
Ksenia Rybakova created IGNITE-4113:
---
Summary: php PDO: CLI crash when execute query using scrollable
cursor and FETCH_ORI_LAST, FETCH_ORI_PRIOR
Key: IGNITE-4113
URL: https://issues.apache.org/jira/browse/IGNITE-4113
Project: Ignite
Issue Type: Bug
Components: odbc
Affects Versions: 1.6
Environment: Windows 10
Ignite ODBC driver is installed
DSN is set up
Reporter: Ksenia Rybakova
CLI crash (when running from command line) and "Process finished with exit code
-1073741819 (0xC005)" (when running from IDE) when execute the following
php function:
{noformat}
function check_query_with_scrollable_cursor($dbh) {
try {
$dbs = $dbh->prepare('SELECT firstName, lastName, salary FROM
"Persons".Person', array(PDO::ATTR_CURSOR => PDO::CURSOR_SCROLL));
$dbs->execute();
$row = $dbs->fetch(PDO::FETCH_NUM, PDO::FETCH_ORI_LAST);
do {
print $row[0] . "\t" . $row[1] . "\t" . $row[2] . "\n";
} while ($row = $dbs->fetch(PDO::FETCH_NUM, PDO::FETCH_ORI_PRIOR));
} catch (PDOException $e) {
print "Error: " . $e->getMessage() . "\n";
} finally {
$dbs = null;
}
}
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-4100) Some typos and missing references in cpp platform instructions
Ksenia Rybakova created IGNITE-4100: --- Summary: Some typos and missing references in cpp platform instructions Key: IGNITE-4100 URL: https://issues.apache.org/jira/browse/IGNITE-4100 Project: Ignite Issue Type: Bug Components: platforms Affects Versions: 1.6 Reporter: Ksenia Rybakova Priority: Minor 1) Fix typo in $IGNITE_HOME\platforms\cpp\DEVNOTES.txt, line 40: "heasders" -> "headers" 2) Fix typo in $IGNITE_HOME\platforms\cpp\README.txt, line 5: "you can execute perform" -> "you can perform" or "you can execute" 3) $IGNITE_HOME\platforms\cpp\DEVNOTES.txt: add some note (to both linux and windows sections or to common section) that user should refer to $IGNITE_HOME\platforms\cpp\odbc\README.txt to install odbc driver 4) $IGNITE_HOME\platforms\cpp\examples\README.txt, line 10 "Apache Ignite C++ must be built according to instructions for your platform": add a reference to the instruction $IGNITE_HOME\platforms\cpp\DEVNOTES.txt 5) $IGNITE_HOME\platforms\cpp\examples\README.txt, line 29 "Apache Ignite ODBC driver must be built and installed according to instructions for your platform.": suggest you moving this to "Common requirements" (since it's actual for both Linux and Win) and adding a reference to the instruction $IGNITE_HOME/platforms/cpp/odbc/README.txt -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-4094) NPE at org.apache.ignite.internal.processors.platform.services.PlatformAbstractService.execute while running ServicesExample
Ksenia Rybakova created IGNITE-4094:
---
Summary: NPE at
org.apache.ignite.internal.processors.platform.services.PlatformAbstractService.execute
while running ServicesExample
Key: IGNITE-4094
URL: https://issues.apache.org/jira/browse/IGNITE-4094
Project: Ignite
Issue Type: Bug
Components: platforms
Affects Versions: 1.6
Reporter: Ksenia Rybakova
1) Build examples according to
%IGNITE_HOME%\platforms\dotnet\examples\README.txt
2) Run 4 standalone Apache Ignite.NET nodes as it is described in
ServicesExample.cs
3) Run ServicesExample
NPE occured at one of the nodes. Also it's strange that
initialized->started->cancelled happened twice.
{noformat}
[15:03:08] Topology snapshot [ver=41, servers=5, clients=0, CPUs=4, heap=18.0GB]
Service initialized: service
Service started: service
Service cancelled: service
Service initialized: service
Service cancelled: service
[15:03:11,062][SEVERE][ignite-#374%null%][GridServiceProcessor] Service
execution stopped with error [name=service,
execId=e27cefac-31a8-46b7-bee9-b56d060d77b3]
java.lang.NullPointerException
at
org.apache.ignite.internal.processors.platform.services.PlatformAbstractService.execute(PlatformAbstractService.java:119)
at
org.apache.ignite.internal.processors.service.GridServiceProcessor$2.run(GridServiceProcessor.java:1101)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
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)
[15:03:11] Topology snapshot [ver=42, servers=4, clients=0, CPUs=4, heap=14.0GB]
{noformat}
The 2nd node has two "initialized->started->cancelled" as well
{noformat}
[15:03:08] Topology snapshot [ver=41, servers=5, clients=0, CPUs=4, heap=18.0GB]
Service initialized: service
Service started: service
Service cancelled: service
Service initialized: service
Service started: service
Service cancelled: service
[15:03:11] Topology snapshot [ver=42, servers=4, clients=0, CPUs=4, heap=14.0GB]
{noformat}
The 3rd and 4th nodes are ok:
{noformat}
[15:03:08] Topology snapshot [ver=41, servers=5, clients=0, CPUs=4, heap=18.0GB]
Service initialized: service
Service started: service
Service cancelled: service
[15:03:11] Topology snapshot [ver=42, servers=4, clients=0, CPUs=4, heap=14.0GB]
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-4002) Incorrect errors/warnings while odbc driver installation
Ksenia Rybakova created IGNITE-4002:
---
Summary: Incorrect errors/warnings while odbc driver installation
Key: IGNITE-4002
URL: https://issues.apache.org/jira/browse/IGNITE-4002
Project: Ignite
Issue Type: Bug
Components: platforms
Affects Versions: 1.7
Environment: Windows 2010 (Rus)
Reporter: Ksenia Rybakova
Priority: Minor
1) Build x64 odbc driver according to $IGNITE_HOME\platforms\cpp\DEVNOTES.txt
2) Install x64 bit driver according to
$IGNITE_HOME\platforms\cpp\odbc\README.txt. Don't pass x32 driver as a second
parameter:
{noformat}
D:\ignite\platforms\cpp\odbc\install>install_amd64.cmd
D:\ignite\platforms\cpp\project\vs\x64\Release\ignite.odbc.dll
Installing 64-bit driver:
D:\ignite\platforms\cpp\project\vs\x64\Release\ignite.odbc.dll
Операция успешно завершена.
Операция успешно завершена.
Операция успешно завершена.
Операция успешно завершена.
Операция успешно завершена.
Ошибка в синтаксисе команды.
{noformat}
Expected: "warning: 32-bit driver is not specified. If you want to install
32-bit driver please specify path to it as a second argument." message
Actual: "Ошибка в синтаксисе команды".
3) Install x64 bit driver according to
$IGNITE_HOME\platforms\cpp\odbc\README.txt. Pass \ (root directory) as a second
parameter (x32 driver):
{noformat}
D:\ignite\platforms\cpp\odbc\install>install_amd64.cmd
D:\ignite\platforms\cpp\project\vs\x64\Release\ignite.odbc.dll \
Installing 64-bit driver:
D:\ignite\platforms\cpp\project\vs\x64\Release\ignite.odbc.dll
Операция успешно завершена.
Операция успешно завершена.
Операция успешно завершена.
Операция успешно завершена.
Операция успешно завершена.
Installing 32-bit driver: \
Операция успешно завершена.
Операция успешно завершена.
Операция успешно завершена.
Операция успешно завершена.
Операция успешно завершена.
{noformat}
Expected:
"warning: The path you have specified seems to be a directory. Note that you
have to specify path to driver file itself instead." warning before "Installing
32-bit driver: \"
Actual: no such a warning (if exist %ODBC_X86%\ -> if exist \\ -> false. So
this check doesn't work in this case).
Please, consider some changes in error handling.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-3707) Throughput drops to 0 during failover test when killed node returns to the grid
Ksenia Rybakova created IGNITE-3707: --- Summary: Throughput drops to 0 during failover test when killed node returns to the grid Key: IGNITE-3707 URL: https://issues.apache.org/jira/browse/IGNITE-3707 Project: Ignite Issue Type: Bug Components: general Affects Versions: 1.6 Reporter: Ksenia Rybakova Throughput drops to 0 periodically during failover test. Also lots of "Found long running transaction" and "Found long running cache future" are in logs at that moment. This happens right after killed node comes back to the grid. When this node is killed again performance returns to normal. Load config: - Benchmark: CacheRandomOperation - Operations: put, put_all, get, get_all, invoke, invoke_all, remove, remove_all, put_if_absent, replace - Heap: 8Gb for servers, 4Gb for clients - 20 clients, 5 servers - Number of caches: 12 - Types of caches (atomicity mode): different (atomic, transactional) - Types of caches (tiered storage mode): different (onheap without eviction, onheap with eviction, offheap_tired, offheap_values) - Types of caches (indexing): different (with and without indexes) - Types of caches (cache mode): different (partitioned, replicated) - Backups count: 1 - Failover: 1 server is being restarted every 15 minutes (5 min between stop and start, 10 min between start and next stop; if several servers are restarted, step between restarts is 30sec) - Duration: 1.5h Yardstick properties file and configs are attached. Logs can be provided on demand. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-3623) Drivers hung during streaming load test
Ksenia Rybakova created IGNITE-3623: --- Summary: Drivers hung during streaming load test Key: IGNITE-3623 URL: https://issues.apache.org/jira/browse/IGNITE-3623 Project: Ignite Issue Type: Bug Affects Versions: 1.7 Reporter: Ksenia Rybakova Drivers hang during streaming load test. Cpu dropps to 0% and test doesn't finish. Every time it happens almost at the end of the test. Config: - benchmark: CacheRandomOperation - 5 hosts - Heap: 8Gb for servers, 1Gb for clients - 20 clients, 40 servers - Number of caches: 12 - Types of caches (atomicity mode): different (atomic, transactional) - Types of caches (tiered storage mode): different (onheap without eviction, onheap with eviction, offheap_tired, offheap_values) - Types of caches (indexing): different (with and without indexes) - Types of caches (cache mode): partitioned - Backups count: 1 - Number of entries: 8M Benchmark property file and xml configs are attached. Thread dump of one of the drivers is attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-3619) "long running transaction/cache operations" during load tests
Ksenia Rybakova created IGNITE-3619:
---
Summary: "long running transaction/cache operations" during load
tests
Key: IGNITE-3619
URL: https://issues.apache.org/jira/browse/IGNITE-3619
Project: Ignite
Issue Type: Bug
Affects Versions: 1.6
Reporter: Ksenia Rybakova
The following warnings appear during load test:
{noformat}
[15:46:07,413][WARN
][grid-timeout-worker-#79%null%][GridCachePartitionExchangeManager] Found long
running transaction [startTime=15:45:04.471, curTime=15:46:07.356,
tx=GridNearTxLocal [mappings=IgniteTxMappingsImpl [], nearLocallyMapped
...
[15:46:07,787][WARN
][grid-timeout-worker-#79%null%][GridCachePartitionExchangeManager] Found long
running cache future [startTime=15:45:04.775, curTime=15:46:07.356,
fut=GridNearTxFinishFuture [futId=905d64b4651-3154c7e5-c2bd-46d5-a2ae-
...
[15:46:07,830][WARN
][grid-timeout-worker-#79%null%][GridCachePartitionExchangeManager] Found long
running cache operations, dump threads.
[15:46:07,831][WARN
][grid-timeout-worker-#79%null%][GridCachePartitionExchangeManager] No
deadlocked threads detected.
{noformat}
In some cases these warnings appear during preloading, in other cases during
performing main test.
In all cases CPU at part of the nodes drops almost to 0% and test hung.
Configs:
1)
- 5 hosts
- benchmark: CacheRandomOperation
- Operations: all (put, put_all, get, get_all, invoke, invoke_all, remove,
remove_all, put_if_absent, replace, scan_query, sql_query, continuous_query)
- Heap: 2Gb for servers, 1Gb for clients
- Number of clients to number of servers: 1:1 (48 clients, 48 servers)
- Number of caches: 12
- Types of caches (atomicity mode): atomic
- Types of caches (tiered storage mode): different (onheap without eviction,
onheap with eviction, offheap_tired, offheap_values)
- Types of caches (indexing): different (with and without indexes)
- Types of caches (cache mode): partitioned
- Backups count: 1
- Duration: 1h
2)
- 5 hosts
- benchmark: CacheRandomOperation
- Operations: all (put, put_all, get, get_all, invoke, invoke_all, remove,
remove_all, put_if_absent, replace, scan_query, sql_query, continuous_query)
- Heap: 8Gb for servers, 4Gb for clients
- Number of clients to number of servers: 1:4 (5 clients, 20 servers)
- Number of caches: 12
- Types of caches (atomicity mode): transactional
- Types of caches (tiered storage mode): different (onheap without eviction,
onheap with eviction, offheap_tired, offheap_values)
- Types of caches (indexing): different (with and without indexes)
- Types of caches (cache mode): partitioned
- Backups count: 1
- Duration: 1h
Property files and xml configs are attached.
Logs can be provided on demand.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-3474) Grid hung during load test with warning "Failed to wait for partition map exchange"
Ksenia Rybakova created IGNITE-3474:
---
Summary: Grid hung during load test with warning "Failed to wait
for partition map exchange"
Key: IGNITE-3474
URL: https://issues.apache.org/jira/browse/IGNITE-3474
Project: Ignite
Issue Type: Bug
Affects Versions: 1.6
Reporter: Ksenia Rybakova
Attachments: 091826_id0_192.168.1.21_part.log
During atomic operations load test grid hung:
{noformat}
[09:22:17,688][WARN
][exchange-worker-#137%null%][GridCachePartitionExchangeManager] Failed to wait
for partition map exchange [topVer=AffinityTopologyVersion [topVer=97,
minorTopVer=0], node=0fe0c0f2-65e1-4ad5-a8c9-92db997fcb7d]. Dumpin
g pending objects that might be the cause:
...
{noformat}
See attached file with more info from logs.
The issue was also reproduced with IGNITE-3239 fixed. So, IGNITE-3239 doesn't
seem to be a root cause.
Load test config:
- Benchmark name: IgniteCacheRandomOperationBenchmark
- Operations: put, put_all, get, get_all, invoke, invoke_all, remove,
remove_all, put_if_absent, replace
- Heap: 2Gb for servers, 1Gb for clients
- 48 clients, 48 servers, 6 hosts
- Preload amount: 2.5M
- Key range: 5M
- Number of caches: 12
- Types of caches (atomicity mode): only atomic
- Types of caches (tiered storage mode): different (onheap without eviction,
onheap with eviction, offheap_tired, offheap_values)
- Types of caches (indexing): different (with and without indexes)
- Types of caches (cache mode): partitioned
- Backups count: 1
Attachments:
- part of log with the problem (for one of the servers)
- xml configs and property file that were used to run yardstick
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-3465) Java crash: problematic frame org.apache.ignite.internal.binary.BinaryObjectImpl.hashCode()
Ksenia Rybakova created IGNITE-3465:
---
Summary: Java crash: problematic frame
org.apache.ignite.internal.binary.BinaryObjectImpl.hashCode()
Key: IGNITE-3465
URL: https://issues.apache.org/jira/browse/IGNITE-3465
Project: Ignite
Issue Type: Bug
Reporter: Ksenia Rybakova
During streaming load test some of JVMs crashed while logging info about
"Failed to wait for partition map exchange" problem
{noformat}
[01:05:23,949][WARN
][exchange-worker-#96%null%][GridCachePartitionExchangeManager] Failed to wait
for partition map exchange [topVer=AffinityTopologyVersion [topVer=61,
minorTopVer=0], node=4f7b195a-62e3-4c32-b496-4a98de50b277]. Dumping
[01:05:23,949][WARN
][exchange-worker-#96%null%][GridCachePartitionExchangeManager] Ready affinity
version: AffinityTopologyVersion [topVer=60, minorTopVer=0]
[01:05:24,107][WARN
][exchange-worker-#96%null%][GridCachePartitionExchangeManager] Last exchange
future: GridDhtPartitionsExchangeFuture [dummy=false, forcePreload=false,
reassign=false, discoEvt=DiscoveryEvent [evtNode=TcpDiscoveryNode
[01:05:24,108][WARN
][exchange-worker-#96%null%][GridCachePartitionExchangeManager] Pending
exchange futures:
[01:05:24,108][WARN
][exchange-worker-#96%null%][GridCachePartitionExchangeManager] Last 10
exchange futures (total: 48):
[01:05:24,109][WARN
][exchange-worker-#96%null%][GridCachePartitionExchangeManager] >>>
GridDhtPartitionsExchangeFuture [dummy=false, forcePreload=false,
reassign=false, discoEvt=DiscoveryEvent [evtNode=TcpDiscoveryNode
[id=7291b03d-ce91
[01:05:24,110][WARN
][exchange-worker-#96%null%][GridCachePartitionExchangeManager] >>>
GridDhtPartitionsExchangeFuture [dummy=false, forcePreload=false,
reassign=false, discoEvt=DiscoveryEvent [evtNode=TcpDiscoveryNode
[id=739ab624-7bce
[01:05:24,111][WARN
][exchange-worker-#96%null%][GridCachePartitionExchangeManager] >>>
GridDhtPartitionsExchangeFuture [dummy=false, forcePreload=false,
reassign=false, discoEvt=DiscoveryEvent [evtNode=TcpDiscoveryNode
[id=93572383-07e8
[01:05:24,111][WARN
][exchange-worker-#96%null%][GridCachePartitionExchangeManager] >>>
GridDhtPartitionsExchangeFuture [dummy=false, forcePreload=false,
reassign=false, discoEvt=DiscoveryEvent [evtNode=TcpDiscoveryNode
[id=3c24caa1-d4b2
[01:05:24,112][WARN
][exchange-worker-#96%null%][GridCachePartitionExchangeManager] >>>
GridDhtPartitionsExchangeFuture [dummy=false, forcePreload=false,
reassign=false, discoEvt=DiscoveryEvent [evtNode=TcpDiscoveryNode
[id=e762044c-8ccc
[01:05:24,118][WARN
][exchange-worker-#96%null%][GridCachePartitionExchangeManager] >>>
GridDhtPartitionsExchangeFuture [dummy=false, forcePreload=false,
reassign=false, discoEvt=DiscoveryEvent [evtNode=TcpDiscoveryNode
[id=5ffbe144-f843
[01:05:24,119][WARN
][exchange-worker-#96%null%][GridCachePartitionExchangeManager] >>>
GridDhtPartitionsExchangeFuture [dummy=false, forcePreload=false,
reassign=false, discoEvt=DiscoveryEvent [evtNode=TcpDiscoveryNode
[id=28199123-fa5b
[01:05:24,119][WARN
][exchange-worker-#96%null%][GridCachePartitionExchangeManager] >>>
GridDhtPartitionsExchangeFuture [dummy=false, forcePreload=false,
reassign=false, discoEvt=DiscoveryEvent [evtNode=TcpDiscoveryNode
[id=14d27ae8-ee26
[01:05:24,120][WARN
][exchange-worker-#96%null%][GridCachePartitionExchangeManager] >>>
GridDhtPartitionsExchangeFuture [dummy=false, forcePreload=false,
reassign=false, discoEvt=DiscoveryEvent [evtNode=TcpDiscoveryNode
[id=fea5c90e-0467
[01:05:24,120][WARN
][exchange-worker-#96%null%][GridCachePartitionExchangeManager] >>>
GridDhtPartitionsExchangeFuture [dummy=false, forcePreload=false,
reassign=false, discoEvt=DiscoveryEvent [evtNode=TcpDiscoveryNode
[id=a5370f23-42bc
[01:05:24,122][WARN
][exchange-worker-#96%null%][GridCachePartitionExchangeManager] Pending
transactions:
[01:05:24,767][WARN
][exchange-worker-#96%null%][GridCachePartitionExchangeManager] >>>
GridDhtTxRemote [nearNodeId=fea5c90e-0467-462a-8755-928b539fb278,
rmtFutId=a52022ed551-938a204f-bf03-451b-8425-be7047673bf6,
nearXidVer=GridCacheVers
[01:05:24,769][WARN
][exchange-worker-#96%null%][GridCachePartitionExchangeManager] >>>
GridDhtTxRemote [nearNodeId=739ab624-7bce-4e4b-81cc-3696f65247bd,
rmtFutId=ddfe12ed551-15e1d48c-8146-44ac-8d7b-370ea34fa44b,
nearXidVer=GridCacheVers
[01:05:24,771][WARN
][exchange-worker-#96%null%][GridCachePartitionExchangeManager] >>>
GridDhtTxRemote [nearNodeId=5ffbe144-f843-4ad1-9ade-688a18f0f872,
rmtFutId=401f12ed551-62727d5b-0dd3-48a0-bb04-72f7363ec19b,
nearXidVer=GridCacheVers
[01:05:24,771][WARN
][exchange-worker-#96%null%][GridCachePartitionExchangeManager] Pending
explicit locks:
[01:05:24,771][WARN
][exchange-worker-#96%null%][GridCachePartitionExchangeManager] Pending cache
futures:
[01:05:24,771][WARN
][exchange-worker-#96%null%][GridCachePartitionExchangeManager] Pending atomic
cache futures:
[jira] [Created] (IGNITE-3401) "Remote node ID is not as expected" errors at driver during load test
Ksenia Rybakova created IGNITE-3401:
---
Summary: "Remote node ID is not as expected" errors at driver
during load test
Key: IGNITE-3401
URL: https://issues.apache.org/jira/browse/IGNITE-3401
Project: Ignite
Issue Type: Bug
Components: general
Reporter: Ksenia Rybakova
Fix For: 1.7
A lot of errors at some drivers after several minutes after grid is up during
load test:
{noformat}
[14:33:42] (err) Failed to execute compound future reducer: Compound future
listener []class org.apache.ignite.IgniteCheckedException: Failed to send
message (node may have left the grid or TCP connection cannot be established
due to fir
at
org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1129)
at
org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1193)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$Buffer.submit(DataStreamerImpl.java:1378)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$Buffer.update(DataStreamerImpl.java:1173)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.load0(DataStreamerImpl.java:756)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.addDataInternal(DataStreamerImpl.java:568)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.addData(DataStreamerImpl.java:604)
at
org.apache.ignite.yardstick.cache.load.IgniteCacheRandomOperationBenchmark$1.run(IgniteCacheRandomOperationBenchmark.java:383)
Caused by: class org.apache.ignite.spi.IgniteSpiException: Failed to send
message to remote node: TcpDiscoveryNode
[id=11da20f5-87c5-4321-8163-ffef85f2d54c, addrs=[10.20.0.215, 127.0.0.1],
sockAddrs=[/127.0.0.1:47503, fosters-215/10.20.0
at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage0(TcpCommunicationSpi.java:1986)
at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage(TcpCommunicationSpi.java:1926)
at
org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1124)
... 7 more
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to connect to
node (is node still alive?). Make sure that each GridComputeTask and
GridCacheTransaction has a timeout set in order to prevent parties from waiting
forever
at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createTcpClient(TcpCommunicationSpi.java:2489)
at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createNioClient(TcpCommunicationSpi.java:2130)
at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.reserveClient(TcpCommunicationSpi.java:2024)
at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage0(TcpCommunicationSpi.java:1960)
... 9 more
Suppressed: class org.apache.ignite.IgniteCheckedException: Failed to
connect to address: fosters-215/10.20.0.215:47103
at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createTcpClient(TcpCommunicationSpi.java:2494)
... 12 more
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to
read remote node recovery handshake (connection closed).
at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.safeHandshake(TcpCommunicationSpi.java:2699)
at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createTcpClient(TcpCommunicationSpi.java:2361)
... 12 more
Suppressed: class org.apache.ignite.IgniteCheckedException: Failed to
connect to address: /127.0.0.1:47103
at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createTcpClient(TcpCommunicationSpi.java:2494)
... 12 more
Caused by: class org.apache.ignite.IgniteCheckedException: Remote node
ID is not as expected [expected=11da20f5-87c5-4321-8163-ffef85f2d54c,
rcvd=03bc7d54-4fec-481d-af24-6f5408b32fe2]
at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.safeHandshake(TcpCommunicationSpi.java:2604)
at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createTcpClient(TcpCommunicationSpi.java:2361)
... 12 more
{noformat}
Tested version: 1.5.27
Load config:
- 7 hosts with 4 servers and 3 drivers each (28 servers and 21 drivers in total)
- benchmark: IgniteCacheRandomOperationBenchmark
- preload: 2M
- key range: 4M
- warmup: 30s
- duration: 10h
- operations: PUT PUT_ALL GET GET_ALL INVOKE INVOKE_ALL REMOVE REMOVE_ALL
PUT_IF_ABSENT REPLACE
-backup count: 1
- GC: G1
- heap size: 8Gb for servers, 4Gb for drivers
- caches:
{noformat}
[jira] [Created] (IGNITE-3402) "Remote node ID is not as expected" errors at driver during load test
Ksenia Rybakova created IGNITE-3402:
---
Summary: "Remote node ID is not as expected" errors at driver
during load test
Key: IGNITE-3402
URL: https://issues.apache.org/jira/browse/IGNITE-3402
Project: Ignite
Issue Type: Bug
Components: general
Reporter: Ksenia Rybakova
Fix For: 1.7
A lot of errors at some drivers after several minutes after grid is up during
load test:
{noformat}
[14:33:42] (err) Failed to execute compound future reducer: Compound future
listener []class org.apache.ignite.IgniteCheckedException: Failed to send
message (node may have left the grid or TCP connection cannot be established
due to fir
at
org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1129)
at
org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1193)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$Buffer.submit(DataStreamerImpl.java:1378)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$Buffer.update(DataStreamerImpl.java:1173)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.load0(DataStreamerImpl.java:756)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.addDataInternal(DataStreamerImpl.java:568)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.addData(DataStreamerImpl.java:604)
at
org.apache.ignite.yardstick.cache.load.IgniteCacheRandomOperationBenchmark$1.run(IgniteCacheRandomOperationBenchmark.java:383)
Caused by: class org.apache.ignite.spi.IgniteSpiException: Failed to send
message to remote node: TcpDiscoveryNode
[id=11da20f5-87c5-4321-8163-ffef85f2d54c, addrs=[10.20.0.215, 127.0.0.1],
sockAddrs=[/127.0.0.1:47503, fosters-215/10.20.0
at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage0(TcpCommunicationSpi.java:1986)
at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage(TcpCommunicationSpi.java:1926)
at
org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1124)
... 7 more
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to connect to
node (is node still alive?). Make sure that each GridComputeTask and
GridCacheTransaction has a timeout set in order to prevent parties from waiting
forever
at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createTcpClient(TcpCommunicationSpi.java:2489)
at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createNioClient(TcpCommunicationSpi.java:2130)
at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.reserveClient(TcpCommunicationSpi.java:2024)
at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage0(TcpCommunicationSpi.java:1960)
... 9 more
Suppressed: class org.apache.ignite.IgniteCheckedException: Failed to
connect to address: fosters-215/10.20.0.215:47103
at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createTcpClient(TcpCommunicationSpi.java:2494)
... 12 more
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to
read remote node recovery handshake (connection closed).
at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.safeHandshake(TcpCommunicationSpi.java:2699)
at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createTcpClient(TcpCommunicationSpi.java:2361)
... 12 more
Suppressed: class org.apache.ignite.IgniteCheckedException: Failed to
connect to address: /127.0.0.1:47103
at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createTcpClient(TcpCommunicationSpi.java:2494)
... 12 more
Caused by: class org.apache.ignite.IgniteCheckedException: Remote node
ID is not as expected [expected=11da20f5-87c5-4321-8163-ffef85f2d54c,
rcvd=03bc7d54-4fec-481d-af24-6f5408b32fe2]
at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.safeHandshake(TcpCommunicationSpi.java:2604)
at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createTcpClient(TcpCommunicationSpi.java:2361)
... 12 more
{noformat}
Tested version: 1.5.27
Load config:
- 7 hosts with 4 servers and 3 drivers each (28 servers and 21 drivers in total)
- benchmark: IgniteCacheRandomOperationBenchmark
- preload: 2M
- key range: 4M
- warmup: 30s
- duration: 10h
- operations: PUT PUT_ALL GET GET_ALL INVOKE INVOKE_ALL REMOVE REMOVE_ALL
PUT_IF_ABSENT REPLACE
-backup count: 1
- GC: G1
- heap size: 8Gb for servers, 4Gb for drivers
- caches:
{noformat}
[jira] [Created] (IGNITE-3358) Yardstick: log exception that causes driver shutdown
Ksenia Rybakova created IGNITE-3358:
---
Summary: Yardstick: log exception that causes driver shutdown
Key: IGNITE-3358
URL: https://issues.apache.org/jira/browse/IGNITE-3358
Project: Ignite
Issue Type: Improvement
Reporter: Ksenia Rybakova
Fix For: 1.7
Some times driver stops during load test with the errors like:
{noformat}
ERROR: The benchmark of random operation failed.
Type '--help' for usage.
Finishing main test [ts=1466613716339, date=Wed Jun 22 09:41:56 PDT 2016]
ERROR: Shutting down benchmark driver to unexpected exception.
Type '--help' for usage.
{noformat}
But there is no info which exactly exception caused this error. If we have many
exceptions in the log it's impossible to identify the root cause.
Please, add stack trace of the exception to the error.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-3338) CachePartialUpdateCheckedException: Failed to update keys during load test with eviction configured
Ksenia Rybakova created IGNITE-3338:
---
Summary: CachePartialUpdateCheckedException: Failed to update keys
during load test with eviction configured
Key: IGNITE-3338
URL: https://issues.apache.org/jira/browse/IGNITE-3338
Project: Ignite
Issue Type: Bug
Components: general
Reporter: Ksenia Rybakova
Fix For: 1.7
The following exceptions occur during load test with eviction configured:
{noformat}
ERROR: The benchmark of random operation failed.
Type '--help' for usage.
Finishing main test [ts=1466178657166, date=Fri Jun 17 08:50:57 PDT 2016]
ERROR: Shutting down benchmark driver to unexpected exception.
Type '--help' for usage.
org.apache.ignite.cache.CachePartialUpdateException: Failed to update keys
(retry update if possible).: [26, 1872066, 1945790, 2405741, 3845651,
4830233, 7284502, 8555643]
at
org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1467)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.cacheException(IgniteCacheProxy.java:1972)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.removeAll(IgniteCacheProxy.java:1416)
at
org.apache.ignite.yardstick.cache.load.IgniteCacheRandomOperationBenchmark.doRemoveAll(IgniteCacheRandomOperationBenchmark.java:809)
at
org.apache.ignite.yardstick.cache.load.IgniteCacheRandomOperationBenchmark.executeRandomOperation(IgniteCacheRandomOperationBenchmark.java:551)
at
org.apache.ignite.yardstick.cache.load.IgniteCacheRandomOperationBenchmark.executeOutOfTx(IgniteCacheRandomOperationBenchmark.java:509)
at
org.apache.ignite.yardstick.cache.load.IgniteCacheRandomOperationBenchmark.test(IgniteCacheRandomOperationBenchmark.java:156)
at
org.yardstickframework.impl.BenchmarkRunner$2.run(BenchmarkRunner.java:176)
at java.lang.Thread.run(Thread.java:745)
Caused by: class
org.apache.ignite.internal.processors.cache.CachePartialUpdateCheckedException:
Failed to update keys (retry update if possible).: [26, 1872066, 1945790,
2405741, 3845651, 4830233, 7284502, 8555643]
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.onResult(GridNearAtomicUpdateFuture.java:311)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.processNearAtomicUpdateResponse(GridDhtAtomicCache.java:2958)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$700(GridDhtAtomicCache.java:129)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$6.apply(GridDhtAtomicCache.java:266)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$6.apply(GridDhtAtomicCache.java:264)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:624)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:322)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:246)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$000(GridCacheIoManager.java:83)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:205)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1219)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:847)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:105)
at
org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:810)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
... 1 more
Suppressed: class org.apache.ignite.IgniteCheckedException: Failed to
update keys on primary node.
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateResponse.addFailedKeys(GridNearAtomicUpdateResponse.java:369)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1711)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1482)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.processNearAtomicUpdateRequest(GridDhtAtomicCache.java:2937)
at
[jira] [Created] (IGNITE-3300) ArrayIndexOutOfBoundsException: -1 during capitalization benchmark running
Ksenia Rybakova created IGNITE-3300:
---
Summary: ArrayIndexOutOfBoundsException: -1 during capitalization
benchmark running
Key: IGNITE-3300
URL: https://issues.apache.org/jira/browse/IGNITE-3300
Project: Ignite
Issue Type: Bug
Components: general
Affects Versions: 1.7
Reporter: Ksenia Rybakova
Test config:
1 client, 16 servers
warmup 60
duration 1h
preload 5M
operations: capitalization benchmark
backups count 1
After ~30 min after start the following errors occur at the driver:
{noformat}
[08:42:51,367][ERROR][sys-#5%null%][GridTaskWorker] Failed to obtain remote job
result policy for result from ComputeTask.result(..) method (will fail the
whole task): GridJobResultImpl [job=C4V2
[r=o.a.i.yardstick.cache.load.IgniteCapitalizationBenchmark$ScanQueryBroadcastClosure@41013d64],
sib=GridJobSiblingImpl
[sesId=bfb21563551-a8d91d06-89bd-41a5-8b4f-6a02416dfc63,
jobId=51c21563551-a8d91d06-89bd-41a5-8b4f-6a02416dfc63,
nodeId=79226bcc-651f-4af7-8d39-fd4019b7708c, isJobDone=false],
jobCtx=GridJobContextImpl
[jobId=51c21563551-a8d91d06-89bd-41a5-8b4f-6a02416dfc63, timeoutObj=null,
attrs={}], node=TcpDiscoveryNode [id=79226bcc-651f-4af7-8d39-fd4019b7708c,
addrs=[10.20.0.216, 127.0.0.1], sockAddrs=[fosters-216/10.20.0.216:47501,
/10.20.0.216:47501, /127.0.0.1:47501], discPort=47501, order=5, intOrder=5,
lastExchangeTime=1465485122287, loc=false, ver=1.7.0#20160603-sha1:82573436,
isClient=false], ex=class o.a.i.compute.ComputeUserUndeclaredException: Failed
to execute job due to unexpected runtime exception
[jobId=51c21563551-a8d91d06-89bd-41a5-8b4f-6a02416dfc63, ses=GridJobSessionImpl
[ses=GridTaskSessionImpl
[taskName=o.a.i.yardstick.cache.load.IgniteCapitalizationBenchmark$ScanQueryBroadcastClosure,
dep=LocalDeployment [super=GridDeployment [ts=1465485111989, depMode=SHARED,
clsLdr=sun.misc.Launcher$AppClassLoader@6da264f1,
clsLdrId=cee28b53551-79226bcc-651f-4af7-8d39-fd4019b7708c, userVer=0, loc=true,
sampleClsName=java.lang.String, pendingUndeploy=false, undeployed=false,
usage=0]],
taskClsName=o.a.i.yardstick.cache.load.IgniteCapitalizationBenchmark$ScanQueryBroadcastClosure,
sesId=bfb21563551-a8d91d06-89bd-41a5-8b4f-6a02416dfc63,
startTime=1465486810898, endTime=9223372036854775807,
taskNodeId=a8d91d06-89bd-41a5-8b4f-6a02416dfc63,
clsLdr=sun.misc.Launcher$AppClassLoader@6da264f1, closed=false, cpSpi=null,
failSpi=null, loadSpi=null, usage=1, fullSup=false,
subjId=a8d91d06-89bd-41a5-8b4f-6a02416dfc63, mapFut=IgniteFuture
[orig=GridFutureAdapter [resFlag=0, res=null, startTime=1465486811180,
endTime=0, ignoreInterrupts=false, state=INIT]]],
jobId=51c21563551-a8d91d06-89bd-41a5-8b4f-6a02416dfc63]], hasRes=true,
isCancelled=false, isOccupied=true]
class org.apache.ignite.IgniteException: Remote job threw user exception
(override or implement ComputeTask.result(..) method if you would like to have
automatic failover for this exception).
at
org.apache.ignite.compute.ComputeTaskAdapter.result(ComputeTaskAdapter.java:101)
at
org.apache.ignite.internal.processors.task.GridTaskWorker$3.apply(GridTaskWorker.java:912)
at
org.apache.ignite.internal.processors.task.GridTaskWorker$3.apply(GridTaskWorker.java:905)
at
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6491)
at
org.apache.ignite.internal.processors.task.GridTaskWorker.result(GridTaskWorker.java:905)
at
org.apache.ignite.internal.processors.task.GridTaskWorker.onResponse(GridTaskWorker.java:801)
at
org.apache.ignite.internal.processors.task.GridTaskProcessor.processJobExecuteResponse(GridTaskProcessor.java:995)
at
org.apache.ignite.internal.processors.task.GridTaskProcessor$JobMessageListener.onMessage(GridTaskProcessor.java:1220)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1219)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:847)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:105)
at
org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:810)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: class org.apache.ignite.compute.ComputeUserUndeclaredException:
Failed to execute job due to unexpected runtime exception
[jobId=51c21563551-a8d91d06-89bd-41a5-8b4f-6a02416dfc63, ses=GridJobSessionImpl
[ses=GridTaskSessionImpl
[taskName=org.apache.ignite.yardstick.cache.load.IgniteCapitalizationBenchmark$ScanQueryBroadcastClosure,
dep=LocalDeployment [super=GridDeployment
[jira] [Created] (IGNITE-3292) Yardstick: add logging of preloading progress
Ksenia Rybakova created IGNITE-3292: --- Summary: Yardstick: add logging of preloading progress Key: IGNITE-3292 URL: https://issues.apache.org/jira/browse/IGNITE-3292 Project: Ignite Issue Type: Wish Components: yardstick Reporter: Ksenia Rybakova Fix For: 1.7 Please, add logging of preloading progress. This is really useful when we load a lot of entries or they are large. For instance: "Preloading: 200 of 1000 loaded". Also adding an option that controls frequency of such output makes sense. For instance, this might be a step (number of entries loaded) - if entries are large, we set small step, if entries are integers, the step will be large. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-3290) Yarstick: log when preloading/warmup started/finished
Ksenia Rybakova created IGNITE-3290: --- Summary: Yarstick: log when preloading/warmup started/finished Key: IGNITE-3290 URL: https://issues.apache.org/jira/browse/IGNITE-3290 Project: Ignite Issue Type: Wish Reporter: Ksenia Rybakova Please, add messages to log that whould indicate that: 1) preloading started 2) preloading finished 3) warmup started -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-3288) Load test benchmark: log current number of operations over caches on demand
Ksenia Rybakova created IGNITE-3288: --- Summary: Load test benchmark: log current number of operations over caches on demand Key: IGNITE-3288 URL: https://issues.apache.org/jira/browse/IGNITE-3288 Project: Ignite Issue Type: Wish Reporter: Ksenia Rybakova Fix For: 1.7 Currently statistics on operations done over each cache is logged only at the end of the test. It whould be really helpful to have an ability to log such statistics on demand during the test (for instance, sending some signal) or over some configured interval (introduce new option). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-3269) Benchmark driver stops working when one of servers left grid and backupcount 0
Ksenia Rybakova created IGNITE-3269:
---
Summary: Benchmark driver stops working when one of servers left
grid and backupcount 0
Key: IGNITE-3269
URL: https://issues.apache.org/jira/browse/IGNITE-3269
Project: Ignite
Issue Type: Bug
Affects Versions: 1.7
Reporter: Ksenia Rybakova
Priority: Minor
Test config: 4 hosts with 4 clients and 1 server each, backup count = 0.
During the test one of the servers was killed. After that one of the clients
stopped working:
{noformat}
[15:31:45,248][WARN ][sys-#27%null%][TcpCommunicationSpi] Connect timed out
(consider increasing 'failureDetectionTimeout' configuration property)
[addr=fosters-216/10.20.0.216:47100, failureDetectionTimeout=1]
[15:31:45,256][WARN ][sys-#27%null%][TcpCommunicationSpi] Failed to connect to
a remote node (make sure that destination node is alive and operating system
firewall is disabled on local and remote hosts)
[addrs=[fosters-216/10.20.0.216:4
[15:31:45,276][WARN ][disco-event-worker-#52%null%][GridDiscoveryManager] Node
FAILED: TcpDiscoveryNode [id=f5bcc4d3-aa56-4e51-8672-e799a42990a6,
addrs=[10.20.0.216, 127.0.0.1], sockAddrs=[fosters-216/10.20.0.216:47500,
/10.20.0.216:4750
[15:31:45,324][INFO ][disco-event-worker-#52%null%][GridDiscoveryManager]
Topology snapshot [ver=22, servers=3, clients=16, CPUs=64, heap=150.0GB]
ERROR: The benchmark of random operation failed.
Type '--help' for usage.
Finishing main test [ts=1465252305413, date=Mon Jun 06 15:31:45 PDT 2016]
[15:31:45] (err) Failed to execute compound future reducer:
GridNearTxFinishFuture [futId=9c7413d2551-758034b3-0248-4d62-b901-be86d119183c,
tx=GridNearTxLocal [mappings=IgniteTxMappingsImpl [], nearLocallyMapped=false,
colocatedLocallyMa
Type '--help' for usage.
[15:31:45] (err) Failed to execute compound future reducer:
GridNearTxFinishFuture [futId=6f7413d2551-758034b3-0248-4d62-b901-be86d119183c,
tx=GridNearTxLocal [mappings=IgniteTxMappingsImpl [], nearLocallyMapped=false,
colocatedLocallyMa
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.finishDhtLocal(IgniteTxHandler.java:700)
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.finish(IgniteTxHandler.java:644)
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processNearTxFinishRequest(IgniteTxHandler.java:607)
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$3.apply(IgniteTxHandler.java:135)
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$3.apply(IgniteTxHandler.java:133)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:624)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:322)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:246)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$000(GridCacheIoManager.java:83)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:205)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1219)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:847)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:105)
at
org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:810)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
[15:31:45] (err) Failed to execute compound future reducer:
GridNearTxFinishFuture [futId=ff7413d2551-758034b3-0248-4d62-b901-be86d119183c,
tx=GridNearTxLocal [mappings=IgniteTxMappingsImpl [], nearLocallyMapped=false,
colocatedLocallyMa
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.finishDhtLocal(IgniteTxHandler.java:700)
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.finish(IgniteTxHandler.java:644)
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processNearTxFinishRequest(IgniteTxHandler.java:607)
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$3.apply(IgniteTxHandler.java:135)
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$3.apply(IgniteTxHandler.java:133)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:624)
at
[jira] [Created] (IGNITE-3239) "Failed to write class name to file xxxxx.classname" error when several clients and server are running at one host
Ksenia Rybakova created IGNITE-3239:
---
Summary: "Failed to write class name to file x.classname"
error when several clients and server are running at one host
Key: IGNITE-3239
URL: https://issues.apache.org/jira/browse/IGNITE-3239
Project: Ignite
Issue Type: Bug
Affects Versions: 1.7
Reporter: Ksenia Rybakova
Priority: Minor
During load test with 4 clients and 1 server per host (total 4 servers) the
following errors occur on server and client sides:
{noformat}
[06:02:28,418][ERROR][marshaller-cache-#96%null%][MarshallerContextImpl] Failed
to write class name to file [id=1023271795,
clsName=o.a.i.yardstick.cache.load.model.key.Identifier,
file=/home/gridgain/krybakova/opts-set-b-0-m-client-rev-3c3ed056-date-0206-060158/yardstick/work/marshaller/1023271795.classname]
java.io.IOException: Resource deadlock avoided
at sun.nio.ch.FileDispatcherImpl.lock0(Native Method)
at sun.nio.ch.FileDispatcherImpl.lock(FileDispatcherImpl.java:90)
at sun.nio.ch.FileChannelImpl.lock(FileChannelImpl.java:1052)
at
org.apache.ignite.internal.MarshallerContextImpl$ContinuousQueryListener.onUpdated(MarshallerContextImpl.java:236)
at
org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.onEntryUpdate(CacheContinuousQueryHandler.java:769)
at
org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.access$700(CacheContinuousQueryHandler.java:91)
at
org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler$1.onEntryUpdated(CacheContinuousQueryHandler.java:412)
at
org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryManager.onEntryUpdated(CacheContinuousQueryManager.java:343)
at
org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryManager.onEntryUpdated(CacheContinuousQueryManager.java:250)
at
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.innerUpdate(GridCacheMapEntry.java:2167)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateSingle(GridDhtAtomicCache.java:2250)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1644)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1484)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.processNearAtomicUpdateRequest(GridDhtAtomicCache.java:2945)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$600(GridDhtAtomicCache.java:129)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$5.apply(GridDhtAtomicCache.java:260)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$5.apply(GridDhtAtomicCache.java:258)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:624)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:322)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:246)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$000(GridCacheIoManager.java:83)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:205)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1219)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:847)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:105)
at
org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:810)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-3212) Servers get stuck with the warning "Failed to wait for initial partition map exchange" during falover test
Ksenia Rybakova created IGNITE-3212:
---
Summary: Servers get stuck with the warning "Failed to wait for
initial partition map exchange" during falover test
Key: IGNITE-3212
URL: https://issues.apache.org/jira/browse/IGNITE-3212
Project: Ignite
Issue Type: Bug
Affects Versions: 1.6
Reporter: Ksenia Rybakova
Servers being restarted during falover test get stuck after some time with the
warning "Failed to wait for initial partition map exchange".
{noformat}
[08:44:41,303][INFO ][disco-event-worker-#80%null%][GridDiscoveryManager] Added
new node to topology: TcpDiscoveryNode
[id=db557f04-43b7-4e28-ae0d-d4dcf4139c89, addrs=
[10.20.0.222, 127.0.0.1], sockAddrs=[fosters-222/10.20.0.222:47503,
/10.20.0.222:47503, /127.0.0.1:47503], discPort=47503, order=44, intOrder=32,
lastExchangeTime=1464
363880917, loc=false, ver=1.6.0#20160525-sha1:48321a40, isClient=false]
[08:44:41,304][INFO ][disco-event-worker-#80%null%][GridDiscoveryManager]
Topology snapshot [ver=44, servers=19, clients=1, CPUs=64, heap=160.0GB]
[08:45:11,455][INFO ][disco-event-worker-#80%null%][GridDiscoveryManager] Added
new node to topology: TcpDiscoveryNode
[id=6fae61a7-c1c1-40e5-8ad0-8bf5d6c86eb7, addrs=
[10.20.0.223, 127.0.0.1], sockAddrs=[fosters-223/10.20.0.223:47503,
/10.20.0.223:47503, /127.0.0.1:47503], discPort=47503, order=45, intOrder=33,
lastExchangeTime=1464
363910999, loc=false, ver=1.6.0#20160525-sha1:48321a40, isClient=false]
[08:45:11,455][INFO ][disco-event-worker-#80%null%][GridDiscoveryManager]
Topology snapshot [ver=45, servers=20, clients=1, CPUs=64, heap=170.0GB]
[08:45:19,942][INFO ][ignite-update-notifier-timer][GridUpdateNotifier] Update
status is not available.
[08:46:20,370][WARN ][main][GridCachePartitionExchangeManager] Failed to wait
for initial partition map exchange. Possible reasons are:
^-- Transactions in deadlock.
^-- Long running transactions (ignore if this is the case).
^-- Unreleased explicit locks.
[08:48:30,375][WARN ][main][GridCachePartitionExchangeManager] Still waiting
for initial partition map exchange ...
{noformat}
"Failed to wait for partition release future" warnings are on other nodes.
{noformat}
[08:09:45,822][WARN
][exchange-worker-#82%null%][GridDhtPartitionsExchangeFuture] Failed to wait
for partition release future [topVer=AffinityTopologyVersion [topVer=29,
minorTopVer=0], node=cab5d0e0-7365-4774-8f99-d9f131c5d896]. Dumping pending
objects that might be the cause:
[08:09:45,822][WARN
][exchange-worker-#82%null%][GridCachePartitionExchangeManager] Ready affinity
version: AffinityTopologyVersion [topVer=28, minorTopVer=1]
[08:09:45,826][WARN
][exchange-worker-#82%null%][GridCachePartitionExchangeManager] Last exchange
future: GridDhtPartitionsExchangeFuture ...
{noformat}
Load config:
- 1 client, 20 servers (5 servers per 1 host)
- warmup 60
- duration 66h
- preload 5M
- key range 10M
- operations: PUT PUT_ALL GET GET_ALL INVOKE INVOKE_ALL REMOVE REMOVE_ALL
PUT_IF_ABSENT REPLACE
- backups count 3
- 3 servers restart every 15 min with 30 sec step, pause between stop and start
5min
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-3208) Add ability to yardstick to restart drivers
Ksenia Rybakova created IGNITE-3208: --- Summary: Add ability to yardstick to restart drivers Key: IGNITE-3208 URL: https://issues.apache.org/jira/browse/IGNITE-3208 Project: Ignite Issue Type: Wish Affects Versions: 1.6 Reporter: Ksenia Rybakova Currently, yardstick supports only RESTART_SERVERS option. Please, add similar option to restart drivers. This is required for fault tolerance tests. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-3114) "IllegalStateException: Row conflict should never happen" during load test
Ksenia Rybakova created IGNITE-3114: --- Summary: "IllegalStateException: Row conflict should never happen" during load test Key: IGNITE-3114 URL: https://issues.apache.org/jira/browse/IGNITE-3114 Project: Ignite Issue Type: Bug Affects Versions: 1.6 Reporter: Ksenia Rybakova Priority: Minor Configuration: - 3 drivers at 1 host, 30 servers at 3 hosts; - all operations are enabled except SCAN_QUERY, SQL_QUERY and CONTINUOUS_QUERY - for other settings see attached benchmark-cache-load.properties file Steps to reproduce: 1) Run load test: ./bin/benchmark-run-all.sh config/benchmark-cache-load.properties 2) Check all server log files. Expected: No exceptions. Actual: "java.lang.IllegalStateException: Row conflict should never happen, unique indexes are not supported" exceptions accur while running load test benchmark. In my case I noticed that all these exceptions happened only at 20th server (1st server node at the 3rd host). java.lang.IllegalStateException: Row conflict should never happen, unique indexes are not supported. at org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.doUpdate(GridH2Table.java:410) at org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.update(GridH2Table.java:340) at org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.store(IgniteH2Indexing.java:524) at org.apache.ignite.internal.processors.query.GridQueryProcessor.store(GridQueryProcessor.java:700) at org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.store(GridCacheQueryManager.java:407) at org.apache.ignite.internal.processors.cache.GridCacheMapEntry.updateIndex(GridCacheMapEntry.java:3849) at org.apache.ignite.internal.processors.cache.GridCacheMapEntry.initialValue(GridCacheMapEntry.java:3309) at org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$IsolatedUpdater.receive(DataStreamerImpl.java:1618) at org.apache.ignite.internal.processors.datastreamer.DataStreamerUpdateJob.call(DataStreamerUpdateJob.java:140) at org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.processRequest(DataStreamProcessor.java:305) at org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.access$000(DataStreamProcessor.java:50) at org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor$1.onMessage(DataStreamProcessor.java:80) at org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1219) at org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:847) at org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:105) at org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:810) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
