[jira] [Created] (IGNITE-13955) Thread Pools incomprehensible metric description
Alexand Polyakov created IGNITE-13955: - Summary: Thread Pools incomprehensible metric description Key: IGNITE-13955 URL: https://issues.apache.org/jira/browse/IGNITE-13955 Project: Ignite Issue Type: Sub-task Reporter: Alexand Polyakov Assignee: Alexand Polyakov There are incomprehensible description for metric RejectedExecutionHandlerClass for each thread pool. For example mbean org.apache:group="Thread Pools",name=GridAffinityExecutor -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13956) ManagementEnabled incomprehensible metric description
Alexand Polyakov created IGNITE-13956: - Summary: ManagementEnabled incomprehensible metric description Key: IGNITE-13956 URL: https://issues.apache.org/jira/browse/IGNITE-13956 Project: Ignite Issue Type: Sub-task Reporter: Alexand Polyakov Assignee: Alexand Polyakov There are incomprehensible description for mben: org.apache:group=CACHE_NAME,name="org.apache.ignite.internal.processors.cache.CacheClusterMetricsMXBeanImpl" ManagementEnabled -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13953) Detaregion metrics without description
Alexand Polyakov created IGNITE-13953: - Summary: Detaregion metrics without description Key: IGNITE-13953 URL: https://issues.apache.org/jira/browse/IGNITE-13953 Project: Ignite Issue Type: Sub-task Reporter: Alexand Polyakov Assignee: Alexand Polyakov List of metrics: ||mbean||attribute||description|| |org.apache:group=DataRegionMetrics,name=default|PageSize|Attribute exposed for management| |org.apache:group=DataRegionMetrics,name=default|TotalAllocatedSize|Attribute exposed for management| |org.apache:group=DataRegionMetrics,name=default|PhysicalMemorySize|Attribute exposed for management| |org.apache:group=DataRegionMetrics,name=default|UsedCheckpointBufferPages|Attribute exposed for management| |org.apache:group=DataRegionMetrics,name=default|UsedCheckpointBufferSize|Attribute exposed for management| |org.apache:group=DataRegionMetrics,name=default|CheckpointBufferSize|Attribute exposed for management| -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13954) TcpDiscoverySpi incomprehensible metric description
Alexand Polyakov created IGNITE-13954: - Summary: TcpDiscoverySpi incomprehensible metric description Key: IGNITE-13954 URL: https://issues.apache.org/jira/browse/IGNITE-13954 Project: Ignite Issue Type: Sub-task Reporter: Alexand Polyakov Assignee: Alexand Polyakov There is an incomprehensible description for metric: org.apache:group=SPIs,name=TcpDiscoverySpi IpFinderCleanFrequency org.apache:group=SPIs,name=TcpDiscoverySpi JoinTimeout -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13952) Cache metrics without description
Alexand Polyakov created IGNITE-13952: - Summary: Cache metrics without description Key: IGNITE-13952 URL: https://issues.apache.org/jira/browse/IGNITE-13952 Project: Ignite Issue Type: Sub-task Reporter: Alexand Polyakov Assignee: Alexand Polyakov list of metrics |org.apache:group=CACHE_NAME,name="org.apache.ignite.internal.processors.cache.CacheClusterMetricsMXBeanImpl"|RebalancedKeys| |org.apache:group=CACHE_NAME,name="org.apache.ignite.internal.processors.cache.CacheClusterMetricsMXBeanImpl"|EstimatedRebalancingKeys| |org.apache:group=CACHE_NAME,name="org.apache.ignite.internal.processors.cache.CacheClusterMetricsMXBeanImpl"|RebalanceClearingPartitionsLeft| |org.apache:group=CACHE_NAME,name="org.apache.ignite.internal.processors.cache.CacheClusterMetricsMXBeanImpl"|EntryProcessorAverageInvocationTime| |org.apache:group=CACHE_NAME,name="org.apache.ignite.internal.processors.cache.CacheClusterMetricsMXBeanImpl"|EntryProcessorHitPercentage| |org.apache:group=CACHE_NAME,name="org.apache.ignite.internal.processors.cache.CacheClusterMetricsMXBeanImpl"|EntryProcessorHits| |org.apache:group=CACHE_NAME,name="org.apache.ignite.internal.processors.cache.CacheClusterMetricsMXBeanImpl"|EntryProcessorInvocations| |org.apache:group=CACHE_NAME,name="org.apache.ignite.internal.processors.cache.CacheClusterMetricsMXBeanImpl"|EntryProcessorMaxInvocationTime| |org.apache:group=CACHE_NAME,name="org.apache.ignite.internal.processors.cache.CacheClusterMetricsMXBeanImpl"|EntryProcessorMinInvocationTime| |org.apache:group=CACHE_NAME,name="org.apache.ignite.internal.processors.cache.CacheClusterMetricsMXBeanImpl"|EntryProcessorMisses| |org.apache:group=CACHE_NAME,name="org.apache.ignite.internal.processors.cache.CacheClusterMetricsMXBeanImpl"|EntryProcessorMissPercentage| |org.apache:group=CACHE_NAME,name="org.apache.ignite.internal.processors.cache.CacheClusterMetricsMXBeanImpl"|EntryProcessorPuts| |org.apache:group=CACHE_NAME,name="org.apache.ignite.internal.processors.cache.CacheClusterMetricsMXBeanImpl"|EntryProcessorReadOnlyInvocations| |org.apache:group=CACHE_NAME,name="org.apache.ignite.internal.processors.cache.CacheClusterMetricsMXBeanImpl"|EntryProcessorRemovals| |org.apache:group=CACHE_NAME,name="org.apache.ignite.internal.processors.cache.CacheLocalMetricsMXBeanImpl"|RebalancedKeys| |org.apache:group=CACHE_NAME,name="org.apache.ignite.internal.processors.cache.CacheLocalMetricsMXBeanImpl"|EstimatedRebalancingKeys| |org.apache:group=CACHE_NAME,name="org.apache.ignite.internal.processors.cache.CacheLocalMetricsMXBeanImpl"|RebalanceClearingPartitionsLeft| |org.apache:group=CACHE_NAME,name="org.apache.ignite.internal.processors.cache.CacheLocalMetricsMXBeanImpl"|EntryProcessorAverageInvocationTime| |org.apache:group=CACHE_NAME,name="org.apache.ignite.internal.processors.cache.CacheLocalMetricsMXBeanImpl"|EntryProcessorHitPercentage| |org.apache:group=CACHE_NAME,name="org.apache.ignite.internal.processors.cache.CacheLocalMetricsMXBeanImpl"|EntryProcessorHits| |org.apache:group=CACHE_NAME,name="org.apache.ignite.internal.processors.cache.CacheLocalMetricsMXBeanImpl"|EntryProcessorInvocations| |org.apache:group=CACHE_NAME,name="org.apache.ignite.internal.processors.cache.CacheLocalMetricsMXBeanImpl"|EntryProcessorMaxInvocationTime| |org.apache:group=CACHE_NAME,name="org.apache.ignite.internal.processors.cache.CacheLocalMetricsMXBeanImpl"|EntryProcessorMinInvocationTime| |org.apache:group=CACHE_NAME,name="org.apache.ignite.internal.processors.cache.CacheLocalMetricsMXBeanImpl"|EntryProcessorMisses| |org.apache:group=CACHE_NAME,name="org.apache.ignite.internal.processors.cache.CacheLocalMetricsMXBeanImpl"|EntryProcessorMissPercentage| |org.apache:group=CACHE_NAME,name="org.apache.ignite.internal.processors.cache.CacheLocalMetricsMXBeanImpl"|EntryProcessorPuts| |org.apache:group=CACHE_NAME,name="org.apache.ignite.internal.processors.cache.CacheLocalMetricsMXBeanImpl"|EntryProcessorReadOnlyInvocations| |org.apache:group=CACHE_NAME,name="org.apache.ignite.internal.processors.cache.CacheLocalMetricsMXBeanImpl"|EntryProcessorRemovals| -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13951) Improve metric description
Alexand Polyakov created IGNITE-13951: - Summary: Improve metric description Key: IGNITE-13951 URL: https://issues.apache.org/jira/browse/IGNITE-13951 Project: Ignite Issue Type: Improvement Reporter: Alexand Polyakov Assignee: Alexand Polyakov There are a lot of metrics in jmx with useless description. There are a lot of metrics in jmx with useless description. Under this task I'll create sub-tasks to improve descriptions. * Cache metrics without description * Detaregion metrics without description * TcpDiscoverySpi incomprehensible metric description * Thread Pools incomprehensible metric description * ManagementEnabled incomprehensible metric description -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13689) Extend test coverage [IGNITE-11512] Add counter left partition for index rebuild in CacheGroupMetricsMXBean
Alexand Polyakov created IGNITE-13689: - Summary: Extend test coverage [IGNITE-11512] Add counter left partition for index rebuild in CacheGroupMetricsMXBean Key: IGNITE-13689 URL: https://issues.apache.org/jira/browse/IGNITE-13689 Project: Ignite Issue Type: Improvement Components: general Affects Versions: 2.9 Reporter: Alexand Polyakov Assignee: Alexand Polyakov New test: Partial rebuild # Start cluster, load data with indexes # Kill single node, create new index, start node. # Make sure that index rebuild count is in range of total new index size and 0 and decreasing # Wait until rebuild finished, assert that no index errors -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13687) Improvement of human-readable format of WAL records (StandaloneWalRecordsIterator)
Alexand Polyakov created IGNITE-13687: - Summary: Improvement of human-readable format of WAL records (StandaloneWalRecordsIterator) Key: IGNITE-13687 URL: https://issues.apache.org/jira/browse/IGNITE-13687 Project: Ignite Issue Type: Improvement Components: persistence Affects Versions: 2.9 Reporter: Alexand Polyakov Assignee: Alexand Polyakov StandaloneWalRecordsIterator is used for PageHistoryDiagnoster and wal-reader utility for printing WAL records in human-readable format. We should add abilities for this iterator and options for IgniteWalIteratorFactory: to print DataRecord entries keys in hex/base64 (see UnwrapDataEntry) to print all records existing in WAL -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13518) Change static cache configuration allowed or not and what operations: add column, drop
Alexand Polyakov created IGNITE-13518: - Summary: Change static cache configuration allowed or not and what operations: add column, drop Key: IGNITE-13518 URL: https://issues.apache.org/jira/browse/IGNITE-13518 Project: Ignite Issue Type: Bug Components: cache Affects Versions: 2.8.1 Reporter: Alexand Polyakov If a new node with a modified configuration cache is connected, the configuration is merged and a new column is added. if the cluster is restarted with a new cache configuration, the changes are ignored and the column is not added 1. you need to determine whether to allow changing the static cache configuration or not to allow it 2. the behavior should be the same (restart cluster, join node) 3. the behavior is not described in the documentation 4. How static cache configuration interacts with dynamic changes from SQL? 5. Export/import database schema 6. There are no messages in the application logs about changing the cache configuration (or about a ban based on the result of point 1) 7. If the configuration can be changed, what should I do with the fields that are missing in the new version of the configuration - delete column? if they were added using SQL -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13175) NPE due to race on cache stop and transaction commit.
Alexand Polyakov created IGNITE-13175:
-
Summary: NPE due to race on cache stop and transaction commit.
Key: IGNITE-13175
URL: https://issues.apache.org/jira/browse/IGNITE-13175
Project: Ignite
Issue Type: Bug
Affects Versions: 2.7
Reporter: Alexand Polyakov
If don't stop load and execute stop cache, sometimes throw NullPointerException
and nodes failed
{code}
java.lang.NullPointerException: null
at
org.apache.ignite.internal.binary.BinaryObjectImpl.finishUnmarshal(BinaryObjectImpl.java:190)
at
org.apache.ignite.internal.processors.cache.transactions.TxEntryValueHolder.unmarshal(TxEntryValueHolder.java:154)
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxEntry.unmarshal(IgniteTxEntry.java:971)
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.unmarshal(IgniteTxHandler.java:354)
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.prepareNearTx(IgniteTxHandler.java:403)
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.prepareNearTx(IgniteTxHandler.java:386)
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processNearTxPrepareRequest0(IgniteTxHandler.java:188)
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.lambda$null$0(IgniteTxHandler.java:644)
at
org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:559)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119)
at java.lang.Thread.run(Thread.java:748)
{code}
transaction use cache context race with stopCache
{code:java}
at
org.apache.ignite.internal.processors.cache.GridCacheContext.cleanup(GridCacheContext.java:2058)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.cleanup(GridCacheProcessor.java:467)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.stopCache(GridCacheProcessor.java:1020)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStop(GridCacheProcessor.java:2539)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStop(GridCacheProcessor.java:2518)
{code}
there is a reproducer who adds CountDownLatch await to IgniteTxEntry#unmarshal
which is countDown in GridCacheContext#cleanup
https://github.com/gridgain/gridgain/tree/sdsb-11837
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-13165) NPE when control utility connect to cluster (VisorTxTask)
Alexand Polyakov created IGNITE-13165:
-
Summary: NPE when control utility connect to cluster (VisorTxTask)
Key: IGNITE-13165
URL: https://issues.apache.org/jira/browse/IGNITE-13165
Project: Ignite
Issue Type: Bug
Affects Versions: 2.5
Reporter: Alexand Polyakov
Attachments: error_kanga24.txt
NullPointerException when control utility connect to cluster for execute
VisorTxTask
{code:java}
2020-05-18
02:47:12.070[ERROR][mgmt-#305526%DPL_GRID%DplGridNodeName%][o.a.i.i.p.r.p.t.GridTcpRestProtocol]
Failed to process client request [ses=GridSelectorNioSessionImpl
[worker=GridWorker [name=grid-nio-worker-tcp-rest-1,
igniteInstanceName=DPL_GRID%DplGridNodeName, finished=false,
heartbeatTs=1589759232067, hashCode=676612820, interrupted=false,
runner=grid-nio-worker-tcp-rest-1-#143%DPL_GRID%DplGridNodeName%]AbstractNioClientWorker
[idx=1, bytesRcvd=0, bytesSent=0, bytesRcvd0=0, bytesSent0=0, select=false,
super=]ByteBufferNioClientWorker [readBuf=java.nio.HeapByteBuffer[pos=85 lim=85
cap=8192], super=], writeBuf=null, readBuf=null, inRecovery=null,
outRecovery=null, super=GridNioSessionImpl [locAddr=/10.104.6.24:11211,
rmtAddr=unuratu101.ca.sbrf.ru/10.104.6.100:57054, createTime=1589759103528,
closeTime=1589759232067, bytesSent=10011, bytesRcvd=10203, bytesSent0=85,
bytesRcvd0=85, sndSchedTime=1589759232057, lastSndTime=1589759232067,
lastRcvTime=1589759230548, readsPaused=false,
filterChain=FilterChain[filters=[, SSL filter], accepted=true,
markedForClose=true]], msg=GridClientTaskRequest
[taskName=o.a.i.i.v.tx.VisorTxTask, arg=VisorTaskArgument [debug=false]]]
...
Caused by: java.lang.NullPointerException: null
at
org.apache.ignite.internal.MarshallerContextImpl.registerClassName(MarshallerContextImpl.java:293)
at
org.apache.ignite.internal.marshaller.optimized.OptimizedMarshallerUtils.classDescriptor(OptimizedMarshallerUtils.java:204)
... 87 common frames omitted
{code}
full stack trace
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-11512) Add counter left partition for index rebuild in CacheGroupMetricsMXBean
Alexand Polyakov created IGNITE-11512: - Summary: Add counter left partition for index rebuild in CacheGroupMetricsMXBean Key: IGNITE-11512 URL: https://issues.apache.org/jira/browse/IGNITE-11512 Project: Ignite Issue Type: Improvement Components: general Affects Versions: 2.7 Reporter: Alexand Polyakov Assignee: Alexand Polyakov Now, if ran rebuild indexes, this can determined only on load CPU and thread dump. The presence of the "how many partitions left to index" metric will help determine whether the rebuilding is going on and on which cache, as well as the percentage of completion. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10949) org.apache.ignite.internal.MarshallerContextImpl.CombinedMap generates NPE
Alexand Polyakov created IGNITE-10949: - Summary: org.apache.ignite.internal.MarshallerContextImpl.CombinedMap generates NPE Key: IGNITE-10949 URL: https://issues.apache.org/jira/browse/IGNITE-10949 Project: Ignite Issue Type: Bug Components: binary Affects Versions: 2.7 Reporter: Alexand Polyakov method entrySet return null then generates NullPointerException in method hashCode, toString and all classes that use an instance of this object. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10557) Control.sh validate index work long and broke down
Alexand Polyakov created IGNITE-10557:
-
Summary: Control.sh validate index work long and broke down
Key: IGNITE-10557
URL: https://issues.apache.org/jira/browse/IGNITE-10557
Project: Ignite
Issue Type: Bug
Components: visor
Affects Versions: 2.6
Reporter: Alexand Polyakov
cluster in the amount of 27Gb
performing validate_indexes took more than 1 hour
and execution failed
{code}
control.sh --cache validate_indexes
Control utility [ver. 2.6]
2018 Copyright(C) Apache Software Foundation
User: pprbusr
Connection to cluster failed.
Error: Failed to perform request (connection failed): /10.117.102.207:11211
You have mail in /var/spool/mail/busr
{code}
analysis of the thread for 40 minutes showed that out of 32 nodes only on 3
nodes were flows ValidateIndexesClosure
at the same time, some threads are blocked
{code}
"pool-55-thread-53" #9255 prio=5 os_prio=0 tid=0x7eb5a0073800 nid=0xb408
waiting for monitor entry [0x7eb6554f3000]
java.lang.Thread.State: BLOCKED (on object monitor)
at
org.apache.ignite.internal.pagemem.PageUtils.getBytes(PageUtils.java:63)
at
org.apache.ignite.internal.processors.cache.persistence.CacheDataRowAdapter.readFullRow(CacheDataRowAdapter.java:296)
at
org.apache.ignite.internal.processors.cache.persistence.CacheDataRowAdapter.initFromLink(CacheDataRowAdapter.java:159)
at
org.apache.ignite.internal.processors.cache.persistence.CacheDataRowAdapter.initFromLink(CacheDataRowAdapter.java:102)
at
org.apache.ignite.internal.processors.query.h2.database.H2RowFactory.getRow(H2RowFactory.java:61)
at
org.apache.ignite.internal.processors.query.h2.database.H2Tree.createRowFromLink(H2Tree.java:152)
at
org.apache.ignite.internal.processors.query.h2.database.io.H2InnerIO.getLookupRow(H2InnerIO.java:60)
at
org.apache.ignite.internal.processors.query.h2.database.io.H2InnerIO.getLookupRow(H2InnerIO.java:33)
at
org.apache.ignite.internal.processors.query.h2.database.H2Tree.getRow(H2Tree.java:170)
at
org.apache.ignite.internal.processors.query.h2.database.H2Tree.getRow(H2Tree.java:47)
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.getRow(BPlusTree.java:4524)
at
org.apache.ignite.internal.processors.query.h2.database.H2Tree.compare(H2Tree.java:212)
at
org.apache.ignite.internal.processors.query.h2.database.H2Tree.compare(H2Tree.java:47)
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.compare(BPlusTree.java:4511)
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.findInsertionPoint(BPlusTree.java:4431)
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.access$1300(BPlusTree.java:90)
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Search.run0(BPlusTree.java:291)
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$GetPageHandler.run(BPlusTree.java:4858)
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Search.run(BPlusTree.java:271)
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$GetPageHandler.run(BPlusTree.java:4843)
at
org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.readPage(PageHandler.java:161)
at
org.apache.ignite.internal.processors.cache.persistence.DataStructure.read(DataStructure.java:332)
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.findDown(BPlusTree.java:1157)
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.doFind(BPlusTree.java:1124)
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.findOne(BPlusTree.java:1091)
at
org.apache.ignite.internal.processors.query.h2.database.H2TreeIndex.find(H2TreeIndex.java:201)
at
org.apache.ignite.internal.visor.verify.ValidateIndexesClosure.processPartition(ValidateIndexesClosure.java:524)
at
org.apache.ignite.internal.visor.verify.ValidateIndexesClosure.access$100(ValidateIndexesClosure.java:86)
at
org.apache.ignite.internal.visor.verify.ValidateIndexesClosure$2.call(ValidateIndexesClosure.java:394)
at
org.apache.ignite.internal.visor.verify.ValidateIndexesClosure$2.call(ValidateIndexesClosure.java:392)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10060) Optimize IncSnapshotNearbyFullSnapshotTest#test use seconds instead of minutes
Alexand Polyakov created IGNITE-10060: - Summary: Optimize IncSnapshotNearbyFullSnapshotTest#test use seconds instead of minutes Key: IGNITE-10060 URL: https://issues.apache.org/jira/browse/IGNITE-10060 Project: Ignite Issue Type: Test Reporter: Alexand Polyakov -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] ignite pull request #5087: IGNITE-10020 control.sh error: Comparison method ...
GitHub user a-polyakov opened a pull request: https://github.com/apache/ignite/pull/5087 IGNITE-10020 control.sh error: Comparison method violates its general contract! You can merge this pull request into a Git repository by running: $ git pull https://github.com/a-polyakov/ignite IGNITE-10020 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5087.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #5087 commit f443238ed020e6c926e91e4adc8e4951c026dd70 Author: a-polyakov Date: 2018-10-26T11:47:38Z IGNITE-10020 control.sh error: Comparison method violates its general contract! Signed-off-by: a-polyakov ---
[jira] [Created] (IGNITE-10020) control.sh error: Comparison method violates its general contract!
Alexand Polyakov created IGNITE-10020: - Summary: control.sh error: Comparison method violates its general contract! Key: IGNITE-10020 URL: https://issues.apache.org/jira/browse/IGNITE-10020 Project: Ignite Issue Type: Bug Reporter: Alexand Polyakov Assignee: Alexand Polyakov ./control.sh --host 192.168.1.1 --cache distribution null Control utility [ver. 2.5#20181002-sha1:3d28432b] 2018 Copyright(C) Apache Software Foundation User: test Check arguments. Error: Comparison method violates its general contract! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] ignite pull request #5079: IGNITE-9990 Control.sh utility should request a p...
GitHub user a-polyakov opened a pull request: https://github.com/apache/ignite/pull/5079 IGNITE-9990 Control.sh utility should request a password if necessary. Signed-off-by: a-polyakov You can merge this pull request into a Git repository by running: $ git pull https://github.com/a-polyakov/ignite IGNITE-9990 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5079.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #5079 commit 538d3d2ef924a5ad8f653c3d0c37397eec405da7 Author: a-polyakov Date: 2018-10-25T13:46:44Z IGNITE-9990 Control.sh utility should request a password if necessary. Signed-off-by: a-polyakov ---
[jira] [Created] (IGNITE-9990) Control.sh utility should request a password if necessary.
Alexand Polyakov created IGNITE-9990:
Summary: Control.sh utility should request a password if necessary.
Key: IGNITE-9990
URL: https://issues.apache.org/jira/browse/IGNITE-9990
Project: Ignite
Issue Type: New Feature
Affects Versions: 2.5
Reporter: Alexand Polyakov
Assignee: Alexand Polyakov
Since password in line parameters may not be safe (stored in console history in
open form).
Use hidden input
{code:java}
Console console = System.console();
char passwordArray[] = console.readPassword("password: ");
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] ignite pull request #4521: GG-13254 Snapshots: Only Full snapshot should be ...
Github user a-polyakov closed the pull request at: https://github.com/apache/ignite/pull/4521 ---
[GitHub] ignite pull request #4843: IGN-11747 [IGNITE-9298] control.sh does not suppo...
GitHub user a-polyakov opened a pull request: https://github.com/apache/ignite/pull/4843 IGN-11747 [IGNITE-9298] control.sh does not support SSL in 5.2.1-p14 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite IGN-11747 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4843.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4843 commit 69d9272009cc6cbec07d8bbc99364ec777c851b5 Author: Sergey Chugunov Date: 2018-05-17T10:10:01Z IGNITE-8474 Fixed WalStateNodeLeaveExchangeTask preventing exchange merge - Fixes #3990. Signed-off-by: Alexey Goncharuk (cherry-picked from commit #ebd669e4c53cfd66708ff18dd59071e4aace38ae) commit 9b80a49d642de27dd6a69daea3921d1c05919df6 Author: Evgeny Stanilovskiy Date: 2018-04-28T12:09:17Z IGNITE-8401: errorneous WalPointers comparation. - Fixes #3931. Signed-off-by: dspavlov commit 40ddce5d046e98b9da4c05a9a302326d4e15e08f Author: Pavel Kovalenko Date: 2018-05-17T12:04:27Z Merge branch 'ignite-2.5.1-master' of github.com:gridgain/apache-ignite into ignite-2.5.1-master commit 31f8d7e445b1ef7986e3b58e700e119b8490c734 Author: Aleksei Scherbakov Date: 2018-05-17T17:11:41Z IGNITE-8423 Control utility may block when joining node is watiting for partition map exchange. - Fixes #4018. Signed-off-by: Alexey Goncharuk commit d9a80ff6c09ac92a78948fcdb292c5e5c28111d0 Author: Anton Kalashnikov Date: 2018-05-18T08:18:39Z IGNITE-8464 Fixed race in WALIterator leading to skipped segments - Fixes #3982. Signed-off-by: Alexey Goncharuk (cherry picked from commit fdad641) commit 68bf746c47d445d5a469d29b7a4ae5ce040b3d9b Author: Pavel Kovalenko Date: 2018-05-18T16:28:45Z IGNITE-8531 Fixed NPE if checkpoint has no pages to write, but has partitions to destroy. - Fixes #4026. Signed-off-by: Alexey Goncharuk (cherry picked from commit 5c8d9ff) commit 18d913c6118b5132859fbc1e5bacfc97392f9bc2 Author: vd-pyatkov Date: 2018-05-18T13:59:14Z IGNITE-8491 Add JMX flag: Is the node in baseline or not - Fixes #4010. Signed-off-by: Ivan Rakov (cherry picked from commit f8ae30d) commit 40bbe65df3cbd8b3f478812b0e204b2973b98d3d Author: Alexey Goncharuk Date: 2018-05-21T12:13:37Z IGNITE-8521 Do not attempt to unregister continuous query if query ID is null commit affc9d47b986e054fb0c229dcf95e64a38cab13f Author: Pavel Kovalenko Date: 2018-05-21T19:33:50Z IGNITE-8544 Use exchange result topology version for local wal state management. - Fixes #4039. Signed-off-by: Alexey Goncharuk commit 3f4b2ae4f594e8c73b5a9c4b86f2351c2bae591e Author: Anton Kalashnikov Date: 2018-05-23T09:24:51Z IGNITE-8561 SingleSegmentLogicalRecordsIterator is broken - Fixes #4045. (cherry picked from commit 21678bc) commit 49929b73a00f758ef099ea99f8c6f54373c30a95 Author: EdShangGG Date: 2018-04-28T16:27:27Z IGNITE-7628 SqlQuery hangs indefinitely with additional not registered in baseline node. Signed-off-by: Andrey Gura commit 95b749460b5fa32deecb946865944e854d9745d3 Author: Dmitriy Sorokin Date: 2018-05-24T13:03:41Z IGNITE-8584 Provide ability to terminate any thread with enabled test features. Signed-off-by: Andrey Gura commit 8ac69e68ecfc1c31b02004d33157d3f9b85a7b6e Author: Andrey Gura Date: 2018-05-24T13:56:42Z IGNITE-8563 Fixed WAL file archiver does not propagate file archiving error to error handler commit ef63514bfa38c595017ebec62c42a93c90e0a062 Author: Dmitriy Govorukhin Date: 2018-05-24T15:04:02Z IGNITE-8583 DataStorageMetricsMXBean.getOffHeapSize include checkpoint buffer size - Fixes #4054. Signed-off-by: dpavlov (cherry picked from commit 86c1899) commit 04d00be82369f633f26955656441147f53cf2da1 Author: Sergey Chugunov Date: 2018-05-24T15:11:47Z IGNITE-8560 Update index validation utility to use statistical check approach - Fixes #4051. Signed-off-by: Ivan Rakov (cherry-picked from commit #76e1fe754d7a8bd059d7ab64d17cbefa4913a702) commit c457aa60084e1805b7fdbbc88d870ffdc36d14fa Author: Pavel Kovalenko Date: 2018-04-06T07:35:17Z IGNITE-7933 Checkpoing file markers should be written atomically - Fixes #3633. Signed-off-by: Alexey Goncharuk (cherry-picked from commit #4a0695ceae2f99c4841e8382e723daff4580ea3d) commit 6b28e8d76bc0119917af0a738d9f07ff794cde20 Author: Anton Kalashnikov Date: 2018-05-25T09:01:10Z IGNITE-8540 Fast cleanup of PDS when joining node is not in baseline - Fixes #4037. Signed-off-by: Alexey Goncharuk (cherry-picked from commit #3f14d2b35d7818196598e8541590186e06b8edbb) commit
[GitHub] ignite pull request #4842: IGN-11747 [IGNITE-9298] control.sh does not suppo...
Github user a-polyakov closed the pull request at: https://github.com/apache/ignite/pull/4842 ---
[GitHub] ignite pull request #4842: IGN-11747 [IGNITE-9298] control.sh does not suppo...
GitHub user a-polyakov opened a pull request: https://github.com/apache/ignite/pull/4842 IGN-11747 [IGNITE-9298] control.sh does not support SSL in 5.2.1-p14 (org.apache.ignite.internal.commandline.CommandHandler) You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite IGN-11747 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4842.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4842 commit ded31b5668ff63993a002cfd7d86e9e4b744ba90 Author: a-polyakov Date: 2018-09-06T13:35:44Z IGN-11747 [IGNITE-9298] control.sh does not support SSL (org.apache.ignite.internal.commandline.CommandHandler) in 5.2.1-p14 ---
[GitHub] ignite pull request #4803: IGNITE-9618 Need to be replace the data compressi...
GitHub user a-polyakov opened a pull request: https://github.com/apache/ignite/pull/4803 IGNITE-9618 Need to be replace the data compression algorithm Signed-off-by: a-polyakov You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite IGNITE-9618 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4803.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4803 commit 8ac5eaa905f9734c28bd39d89c61d19eab607f47 Author: a-polyakov Date: 2018-09-21T10:23:16Z IGNITE-9618 Need to be replace the data compression algorithm Signed-off-by: a-polyakov ---
[jira] [Created] (IGNITE-9618) Need to be replace the data compression algorithm
Alexand Polyakov created IGNITE-9618: Summary: Need to be replace the data compression algorithm Key: IGNITE-9618 URL: https://issues.apache.org/jira/browse/IGNITE-9618 Project: Ignite Issue Type: New Feature Components: persistence Reporter: Alexand Polyakov Now used zip and its speed slow Exist alternatives and on tests in terms of performance they showed themselves to be better source file wal 1Gb result ||algoritm||time, ms||size, byte|| |zip|18 889|79 950 283| |[Snappy|https://github.com/xerial/snappy-java]|3 372|156 482 623| |[lz4|https://github.com/lz4/lz4-java]|2 047|128 591 795| -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] ignite pull request #4759: IGNITE-9599 Add ability to manage compression lev...
Github user a-polyakov closed the pull request at: https://github.com/apache/ignite/pull/4759 ---
[GitHub] ignite pull request #4763: Ignite 9599 mx bean
GitHub user a-polyakov opened a pull request: https://github.com/apache/ignite/pull/4763 Ignite 9599 mx bean You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite IGNITE-9599_MXBean Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4763.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4763 commit 86accac5b9db0e08a65ca61f4fbc7f26fcd326be Author: a-polyakov Date: 2018-09-14T10:38:50Z IGNITE-9599 Add ability to manage compression level for compressed WAL archives Signed-off-by: a-polyakov commit a60e270e4e3ad84ef0d7d8150c19367d7a562ba3 Author: a-polyakov Date: 2018-09-14T13:59:21Z IGNITE-9599 MXBean control level for compressed WAL archives Signed-off-by: a-polyakov ---
[GitHub] ignite pull request #4759: IGNITE-9599 Add ability to manage compression lev...
GitHub user a-polyakov opened a pull request: https://github.com/apache/ignite/pull/4759 IGNITE-9599 Add ability to manage compression level for compressed WAL archives You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite IGNITE-9599 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4759.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4759 commit 73b2170fe87595be35bce4cea74c6f86729e2ad7 Author: a-polyakov Date: 2018-09-14T10:38:50Z IGNITE-9599 Add ability to manage compression level for compressed WAL archives Signed-off-by: a-polyakov ---
[GitHub] ignite pull request #4737: IGNITE-9544 BinaryOutputStream#writeByte excessiv...
GitHub user a-polyakov opened a pull request: https://github.com/apache/ignite/pull/4737 IGNITE-9544 BinaryOutputStream#writeByte excessive copying after reaching 1Gb You can merge this pull request into a Git repository by running: $ git pull https://github.com/a-polyakov/ignite IGNITE-9544 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4737.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4737 commit 0b73c53f1a11698fbfb73dee64725f24391cba5f Author: a-polyakov Date: 2018-09-12T13:45:27Z IGNITE-9544 BinaryOutputStream#writeByte excessive copying after reaching 1Gb Signed-off-by: a-polyakov ---
[GitHub] ignite pull request #4734: IGNITE-9549 control.sh add command to collect inf...
GitHub user a-polyakov opened a pull request: https://github.com/apache/ignite/pull/4734 IGNITE-9549 control.sh add command to collect information on the dist⦠â¦ribution of partitions and reset lost partitions Signed-off-by: a-polyakov You can merge this pull request into a Git repository by running: $ git pull https://github.com/a-polyakov/ignite IGNITE-9549 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4734.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4734 commit 17bc1534e4b8bf9c13cb072ac424a7592d310fba Author: a-polyakov Date: 2018-09-12T10:16:34Z IGNITE-9549 control.sh add command to collect information on the distribution of partitions and reset lost partitions Signed-off-by: a-polyakov ---
[jira] [Created] (IGNITE-9549) control.sh add command to collect information on the distribution of partitions and reset lost partitions
Alexand Polyakov created IGNITE-9549: Summary: control.sh add command to collect information on the distribution of partitions and reset lost partitions Key: IGNITE-9549 URL: https://issues.apache.org/jira/browse/IGNITE-9549 Project: Ignite Issue Type: Improvement Reporter: Alexand Polyakov Assignee: Alexand Polyakov control.sh add command to collect information on the distribution of partitions control.sh --cache distribution [nodeId|null] [cacheName1[,...,cacheNameN]] [--user-attributes userAttribute[,...,userAttributeN]] return [next group: id=??, name=??] groupId,partition,nodeId,primary,state,updateCounter,size,nodeAddresses[,userAttribute[,...,userAttributeN]] ... groupId,partition,nodeId,primary,state,updateCounter,size,nodeAddresses[,userAttribute[,...,userAttributeN]] reset lost partitions control.sh --cache cacheName1[,...,cacheNameN] return Reset LOST-partitions performed successfully. Cache group (name = '??', id = ??) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9544) BinaryOutputStream#writeByte excessive copying after reaching 1Gb
Alexand Polyakov created IGNITE-9544:
Summary: BinaryOutputStream#writeByte excessive copying after
reaching 1Gb
Key: IGNITE-9544
URL: https://issues.apache.org/jira/browse/IGNITE-9544
Project: Ignite
Issue Type: Improvement
Reporter: Alexand Polyakov
need correction
org.apache.ignite.internal.binary.streams.BinaryAbstractOutputStream#capacity
{code:java}
if (newCap < reqCap)
newCap=Integer.MAX_VALUE - 8;
{code}
see java.util.ArrayList#MAX_ARRAY_SIZE
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] ignite pull request #4697: IGNITE-9298 control.sh does not support SSL
GitHub user a-polyakov opened a pull request: https://github.com/apache/ignite/pull/4697 IGNITE-9298 control.sh does not support SSL Signed-off-by: a-polyakov You can merge this pull request into a Git repository by running: $ git pull https://github.com/a-polyakov/ignite IGNITE-9298 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4697.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4697 commit a6f25a94aa0885b6fe7f63f638a4f0e67b4a4327 Author: a-polyakov Date: 2018-09-06T13:35:44Z IGNITE-9298 control.sh does not support SSL Signed-off-by: a-polyakov ---
[GitHub] ignite pull request #4695: GG-14173 Utilities doesn't work with SSL connecto...
Github user a-polyakov closed the pull request at: https://github.com/apache/ignite/pull/4695 ---
[GitHub] ignite pull request #4695: GG-14173 Utilities doesn't work with SSL connecto...
GitHub user a-polyakov opened a pull request: https://github.com/apache/ignite/pull/4695 GG-14173 Utilities doesn't work with SSL connector configuration You can merge this pull request into a Git repository by running: $ git pull https://github.com/a-polyakov/ignite ignite-gg-14173 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4695.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4695 commit 6273b18f4fe02d9c8e8083cfb509406a2e9a7f47 Author: a-polyakov Date: 2018-09-06T13:35:44Z GG-14173 Utilities doesn't work with SSL connector configuration (part control.sh) Signed-off-by: a-polyakov ---
[GitHub] ignite pull request #4656: IGNITE-9440 control.sh --wal delete do not delete...
GitHub user a-polyakov opened a pull request: https://github.com/apache/ignite/pull/4656 IGNITE-9440 control.sh --wal delete do not delete files Do not delete the files by the utility on command "control.sh --wal delete". Remain both checkpoints and wal in the archive. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite IGNITE-9440 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4656.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4656 commit d7e976b1247c2efc0c35b8fb679130acf5602dfd Author: a-polyakov Date: 2018-08-31T02:18:42Z IGNITE-9440 control.sh --wal delete do not delete files Signed-off-by: a-polyakov ---
[jira] [Created] (IGNITE-9440) control.sh --wal delete do not delete files
Alexand Polyakov created IGNITE-9440: Summary: control.sh --wal delete do not delete files Key: IGNITE-9440 URL: https://issues.apache.org/jira/browse/IGNITE-9440 Project: Ignite Issue Type: Bug Affects Versions: 2.5 Reporter: Alexand Polyakov Assignee: Alexand Polyakov Do not delete the files by the utility on command "control.sh --wal delete". Remain both checkpoints and wal in the archive. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] ignite pull request #4521: GG-13254 Snapshots: Only Full snapshot should be ...
GitHub user a-polyakov opened a pull request: https://github.com/apache/ignite/pull/4521 GG-13254 Snapshots: Only Full snapshot should be created in case FULL and INC schedules intersected. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-13254 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4521.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4521 commit fab0cc4cb88d5549210a15b00d87d5c10afc4b2c Author: a-polyakov Date: 2018-08-12T05:36:52Z GG-13254 Snapshots: Only Full snapshot should be created in case FULL and INC schedules intersected. Signed-off-by: a-polyakov ---
[jira] [Created] (IGNITE-9122) Control.sh transactions utility not kill hang rollback transaction
Alexand Polyakov created IGNITE-9122: Summary: Control.sh transactions utility not kill hang rollback transaction Key: IGNITE-9122 URL: https://issues.apache.org/jira/browse/IGNITE-9122 Project: Ignite Issue Type: Bug Reporter: Alexand Polyakov Transaction for a long time in status rollback After run "–tx xid XID kill" nothing happens. The transaction displayed in list. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9120) Metadata writer does not propagate error to failure handler
Alexand Polyakov created IGNITE-9120:
Summary: Metadata writer does not propagate error to failure
handler
Key: IGNITE-9120
URL: https://issues.apache.org/jira/browse/IGNITE-9120
Project: Ignite
Issue Type: Bug
Reporter: Alexand Polyakov
In logs
{code:java}
[WARN] [tcp-disco-msg-worker- # 2% DPL_GRID% DplGridNodeName%]
[o.a.i.i.p.c.b.CacheObjectBinaryProcessorImpl] Failed to save metadata for
typeId: 978611101; The exception was selected: there was no space left on the
device{code}
Node does not shut down
With time, detected endless transactions.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-8991) Failed server node if predicate in scan query throw AssertionError
Alexand Polyakov created IGNITE-8991: Summary: Failed server node if predicate in scan query throw AssertionError Key: IGNITE-8991 URL: https://issues.apache.org/jira/browse/IGNITE-8991 Project: Ignite Issue Type: Improvement Components: cache Affects Versions: 2.5 Reporter: Alexand Polyakov -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] ignite pull request #4128: IGNITE-8620 Remove intOrder and loc keys from nod...
GitHub user a-polyakov opened a pull request: https://github.com/apache/ignite/pull/4128 IGNITE-8620 Remove intOrder and loc keys from node info in control.sh --tx utility You can merge this pull request into a Git repository by running: $ git pull https://github.com/a-polyakov/ignite IGNITE-8620 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4128.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4128 commit d6539014902a69e5ab2766f550f51c82713b09dd Author: a-polyakov Date: 2018-06-05T07:00:59Z IGNITE-8620 Remove intOrder and loc keys from node info in control.sh --tx utility ---
[GitHub] ignite pull request #4069: IGNITE-8467 fix filter minSize for transactions u...
GitHub user a-polyakov opened a pull request: https://github.com/apache/ignite/pull/4069 IGNITE-8467 fix filter minSize for transactions utility control.sh You can merge this pull request into a Git repository by running: $ git pull https://github.com/a-polyakov/ignite IGNITE-8467 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4069.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4069 commit 286870756085d4169dcef775607df10a8bafe3df Author: a-polyakov <polyakov.alexandr.alexandrovich@...> Date: 2018-05-25T11:08:13Z IGNITE-8467 fix filter minSize for transactions utility control.sh and add test ---
[GitHub] ignite pull request #3921: IGNITE-7883 add check property "key configuration...
GitHub user a-polyakov reopened a pull request: https://github.com/apache/ignite/pull/3921 IGNITE-7883 add check property "key configuration" in cache configuration â¦tions You can merge this pull request into a Git repository by running: $ git pull https://github.com/a-polyakov/ignite IGNITE-7883 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/3921.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #3921 commit f1e77e4daf9d9389d078954dfaa91cd5bba37494 Author: a-polyakov <polyakov.alexandr.alexandrovich@...> Date: 2018-05-17T13:59:35Z IGNITE-7883 add check property "key configuration" in cache configurations ---
[GitHub] ignite pull request #3921: IGNITE-7883 add check property "key configuration...
Github user a-polyakov closed the pull request at: https://github.com/apache/ignite/pull/3921 ---
[GitHub] ignite pull request #3921: IGNITE-7883 add check property "key configuration...
GitHub user a-polyakov opened a pull request: https://github.com/apache/ignite/pull/3921 IGNITE-7883 add check property "key configuration" in cache configuration â¦tions You can merge this pull request into a Git repository by running: $ git pull https://github.com/a-polyakov/ignite IGNITE-7883 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/3921.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #3921 commit ed326d0e83699095e3694795350abb213986594e Author: a-polyakov <polyakov.alexandr.alexandrovich@...> Date: 2018-04-26T10:57:06Z IGNITE-7883 add check property "key configuration" in cache configurations ---
