[
https://issues.apache.org/jira/browse/IGNITE-12089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16923860#comment-16923860
]
temp2 edited comment on IGNITE-12089 at 9/6/19 1:58 AM:
--------------------------------------------------------
hi Stanilovsky Evgeny,
I don't understand what cluster configuration inconsistency means and why need
isClient=false.
The whole test environment and step I will elaborate on:
1. Prepare 4 physical machines, 3 servers and 1 client. Install Oracle
jdk1.8.0_101 in all 4 machines. make all kinds of necessary directories in each
machine.
2. In one of the three server-side machines, decompress
"apache-ignite-2.7.5-bin.zip", modify "bin\ignite.sh" file in decompression
directory, increase -Xmx value to 10g, modify "config\default-config.xml", see
the attachments above.
3. Copy the entire directory of the decompressed and modified apache-ignite to
two other server machines.
4. Select two of the server-side machines to run "bin\ignite. sh
config\default-config. xml", start two server-side nodes
5. Select one of the server-side machines to run "bin\control.sh --activate",
activate the cluster. This step can also be avoided.
6. Put IgniteTest2 test code and dependency jars (apache-ignite-2.7.5-bin.zip
is not required) into the fourth machine and run directly with Java command.
The running parameters are "com.test.IgniteTest2 5 0 test 2000000000
192.168.20.12:49500 192.168.20.13:49500 192.168.20.14:49500".
7. 20 minutes later, the third server-side machines to run "bin\ignite. sh
config\default-config. xml"
8. A few minutes later after the start of the third server, one or two of the
first two servers will appear "Partitions cache sizes are inconsistent", and
then a moment later one or two of the first two servers the JVM will exit with
the errores.
was (Author: temp2):
hi Stanilovsky Evgeny,
I don't understand what cluster configuration inconsistency means.
The whole test environment and step I will elaborate on:
1. Prepare 4 physical machines, 3 servers and 1 client. Install Oracle
jdk1.8.0_101 in all 4 machines. make all kinds of necessary directories in each
machine.
2. In one of the three server-side machines, decompress
"apache-ignite-2.7.5-bin.zip", modify "bin\ignite.sh" file in decompression
directory, increase -Xmx value to 10g, modify "config\default-config.xml", see
the attachments above.
3. Copy the entire directory of the decompressed and modified apache-ignite to
two other server machines.
4. Select two of the server-side machines to run "bin\ignite. sh
config\default-config. xml", start two server-side nodes
5. Select one of the server-side machines to run "bin\control.sh --activate",
activate the cluster. This step can also be avoided.
6. Put IgniteTest2 test code and dependency jars (apache-ignite-2.7.5-bin.zip
is not required) into the fourth machine and run directly with Java command.
The running parameters are "com.test.IgniteTest2 5 0 test 2000000000
192.168.20.12:49500 192.168.20.13:49500 192.168.20.14:49500".
7. 20 minutes later, the third server-side machines to run "bin\ignite. sh
config\default-config. xml"
8. A few minutes later after the start of the third server, one or two of the
first two serveres will appear "Partitions cache sizes are inconsistent", and
then a moment later one or two of the first two serveres the JVM will exit
with the errores.
> JVM is halted after this error during rolling restart of a cluster
> ------------------------------------------------------------------
>
> Key: IGNITE-12089
> URL: https://issues.apache.org/jira/browse/IGNITE-12089
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.6
> Reporter: temp2
> Priority: Critical
> Attachments: IgniteTest2.java, default-config.xml, ignite27.log,
> ignite42.log
>
>
> JVM is halted after this error during rolling restart of a cluster:
> excepition is :528-a852-c65782e337f0][2019-08-20
> 17:22:10,901][ERROR][ttl-cleanup-worker-#155][] Critical system error
> detected. Will be handled accordingly to configured handler [hnd=class
> o.a.i.failure.StopNodeOrHaltFailure528-a852-c65782e337f0][2019-08-20
> 17:22:10,901][ERROR][ttl-cleanup-worker-#155][] Critical system error
> detected. Will be handled accordingly to configured handler [hnd=class
> o.a.i.failure.StopNodeOrHaltFailureHandler, failureCtx=FailureContext
> [type=SYSTEM_WORKER_TERMINATION, err=class o.a.i.IgniteException: Runtime
> failure on bounds: [lower=PendingRow [], upper=PendingRow
> []]]]org.apache.ignite.IgniteException: Runtime failure on bounds:
> [lower=PendingRow [], upper=PendingRow []] at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.find(BPlusTree.java:971)
> ~[ignite-core-2.6.0.jar:2.6.0] at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.find(BPlusTree.java:950)
> ~[ignite-core-2.6.0.jar:2.6.0] at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.expire(IgniteCacheOffheapManagerImpl.java:1022)
> ~[ignite-core-2.6.0.jar:2.6.0] at
> org.apache.ignite.internal.processors.cache.GridCacheTtlManager.expire(GridCacheTtlManager.java:197)
> ~[ignite-core-2.6.0.jar:2.6.0] at
> org.apache.ignite.internal.processors.cache.GridCacheSharedTtlCleanupManager$CleanupWorker.body(GridCacheSharedTtlCleanupManager.java:137)
> [ignite-core-2.6.0.jar:2.6.0] at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> [ignite-core-2.6.0.jar:2.6.0] at java.lang.Thread.run(Thread.java:745)
> [?:1.8.0_101]Caused by: java.lang.IllegalStateException: Failed to get page
> IO instance (page content is corrupted) at
> org.apache.ignite.internal.processors.cache.persistence.tree.io.IOVersions.forVersion(IOVersions.java:83)
> ~[ignite-core-2.6.0.jar:2.6.0] at
> org.apache.ignite.internal.processors.cache.persistence.tree.io.IOVersions.forPage(IOVersions.java:95)
> ~[ignite-core-2.6.0.jar:2.6.0] at
> org.apache.ignite.internal.processors.cache.persistence.CacheDataRowAdapter.initFromLink(CacheDataRowAdapter.java:148)
> ~[ignite-core-2.6.0.jar:2.6.0] at
> org.apache.ignite.internal.processors.cache.persistence.CacheDataRowAdapter.initFromLink(CacheDataRowAdapter.java:102)
> ~[ignite-core-2.6.0.jar:2.6.0] at
> org.apache.ignite.internal.processors.cache.tree.PendingRow.initKey(PendingRow.java:72)
> ~[ignite-core-2.6.0.jar:2.6.0] at
> org.apache.ignite.internal.processors.cache.tree.PendingEntriesTree.getRow(PendingEntriesTree.java:118)
> ~[ignite-core-2.6.0.jar:2.6.0] at
> org.apache.ignite.internal.processors.cache.tree.PendingEntriesTree.getRow(PendingEntriesTree.java:31)
> ~[ignite-core-2.6.0.jar:2.6.0] at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$ForwardCursor.fillFromBuffer(BPlusTree.java:4660)
> ~[ignite-core-2.6.0.jar:2.6.0] at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$ForwardCursor.init(BPlusTree.java:4562)
> ~[ignite-core-2.6.0.jar:2.6.0] at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$ForwardCursor.access$5300(BPlusTree.java:4501)
> ~[ignite-core-2.6.0.jar:2.6.0] at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$GetCursor.notFound(BPlusTree.java:2633)
> ~[ignite-core-2.6.0.jar:2.6.0] at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Search.run0(BPlusTree.java:293)
> ~[ignite-core-2.6.0.jar:2.6.0] at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$GetPageHandler.run(BPlusTree.java:4816)
> ~[ignite-core-2.6.0.jar:2.6.0] at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$GetPageHandler.run(BPlusTree.java:4801)
> ~[ignite-core-2.6.0.jar:2.6.0] at
> org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.readPage(PageHandler.java:158)
> ~[ignite-core-2.6.0.jar:2.6.0] at
> org.apache.ignite.internal.processors.cache.persistence.DataStructure.read(DataStructure.java:332)
> ~[ignite-core-2.6.0.jar:2.6.0] at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.findDown(BPlusTree.java:1140)
> ~[ignite-core-2.6.0.jar:2.6.0] at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.findDown(BPlusTree.java:1149)
> ~[ignite-core-2.6.0.jar:2.6.0] at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.doFind(BPlusTree.java:1107)
> ~[ignite-core-2.6.0.jar:2.6.0] at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.access$15800(BPlusTree.java:83)
> ~[ignite-core-2.6.0.jar:2.6.0] at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$ForwardCursor.find(BPlusTree.java:4716)
> ~[ignite-core-2.6.0.jar:2.6.0] at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$ForwardCursor.access$5400(BPlusTree.java:4501)
> ~[ignite-core-2.6.0.jar:2.6.0] at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.find(BPlusTree.java:963)
> ~[ignite-core-2.6.0.jar:2.6.0] ... 6 more[2019-08-20
> 17:22:10,909][ERROR][ttl-cleanup-worker-#155][] JVM will be halted
> immediately due to the failure: [failureCtx=FailureContext
> [type=SYSTEM_WORKER_TERMINATION, err=class o.a.i.IgniteException: Runtime
> failure on bounds: [lower=PendingRow [], upper=PendingRow []]]]
>
>
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
