[jira] [Created] (IGNITE-14572) Include metastorage into snapshot
Maxim Muzafarov created IGNITE-14572: Summary: Include metastorage into snapshot Key: IGNITE-14572 URL: https://issues.apache.org/jira/browse/IGNITE-14572 Project: Ignite Issue Type: Task Reporter: Maxim Muzafarov Assignee: Maxim Muzafarov Fix For: 2.11 Currently, only cache and cache groups with CacheType.USER included into a snapshot. We must also include into snapshot the metastorage data. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14515) Support MissingSwitchDefaultCheck checkstyle check
Maxim Muzafarov created IGNITE-14515: Summary: Support MissingSwitchDefaultCheck checkstyle check Key: IGNITE-14515 URL: https://issues.apache.org/jira/browse/IGNITE-14515 Project: Ignite Issue Type: Task Reporter: Maxim Muzafarov Assignee: Maxim Muzafarov Fix For: 2.11 Every switch statement should include a default case. The break in the default case is redundant, but it prevents a fall-through error if later another case is added. https://www.oracle.com/java/technologies/javase/codeconventions-statements.html#468 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14462) Enable EmptyCatchBlock checkstyle check
Maxim Muzafarov created IGNITE-14462:
Summary: Enable EmptyCatchBlock checkstyle check
Key: IGNITE-14462
URL: https://issues.apache.org/jira/browse/IGNITE-14462
Project: Ignite
Issue Type: Task
Reporter: Maxim Muzafarov
Assignee: Maxim Muzafarov
Fix For: 2.11
Checks for empty catch blocks. By default, check allows an empty catch block
with any comment inside.
{code}
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14309) Document snapshot check command
Maxim Muzafarov created IGNITE-14309: Summary: Document snapshot check command Key: IGNITE-14309 URL: https://issues.apache.org/jira/browse/IGNITE-14309 Project: Ignite Issue Type: Bug Components: documentation Reporter: Maxim Muzafarov Assignee: Maxim Muzafarov Fix For: 2.11 The changes related to the checking snapshot via the command line must be well documented. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14286) Fix snapshot check command for client nodes
Maxim Muzafarov created IGNITE-14286:
Summary: Fix snapshot check command for client nodes
Key: IGNITE-14286
URL: https://issues.apache.org/jira/browse/IGNITE-14286
Project: Ignite
Issue Type: Bug
Reporter: Maxim Muzafarov
Assignee: Maxim Muzafarov
Fix For: 2.11
{code}
[2021-03-07 22:32:11,828][INFO ][main][root] >>> Non-Heap: 66 MB used / 73 MB
commited / 0 MB max <<<
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at
org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2391)
at java.lang.Thread.run(Thread.java:748)
Caused by: class org.apache.ignite.compute.ComputeUserUndeclaredException:
Failed to reduce job results due to undeclared user exception
[task=org.apache.ignite.internal.processors.cache.persistence.snapshot.SnapshotMetadataCollectorTask@3d6925bf,
err=class
org.apache.ignite.internal.processors.cache.persistence.snapshot.IgniteSnapshotVerifyException:
null]
at
org.apache.ignite.internal.processors.task.GridTaskWorker.reduce(GridTaskWorker.java:1188)
at
org.apache.ignite.internal.processors.task.GridTaskWorker.onResponse(GridTaskWorker.java:976)
at
org.apache.ignite.internal.processors.task.GridTaskProcessor.processJobExecuteResponse(GridTaskProcessor.java:1161)
at
org.apache.ignite.internal.processors.task.GridTaskProcessor$JobMessageListener.onMessage(GridTaskProcessor.java:1396)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1908)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1529)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$5300(GridIoManager.java:242)
at
org.apache.ignite.internal.managers.communication.GridIoManager$9.execute(GridIoManager.java:1422)
at
org.apache.ignite.internal.managers.communication.TraceRunnable.run(TraceRunnable.java:55)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
... 1 more
Caused by: class
org.apache.ignite.internal.processors.cache.persistence.snapshot.IgniteSnapshotVerifyException:
null
at
org.apache.ignite.internal.processors.cache.persistence.snapshot.SnapshotMetadataCollectorTask.reduce(SnapshotMetadataCollectorTask.java:103)
at
org.apache.ignite.internal.processors.cache.persistence.snapshot.SnapshotMetadataCollectorTask.reduce(SnapshotMetadataCollectorTask.java:39)
at
org.apache.ignite.internal.processors.task.GridTaskWorker$6.call(GridTaskWorker.java:1149)
at
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:7085)
at
org.apache.ignite.internal.processors.task.GridTaskWorker.reduce(GridTaskWorker.java:1147)
... 11 more
class org.apache.ignite.IgniteCheckedException: Failed to reduce job results
due to undeclared user exception
[task=org.apache.ignite.internal.processors.cache.persistence.snapshot.SnapshotMetadataCollectorTask@3d6925bf,
err=class
org.apache.ignite.internal.processors.cache.persistence.snapshot.IgniteSnapshotVerifyException:
null]
at
org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7587)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.resolve(GridFutureAdapter.java:260)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:191)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:141)
at
org.apache.ignite.internal.processors.cache.persistence.snapshot.IgniteClusterSnapshotCheckTest.testClusterSnapshotCheck(IgniteClusterSnapshotCheckTest.java:71)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
[jira] [Created] (IGNITE-14273) ignite-extensions: Export data from snapshot to custom format
Maxim Muzafarov created IGNITE-14273: Summary: ignite-extensions: Export data from snapshot to custom format Key: IGNITE-14273 URL: https://issues.apache.org/jira/browse/IGNITE-14273 Project: Ignite Issue Type: Improvement Components: extensions Reporter: Maxim Muzafarov Assignee: Maxim Muzafarov The user must be able to use offline command-line tools to export data from a snapshot to an external appropriate format e.g. CSV, parquet, JSON. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14267) Cluster snapshot must support encrypted caches
Maxim Muzafarov created IGNITE-14267: Summary: Cluster snapshot must support encrypted caches Key: IGNITE-14267 URL: https://issues.apache.org/jira/browse/IGNITE-14267 Project: Ignite Issue Type: Improvement Reporter: Maxim Muzafarov Assignee: Maxim Muzafarov Fix For: 2.11 Currently, the snapshot procedure doesn't support taking a cluster snapshot for caches with enabled encryption. We should support such a feature, so the user will be able to create and restore for such snapshots. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14266) System views for page statistics must include the bucktes sizes
Maxim Muzafarov created IGNITE-14266: Summary: System views for page statistics must include the bucktes sizes Key: IGNITE-14266 URL: https://issues.apache.org/jira/browse/IGNITE-14266 Project: Ignite Issue Type: Improvement Reporter: Maxim Muzafarov Fix For: 2.11 Affected system views: CACHE_GROUP_PAGE_LISTS, DATA_REGION_PAGE_LISTS The bucket index corresponds to the interval of free space on pages it contains. We must add this info to the system views. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14261) Add references to the new documentation metrics pages from the legacy page
Maxim Muzafarov created IGNITE-14261: Summary: Add references to the new documentation metrics pages from the legacy page Key: IGNITE-14261 URL: https://issues.apache.org/jira/browse/IGNITE-14261 Project: Ignite Issue Type: Task Reporter: Maxim Muzafarov Assignee: Maxim Muzafarov Fix For: 2.10 The legacy JMX metrics [1] must have a reference to the new metrics framework which was introduced in the 2.8 release. [1] https://ignite.apache.org/docs/latest/monitoring-metrics/metrics -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14252) CorruptedTreeException for persistence 2.7.5 running on 2.9.1 version
Maxim Muzafarov created IGNITE-14252:
Summary: CorruptedTreeException for persistence 2.7.5 running on
2.9.1 version
Key: IGNITE-14252
URL: https://issues.apache.org/jira/browse/IGNITE-14252
Project: Ignite
Issue Type: Task
Reporter: Maxim Muzafarov
PDS Version - 2.7.5
Ignite node verision - 2.9.1
h3. Cache configuration
{code}
DataRegionConfiguration dataRegionCfg = new DataRegionConfiguration();
dataRegionCfg.setName(DATA_REGION_NAME)
.setInitialSize(200_000_000)
.setMaxSize(200_000_000)
.setPersistenceEnabled(true)
.setMetricsEnabled(true);
DataStorageConfiguration storageCfg = new DataStorageConfiguration();
storageCfg.setDataRegionConfigurations(dataRegionCfg)
.setWriteThrottlingEnabled(true)
.setMetricsEnabled(true);
IgniteConfiguration ignCfg = new IgniteConfiguration();
ignCfg.setWorkDirectory(workDirectory)
.setDataStorageConfiguration(storageCfg)
.setIgniteInstanceName("instanceName")
.setSystemWorkerBlockedTimeout(1)
.setFailureDetectionTimeout(1)
{code}
h3. Exception
{code}
2021-02-19 13:30:38,175 ERROR STDIO [pool-32-thread-5] {} Feb 19, 2021 1:30:38
PM org.apache.ignite.logger.java.JavaLogger error
SEVERE: Critical system error detected. Will be handled accordingly to
configured handler [hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0,
super=AbstractFailureHandler
[ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED,
SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], failureCtx=FailureContext
[type=CRITICAL_ERROR, err=class
o.a.i.i.processors.cache.persistence.tree.CorruptedTreeException: B+Tree is
corrupted [pages(groupId, pageId)=[IgniteBiTuple [val1=-128547534,
val2=281474976721835]], msg=Runtime failure on lookup row: SearchRow
[key=com.bloomberg.aim.wingman.cachemgr.Ts3DataCache$Ts3SecurityCacheKey
[idHash=1436767547, hash=-931214342,
accountCusip=com.bloomberg.aim.wingman.common.dto.submgr.AccountCusip
[idHash=316813954, hash=343304888, accountId=0,
cusip=com.bloomberg.aim.wingman.common.dto.Cusip [idHash=1325824124,
hash=2123451959, cusip1=136125, cusip2=9001, cusip3=541401120, dept=2,
subflag=2]]], hash=-931214342, cacheId=0
class
org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
B+Tree is corrupted [pages(groupId, pageId)=[IgniteBiTuple [val1=-128547534,
val2=281474976721835]], msg=Runtime failure on lookup row: SearchRow
[key=com.bloomberg.aim.wingman.cachemgr.Ts3DataCache$Ts3SecurityCacheKey
[idHash=1436767547, hash=-931214342, accountCusip=
com.bloomberg.aim.wingman.common.dto.submgr.AccountCusip [idHash=316813954,
hash=343304888, accountId=0, cusip=com.bloomberg.aim.wingman.common.dto.Cusip
[idHash=1325824124, hash=2123451959, cusip1=136125, cusip2=9001,
cusip3=541401120, dept=2, subflag=2]]], hash=-931214342, cacheId=0]]
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.corruptedTreeException(BPlusTree.java:6106)
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.findOne(BPlusTree.java:1367)
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.findOne(BPlusTree.java:1344)
at
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.find(IgniteCacheOffheapManagerImpl.java:2755)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.find(GridCacheOffheapManager.java:2469)
at
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.read(IgniteCacheOffheapManagerImpl.java:637)
at
org.apache.ignite.internal.processors.cache.local.atomic.GridLocalAtomicCache.getAllInternal(GridLocalAtomicCache.java:410)
at
org.apache.ignite.internal.processors.cache.local.atomic.GridLocalAtomicCache.getAll(GridLocalAtomicCache.java:323)
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter.repairableGetAll(GridCacheAdapter.java:4907)
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter.getAll(GridCacheAdapter.java:1617)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.getAll(IgniteCacheProxyImpl.java:1157)
at
org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.getAll(GatewayProtectedCacheProxy.java:724)
at
com.bloomberg.aim.wingman.cachemgr.Ts3DataCache.fetchCalcrtDataByKeySync(Ts3DataCache.java:1535)
at
com.bloomberg.aim.wingman.cachemgr.Ts3DataCache.lambda$fetchCalcrtDataBySecurityKeyAccountAsync$11(Ts3DataCache.java:895)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at
[jira] [Created] (IGNITE-14247) Add documentation pages for snapshot check command
Maxim Muzafarov created IGNITE-14247: Summary: Add documentation pages for snapshot check command Key: IGNITE-14247 URL: https://issues.apache.org/jira/browse/IGNITE-14247 Project: Ignite Issue Type: Task Components: documentation Reporter: Maxim Muzafarov Assignee: Maxim Muzafarov Fix For: 2.11 The snapshot check command must be properly documented. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14223) Remove FilePageStoreFactory internal interface
Maxim Muzafarov created IGNITE-14223: Summary: Remove FilePageStoreFactory internal interface Key: IGNITE-14223 URL: https://issues.apache.org/jira/browse/IGNITE-14223 Project: Ignite Issue Type: Task Reporter: Maxim Muzafarov Assignee: Maxim Muzafarov Fix For: 2.11 The FilePageStoreFactory can be simplified since this factory has a single implementation that produces FilePageStore's. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14166) Fix javadocs of pulic monitoring API which refer to internal classes
Maxim Muzafarov created IGNITE-14166: Summary: Fix javadocs of pulic monitoring API which refer to internal classes Key: IGNITE-14166 URL: https://issues.apache.org/jira/browse/IGNITE-14166 Project: Ignite Issue Type: Task Reporter: Maxim Muzafarov Assignee: Maxim Muzafarov Fix For: 2.11 Currently, for the public monitoring API, some of javadocs still refer to the internal implementation GridMetricManager (e.g. CacheGroupMetricsMXBean). The right links must be the following: - ReadOnlyMetricRegistry - ReadOnlyMetricManager - MetricExporterSpi -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14141) Remove unnecessary storage configuration from PageStore
Maxim Muzafarov created IGNITE-14141:
Summary: Remove unnecessary storage configuration from PageStore
Key: IGNITE-14141
URL: https://issues.apache.org/jira/browse/IGNITE-14141
Project: Ignite
Issue Type: Task
Reporter: Maxim Muzafarov
Assignee: Maxim Muzafarov
The {{DataStorageConfiguration}} is used only for getting the {{pageSize}} in
the {{FilePageStore}} implementation and can be removed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14134) Snapshot check command must cacluate primary and backup partition hashes
Maxim Muzafarov created IGNITE-14134: Summary: Snapshot check command must cacluate primary and backup partition hashes Key: IGNITE-14134 URL: https://issues.apache.org/jira/browse/IGNITE-14134 Project: Ignite Issue Type: Improvement Reporter: Maxim Muzafarov Fix For: 2.11 The snapshot verify procedure must calculate primary and backup partition hashes. The procedure should read each K-V pairs from each partition and calculate a resulted checksum. This collection of checksums must be compared between primary and backup partition to ensue the same data stored in each partition copy. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14107) Update release branch version for 2.10
Maxim Muzafarov created IGNITE-14107: Summary: Update release branch version for 2.10 Key: IGNITE-14107 URL: https://issues.apache.org/jira/browse/IGNITE-14107 Project: Ignite Issue Type: Task Reporter: Maxim Muzafarov Assignee: Maxim Muzafarov The version of components for the ignite-2.10 branch must be upated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14069) Add RELEASE_NOTES for 2.10
Maxim Muzafarov created IGNITE-14069: Summary: Add RELEASE_NOTES for 2.10 Key: IGNITE-14069 URL: https://issues.apache.org/jira/browse/IGNITE-14069 Project: Ignite Issue Type: Task Reporter: Maxim Muzafarov Assignee: Maxim Muzafarov The RELEASE_NOTES must be updated for the 2.10 release. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13968) Add documentation for snapshot events
Maxim Muzafarov created IGNITE-13968: Summary: Add documentation for snapshot events Key: IGNITE-13968 URL: https://issues.apache.org/jira/browse/IGNITE-13968 Project: Ignite Issue Type: Task Components: documentation Reporter: Maxim Muzafarov Assignee: Maxim Muzafarov The documentation pages must be added for newly created snapshot events: EVT_CLUSTER_SNAPSHOT_STARTED, EVT_CLUSTER_SNAPSHOT_FINISHED, EVT_CLUSTER_SNAPSHOT_FAILED -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13966) Change copyrights to 2021
Maxim Muzafarov created IGNITE-13966: Summary: Change copyrights to 2021 Key: IGNITE-13966 URL: https://issues.apache.org/jira/browse/IGNITE-13966 Project: Ignite Issue Type: Task Reporter: Maxim Muzafarov Assignee: Maxim Muzafarov The copyrights of 2020 must be changed to 2021. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13930) Update pom depencencies to 2.11.0-SNAPSHOT version
Maxim Muzafarov created IGNITE-13930: Summary: Update pom depencencies to 2.11.0-SNAPSHOT version Key: IGNITE-13930 URL: https://issues.apache.org/jira/browse/IGNITE-13930 Project: Ignite Issue Type: Task Reporter: Maxim Muzafarov Assignee: Maxim Muzafarov The pom dependencies must be updated due to the ignite-2.10 branch has been created. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13887) Checkpoint write lock missed during snapshot operation
Maxim Muzafarov created IGNITE-13887:
Summary: Checkpoint write lock missed during snapshot operation
Key: IGNITE-13887
URL: https://issues.apache.org/jira/browse/IGNITE-13887
Project: Ignite
Issue Type: Bug
Reporter: Maxim Muzafarov
Assignee: Maxim Muzafarov
{code:java}
2020-12-22 16:15:21.243 [INFO
][exchange-worker-#163%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.p.s.SnapshotFutureTask]
Snapshot operation is scheduled on local node and will be handled by the
checkpoint listener [sctx=SnapshotFutureTask
[pageStore=GridCacheSharedManagerAdapter [starting=true, stop=false],
srcNodeId=4f43f04d-3ca8-4f00-9d91-017d6ef285cd, snpName=backup01, tmpSnpWork
Dir=/ssd/snp/backup01,
locBuff=java.lang.ThreadLocal$SuppliedThreadLocal@6dc562dc,
ioFactory=org.apache.ignite.internal.processors.cache.persistence.f
ile.RandomAccessFileIOFactory@6b9dab32,
cpEndFut=java.util.concurrent.CompletableFuture@4e6e4123[Not completed],
startedFut=GridFutureAdapter [ignoreInterrupts=false, state=INIT, res=null, h
ash=2127381016], tmpConsIdDir=/ssd/snp/backup01/db/10_116_69_218_47500,
closeFut=null, err=null, started=true], topVer=AffinityTopologyVersion [topVer
=16, minorTopVer=4]]
2020-12-22 16:15:21.385
[ERROR][db-checkpoint-thread-#232%DPL_GRID%DplGridNodeName%][org.apache.ignite.Ignite]
Critical system error detected. Will be handled accordingly to configured handl
er [hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0,
super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet
[SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]]
, failureCtx=FailureContext [type=SYSTEM_WORKER_TERMINATION,
err=java.lang.AssertionError]]
java.lang.AssertionError: null
at
org.apache.ignite.internal.processors.cache.persistence.snapshot.SnapshotFutureTask$PageStoreSerialWriter.(SnapshotFutureTask.java:819)
at
org.apache.ignite.internal.processors.cache.persistence.snapshot.SnapshotFutureTask.onMarkCheckpointBegin(SnapshotFutureTask.java:466)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.markCheckpointBegin(GridCacheDatabaseSharedManager.java:3915)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.doCheckpoint(GridCacheDatabaseSharedManager.java:3515)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.body(GridCacheDatabaseSharedManager.java:3404)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at java.lang.Thread.run(Thread.java:748)
2020-12-22 16:15:21.418 [WARN
][db-checkpoint-thread-#232%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.CacheDiagnosticManager]
Page locks dump:
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-13725) Add snapshot check command
Maxim Muzafarov created IGNITE-13725:
Summary: Add snapshot check command
Key: IGNITE-13725
URL: https://issues.apache.org/jira/browse/IGNITE-13725
Project: Ignite
Issue Type: Improvement
Reporter: Maxim Muzafarov
Assignee: Maxim Muzafarov
Fix For: 2.10
A created snapshot should be validated on its consistency the same way as it
idle_verify does. The command must available through {{java}}, {{JMX}},
{{control.sh}} APIs.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-13724) Checkstyle not check on ignite-examples due to the source directory swap
Maxim Muzafarov created IGNITE-13724:
Summary: Checkstyle not check on ignite-examples due to the source
directory swap
Key: IGNITE-13724
URL: https://issues.apache.org/jira/browse/IGNITE-13724
Project: Ignite
Issue Type: Task
Reporter: Maxim Muzafarov
Assignee: Maxim Muzafarov
Not all of the classes in the {{ignite-examples}} module check by the
chekcstyle. The cause is that under the {{lgpl}} profile the source directory
attached dynamically on the validate phase by build-helper-maven-plugin.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-13654) Add snapshot commands to REST API
Maxim Muzafarov created IGNITE-13654: Summary: Add snapshot commands to REST API Key: IGNITE-13654 URL: https://issues.apache.org/jira/browse/IGNITE-13654 Project: Ignite Issue Type: Task Reporter: Maxim Muzafarov Assignee: Maxim Muzafarov Fix For: 2.10 Snapshot create/cancel commands must be added to the Apache Ignite REST API. Documentation must be also updated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13535) Support cluster snapshot security permissions
Maxim Muzafarov created IGNITE-13535: Summary: Support cluster snapshot security permissions Key: IGNITE-13535 URL: https://issues.apache.org/jira/browse/IGNITE-13535 Project: Ignite Issue Type: Task Reporter: Maxim Muzafarov Assignee: Maxim Muzafarov Need to add a capability to specify permissions to allow/disallow executions of cluster snapshot operation. The following permissions should be added to the SecurityPermission enum: - ADMIN_SNAPSHOT_OPS - for creating/cancelling snapshot opreation -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13467) Add events for snapshot operation
Maxim Muzafarov created IGNITE-13467: Summary: Add events for snapshot operation Key: IGNITE-13467 URL: https://issues.apache.org/jira/browse/IGNITE-13467 Project: Ignite Issue Type: Task Reporter: Maxim Muzafarov Assignee: Maxim Muzafarov Fix For: 2.10 The snapshot operation states must be exposed to the user by firing Ignite events: - snapshot operation started - snapshot operation finished -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13400) Add compatibility test to check pds with indexes
Maxim Muzafarov created IGNITE-13400:
Summary: Add compatibility test to check pds with indexes
Key: IGNITE-13400
URL: https://issues.apache.org/jira/browse/IGNITE-13400
Project: Ignite
Issue Type: Task
Reporter: Maxim Muzafarov
Assignee: Maxim Muzafarov
An exception occurred during staring a new Ignite 2.8.1 version on the 2.8.0
persistence data store.
{code}
2020-09-02 15:51:47.058 [ERROR][main][org.apache.ignite.internal.IgniteKernal]
Got exception while starting (will rollback startup routine).
java.lang.AssertionError: null
at
org.apache.ignite.internal.processors.cache.persistence.tree.io.BPlusMetaIO.inlineObjectSupported(BPlusMetaIO.java:231)
~[ignite-core-2.8.1.jar:2.8.1]
at
org.apache.ignite.internal.processors.query.h2.database.H2Tree$MetaPageInfo.(H2Tree.java:709)
~[ignite-indexing-2.8.1.jar:2.8.1]
at
org.apache.ignite.internal.processors.query.h2.database.H2Tree.getMetaInfo(H2Tree.java:376)
~[ignite-indexing-2.8.1.jar:2.8.1]
at
org.apache.ignite.internal.processors.query.h2.database.H2Tree.(H2Tree.java:212)
~[ignite-indexing-2.8.1.jar:2.8.1]
at
org.apache.ignite.internal.processors.query.h2.database.H2TreeIndex.(H2TreeIndex.java:254)
~[ignite-indexing-2.8.1.jar:2.8.1]
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.createSortedIndex(IgniteH2Indexing.java:472)
~[ignite-indexing-2.8.1.jar:2.8.1]
at
org.apache.ignite.internal.processors.query.h2.H2TableDescriptor.createSystemIndexes(H2TableDescriptor.java:233)
~[ignite-indexing-2.8.1.jar:2.8.1]
at
org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.(GridH2Table.java:206)
~[ignite-indexing-2.8.1.jar:2.8.1]
at
org.apache.ignite.internal.processors.query.h2.H2TableEngine.createTable(H2TableEngine.java:81)
~[ignite-indexing-2.8.1.jar:2.8.1]
at
org.apache.ignite.internal.processors.query.h2.H2TableEngine.createTable(H2TableEngine.java:32)
~[ignite-indexing-2.8.1.jar:2.8.1]
at org.h2.schema.Schema.createTable(Schema.java:670)
~[h2-1.4.197.jar:1.4.197]
at org.h2.command.ddl.CreateTable.update(CreateTable.java:100)
~[h2-1.4.197.jar:1.4.197]
at org.h2.command.CommandContainer.update(CommandContainer.java:102)
~[h2-1.4.197.jar:1.4.197]
at org.h2.command.Command.executeUpdate(Command.java:261)
~[h2-1.4.197.jar:1.4.197]
at org.h2.jdbc.JdbcStatement.executeInternal(JdbcStatement.java:233)
~[h2-1.4.197.jar:1.4.197]
at org.h2.jdbc.JdbcStatement.execute(JdbcStatement.java:205)
~[h2-1.4.197.jar:1.4.197]
at
org.apache.ignite.internal.processors.query.h2.H2TableEngine.createTable(H2TableEngine.java:65)
~[ignite-indexing-2.8.1.jar:2.8.1]
at
org.apache.ignite.internal.processors.query.h2.SchemaManager.createTable(SchemaManager.java:543)
~[ignite-indexing-2.8.1.jar:2.8.1]
at
org.apache.ignite.internal.processors.query.h2.SchemaManager.onCacheTypeCreated(SchemaManager.java:328)
~[ignite-indexing-2.8.1.jar:2.8.1]
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.registerType(IgniteH2Indexing.java:1822)
~[ignite-indexing-2.8.1.jar:2.8.1]
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.registerCache0(GridQueryProcessor.java:1805)
~[ignite-core-2.8.1.jar:2.8.1]
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart0(GridQueryProcessor.java:845)
~[ignite-core-2.8.1.jar:2.8.1]
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart(GridQueryProcessor.java:908)
~[ignite-core-2.8.1.jar:2.8.1]
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCacheInRecoveryMode(GridCacheProcessor.java:2323)
~[ignite-core-2.8.1.jar:2.8.1]
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.access$1700(GridCacheProcessor.java:205)
~[ignite-core-2.8.1.jar:2.8.1]
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor$CacheRecoveryLifecycle.afterBinaryMemoryRestore(GridCacheProcessor.java:5402)
~[ignite-core-2.8.1.jar:2.8.1]
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.restoreBinaryMemory(GridCacheDatabaseSharedManager.java:1075)
~[ignite-core-2.8.1.jar:2.8.1]
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.startMemoryRestore(GridCacheDatabaseSharedManager.java:2049)
~[ignite-core-2.8.1.jar:2.8.1]
at
org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1254)
[ignite-core-2.8.1.jar:2.8.1]
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2045)
[ignite-core-2.8.1.jar:2.8.1]
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1703)
[jira] [Created] (IGNITE-13329) Use checkstyle from command line check on validate phase
Maxim Muzafarov created IGNITE-13329: Summary: Use checkstyle from command line check on validate phase Key: IGNITE-13329 URL: https://issues.apache.org/jira/browse/IGNITE-13329 Project: Ignite Issue Type: Task Reporter: Maxim Muzafarov Assignee: Maxim Muzafarov Fix For: 2.10 Currently, the checkstyle plugin configured to run on the `compile` maven phase due to the custom OverrideAnnotationOnTheSameLineCheck check must be compiled. However, it will be faster to run checkstyle on `validate` maven phase check all the configured rules locally prior to pushing by running the `mvn checkstyle:check` command. [https://maven.apache.org/plugins/maven-checkstyle-plugin/usage.html] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13318) Update travis configuration to support jdk11
Maxim Muzafarov created IGNITE-13318:
Summary: Update travis configuration to support jdk11
Key: IGNITE-13318
URL: https://issues.apache.org/jira/browse/IGNITE-13318
Project: Ignite
Issue Type: Task
Reporter: Maxim Muzafarov
Assignee: Maxim Muzafarov
We should enable spark modules since compilation under jdk11 has been fixed.
{code:java}
The command "mvn test-compile
-Pall-java,licenses,lgpl,checkstyle,examples,check-licenses,!spark-2.4,!spark,!scala
-Dmaven.javadoc.skip=true -B -V" exited with 1. {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-13155) Snapshot creation throws NPE on an in-memory cluster
Maxim Muzafarov created IGNITE-13155:
Summary: Snapshot creation throws NPE on an in-memory cluster
Key: IGNITE-13155
URL: https://issues.apache.org/jira/browse/IGNITE-13155
Project: Ignite
Issue Type: Bug
Reporter: Maxim Muzafarov
Assignee: Maxim Muzafarov
Fix For: 2.9
Snapshot creation throws NPE on an in-memory cluster.
{code}
Error stack trace:
class org.apache.ignite.internal.client.GridClientException: Failed to handle
request: [req=EXE,
taskName=org.apache.ignite.internal.visor.snapshot.VisorSnapshotCreateTask,
params=[VisorTaskArgument [debug=false]], err=Failed to reduce job results due
to undeclared user exception
[task=org.apache.ignite.internal.visor.snapshot.VisorSnapshotCreateTask@4d45b97f,
err=class org.apache.ignite.IgniteException: null], trace=class
org.apache.ignite.IgniteCheckedException: Failed to reduce job results due to
undeclared user exception
[task=org.apache.ignite.internal.visor.snapshot.VisorSnapshotCreateTask@4d45b97f,
err=class org.apache.ignite.IgniteException: null]
at
org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7566)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.resolve(GridFutureAdapter.java:260)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:172)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:141)
at
org.apache.ignite.internal.processors.rest.handlers.task.GridTaskCommandHandler$2.apply(GridTaskCommandHandler.java:263)
at
org.apache.ignite.internal.processors.rest.handlers.task.GridTaskCommandHandler$2.apply(GridTaskCommandHandler.java:257)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:399)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:354)
at
org.apache.ignite.internal.processors.rest.handlers.task.GridTaskCommandHandler.handleAsyncUnsafe(GridTaskCommandHandler.java:257)
at
org.apache.ignite.internal.processors.rest.handlers.task.GridTaskCommandHandler.handleAsync(GridTaskCommandHandler.java:163)
at
org.apache.ignite.internal.processors.rest.GridRestProcessor.handleRequest(GridRestProcessor.java:325)
at
org.apache.ignite.internal.processors.rest.GridRestProcessor.access$100(GridRestProcessor.java:104)
at
org.apache.ignite.internal.processors.rest.GridRestProcessor$2.body(GridRestProcessor.java:179)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: class org.apache.ignite.compute.ComputeUserUndeclaredException:
Failed to reduce job results due to undeclared user exception
[task=org.apache.ignite.internal.visor.snapshot.VisorSnapshotCreateTask@4d45b97f,
err=class org.apache.ignite.IgniteException: null]
at
org.apache.ignite.internal.processors.task.GridTaskWorker.reduce(GridTaskWorker.java:1184)
at
org.apache.ignite.internal.processors.task.GridTaskWorker.onResponse(GridTaskWorker.java:974)
at
org.apache.ignite.internal.processors.task.GridTaskWorker.processDelayedResponses(GridTaskWorker.java:711)
at
org.apache.ignite.internal.processors.task.GridTaskWorker.body(GridTaskWorker.java:542)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at
org.apache.ignite.internal.processors.task.GridTaskProcessor.startTask(GridTaskProcessor.java:830)
at
org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:555)
at
org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:535)
at
org.apache.ignite.internal.processors.rest.handlers.task.GridTaskCommandHandler.handleAsyncUnsafe(GridTaskCommandHandler.java:227)
... 8 more
Caused by: class org.apache.ignite.IgniteException: null
at
org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:1086)
at
org.apache.ignite.internal.util.future.IgniteFutureImpl.convertException(IgniteFutureImpl.java:168)
at
org.apache.ignite.internal.util.future.IgniteFutureImpl.get(IgniteFutureImpl.java:137)
at
org.apache.ignite.internal.processors.cache.persistence.snapshot.SnapshotMXBeanImpl.createSnapshot(SnapshotMXBeanImpl.java:43)
at
org.apache.ignite.internal.visor.snapshot.VisorSnapshotCreateTask$VisorSnapshotCreateJob.run(VisorSnapshotCreateTask.java:57)
at
[jira] [Created] (IGNITE-13126) Refactor of Continuous Query buffers to reduce heap usage
Maxim Muzafarov created IGNITE-13126:
Summary: Refactor of Continuous Query buffers to reduce heap usage
Key: IGNITE-13126
URL: https://issues.apache.org/jira/browse/IGNITE-13126
Project: Ignite
Issue Type: Improvement
Reporter: Maxim Muzafarov
Assignee: Maxim Muzafarov
There are several unnecessary changes needs to be done to reduce continuous
query buffer usage:
- CacheContinuousQueryEventBuffer.part is unnecessary;
- CacheContinuousQueryEventBuffer.backupQ must be changed to
ConcurrentLinkedDeque;
- Use lambda instead for partition counter resolving instead on anonymous class
creation for CacheContinuousQueryEventBuffer;
- Batch local variables may be {{short}} type;
etc.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-13122) Snapshot task may throw NullPointerException on concurrent stop
Maxim Muzafarov created IGNITE-13122:
Summary: Snapshot task may throw NullPointerException on
concurrent stop
Key: IGNITE-13122
URL: https://issues.apache.org/jira/browse/IGNITE-13122
Project: Ignite
Issue Type: Bug
Reporter: Maxim Muzafarov
Assignee: Maxim Muzafarov
https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_Queries1/5364908
{code}
[00:03:00]W: [org.apache.ignite:ignite-indexing] [2020-06-05
00:03:00,943][ERROR][rest-#231430%gridCommandHandlerTest0%][SnapshotFutureTask]
SnapshotFutureTask cancellation failed
[00:03:00]W: [org.apache.ignite:ignite-indexing]
java.util.concurrent.ExecutionException: java.lang.NullPointerException
[00:03:00]W: [org.apache.ignite:ignite-indexing]at
java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357)
[00:03:00]W: [org.apache.ignite:ignite-indexing]at
java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1895)
[00:03:00]W: [org.apache.ignite:ignite-indexing]at
org.apache.ignite.internal.processors.cache.persistence.snapshot.SnapshotFutureTask.cancel(SnapshotFutureTask.java:636)
[00:03:00]W: [org.apache.ignite:ignite-indexing]at
org.apache.ignite.internal.processors.cache.persistence.snapshot.IgniteSnapshotManager.cancelLocalSnapshotTask(IgniteSnapshotManager.java:695)
[00:03:00]W: [org.apache.ignite:ignite-indexing]at
org.apache.ignite.internal.processors.cache.persistence.snapshot.IgniteSnapshotManager$CancelSnapshotClosure.apply(IgniteSnapshotManager.java:1367)
[00:03:00]W: [org.apache.ignite:ignite-indexing]at
org.apache.ignite.internal.processors.cache.persistence.snapshot.IgniteSnapshotManager$CancelSnapshotClosure.apply(IgniteSnapshotManager.java:1356)
[00:03:00]W: [org.apache.ignite:ignite-indexing]at
org.apache.ignite.internal.processors.closure.GridClosureProcessor$C1.execute(GridClosureProcessor.java:1752)
[00:03:00]W: [org.apache.ignite:ignite-indexing]at
org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:599)
[00:03:00]W: [org.apache.ignite:ignite-indexing]at
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:7064)
[00:03:00]W: [org.apache.ignite:ignite-indexing]at
org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:593)
[00:03:00]W: [org.apache.ignite:ignite-indexing]at
org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:522)
[00:03:00]W: [org.apache.ignite:ignite-indexing]at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
[00:03:00]W: [org.apache.ignite:ignite-indexing]at
org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1294)
[00:03:00]W: [org.apache.ignite:ignite-indexing]at
org.apache.ignite.internal.processors.task.GridTaskWorker.sendRequest(GridTaskWorker.java:1429)
[00:03:00]W: [org.apache.ignite:ignite-indexing]at
org.apache.ignite.internal.processors.task.GridTaskWorker.processMappedJobs(GridTaskWorker.java:664)
[00:03:00]W: [org.apache.ignite:ignite-indexing]at
org.apache.ignite.internal.processors.task.GridTaskWorker.body(GridTaskWorker.java:536)
[00:03:00]W: [org.apache.ignite:ignite-indexing]at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
[00:03:00]W: [org.apache.ignite:ignite-indexing]at
org.apache.ignite.internal.processors.task.GridTaskProcessor.startTask(GridTaskProcessor.java:830)
[00:03:00]W: [org.apache.ignite:ignite-indexing]at
org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:498)
[00:03:00]W: [org.apache.ignite:ignite-indexing]at
org.apache.ignite.internal.processors.closure.GridClosureProcessor.broadcast(GridClosureProcessor.java:722)
[00:03:00]W: [org.apache.ignite:ignite-indexing]at
org.apache.ignite.internal.processors.cache.persistence.snapshot.IgniteSnapshotManager.cancelSnapshot(IgniteSnapshotManager.java:667)
[00:03:00]W: [org.apache.ignite:ignite-indexing]at
org.apache.ignite.internal.processors.cache.persistence.snapshot.SnapshotMXBeanImpl.cancelSnapshot(SnapshotMXBeanImpl.java:48)
[00:03:00]W: [org.apache.ignite:ignite-indexing]at
org.apache.ignite.internal.visor.snapshot.VisorSnapshotCancelTask$VisorSnapshotCancelJob.run(VisorSnapshotCancelTask.java:57)
[00:03:00]W: [org.apache.ignite:ignite-indexing]at
org.apache.ignite.internal.visor.snapshot.VisorSnapshotCancelTask$VisorSnapshotCancelJob.run(VisorSnapshotCancelTask.java:43)
[jira] [Created] (IGNITE-13108) Decrease number of clients for IgniteCache150ClientsTest
Maxim Muzafarov created IGNITE-13108:
Summary: Decrease number of clients for IgniteCache150ClientsTest
Key: IGNITE-13108
URL: https://issues.apache.org/jira/browse/IGNITE-13108
Project: Ignite
Issue Type: Bug
Reporter: Maxim Muzafarov
Assignee: Maxim Muzafarov
The number of clients for the {{IgniteCache150ClientsTest}} due to not
sufficient TeamCity resources available on agents.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-13089) Add Apache Ignite health status to README.md
Maxim Muzafarov created IGNITE-13089: Summary: Add Apache Ignite health status to README.md Key: IGNITE-13089 URL: https://issues.apache.org/jira/browse/IGNITE-13089 Project: Ignite Issue Type: Improvement Reporter: Maxim Muzafarov Assignee: Maxim Muzafarov Fix For: 2.9 It's necessary to add the Apache Ignite health status to the README.md: - Build Status [added] - Coverage Status - Maven Central GitHub release - License - Twitter Follow -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13067) AssertionError waiting response from primary for thin client
Maxim Muzafarov created IGNITE-13067:
Summary: AssertionError waiting response from primary for thin
client
Key: IGNITE-13067
URL: https://issues.apache.org/jira/browse/IGNITE-13067
Project: Ignite
Issue Type: Task
Reporter: Maxim Muzafarov
The thin client TeamCity suite fails with assertion error. Investigation and
reproducer required.
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_JavaThinClient=buildTypeStatusDiv_IgniteTests24Java8=%3Cdefault%3E
{code:java}
[00:58:49]W: [org.apache.ignite:ignite-indexing]
java.lang.AssertionError[00:58:49]W: [org.apache.ignite:ignite-indexing]
java.lang.AssertionError[00:58:49]W: [org.apache.ignite:ignite-indexing] at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.onPrimaryResponse(GridNearAtomicSingleUpdateFuture.java:246)[00:58:49]W:
[org.apache.ignite:ignite-indexing] at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.processNearAtomicUpdateResponse(GridDhtAtomicCache.java:3338)[00:58:49]W:
[org.apache.ignite:ignite-indexing] at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$500(GridDhtAtomicCache.java:141)[00:58:49]W:
[org.apache.ignite:ignite-indexing] at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$6.apply(GridDhtAtomicCache.java:292)[00:58:49]W:
[org.apache.ignite:ignite-indexing] at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$6.apply(GridDhtAtomicCache.java:287)[00:58:49]W:
[org.apache.ignite:ignite-indexing] at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1142)[00:58:49]W:
[org.apache.ignite:ignite-indexing] at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:591)[00:58:49]W:
[org.apache.ignite:ignite-indexing] at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:392)[00:58:49]W:
[org.apache.ignite:ignite-indexing] at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:318)[00:58:49]W:
[org.apache.ignite:ignite-indexing] at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:109)[00:58:49]W:
[org.apache.ignite:ignite-indexing] at
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:308)[00:58:49]W:
[org.apache.ignite:ignite-indexing] at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1847)[00:58:49]W:
[org.apache.ignite:ignite-indexing] at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1472)[00:58:49]W:
[org.apache.ignite:ignite-indexing] at
org.apache.ignite.internal.managers.communication.GridIoManager.access$5200(GridIoManager.java:229)[00:58:49]W:
[org.apache.ignite:ignite-indexing] at
org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1367)[00:58:49]W:
[org.apache.ignite:ignite-indexing] at
org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:565)[00:58:49]W:
[org.apache.ignite:ignite-indexing] at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)[00:58:49]W:
[org.apache.ignite:ignite-indexing]
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-13066) Test framework must print which tests start regardless logger configured or not
Maxim Muzafarov created IGNITE-13066:
Summary: Test framework must print which tests start regardless
logger configured or not
Key: IGNITE-13066
URL: https://issues.apache.org/jira/browse/IGNITE-13066
Project: Ignite
Issue Type: Task
Reporter: Maxim Muzafarov
Assignee: Maxim Muzafarov
For most of the TeamCity test suites logger is turned off for performance
reasons (log size can be more than a thousand MB). In case of exceptions
happened it's hard to identify which of running tests fail.
It is necessary to log which tests are started regardless of the logger
configured or not.
Example:
{code:java}
info(">>> Starting test: " + testDescription() + " <<<"); {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-13063) Bottom-up index rebuild
Maxim Muzafarov created IGNITE-13063: Summary: Bottom-up index rebuild Key: IGNITE-13063 URL: https://issues.apache.org/jira/browse/IGNITE-13063 Project: Ignite Issue Type: Improvement Reporter: Maxim Muzafarov Assignee: Maxim Muzafarov As part of [IEP-22: Direct Data Load|https://cwiki.apache.org/confluence/display/IGNITE/IEP-22%3A+Direct+Data+Load] the PoC needs to be implemented for the new algorithm of rebuilding an index. Compare the approach of the bottom-up index rebuild with the default implementation (from the root). See details in the IEP-22. h4. High-level overview We will not update PK and secondary indexes during the data load, so it is necessary to rebuild them in the end. The most efficient way to build indexes is bottom-up approach, when the lowest level of BTree is built first, and the root is build last. We will need a buffer where indexed values and respective links will be sorted in index order. If the buffer is big enough and all the data fits into it, index will be created in one hop. Otherwise it is necessary to sort indexed values in several runs using an external sort. It is necessary to let users configure sort parameters - buffer size (ideally - in bytes), and the file system path where temp files will be stored. The latter is critical - typically users would like to keep temp files on a separate disk, so that WAL and checkpoint operations are not affected. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13055) ExecutorServices must handle AssertionErrors and log uncaught exceptions
Maxim Muzafarov created IGNITE-13055:
Summary: ExecutorServices must handle AssertionErrors and log
uncaught exceptions
Key: IGNITE-13055
URL: https://issues.apache.org/jira/browse/IGNITE-13055
Project: Ignite
Issue Type: Improvement
Reporter: Maxim Muzafarov
Currently, most of ExecuterServices (e.g. {{sysExecSvc}}) handles only
OutOfMemoryException. Services must also handle AssertionErrors and log any
uncaught exceptions.
The most important list of executor services configured with OOM handler only:
- execSvc
- svcExecSvc
- sysExecSvc
- p2pExecSvc
- restExecSvc
- utilityCacheExecSvc
- affExecSvc
- qryExecSvc
See the dev-list discussion for details.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-13049) AssertionError with JmxExporterSpi on cache stop. Test testCacheConfigSingleLineOutputFormatTwoNodeManyCaches
Maxim Muzafarov created IGNITE-13049:
Summary: AssertionError with JmxExporterSpi on cache stop. Test
testCacheConfigSingleLineOutputFormatTwoNodeManyCaches
Key: IGNITE-13049
URL: https://issues.apache.org/jira/browse/IGNITE-13049
Project: Ignite
Issue Type: Test
Reporter: Maxim Muzafarov
The test throws AssertionError if {{JmxExporterSpi}} configured
{{GridCommandHandlerClusterByClassWithSSLTest#testCacheConfigSingleLineOutputFormatTwoNodeManyCaches}}.
Reproduced locally time to time.
1. Configure JmxExporterSpi for default {{getConfiguration}} method (see
{{org.apache.ignite.util.GridCommandHandlerAbstractTest#getConfiguration}})
2. Run with SSL testCacheConfigSingleLineOutputFormatTwoNodeManyCaches
{code}
[12:17:28]W: [org.apache.ignite:ignite-core] [2020-05-21
12:17:28,500][ERROR][exchange-worker-#16994%gridCommandHandlerTest0%][IgniteTestResources]
Critical system error detected. Will be handled accordingly to configured
handler [hnd=NoOpFailureHandler [super=AbstractFailureHandler
[ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED,
SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], failureCtx=FailureContext
[type=SYSTEM_WORKER_TERMINATION, err=java.lang.AssertionError]]
[12:17:28]W: [org.apache.ignite:ignite-core]
java.lang.AssertionError
[12:17:28]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.spi.metric.jmx.JmxMetricExporterSpi.unregister(JmxMetricExporterSpi.java:110)
[12:17:28]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.internal.util.IgniteUtils.notifyListeners(IgniteUtils.java:11694)
[12:17:28]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.internal.processors.metric.GridMetricManager.remove(GridMetricManager.java:393)
[12:17:28]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.internal.processors.cache.CacheGroupContext.removeIOStatistic(CacheGroupContext.java:1321)
[12:17:28]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.cleanup(GridCacheProcessor.java:513)
[12:17:28]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.stopCacheGroup(GridCacheProcessor.java:2900)
[12:17:28]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.stopCacheGroup(GridCacheProcessor.java:2888)
[12:17:28]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.processCacheStopRequestOnExchangeDone(GridCacheProcessor.java:2780)
[12:17:28]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.onExchangeDone(GridCacheProcessor.java:2877)
[12:17:28]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onDone(GridDhtPartitionsExchangeFuture.java:2404)
[12:17:28]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.finishExchangeOnCoordinator(GridDhtPartitionsExchangeFuture.java:3822)
[12:17:28]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onAllReceived(GridDhtPartitionsExchangeFuture.java:3590)
[12:17:28]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.processSingleMessage(GridDhtPartitionsExchangeFuture.java:3180)
[12:17:28]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.access$200(GridDhtPartitionsExchangeFuture.java:155)
[12:17:28]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2.apply(GridDhtPartitionsExchangeFuture.java:2967)
[12:17:28]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2.apply(GridDhtPartitionsExchangeFuture.java:2955)
[12:17:28]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:399)
[12:17:28]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:354)
[12:17:28]W: [org.apache.ignite:ignite-core]at
[jira] [Created] (IGNITE-13045) SystemWorkersBlockingTest may fail NullPointerException if MXBean not found
Maxim Muzafarov created IGNITE-13045:
Summary: SystemWorkersBlockingTest may fail NullPointerException
if MXBean not found
Key: IGNITE-13045
URL: https://issues.apache.org/jira/browse/IGNITE-13045
Project: Ignite
Issue Type: Test
Reporter: Maxim Muzafarov
The test may fail with NullPointerException during a stop.
Investigation and reproducer required.
{code}
[17:12:56] : [org.apache.ignite:ignite-core] [2020-05-20
17:12:56,374][INFO ][main][root] >>> Stopping test:
SystemWorkersBlockingTest#testBlockingWorker in 5910 ms <<<
[17:12:56]W: [org.apache.ignite:ignite-core] [2020-05-20
17:12:56,374][ERROR][tcp-disco-msg-worker-[crd]-#186%failure.SystemWorkersBlockingTest0%-#1778%failure.SystemWorkersBlockingTest0%][TestTcpDiscoverySpi]
TcpDiscoverSpi's message worker thread failed abnormally. Stopping the node in
order to prevent cluster wide instability.
[17:12:56]W: [org.apache.ignite:ignite-core]
java.lang.NullPointerException
[17:12:56]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.internal.util.IgniteUtils.dumpThread(IgniteUtils.java:1501)
[17:12:56]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.internal.worker.WorkersRegistry.onIdle(WorkersRegistry.java:232)
[17:12:56]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.internal.util.worker.GridWorker.onIdle(GridWorker.java:297)
[17:12:56]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.lambda$new$0(ServerImpl.java:2881)
[17:12:56]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorker.body(ServerImpl.java:7738)
[17:12:56]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.body(ServerImpl.java:2969)
[17:12:56] : [org.apache.ignite:ignite-core] [2020-05-20
17:12:56,374][INFO ][main][root] >>> Stopping grid
[name=failure.SystemWorkersBlockingTest0,
id=6a13078b-0050-48bd-91e1-f201e1b0]
[17:12:56]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
[17:12:56]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerThread.body(ServerImpl.java:7676)
[17:12:56]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:58)
[17:12:56]W: [org.apache.ignite:ignite-core] [2020-05-20
17:12:56,378][ERROR][tcp-disco-msg-worker-[crd]-#186%failure.SystemWorkersBlockingTest0%-#1778%failure.SystemWorkersBlockingTest0%][IgniteTestResources]
Critical system error detected. Will be handled accordingly to configured
handler [hnd=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet
[SYSTEM_CRITICAL_OPERATION_TIMEOUT]], failureCtx=FailureContext
[type=SYSTEM_WORKER_TERMINATION, err=java.lang.NullPointerException]]
[17:12:56]W: [org.apache.ignite:ignite-core]
java.lang.NullPointerException
[17:12:56]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.internal.util.IgniteUtils.dumpThread(IgniteUtils.java:1501)
[17:12:56]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.internal.worker.WorkersRegistry.onIdle(WorkersRegistry.java:232)
[17:12:56]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.internal.util.worker.GridWorker.onIdle(GridWorker.java:297)
[17:12:56]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.lambda$new$0(ServerImpl.java:2881)
[17:12:56]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorker.body(ServerImpl.java:7738)
[17:12:56]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.body(ServerImpl.java:2969)
[17:12:56]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
[17:12:56]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerThread.body(ServerImpl.java:7676)
[17:12:56]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:58)
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12982) NullPointerException on TcpCommunicationMetricsListener for some of the cases
Maxim Muzafarov created IGNITE-12982:
Summary: NullPointerException on TcpCommunicationMetricsListener
for some of the cases
Key: IGNITE-12982
URL: https://issues.apache.org/jira/browse/IGNITE-12982
Project: Ignite
Issue Type: Bug
Reporter: Maxim Muzafarov
The code block below throws an {{NullPointerException}} for some of the cases.
Investigation required.
{code}
@Override public void onMessageSent(GridNioSession ses, Message
msg) {
Object consistentId = ses.meta(CONSISTENT_ID_META);
if (consistentId != null)
metricsLsnr.onMessageSent(msg, consistentId);
}
{code}
{code}
[2020-05-04
18:12:12,991][ERROR][grid-nio-worker-tcp-comm-0-#543%snapshot.IgniteClusterSnapshotSelfTest2%][TestRecordingCommunicationSpi]
Failed to process selector key [ses=GridSelectorNioSessionImpl
[worker=DirectNioClientWorker [super=AbstractNioClientWorker [idx=0,
bytesRcvd=42, bytesSent=18, bytesRcvd0=42, bytesSent0=18, select=true,
super=GridWorker [name=grid-nio-worker-tcp-comm-0,
igniteInstanceName=snapshot.IgniteClusterSnapshotSelfTest2, finished=false,
heartbeatTs=1588605131981, hashCode=1038334332, interrupted=false,
runner=grid-nio-worker-tcp-comm-0-#543%snapshot.IgniteClusterSnapshotSelfTest2%]]],
writeBuf=java.nio.DirectByteBuffer[pos=10 lim=32768 cap=32768],
readBuf=java.nio.DirectByteBuffer[pos=0 lim=32768 cap=32768],
inRecovery=GridNioRecoveryDescriptor [acked=0, resendCnt=0, rcvCnt=0,
sentCnt=0, reserved=true, lastAck=0, nodeLeft=false, node=TcpDiscoveryNode
[id=7f78d082-6ce9-42b1-ab08-da1fde40,
consistentId=snapshot.IgniteClusterSnapshotSelfTest0, addrs=ArrayList
[127.0.0.1], sockAddrs=HashSet [/127.0.0.1:47500], discPort=47500, order=1,
intOrder=1, lastExchangeTime=1588605131971, loc=false,
ver=2.9.0#20200428-sha1:e551fa71, isClient=false], connected=true,
connectCnt=0, queueLimit=4096, reserveCnt=1, pairedConnections=false],
outRecovery=GridNioRecoveryDescriptor [acked=0, resendCnt=0, rcvCnt=0,
sentCnt=0, reserved=true, lastAck=0, nodeLeft=false, node=TcpDiscoveryNode
[id=7f78d082-6ce9-42b1-ab08-da1fde40,
consistentId=snapshot.IgniteClusterSnapshotSelfTest0, addrs=ArrayList
[127.0.0.1], sockAddrs=HashSet [/127.0.0.1:47500], discPort=47500, order=1,
intOrder=1, lastExchangeTime=1588605131971, loc=false,
ver=2.9.0#20200428-sha1:e551fa71, isClient=false], connected=true,
connectCnt=0, queueLimit=4096, reserveCnt=1, pairedConnections=false],
closeSocket=true,
outboundMessagesQueueSizeMetric=o.a.i.i.processors.metric.impl.LongAdderMetric@69a257d1,
super=GridNioSessionImpl [locAddr=/127.0.0.1:47102, rmtAddr=/127.0.0.1:50655,
createTime=1588605131981, closeTime=0, bytesSent=18, bytesRcvd=42,
bytesSent0=18, bytesRcvd0=42, sndSchedTime=1588605131981,
lastSndTime=1588605131981, lastRcvTime=1588605131981, readsPaused=false,
filterChain=FilterChain[filters=[GridNioCodecFilter
[parser=o.a.i.i.util.nio.GridDirectParser@fc19b0b, directMode=true],
GridConnectionBytesVerifyFilter], accepted=true, markedForClose=true]]]
java.lang.NullPointerException
at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi$1.onMessageSent(TcpCommunicationSpi.java:803)
at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi$1.onMessageSent(TcpCommunicationSpi.java:472)
at
org.apache.ignite.internal.util.nio.GridNioServer.onMessageWritten(GridNioServer.java:1764)
at
org.apache.ignite.internal.util.nio.GridNioServer.access$1800(GridNioServer.java:99)
at
org.apache.ignite.internal.util.nio.GridNioServer$DirectNioClientWorker.processWrite0(GridNioServer.java:1665)
at
org.apache.ignite.internal.util.nio.GridNioServer$DirectNioClientWorker.processWrite(GridNioServer.java:1365)
at
org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNioServer.java:2437)
at
org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:2201)
at
org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1842)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at java.lang.Thread.run(Thread.java:748)
[2020-05-04
18:12:12,993][ERROR][grid-nio-worker-tcp-comm-0-#543%snapshot.IgniteClusterSnapshotSelfTest2%][TestRecordingCommunicationSpi]
Closing NIO session because of unhandled exception.
class org.apache.ignite.internal.util.nio.GridNioException: null
at
org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNioServer.java:2460)
at
org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:2201)
at
[jira] [Created] (IGNITE-12981) Snapshot operation fails on exchange if coordinator left the cluster
Maxim Muzafarov created IGNITE-12981:
Summary: Snapshot operation fails on exchange if coordinator left
the cluster
Key: IGNITE-12981
URL: https://issues.apache.org/jira/browse/IGNITE-12981
Project: Ignite
Issue Type: Bug
Reporter: Maxim Muzafarov
Assignee: Maxim Muzafarov
Fix For: 2.9
Possible steps:
1. Start snapshot operation with {{SnapshotDicoveryMessage}} with triggering
pme-free.
2. Stop the coordinator node.
3. Fails on assertion (SingleMessage should not be sent).
{code}
[2020-05-03
15:05:35,548][ERROR][sys-#94%snapshot.IgniteClusterSnapshotSelfTest1%][IgniteTestResources]
Critical system error detected. Will be handled accordingly to configured
handler [hnd=NoOpFailureHandler [super=AbstractFailureHandler
[ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED,
SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], failureCtx=FailureContext
[type=CRITICAL_ERROR, err=java.lang.AssertionError:
GridDhtPartitionsExchangeFuture [firstDiscoEvt=DiscoveryCustomEvent
[customMsg=null, affTopVer=AffinityTopologyVersion [topVer=3, minorTopVer=1],
super=DiscoveryEvent [evtNode=TcpDiscoveryNode
[id=ed2e276b-79a3-4de3-925a-68d60200,
consistentId=snapshot.IgniteClusterSnapshotSelfTest0, addrs=ArrayList
[127.0.0.1], sockAddrs=HashSet [/127.0.0.1:47500], discPort=47500, order=1,
intOrder=1, lastExchangeTime=1588507532715, loc=false,
ver=2.9.0#20200503-sha1:, isClient=false], topVer=3, nodeId8=f6fa6fad,
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1588507535430]],
crd=TcpDiscoveryNode [id=ed2e276b-79a3-4de3-925a-68d60200,
consistentId=snapshot.IgniteClusterSnapshotSelfTest0, addrs=ArrayList
[127.0.0.1], sockAddrs=HashSet [/127.0.0.1:47500], discPort=47500, order=1,
intOrder=1, lastExchangeTime=1588507532715, loc=false,
ver=2.9.0#20200503-sha1:, isClient=false],
exchId=GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=3,
minorTopVer=1], discoEvt=DiscoveryCustomEvent [customMsg=null,
affTopVer=AffinityTopologyVersion [topVer=3, minorTopVer=1],
super=DiscoveryEvent [evtNode=TcpDiscoveryNode
[id=ed2e276b-79a3-4de3-925a-68d60200,
consistentId=snapshot.IgniteClusterSnapshotSelfTest0, addrs=ArrayList
[127.0.0.1], sockAddrs=HashSet [/127.0.0.1:47500], discPort=47500, order=1,
intOrder=1, lastExchangeTime=1588507532715, loc=false,
ver=2.9.0#20200503-sha1:, isClient=false], topVer=3, nodeId8=f6fa6fad,
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1588507535430]], nodeId=ed2e276b,
evt=DISCOVERY_CUSTOM_EVT], added=true, exchangeType=ALL,
initFut=GridFutureAdapter [ignoreInterrupts=false, state=DONE, res=true,
hash=1771643357], init=false, lastVer=null,
partReleaseFut=PartitionReleaseFuture [topVer=AffinityTopologyVersion
[topVer=3, minorTopVer=1], futures=[ExplicitLockReleaseFuture
[topVer=AffinityTopologyVersion [topVer=3, minorTopVer=1], futures=[]],
AtomicUpdateReleaseFuture [topVer=AffinityTopologyVersion [topVer=3,
minorTopVer=1], futures=[]], DataStreamerReleaseFuture
[topVer=AffinityTopologyVersion [topVer=3, minorTopVer=1], futures=[]],
LocalTxReleaseFuture [topVer=AffinityTopologyVersion [topVer=3, minorTopVer=1],
futures=[]], AllTxReleaseFuture [topVer=AffinityTopologyVersion [topVer=3,
minorTopVer=1], futures=[RemoteTxReleaseFuture [topVer=AffinityTopologyVersion
[topVer=3, minorTopVer=1], futures=[]], exchActions=null,
affChangeMsg=null, centralizedAff=false, forceAffReassignment=false,
exchangeLocE=null, cacheChangeFailureMsgSent=false, done=true, state=SRV,
registerCachesFuture=null, partitionsSent=false, partitionsReceived=false,
delayedLatestMsg=null, afterLsnrCompleteFut=GridFutureAdapter
[ignoreInterrupts=false, state=DONE, res=null, hash=197787912],
timeBag=o.a.i.i.util.TimeBag@1d97d94c, startTime=1365700834756,
initTime=1588507535439, rebalanced=false, evtLatch=0, remaining=HashSet
[ed2e276b-79a3-4de3-925a-68d60200], mergedJoinExchMsgs=null,
awaitMergedMsgs=0, super=GridFutureAdapter [ignoreInterrupts=false, state=DONE,
res=AffinityTopologyVersion [topVer=3, minorTopVer=1], hash=530592354
java.lang.AssertionError: GridDhtPartitionsExchangeFuture
[firstDiscoEvt=DiscoveryCustomEvent [customMsg=null,
affTopVer=AffinityTopologyVersion [topVer=3, minorTopVer=1],
super=DiscoveryEvent [evtNode=TcpDiscoveryNode
[id=ed2e276b-79a3-4de3-925a-68d60200,
consistentId=snapshot.IgniteClusterSnapshotSelfTest0, addrs=ArrayList
[127.0.0.1], sockAddrs=HashSet [/127.0.0.1:47500], discPort=47500, order=1,
intOrder=1, lastExchangeTime=1588507532715, loc=false,
ver=2.9.0#20200503-sha1:, isClient=false], topVer=3, nodeId8=f6fa6fad,
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1588507535430]],
crd=TcpDiscoveryNode [id=ed2e276b-79a3-4de3-925a-68d60200,
consistentId=snapshot.IgniteClusterSnapshotSelfTest0, addrs=ArrayList
[127.0.0.1], sockAddrs=HashSet
[jira] [Created] (IGNITE-12978) Cancel snapshot command
Maxim Muzafarov created IGNITE-12978: Summary: Cancel snapshot command Key: IGNITE-12978 URL: https://issues.apache.org/jira/browse/IGNITE-12978 Project: Ignite Issue Type: Improvement Reporter: Maxim Muzafarov Assignee: Maxim Muzafarov Fix For: 2.9 Add the ability to cancel snapshot operation through JMX and command line. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12971) Create snapshot view to show available cluster snapshots
Maxim Muzafarov created IGNITE-12971: Summary: Create snapshot view to show available cluster snapshots Key: IGNITE-12971 URL: https://issues.apache.org/jira/browse/IGNITE-12971 Project: Ignite Issue Type: Improvement Reporter: Maxim Muzafarov Users must be able to see available information about cluster snapshots through the view: 1. Snapshot name 2. Affected BLT nodes 3. List of cache groups in a snapshot 4. Partition states (e.g. the snapshot has LOST partitions) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12970) Cluster snapshot must support encryption caches
Maxim Muzafarov created IGNITE-12970:
Summary: Cluster snapshot must support encryption caches
Key: IGNITE-12970
URL: https://issues.apache.org/jira/browse/IGNITE-12970
Project: Ignite
Issue Type: Improvement
Reporter: Maxim Muzafarov
Currently, a cluster snapshot operation not supports including encrypted caches
to the snapshot. The {{EncryptionFileIO}} must be added for coping cache
partition files and its deltas (see IEP-43 for details about copying cache
partition files).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12968) Create cluster snapshot documentation pages
Maxim Muzafarov created IGNITE-12968: Summary: Create cluster snapshot documentation pages Key: IGNITE-12968 URL: https://issues.apache.org/jira/browse/IGNITE-12968 Project: Ignite Issue Type: Improvement Components: documentation Reporter: Maxim Muzafarov Assignee: Maxim Muzafarov Fix For: 2.9 Add the following to the Apache Ignite documentation: 1. How to create a cluster snapshot (describe API, limitations) 2. How to configure a destination directory 3. Manual steps for a snapshot restore 4. Examples -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12967) Start cluster snapshot from client node
Maxim Muzafarov created IGNITE-12967: Summary: Start cluster snapshot from client node Key: IGNITE-12967 URL: https://issues.apache.org/jira/browse/IGNITE-12967 Project: Ignite Issue Type: Improvement Reporter: Maxim Muzafarov Assignee: Maxim Muzafarov Fix For: 2.9 Users should be able to start cluster snapshots from client node by sending compute requests on server node. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12963) Request snapshot from remote node
Maxim Muzafarov created IGNITE-12963: Summary: Request snapshot from remote node Key: IGNITE-12963 URL: https://issues.apache.org/jira/browse/IGNITE-12963 Project: Ignite Issue Type: Sub-task Reporter: Maxim Muzafarov Assignee: Maxim Muzafarov -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12961) Start snapshot operation via control.sh
Maxim Muzafarov created IGNITE-12961: Summary: Start snapshot operation via control.sh Key: IGNITE-12961 URL: https://issues.apache.org/jira/browse/IGNITE-12961 Project: Ignite Issue Type: Task Reporter: Maxim Muzafarov Assignee: Maxim Muzafarov Fix For: 2.9 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12954) Remove checkstyle suppression for XGBoostModelLexer,XGBoostModelParser
Maxim Muzafarov created IGNITE-12954:
Summary: Remove checkstyle suppression for
XGBoostModelLexer,XGBoostModelParser
Key: IGNITE-12954
URL: https://issues.apache.org/jira/browse/IGNITE-12954
Project: Ignite
Issue Type: Task
Reporter: Maxim Muzafarov
Assignee: Maxim Muzafarov
Currently, there are some redundant suppressions for the checkstyle rules which
can be removed:
{code}
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12939) Add WhitespaceAround support checkstyle rule
Maxim Muzafarov created IGNITE-12939:
Summary: Add WhitespaceAround support checkstyle rule
Key: IGNITE-12939
URL: https://issues.apache.org/jira/browse/IGNITE-12939
Project: Ignite
Issue Type: Task
Reporter: Maxim Muzafarov
Assignee: Maxim Muzafarov
Fix For: 2.9
White spaces must be checked according to java naming conventions.
Add the appropriate checkstyle rule.
{code}
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12937) Create pull-request template for the github repo
Maxim Muzafarov created IGNITE-12937:
Summary: Create pull-request template for the github repo
Key: IGNITE-12937
URL: https://issues.apache.org/jira/browse/IGNITE-12937
Project: Ignite
Issue Type: Task
Reporter: Maxim Muzafarov
Create {{.github/pull_request_template.md}} to allow users to have a
pull-request all usefull information while contributing to the Apache Ignite.
Example:
[ ] Coding Guidelines are followed
[ ] TeamCity build passes
[ ] JIRA ticked is in Patch Available state, a review has been requested in
comments
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12930) DistributedProcess fails node if unable to send single message to coordinator
Maxim Muzafarov created IGNITE-12930:
Summary: DistributedProcess fails node if unable to send single
message to coordinator
Key: IGNITE-12930
URL: https://issues.apache.org/jira/browse/IGNITE-12930
Project: Ignite
Issue Type: Task
Reporter: Maxim Muzafarov
The
[DistributedProcess|https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/util/distributed/DistributedProcess.java]
fails the local node ({{FailureHandler}} CRITICAL_ERROR thrown) if unable to
send a message to the coordinator (e.g. the coordinator fails right before the
single message is sent).
{code:java}
try {
ctx.io().sendToGridTopic(p.crdId,
GridTopic.TOPIC_DISTRIBUTED_PROCESS, singleMsg, SYSTEM_POOL);
}
catch (IgniteCheckedException e) {
log.error("Unable to send message to coordinator.", e);
ctx.failure().process(new FailureContext(CRITICAL_ERROR,
new Exception("Unable to send message to coordinator.",
e)));
}
{code}
h4. Expected behaviour
If the {{ClusterTopologyCheckedException}} occurs need to wait for the
NODE_LEFT event of the coordinator node and re-init the distributed process
future.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12929) Incorrect setClientMode calls instead of startClientGrid
Maxim Muzafarov created IGNITE-12929:
Summary: Incorrect setClientMode calls instead of startClientGrid
Key: IGNITE-12929
URL: https://issues.apache.org/jira/browse/IGNITE-12929
Project: Ignite
Issue Type: Task
Reporter: Maxim Muzafarov
There were some places left after IGNITE-12493 merge where {{setClientMode}}
instead of {{startClientGrid}}.
Need to be fixed.
Examples:
https://github.com/apache/ignite/blob/master/modules/core/src/test/java/org/apache/ignite/internal/processors/database/IgniteDbAbstractTest.java#L168
https://github.com/apache/ignite/blob/master/modules/indexing/src/test/java/org/apache/ignite/internal/processors/cache/SqlCacheStartStopTest.java#L81
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12916) Add travis-ci configuration to run builds
Maxim Muzafarov created IGNITE-12916:
Summary: Add travis-ci configuration to run builds
Key: IGNITE-12916
URL: https://issues.apache.org/jira/browse/IGNITE-12916
Project: Ignite
Issue Type: Task
Reporter: Maxim Muzafarov
Assignee: Maxim Muzafarov
{{.travis.yml}} configuration for running builds over Travis-ci
(https://travis-ci.org/github/apache/ignite) needs to be added for builds.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12893) Add support for the SimplifyBooleanExpression rule to checkstyle
Maxim Muzafarov created IGNITE-12893:
Summary: Add support for the SimplifyBooleanExpression rule to
checkstyle
Key: IGNITE-12893
URL: https://issues.apache.org/jira/browse/IGNITE-12893
Project: Ignite
Issue Type: Task
Reporter: Maxim Muzafarov
Assignee: Maxim Muzafarov
The rule must be supported by the checkstyle according to Ignite coding
conventions [1].
{code}
{code}
https://checkstyle.sourceforge.io/config_coding.html#SimplifyBooleanExpression
https://cwiki.apache.org/confluence/display/IGNITE/Coding+Guidelines#CodingGuidelines-Useof%22!%22insteadofexplicit%22==true%22and%22==false%22
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12888) Add support for ConstantName to checkstyle rules
Maxim Muzafarov created IGNITE-12888: Summary: Add support for ConstantName to checkstyle rules Key: IGNITE-12888 URL: https://issues.apache.org/jira/browse/IGNITE-12888 Project: Ignite Issue Type: Task Reporter: Maxim Muzafarov Assignee: Maxim Muzafarov Add a new rule to checkstyle according to Apache Ignite naming conventions. https://cwiki.apache.org/confluence/display/IGNITE/Coding+Guidelines#CodingGuidelines-Naming -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12796) pendingTree of the persisted cache data store must be marked as destroyed
Maxim Muzafarov created IGNITE-12796:
Summary: pendingTree of the persisted cache data store must be
marked as destroyed
Key: IGNITE-12796
URL: https://issues.apache.org/jira/browse/IGNITE-12796
Project: Ignite
Issue Type: Task
Reporter: Maxim Muzafarov
{{pendingTree}} of the persisted cache data store ({{GridCacheDataStore}} may
fail to find rows during concurrent cache stop operation or {{purgeExpired}}
with simultaneously partition eviction occurred (e.g. moved to another node on
a new node joins).
Probably we should mark {{pendingTree}} as destroyed
{{BPlusTree#markDestroyed}} the same way as it happens for
{{IgniteCacheOffheapManagerImpl.CacheDataStoreImpl#dataTree}}.
Investigation and reproducer required.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12765) Slim binary release and docker image for Apache Ignite
Maxim Muzafarov created IGNITE-12765:
Summary: Slim binary release and docker image for Apache Ignite
Key: IGNITE-12765
URL: https://issues.apache.org/jira/browse/IGNITE-12765
Project: Ignite
Issue Type: Task
Reporter: Maxim Muzafarov
Fix For: 2.8.1
1. Prepare Apache Ignite "slim" distribution (example:
https://github.com/apache/ignite/tree/ignite-slim)
2. Update configuration and check Apache Ignite RELEASE TeamCity Suite
according to a new additional package distribution.
See - discussion on dev-list
http://apache-ignite-developers.2346864.n4.nabble.com/Slim-binary-release-and-docker-image-for-Apache-Ignite-td45110.html
{code}
libs:
core/shmem/jcache
ignite-indexing
ignite-spring
libs/optional:
ignite-compress
ignite-kubernetes
ignite-log4j2
ignite-rest-http
ignite-spring-data_2.2
ignite-jta ignite-log4j ignite-opencensus ignite-slf4j
ignite-urideploy
* ignite-core
* ignite-indexing
* ignite-rest-http
* ignite-spring
* ignite-log4j
* ignite-log4j2
* ignite-slf4j
* ignite-urideploy
* ignite-kubernetes
* ignite-opencensus
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12733) File transmission must notify listeners when transmission ends and resources released
Maxim Muzafarov created IGNITE-12733:
Summary: File transmission must notify listeners when transmission
ends and resources released
Key: IGNITE-12733
URL: https://issues.apache.org/jira/browse/IGNITE-12733
Project: Ignite
Issue Type: Bug
Reporter: Maxim Muzafarov
Assignee: Maxim Muzafarov
Currently, there is no such ability to notify a users receiver listener
({{TransmissionHandler}}) when a file transmission is fully ended.
So, in case of the next transmission request will be fired right after the
current on we may get an error -- "Error has been sent back to a remote node.
The receiver holds the local topic" due to channel resources are not released
yet.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12707) Update release branch version for 2.8
Maxim Muzafarov created IGNITE-12707: Summary: Update release branch version for 2.8 Key: IGNITE-12707 URL: https://issues.apache.org/jira/browse/IGNITE-12707 Project: Ignite Issue Type: Task Reporter: Maxim Muzafarov Assignee: Maxim Muzafarov Fix For: 2.8 The following need to be done: 1. Update pom.xml version to 2.8.0 2. Update Linux package version to 2.8.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12690) Remove deprecation from DataRegionMetrics and mark ReadOnlyMetricRegistry with IgniteExperimental
Maxim Muzafarov created IGNITE-12690: Summary: Remove deprecation from DataRegionMetrics and mark ReadOnlyMetricRegistry with IgniteExperimental Key: IGNITE-12690 URL: https://issues.apache.org/jira/browse/IGNITE-12690 Project: Ignite Issue Type: Task Reporter: Maxim Muzafarov Assignee: Maxim Muzafarov Fix For: 2.8 According to the vote [1] results and the discussion thread [2] the following needs to be done: 1. Remove @deprecated from DataRegionMetric 2. Mark new metrics API with @IgniteExperimental [1] http://apache-ignite-developers.2346864.n4.nabble.com/RESULT-VOTE-Allow-or-prohibit-a-joint-use-of-deprecated-and-IgniteExperimental-td45863.html [2] http://apache-ignite-developers.2346864.n4.nabble.com/Internal-classes-are-exposed-in-public-API-td45146.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12669) Remove not used rebalanceDelay from production code
Maxim Muzafarov created IGNITE-12669:
Summary: Remove not used rebalanceDelay from production code
Key: IGNITE-12669
URL: https://issues.apache.org/jira/browse/IGNITE-12669
Project: Ignite
Issue Type: Task
Reporter: Maxim Muzafarov
Currently, we've got rebalanceDelay property which is not used (in tests too)
and persists in production code.
Must be removed.
{code}
/** Delay before rebalancing code is start executing after exchange
completion. For tests only. */
private volatile long rebalanceDelay;
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12650) Mark MVCC with @IgniteExperimental annotation
Maxim Muzafarov created IGNITE-12650: Summary: Mark MVCC with @IgniteExperimental annotation Key: IGNITE-12650 URL: https://issues.apache.org/jira/browse/IGNITE-12650 Project: Ignite Issue Type: Task Reporter: Maxim Muzafarov MVCC should be marked with the @IgniteExperimental annotation. * Beta version of Transactional SQL and MVCC * In Ignite v2.7, Transactional SQL and MVCC are released as beta versions to allow users to experiment and share feedback. * This version of Transactional SQL and MVCC should not be considered for production. [1] https://apacheignite.readme.io/docs/multiversion-concurrency-control -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12626) Add RELEASE_NOTES about 2.8
Maxim Muzafarov created IGNITE-12626: Summary: Add RELEASE_NOTES about 2.8 Key: IGNITE-12626 URL: https://issues.apache.org/jira/browse/IGNITE-12626 Project: Ignite Issue Type: Task Reporter: Maxim Muzafarov Assignee: Maxim Muzafarov Fix For: 2.8 Update RELEASE_NOTES for the 2.8 release -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12539) JAVADOC broken for hibernate 5.3 module
Maxim Muzafarov created IGNITE-12539:
Summary: JAVADOC broken for hibernate 5.3 module
Key: IGNITE-12539
URL: https://issues.apache.org/jira/browse/IGNITE-12539
Project: Ignite
Issue Type: Task
Reporter: Maxim Muzafarov
Assignee: Maxim Muzafarov
Fix For: 2.8
{code}
[17:02:15]W: [Step 2/2] [ERROR] Failed to execute goal
org.apache.maven.plugins:maven-antrun-plugin:1.7:run
(javadoc-postprocessing-new) on project apache-ignite: An Ant BuildException
has occured: Execution failed due to: Class doesn't have description in file:
/opt/buildagent/work/7bc1c54bc719b67c/target/javadoc/core/org/apache/ignite/cache/hibernate/IgniteCollectionDataAccess.html
[17:02:15]W: [Step 2/2] [ERROR] Class doesn't have description in file:
/opt/buildagent/work/7bc1c54bc719b67c/target/javadoc/core/org/apache/ignite/cache/hibernate/IgniteDomainDataRegion.html
[17:02:15]W: [Step 2/2] [ERROR] Class doesn't have description in file:
/opt/buildagent/work/7bc1c54bc719b67c/target/javadoc/core/org/apache/ignite/cache/hibernate/IgniteEntityDataAccess.html
[17:02:15]W: [Step 2/2] [ERROR] Class doesn't have description in file:
/opt/buildagent/work/7bc1c54bc719b67c/target/javadoc/core/org/apache/ignite/cache/hibernate/IgniteNaturalIdDataAccess.html
[17:02:15]W: [Step 2/2] [ERROR]
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12528) JAVADOC build fails when appropriate profile is enabled
Maxim Muzafarov created IGNITE-12528:
Summary: JAVADOC build fails when appropriate profile is enabled
Key: IGNITE-12528
URL: https://issues.apache.org/jira/browse/IGNITE-12528
Project: Ignite
Issue Type: Task
Reporter: Maxim Muzafarov
Command: {{mvn initialize -Pjavadoc}} fails:
{code}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-antrun-plugin:1.7:run
(javadoc-postprocessing-new) on project apache-ignite: An Ant BuildException
has occured: Execution failed due to: 'Other Packages' section should not be
present, all packages should have corresponding documentation groups:
C:\Users\Mmuza\IdeaProjects\ignite\target\javadoc\core/overview-summary.html;Please
add packages description to parent/pom.xml into (maven-javadoc-plugin)
/ /
[ERROR]
[ERROR] around Ant part ..
@ 11:51 in C:\Users\Mmuza\IdeaProjects\ignite\target\antrun\build-main.xml
[ERROR] -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-antrun-plugin:1.7:run
(javadoc-postprocessing-new) on project apache-ignite: An Ant BuildException
has occured: Execution failed due to: 'Other Packages' section should not be
present, all packages should have corresponding documentation groups:
C:\Users\Mmuza\IdeaProjects\ignite\target\javadoc\core/overview-summary.html;Please
add packages description to parent/pom.xml into (maven-javadoc-plugin)
/ /
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12521) Change copyrights to 2020
Maxim Muzafarov created IGNITE-12521: Summary: Change copyrights to 2020 Key: IGNITE-12521 URL: https://issues.apache.org/jira/browse/IGNITE-12521 Project: Ignite Issue Type: Task Reporter: Maxim Muzafarov Assignee: Maxim Muzafarov Fix For: 2.8 The `2019 Copyright Apache Software Foundation` needs to be changed to the new 2020 year. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12495) Make historical rebalance wokring per-partition level
Maxim Muzafarov created IGNITE-12495: Summary: Make historical rebalance wokring per-partition level Key: IGNITE-12495 URL: https://issues.apache.org/jira/browse/IGNITE-12495 Project: Ignite Issue Type: Sub-task Reporter: Maxim Muzafarov Currently, historical rebalance run after all cache group partition files have been preloaded and inited. To make file-rebalance faster historical rebalance can be started on per-partition level right after each cache group partition file loaded and inited. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12494) Design an cluster traversal algorithm to preload cache groups as faster as possible
Maxim Muzafarov created IGNITE-12494: Summary: Design an cluster traversal algorithm to preload cache groups as faster as possible Key: IGNITE-12494 URL: https://issues.apache.org/jira/browse/IGNITE-12494 Project: Ignite Issue Type: Task Reporter: Maxim Muzafarov Currently, we are preloading cache group partitions sequentially bypassing each cluster node. To preload each cache group faster we need to design a new cluster nodes traversal algorithm which preload, for instance, a large cache groups first. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12436) ignite.properties must be handled by maven update-version profile
Maxim Muzafarov created IGNITE-12436:
Summary: ignite.properties must be handled by maven update-version
profile
Key: IGNITE-12436
URL: https://issues.apache.org/jira/browse/IGNITE-12436
Project: Ignite
Issue Type: Bug
Reporter: Maxim Muzafarov
Assignee: Maxim Muzafarov
Currently {{ignite\modules\core\src\main\resources\ignite.properties}} is
manually handled to change the actually used {{ignite.version}} (e.g. a new
release version occurred)
This should be done automatically when the update-version profile is active.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12421) Update pom depencencies to 2.9.0-SNAPSHOT version
Maxim Muzafarov created IGNITE-12421:
Summary: Update pom depencencies to 2.9.0-SNAPSHOT version
Key: IGNITE-12421
URL: https://issues.apache.org/jira/browse/IGNITE-12421
Project: Ignite
Issue Type: Bug
Reporter: Maxim Muzafarov
Assignee: Maxim Muzafarov
Since the {{ignite-2.8}} the release branch created all version dependencies
must be updated to {{2.9.0-SNAPSHOT}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12373) Handshake timeout while opening a channel connection from different nodes
Maxim Muzafarov created IGNITE-12373:
Summary: Handshake timeout while opening a channel connection from
different nodes
Key: IGNITE-12373
URL: https://issues.apache.org/jira/browse/IGNITE-12373
Project: Ignite
Issue Type: Bug
Reporter: Maxim Muzafarov
Assignee: Maxim Muzafarov
Steps to reproduce,
1. Open transmission sender on the node1
2. Open transmission sender on the node2
3. Simultaneously send a file from node1 to node2 and from node2 to node1.
{code:java}
[2019-11-14
22:37:41,685][ERROR][async-runnable-runner-1][GridIoManagerFileTransmissionSelfTest$BlockingOpenChannelCommunicationSpi]
Failed to read from channel:
java.nio.channels.AsynchronousCloseException
at
java.nio.channels.spi.AbstractInterruptibleChannel.end(AbstractInterruptibleChannel.java:205)
at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:407)
at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.safeTcpHandshake(TcpCommunicationSpi.java:3999)
at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createNioSession(TcpCommunicationSpi.java:3536)
at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.openChannel(TcpCommunicationSpi.java:4384)
at
org.apache.ignite.internal.managers.communication.GridIoManagerFileTransmissionSelfTest$BlockingOpenChannelCommunicationSpi.openChannel(GridIoManagerFileTransmissionSelfTest.java:1068)
at
org.apache.ignite.internal.managers.communication.GridIoManager.openChannel(GridIoManager.java:1959)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$6500(GridIoManager.java:229)
at
org.apache.ignite.internal.managers.communication.GridIoManager$TransmissionSender.connect(GridIoManager.java:3145)
at
org.apache.ignite.internal.managers.communication.GridIoManager$TransmissionSender.send(GridIoManager.java:3244)
at
org.apache.ignite.internal.managers.communication.GridIoManager$TransmissionSender.send(GridIoManager.java:3194)
at
org.apache.ignite.internal.managers.communication.GridIoManagerFileTransmissionSelfTest.lambda$testFileHandlerCrossConnections$1(GridIoManagerFileTransmissionSelfTest.java:314)
at
org.apache.ignite.testframework.GridTestUtils.lambda$runAsync$1(GridTestUtils.java:1039)
at
org.apache.ignite.testframework.GridTestUtils.lambda$runAsync$2(GridTestUtils.java:1095)
at
org.apache.ignite.testframework.GridTestUtils$7.call(GridTestUtils.java:1416)
at
org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:84)
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12366) Gracefullly iterrupt the file transmission session
Maxim Muzafarov created IGNITE-12366: Summary: Gracefullly iterrupt the file transmission session Key: IGNITE-12366 URL: https://issues.apache.org/jira/browse/IGNITE-12366 Project: Ignite Issue Type: Task Reporter: Maxim Muzafarov Assignee: Maxim Muzafarov Currently, if the node-receiver decides to interrupt a file transmission it must throw a runtime exception which looks odd due to exception logging Since cancellation a file transmission is a regular operation errors in the log will confuse the user too much. The node-receiver must have an ability to gracefully stop a file transmission locally and on the node-sender. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12289) TestBinaryContext should be removed from production code
Maxim Muzafarov created IGNITE-12289: Summary: TestBinaryContext should be removed from production code Key: IGNITE-12289 URL: https://issues.apache.org/jira/browse/IGNITE-12289 Project: Ignite Issue Type: Task Reporter: Maxim Muzafarov Fix For: 2.9 Currently, `TestBinaryContext` is used only for testing. It is not the right way to keep such classes in production code since it can lead to unpredictable issues. Also, making inner static classes `public` violates coding best practices. `TestBinaryContext` should be moved to the test environment and used only there. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12287) Checkstyle violation unused imports JavaEmbeddedIgniteRDDWithLocalStoreSelfTest
Maxim Muzafarov created IGNITE-12287:
Summary: Checkstyle violation unused imports
JavaEmbeddedIgniteRDDWithLocalStoreSelfTest
Key: IGNITE-12287
URL: https://issues.apache.org/jira/browse/IGNITE-12287
Project: Ignite
Issue Type: Task
Reporter: Maxim Muzafarov
Assignee: Maxim Muzafarov
Fix For: 2.8
Fail to build the Apache Ignite master branch with enabled checkstyle. The
build fails on JavaEmbeddedIgniteRDDWithLocalStoreSelfTest.
{code}
[15:54:03] [Step 3/4] [ERROR]
/opt/buildagent/work/7bc1c54bc719b67c/modules/spark/src/test/java/org/apache/ignite/spark/JavaEmbeddedIgniteRDDWithLocalStoreSelfTest.java:20:8:
Unused import - java.util.List. [UnusedImports]
[15:54:03] [Step 3/4] [ERROR]
/opt/buildagent/work/7bc1c54bc719b67c/modules/spark/src/test/java/org/apache/ignite/spark/JavaEmbeddedIgniteRDDWithLocalStoreSelfTest.java:34:8:
Unused import - org.apache.spark.api.java.JavaRDD. [UnusedImports]
[15:54:03] [Step 3/4] [ERROR]
/opt/buildagent/work/7bc1c54bc719b67c/modules/spark/src/test/java/org/apache/ignite/spark/JavaEmbeddedIgniteRDDWithLocalStoreSelfTest.java:36:8:
Unused import - org.apache.spark.api.java.function.Function. [UnusedImports]
[15:54:03] [Step 3/4] [ERROR]
/opt/buildagent/work/7bc1c54bc719b67c/modules/spark/src/test/java/org/apache/ignite/spark/JavaEmbeddedIgniteRDDWithLocalStoreSelfTest.java:37:8:
Unused import - org.apache.spark.api.java.function.Function2. [UnusedImports]
[15:54:03] [Step 3/4] [ERROR]
/opt/buildagent/work/7bc1c54bc719b67c/modules/spark/src/test/java/org/apache/ignite/spark/JavaEmbeddedIgniteRDDWithLocalStoreSelfTest.java:39:8:
Unused import - org.apache.spark.sql.Column. [UnusedImports]
[15:54:03] [Step 3/4] [ERROR]
/opt/buildagent/work/7bc1c54bc719b67c/modules/spark/src/test/java/org/apache/ignite/spark/JavaEmbeddedIgniteRDDWithLocalStoreSelfTest.java:40:8:
Unused import - org.apache.spark.sql.Dataset. [UnusedImports]
[15:54:03] [Step 3/4] [ERROR]
/opt/buildagent/work/7bc1c54bc719b67c/modules/spark/src/test/java/org/apache/ignite/spark/JavaEmbeddedIgniteRDDWithLocalStoreSelfTest.java:41:8:
Unused import - org.apache.spark.sql.Row. [UnusedImports]
[15:54:03] [Step 3/4] Audit done.
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12196) [Phase-4] Deprecate old rebalancing cache metrics
Maxim Muzafarov created IGNITE-12196: Summary: [Phase-4] Deprecate old rebalancing cache metrics Key: IGNITE-12196 URL: https://issues.apache.org/jira/browse/IGNITE-12196 Project: Ignite Issue Type: Sub-task Reporter: Maxim Muzafarov We need to mark rebalancing CacheMetrics deprecated and remove them from metrics a newly introduced metrics framework IGNITE-11961. Such cache metrics should be implemented in an old-fashion way (like they were before the metrics framework added) to keep backwards compatibility. Removed it Apache Ignite 3.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12195) [Phase-3] Rebalance HitRate metrics
Maxim Muzafarov created IGNITE-12195: Summary: [Phase-3] Rebalance HitRate metrics Key: IGNITE-12195 URL: https://issues.apache.org/jira/browse/IGNITE-12195 Project: Ignite Issue Type: Sub-task Reporter: Maxim Muzafarov Currently, HitRate metric can consume a lot of CPU resources. We need to investigate such performance issues and disable these metrics by default. * rebalancingKeysRate HitRate metric * rebalancingBytesRate HitRate metric -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12194) [Phase-2] Calculate expected rebalancing cache group keys
Maxim Muzafarov created IGNITE-12194: Summary: [Phase-2] Calculate expected rebalancing cache group keys Key: IGNITE-12194 URL: https://issues.apache.org/jira/browse/IGNITE-12194 Project: Ignite Issue Type: Sub-task Reporter: Maxim Muzafarov We need to implement expected to be rebalanced cache group keys and total bytes. Currently, 'estimatedKeysCount' cache metric returns '-1' for some of the cases (see comments IGNITE-11330). * rebalancingExpectedKeys long metric * rebalancingExpectedBytes long metric * rebalancingEvictedPartitionsLeft long metric -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12193) [Phase-1] Rebalancing cache group keys metric counters
Maxim Muzafarov created IGNITE-12193: Summary: [Phase-1] Rebalancing cache group keys metric counters Key: IGNITE-12193 URL: https://issues.apache.org/jira/browse/IGNITE-12193 Project: Ignite Issue Type: Sub-task Reporter: Maxim Muzafarov Implement metrics counters related to the cache group: * rebalancingPartitionsLeft long metric * rebalancingReceivedKeys long metric * rebalancingReceivedBytes long metric * rebalancingStartTime long metric * rebalancingFinishTime long metric -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12181) Rebalance hangs on BLT change on cluster with in-memory regions
Maxim Muzafarov created IGNITE-12181: Summary: Rebalance hangs on BLT change on cluster with in-memory regions Key: IGNITE-12181 URL: https://issues.apache.org/jira/browse/IGNITE-12181 Project: Ignite Issue Type: Bug Reporter: Maxim Muzafarov Assignee: Maxim Muzafarov Fix For: 2.8 Attachments: RebalanceInMemoryWithPersistence.java # Configured BLT on the _node-1_ (cluster activated) # Configured in-memory region with a single cache on the _node-1_ # A new _node-2_ join to the cluster # Set new BLT based on two nodes # Rebalance hangs -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (IGNITE-12100) Checkstyle must support TodoComment rule
Maxim Muzafarov created IGNITE-12100: Summary: Checkstyle must support TodoComment rule Key: IGNITE-12100 URL: https://issues.apache.org/jira/browse/IGNITE-12100 Project: Ignite Issue Type: Improvement Reporter: Maxim Muzafarov We should force Apache Ignite source code of using TODO comments only the specific format [2]. [1] https://checkstyle.org/config_misc.html#TodoComment [2] https://cwiki.apache.org/confluence/display/IGNITE/Coding+Guidelines#CodingGuidelines-TODOs -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (IGNITE-12098) Provide benchmark for the rebalance procedure
Maxim Muzafarov created IGNITE-12098: Summary: Provide benchmark for the rebalance procedure Key: IGNITE-12098 URL: https://issues.apache.org/jira/browse/IGNITE-12098 Project: Ignite Issue Type: Sub-task Reporter: Maxim Muzafarov Assignee: Maxim Muzafarov To correctly evaluate the proposed improvement additional test-cases need to be developed. The goal is the evaluation of rebalancing procedure speed on a stable test environment with fixed configuration parameters. To be done: * list of test-cases to check * benchmark scripts -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (IGNITE-12069) Create cache shared preloader
Maxim Muzafarov created IGNITE-12069:
Summary: Create cache shared preloader
Key: IGNITE-12069
URL: https://issues.apache.org/jira/browse/IGNITE-12069
Project: Ignite
Issue Type: Sub-task
Reporter: Maxim Muzafarov
Assignee: Pavel Pereslegin
{{CacheSharedPreloader}} must do the following:
# build the map of partitions and corresponding supplier nodes from which
partitions will be loaded;
# switching cache data storage to {{no-op}} and back to original (HWM must be
fixed here for the needs of historical rebalance) under the checkpoint and keep
the partition update counter for each partition;
# run async the eviction indexes for the list of collected partitions (API must
be provided by IGNITE-11075);
# Send a request message to each node one by one with the list of partitions to
load;
# Listening for the transmission handler to receive files;
# Run rebuild indexes async over the receiving partitions (API must be provided
by IGNITE-11075);
# Run historical rebalance from LWM to HWM collected above (LWM can be read
from received file meta page)
NOTE. Check the following things:
# Rebalancing of MVCC cache groups;
# How LWM and HWM will be set for the historical rebalance;
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Created] (IGNITE-12066) Add transmission chunk size to IgniteConfiguration
Maxim Muzafarov created IGNITE-12066:
Summary: Add transmission chunk size to IgniteConfiguration
Key: IGNITE-12066
URL: https://issues.apache.org/jira/browse/IGNITE-12066
Project: Ignite
Issue Type: Improvement
Reporter: Maxim Muzafarov
Currently, the {{DFLT_CHUNK_SIZE_BYTES}} constant value is used to set the size
of chunks with data sending to the remote node during the file transmission.
This value must be set from IgniteConfiguration.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Created] (IGNITE-12065) File transmission speed limit
Maxim Muzafarov created IGNITE-12065: Summary: File transmission speed limit Key: IGNITE-12065 URL: https://issues.apache.org/jira/browse/IGNITE-12065 Project: Ignite Issue Type: Improvement Reporter: Maxim Muzafarov We need to limit transmission speed since the system resources can be exhausted. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (IGNITE-12064) Check licence headers by checkstyle plugin
Maxim Muzafarov created IGNITE-12064:
Summary: Check licence headers by checkstyle plugin
Key: IGNITE-12064
URL: https://issues.apache.org/jira/browse/IGNITE-12064
Project: Ignite
Issue Type: Improvement
Reporter: Maxim Muzafarov
Currently, the {{apache-rat-plugin}} is used to check that source files contain
the specific license header. The suite {{[Licenses Headers]}} is configured on
TC to do so.
It is possible to achieve the same thing with {{checkstyle-plugin}} (such it is
already run on each build). This will save TC resources consumed to run both
suites and simplify Ignite {{pom.xml}}.
[1] https://checkstyle.sourceforge.io/config_header.html
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Created] (IGNITE-12053) Total time threads parked if checkpoint throttling occurred
Maxim Muzafarov created IGNITE-12053: Summary: Total time threads parked if checkpoint throttling occurred Key: IGNITE-12053 URL: https://issues.apache.org/jira/browse/IGNITE-12053 Project: Ignite Issue Type: Improvement Reporter: Maxim Muzafarov Fix For: 2.8 Currently, threads that generate dirty pages during an ongoing checkpoint are throttled. User should have the ability to see total time threads are parked during the checkpoint writing marked pages. Such a metric must be dropped down at checkpoint end. See `PagesWriteThrottle` class as a start point of investigation. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (IGNITE-12051) Update javadoc for the IgniteKernal class
Maxim Muzafarov created IGNITE-12051:
Summary: Update javadoc for the IgniteKernal class
Key: IGNITE-12051
URL: https://issues.apache.org/jira/browse/IGNITE-12051
Project: Ignite
Issue Type: Task
Reporter: Maxim Muzafarov
Assignee: Maxim Muzafarov
Update all ambiguous an empty javadoc comments, such as:
{code}
/** */
/** Periodic starvation check interval. */
private static final long PERIODIC_STARVATION_CHECK_FREQ = 1000 * 30;
/** Long jvm pause detector. */
private LongJVMPauseDetector longJVMPauseDetector;
/** Scheduler. */
private IgniteScheduler scheduler;
/** Stop guard. */
private final AtomicBoolean stopGuard = new AtomicBoolean();
{code}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Created] (IGNITE-12035) Deprecate EVT_CACHE_REBALANCE_OBJECT_LOADED cache events
Maxim Muzafarov created IGNITE-12035: Summary: Deprecate EVT_CACHE_REBALANCE_OBJECT_LOADED cache events Key: IGNITE-12035 URL: https://issues.apache.org/jira/browse/IGNITE-12035 Project: Ignite Issue Type: Improvement Reporter: Maxim Muzafarov Assignee: Maxim Muzafarov Fix For: 2.8 Events # [EVT_CACHE_REBALANCE_OBJECT_LOADED|https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/events/EventType.html#EVT_CACHE_REBALANCE_OBJECT_LOADED] # [EVT_CACHE_REBALANCE_OBJECT_UNLOADED|https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/events/EventType.html#EVT_CACHE_REBALANCE_OBJECT_UNLOADED] currently not used and should be deprecated for the _2.8_ release and removed in _3.0_. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (IGNITE-11989) Preload predicate not used in GridCachePreloader
Maxim Muzafarov created IGNITE-11989:
Summary: Preload predicate not used in GridCachePreloader
Key: IGNITE-11989
URL: https://issues.apache.org/jira/browse/IGNITE-11989
Project: Ignite
Issue Type: Improvement
Reporter: Maxim Muzafarov
Assignee: Maxim Muzafarov
Fix For: 2.8
{code:title=GridCachePreloader.java}
/**
* @return Preload predicate. If not {@code null}, will evaluate each
preloaded entry during
* send and receive, and if predicate evaluates to {@code false},
entry will be skipped.
*/
public IgnitePredicate preloadPredicate();
{code}
This is internal cache preload predicate, which is not used and not tested for
entry preloading. Can be removed to keep code simple.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Created] (IGNITE-11943) Checkstyle must support RedundantImport rule
Maxim Muzafarov created IGNITE-11943:
Summary: Checkstyle must support RedundantImport rule
Key: IGNITE-11943
URL: https://issues.apache.org/jira/browse/IGNITE-11943
Project: Ignite
Issue Type: Bug
Reporter: Maxim Muzafarov
Assignee: Maxim Muzafarov
Fix For: 2.8
Add support {{}} checkstyle plugin.
https://checkstyle.sourceforge.io/config_imports.html#RedundantImport
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11935) Checkstyle must support NewlineAtEndOfFile rule
Maxim Muzafarov created IGNITE-11935:
Summary: Checkstyle must support NewlineAtEndOfFile rule
Key: IGNITE-11935
URL: https://issues.apache.org/jira/browse/IGNITE-11935
Project: Ignite
Issue Type: Bug
Reporter: Maxim Muzafarov
Assignee: Maxim Muzafarov
Fix For: 2.8
Add support {{
[jira] [Created] (IGNITE-11903) Checkstyle must support to JavadocStyle rule
Maxim Muzafarov created IGNITE-11903:
Summary: Checkstyle must support to JavadocStyle rule
Key: IGNITE-11903
URL: https://issues.apache.org/jira/browse/IGNITE-11903
Project: Ignite
Issue Type: Bug
Reporter: Maxim Muzafarov
Add support to to checkstyle plugin. Analyze and
set the best-fit configuration properties for the Apache Ignite needs.
[http://checkstyle.sourceforge.net/config_javadoc.html#JavadocStyle]
{noformat}
Validates Javadoc comments to help ensure they are well formed. The following
checks are performed:
Ensures the first sentence ends with proper punctuation (That is a period,
question mark, or exclamation mark, by default). Javadoc automatically places
the first sentence in the method summary table and index. Without proper
punctuation the Javadoc may be malformed. All items eligible for the
{@inheritDoc} tag are exempt from this requirement.
Check text for Javadoc statements that do not have any description. This
includes both completely empty Javadoc, and Javadoc with only tags such as
@param and @return.
Check text for incomplete HTML tags. Verifies that HTML tags have corresponding
end tags and issues an "Unclosed HTML tag found:" error if not. An "Extra HTML
tag found:" error is issued if an end tag is found without a previous open tag.
Check that a package Javadoc comment is well-formed (as described above) and
NOT missing from any package-info.java files.
Check for allowed HTML tags. The list of allowed HTML tags is "a", "abbr",
"acronym", "address", "area", "b", "bdo", "big", "blockquote", "br", "caption",
"cite", "code", "colgroup", "dd", "del", "div", "dfn", "dl", "dt", "em",
"fieldset", "font", "h1" to "h6", "hr", "i", "img", "ins", "kbd", "li", "ol",
"p", "pre", "q", "samp", "small", "span", "strong", "sub", "sup", "table",
"tbody", "td", "tfoot", "th", "thread", "tr", "tt", "u", "ul".
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11902) Checkstyle must support MagicNumbers rule
Maxim Muzafarov created IGNITE-11902:
Summary: Checkstyle must support MagicNumbers rule
Key: IGNITE-11902
URL: https://issues.apache.org/jira/browse/IGNITE-11902
Project: Ignite
Issue Type: Bug
Reporter: Maxim Muzafarov
Add support to checkstyle plugin.
Checks that there are no "magic numbers" where a magic number is a numeric
literal that is not defined as a constant. By default, -1, 0, 1, and 2 are not
considered to be magic numbers.
Constant definition is any variable/field that has 'final' modifier. It is fine
to have one constant defining multiple numeric literals within one expression:
{code}
static final int SECONDS_PER_DAY = 24 * 60 * 60;
static final double SPECIAL_RATIO = 4.0 / 3.0;
static final double SPECIAL_SUM = 1 + Math.E;
static final double SPECIAL_DIFFERENCE = 4 - Math.PI;
static final Border STANDARD_BORDER = BorderFactory.createEmptyBorder(3, 3, 3,
3);
static final Integer ANSWER_TO_THE_ULTIMATE_QUESTION_OF_LIFE = new Integer(42);
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11899) Fix code style violation
Maxim Muzafarov created IGNITE-11899:
Summary: Fix code style violation
Key: IGNITE-11899
URL: https://issues.apache.org/jira/browse/IGNITE-11899
Project: Ignite
Issue Type: Bug
Reporter: Maxim Muzafarov
Assignee: Maxim Muzafarov
All the code style issues must be fixed, see the sample below.
{code}
[09:38:03] [Step 2/2] [ERROR]
/opt/buildagent/work/69588afcb2ab3382/modules/core/src/main/java/org/apache/ignite/internal/commandline/diagnostic/PageLocksCommand.java:50:
'VARIABLE_DEF' should be separated from previous statement.
[EmptyLineSeparator]
[09:38:03] [Step 2/2] [ERROR]
/opt/buildagent/work/69588afcb2ab3382/modules/core/src/main/java/org/apache/ignite/internal/commandline/diagnostic/PageLocksCommand.java:183:
'VARIABLE_DEF' should be separated from previous statement.
[EmptyLineSeparator]
[09:38:03] [Step 2/2] [ERROR]
/opt/buildagent/work/69588afcb2ab3382/modules/core/src/main/java/org/apache/ignite/internal/commandline/diagnostic/PageLocksCommand.java:187:
'VARIABLE_DEF' should be separated from previous statement.
[EmptyLineSeparator]
[09:38:03] [Step 2/2] [ERROR]
/opt/buildagent/work/69588afcb2ab3382/modules/core/src/main/java/org/apache/ignite/internal/commandline/diagnostic/PageLocksCommand.java:191:
'VARIABLE_DEF' should be separated from previous statement.
[EmptyLineSeparator]
{code}
TC log:
https://ci.ignite.apache.org/viewLog.html?buildId=4062737=IgniteTests24Java8_CheckCodeStyle=buildLog_IgniteTests24Java8=%3Cdefault%3E
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11821) Move rebalanceBatchSize and rebalanceBatchesPrefetchCnt to IgniteConfiguration level
Maxim Muzafarov created IGNITE-11821:
Summary: Move rebalanceBatchSize and rebalanceBatchesPrefetchCnt
to IgniteConfiguration level
Key: IGNITE-11821
URL: https://issues.apache.org/jira/browse/IGNITE-11821
Project: Ignite
Issue Type: Improvement
Reporter: Maxim Muzafarov
Assignee: Maxim Muzafarov
Fix For: 2.8
The set of cluster rebalancing properties below must be maintained and provided
by {{IgniteConfiguration}}, so an administrator will be able to tune the
cluster rebalance behaviour depending on used hardware (e.g. the different
hardware can have different maximum transmission unit (MTU) and it's strongly
recommended to use specific rebalanceBatchSize for each cluster environment).
Currently, there is no way to change these properties for already created
persistent caches.
{code:title=CacheConfiguration.java}
/** Rebalance timeout. */
private long rebalanceTimeout = DFLT_REBALANCE_TIMEOUT;
/** Rebalance batch size. */
private int rebalanceBatchSize = DFLT_REBALANCE_BATCH_SIZE;
/** Rebalance batches prefetch count. */
private long rebalanceBatchesPrefetchCnt =
DFLT_REBALANCE_BATCHES_PREFETCH_COUNT;
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11277) Use maven plugin as default code style checker for project
Maxim Muzafarov created IGNITE-11277:
Summary: Use maven plugin as default code style checker for project
Key: IGNITE-11277
URL: https://issues.apache.org/jira/browse/IGNITE-11277
Project: Ignite
Issue Type: Task
Reporter: Maxim Muzafarov
Assignee: Maxim Muzafarov
Fix For: 2.8
Currently, {{[Inspections] Core suite}} [1] on TC doesn't work well enough. The
suite has a {{FAILED}} status for more than 2 months due to some issues on
TeamCity application [2]. It confuses most of the members of the Apache Ignite
community.
Moreover, this suite is no longer checks configured rules. For instance, in the
master branch, 11 {{Unused imports}} can be found (e.g. for
{{IgniteCachePutAllRestartTest}
[3]).
I think the maven-checkstyle-plugin should be used as the default code style
checker.
_Advantages:_
* An IDE agnostic way for code checks
* Can be used with different CI and build tools
* Executable from the command line
* Single configuration
[1]
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_InspectionsCore_IgniteTests24Java8=%3Cdefault%3E=buildTypeStatusDiv
[2] https://youtrack.jetbrains.com/issue/TW-58504
[3]
https://github.com/apache/ignite/blob/master/modules/core/src/test/java/org/apache/ignite/internal/processors/cache/IgniteCachePutAllRestartTest.java#L29
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11073) Add Copy-on-Write machinery to the Checkpoiner
Maxim Muzafarov created IGNITE-11073: Summary: Add Copy-on-Write machinery to the Checkpoiner Key: IGNITE-11073 URL: https://issues.apache.org/jira/browse/IGNITE-11073 Project: Ignite Issue Type: Sub-task Reporter: Maxim Muzafarov Assignee: Maxim Muzafarov *Checkpointer* When the supplier node receives the cache partition file demand request it will send the file over the CommunicationSpi. The cache partition file can be concurrently updated by checkpoint thread during its transmission. To guarantee the file consistency Сheckpointer must use Copy-on-Write [3] tehnique and save a copy of updated chunk into the temporary file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11075) Implement index rebuild procedure after partitions uploaded
Maxim Muzafarov created IGNITE-11075:
Summary: Implement index rebuild procedure after partitions
uploaded
Key: IGNITE-11075
URL: https://issues.apache.org/jira/browse/IGNITE-11075
Project: Ignite
Issue Type: Sub-task
Reporter: Maxim Muzafarov
Assignee: Maxim Muzafarov
We need to rebuild a {{index.bin}} file when all demanded partitions uploaded
successfully to the demander node.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
