[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)
[jira] [Commented] (IGNITE-7072) IgniteCache.replace(k, v, nv) does not work in binary mode without classes
[
https://issues.apache.org/jira/browse/IGNITE-7072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665090#comment-16665090
]
Ignite TC Bot commented on IGNITE-7072:
---
{panel:title=Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Queries (Binary Objects Simple Mapper){color} [[tests 0 Exit
Code |https://ci.ignite.apache.org/viewLog.html?buildId=2166798]]
{panel}
[TeamCity Run All
Results|http://ci.ignite.apache.org/viewLog.html?buildId=2156199buildTypeId=IgniteTests24Java8_RunAll]
> IgniteCache.replace(k, v, nv) does not work in binary mode without classes
> --
>
> Key: IGNITE-7072
> URL: https://issues.apache.org/jira/browse/IGNITE-7072
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Reporter: Pavel Tupitsyn
>Assignee: Igor Sapego
>Priority: Major
> Fix For: 2.8
>
>
> {{IgniteCache.replace(K key, V oldVal, V newVal)}} method deserializes cache
> values in order to compare them, which causes exception when classes are not
> present on server:
> {code}
> class org.apache.ignite.IgniteCheckedException: Unknown pair [platformId=0,
> typeId=-1690383137]
> at
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7260)
> at
> org.apache.ignite.internal.processors.cache.GridCacheContext.isAll(GridCacheContext.java:1242)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.onEntriesLocked(GridDhtTxPrepareFuture.java:464)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.prepare0(GridDhtTxPrepareFuture.java:1223)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.mapIfLocked(GridDhtTxPrepareFuture.java:666)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.prepare(GridDhtTxPrepareFuture.java:1040)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.prepareAsyncLocal(GridNearTxLocal.java:3452)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.prepareColocatedTx(IgniteTxHandler.java:257)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearOptimisticTxPrepareFuture.proceedPrepare(GridNearOptimisticTxPrepareFuture.java:574)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearOptimisticTxPrepareFuture.prepareSingle(GridNearOptimisticTxPrepareFuture.java:401)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearOptimisticTxPrepareFuture.prepare0(GridNearOptimisticTxPrepareFuture.java:344)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearOptimisticTxPrepareFutureAdapter.prepareOnTopology(GridNearOptimisticTxPrepareFutureAdapter.java:137)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearOptimisticTxPrepareFutureAdapter.prepare(GridNearOptimisticTxPrepareFutureAdapter.java:74)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.prepareNearTxLocal(GridNearTxLocal.java:3161)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.commitNearTxLocalAsync(GridNearTxLocal.java:3221)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.optimisticPutFuture(GridNearTxLocal.java:2391)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.putAsync0(GridNearTxLocal.java:622)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.putAsync(GridNearTxLocal.java:385)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter$34.op(GridCacheAdapter.java:2707)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter$AsyncOp.op(GridCacheAdapter.java:5120)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.asyncOp(GridCacheAdapter.java:4260)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter$AsyncOpRetryFuture.execute(GridCacheAdapter.java:4841)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.asyncOp(GridCacheAdapter.java:4173)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.putAsync0(GridCacheAdapter.java:2705)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.putAsync(GridCacheAdapter.java:2689)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.replaceAsync(GridCacheAdapter.java:2776)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.replaceAsync(IgniteCacheProxyImpl.java:1182)
> at
>
[jira] [Commented] (IGNITE-9910) [ML] Move the static copy-pasted datasets from examples to special Util class
[ https://issues.apache.org/jira/browse/IGNITE-9910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665148#comment-16665148 ] ASF GitHub Bot commented on IGNITE-9910: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5028 > [ML] Move the static copy-pasted datasets from examples to special Util class > - > > Key: IGNITE-9910 > URL: https://issues.apache.org/jira/browse/IGNITE-9910 > Project: Ignite > Issue Type: Improvement > Components: ml >Affects Versions: 2.8 >Reporter: Aleksey Zinoviev >Assignee: Aleksey Zinoviev >Priority: Major > Fix For: 2.8 > > > There are a few copy-pasted datasets like Iris, Titanic and etc. > They should be refactored to one dataset class with constants -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10022) JS, PHP thin clients: a more meaningful exception when ENUM type is not registered
Alexey Kosenchuk created IGNITE-10022: - Summary: JS, PHP thin clients: a more meaningful exception when ENUM type is not registered Key: IGNITE-10022 URL: https://issues.apache.org/jira/browse/IGNITE-10022 Project: Ignite Issue Type: Bug Components: thin client Affects Versions: 2.7 Reporter: Alexey Kosenchuk Assignee: ekaterina.vergizova NodeJS and PHP thin clients should throw a more meaningful exception for put/get ENUM type data in case the ENUM type is not registered. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9418) Avoid initialize file page store manager for caches during PME synchronously
[ https://issues.apache.org/jira/browse/IGNITE-9418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665242#comment-16665242 ] Sergey Chugunov commented on IGNITE-9418: - [~zstan], Although overall change looks good to me I left a comment in gitHub pull request. I think we should pay more attention to exception handling during lazy store initialization and call FailureHandler explicitly when something goes wrong. > Avoid initialize file page store manager for caches during PME synchronously > > > Key: IGNITE-9418 > URL: https://issues.apache.org/jira/browse/IGNITE-9418 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.5 >Reporter: Pavel Kovalenko >Assignee: Stanilovsky Evgeny >Priority: Critical > Fix For: 2.8 > > > Currently, we do creation for partition and index files during PME for > starting caches at the beginning of > org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager#readCheckpointAndRestoreMemory > method. > We should avoid this because sometimes it took a long time as we perform > writing to disk. > If the cache was registered during PME we should initialize page store lazy > or asynchronously. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10004) Parse error leads to leave the transaction
[
https://issues.apache.org/jira/browse/IGNITE-10004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov updated IGNITE-10004:
---
Description:
1. Start 2 nodes + connect sqlline
2. Execute following queries:
{noformat}
create table t10 (a int, b varchar, primary key(a)) with
"ATOMICITY=TRANSACTIONAL_SNAPSHOT,backups=1";
begin;
insert into t10 values(1); <- wrong set
insert into t10 values(2, '2'); <- correct set
commit;
{noformat}
The output:
{noformat}
0: jdbc:ignite:thin://127.0.0.1/> create table t10 (a int, b varchar, primary
key(a)) with "ATOMICITY=TRANSACTIONAL_SNAP
SHOT,backups=1";
No rows affected (0,032 seconds)
0: jdbc:ignite:thin://127.0.0.1/> begin;
No rows affected (0 seconds)
0: jdbc:ignite:thin://127.0.0.1/> insert into t10 values(1);
Error: Failed to parse query. ═хтхЁэюх ъюышўхёЄтю ёЄюысЎют
Column count does not match; SQL statement:
insert into t10 values(1) [21002-197] (state=42000,code=1001)
java.sql.SQLException: Failed to parse query. Неверное количество столбцов
Column count does not match; SQL statement:
insert into t10 values(1) [21002-197]
at
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:750)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
at sqlline.Commands.execute(Commands.java:823)
at sqlline.Commands.sql(Commands.java:733)
at sqlline.SqlLine.dispatch(SqlLine.java:795)
at sqlline.SqlLine.begin(SqlLine.java:668)
at sqlline.SqlLine.start(SqlLine.java:373)
at sqlline.SqlLine.main(SqlLine.java:265)
0: jdbc:ignite:thin://127.0.0.1/> insert into t10 values(2, '2');
Error: Transaction is already completed. (state=25000,code=5004)
java.sql.SQLException: Transaction is already completed.
at
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:750)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
at sqlline.Commands.execute(Commands.java:823)
at sqlline.Commands.sql(Commands.java:733)
at sqlline.SqlLine.dispatch(SqlLine.java:795)
at sqlline.SqlLine.begin(SqlLine.java:668)
at sqlline.SqlLine.start(SqlLine.java:373)
at sqlline.SqlLine.main(SqlLine.java:265)
{noformat}
was:
1. Start 2 nodes + connect sqlline
2. Execute following queries:
{noformat}
create table t10 (a int, b varchar, primary key(a)) with
"ATOMICITY=TRANSACTIONAL_SNAPSHOT,backups=1";
begin;
insert into t10 values(1); <- worng set
insert into t10 values(2, '2'); <- coorect set
commit;
{noformat}
The output:
{noformat}
0: jdbc:ignite:thin://127.0.0.1/> create table t10 (a int, b varchar, primary
key(a)) with "ATOMICITY=TRANSACTIONAL_SNAP
SHOT,backups=1";
No rows affected (0,032 seconds)
0: jdbc:ignite:thin://127.0.0.1/> begin;
No rows affected (0 seconds)
0: jdbc:ignite:thin://127.0.0.1/> insert into t10 values(1);
Error: Failed to parse query. ═хтхЁэюх ъюышўхёЄтю ёЄюысЎют
Column count does not match; SQL statement:
insert into t10 values(1) [21002-197] (state=42000,code=1001)
java.sql.SQLException: Failed to parse query. Неверное количество столбцов
Column count does not match; SQL statement:
insert into t10 values(1) [21002-197]
at
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:750)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
at sqlline.Commands.execute(Commands.java:823)
at sqlline.Commands.sql(Commands.java:733)
at sqlline.SqlLine.dispatch(SqlLine.java:795)
at sqlline.SqlLine.begin(SqlLine.java:668)
at sqlline.SqlLine.start(SqlLine.java:373)
at sqlline.SqlLine.main(SqlLine.java:265)
0: jdbc:ignite:thin://127.0.0.1/> insert into t10 values(2, '2');
Error: Transaction is already completed. (state=25000,code=5004)
java.sql.SQLException: Transaction is already completed.
at
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:750)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
at sqlline.Commands.execute(Commands.java:823)
at sqlline.Commands.sql(Commands.java:733)
at sqlline.SqlLine.dispatch(SqlLine.java:795)
at sqlline.SqlLine.begin(SqlLine.java:668)
at sqlline.SqlLine.start(SqlLine.java:373)
at
[jira] [Commented] (IGNITE-10028) Incorrect handling of page on replacement
[ https://issues.apache.org/jira/browse/IGNITE-10028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665318#comment-16665318 ] ASF GitHub Bot commented on IGNITE-10028: - GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/5093 IGNITE-10028 Incorrect handling of page on replacement You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-10028 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5093.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 #5093 commit 26c25b1a64ba950cbfdd0580928af286308a7552 Author: vd-pyatkov Date: 2018-10-26T15:43:44Z IGNITE-10028 Incorrect handling of page on replacement > Incorrect handling of page on replacement > - > > Key: IGNITE-10028 > URL: https://issues.apache.org/jira/browse/IGNITE-10028 > Project: Ignite > Issue Type: Bug >Reporter: Vladislav Pyatkov >Assignee: Vladislav Pyatkov >Priority: Major > > We can to pass incorrect page version to IgniteCacheSnapshotManager. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9009) Local continuous query listeners may be called on partition reassignment
[
https://issues.apache.org/jira/browse/IGNITE-9009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665317#comment-16665317
]
Ignite TC Bot commented on IGNITE-9009:
---
{panel:title=No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity Run All
Results|http://ci.ignite.apache.org/viewLog.html?buildId=2153738buildTypeId=IgniteTests24Java8_RunAll]
> Local continuous query listeners may be called on partition reassignment
>
>
> Key: IGNITE-9009
> URL: https://issues.apache.org/jira/browse/IGNITE-9009
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Denis Mekhanikov
>Assignee: Denis Mekhanikov
>Priority: Major
> Fix For: 2.8
>
> Attachments: ContinuousQueryReassignmentTest.java
>
>
> When a node becomes primary for some partitions, then local continuous query
> listeners receive updates on entries from that partitions. Such invocations
> shouldn't happen.
> Attached test class demonstrates this behaviour.
> Dev list discussion:
> http://apache-ignite-developers.2346864.n4.nabble.com/Backup-queue-for-local-continuous-query-td33391.html
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10019) Documentation: partition preloading
[ https://issues.apache.org/jira/browse/IGNITE-10019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-10019: -- Ignite Flags: (was: Docs Required) > Documentation: partition preloading > --- > > Key: IGNITE-10019 > URL: https://issues.apache.org/jira/browse/IGNITE-10019 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Alexei Scherbakov >Assignee: Artem Budnikov >Priority: Major > Fix For: 2.8 > > > We have to add documentation for partition preloading feature: > IgniteCache.preloadPartition -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7196) Exchange can stuck and wait while new node restoring state from disk and starting caches
[
https://issues.apache.org/jira/browse/IGNITE-7196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665071#comment-16665071
]
Ignite TC Bot commented on IGNITE-7196:
---
{panel:title=No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity Run All
Results|http://ci.ignite.apache.org/viewLog.html?buildId=2164249buildTypeId=IgniteTests24Java8_RunAll]
> Exchange can stuck and wait while new node restoring state from disk and
> starting caches
>
>
> Key: IGNITE-7196
> URL: https://issues.apache.org/jira/browse/IGNITE-7196
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.3
>Reporter: Mikhail Cherkasov
>Assignee: Maxim Muzafarov
>Priority: Critical
> Fix For: 2.8
>
>
> Exchange can stuck and wait while new node restoring state from disk and
> starting caches, there's a log snippet from a just joined new node that shows
> the issue:
> {noformat}
> [21:36:13,023][INFO][exchange-worker-#62%statement_grid%][time] Started
> exchange init [topVer=AffinityTopologyVersion [topVer=57, minorTopVer=0],
> crd=false, evt=NODE_JOINED, evtNode=3ac1160e-0de4-41bc-a366-59292c9f03c1,
> customEvt=null, allowMerge=true]
> [21:36:13,023][INFO][exchange-worker-#62%statement_grid%][FilePageStoreManager]
> Resolved page store work directory:
> /mnt/store/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463
> [21:36:13,024][INFO][exchange-worker-#62%statement_grid%][FileWriteAheadLogManager]
> Resolved write ahead log work directory:
> /mnt/wal/WAL/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463
> [21:36:13,024][INFO][exchange-worker-#62%statement_grid%][FileWriteAheadLogManager]
> Resolved write ahead log archive directory:
> /mnt/wal/WAL_archive/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463
> [21:36:13,046][INFO][exchange-worker-#62%statement_grid%][FileWriteAheadLogManager]
> Started write-ahead log manager [mode=DEFAULT]
> [21:36:13,065][INFO][exchange-worker-#62%statement_grid%][PageMemoryImpl]
> Started page memory [memoryAllocated=100.0 MiB, pages=6352, tableSize=373.4
> KiB, checkpointBuffer=100.0 MiB]
> [21:36:13,105][INFO][exchange-worker-#62%statement_grid%][PageMemoryImpl]
> Started page memory [memoryAllocated=32.0 GiB, pages=2083376, tableSize=119.6
> MiB, checkpointBuffer=896.0 MiB]
> [21:36:13,428][INFO][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager]
> Read checkpoint status
> [startMarker=/mnt/store/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463/cp/1512930965253-306c0895-1f5f-4237-bebf-8bf2b49682af-START.bin,
>
> endMarker=/mnt/store/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463/cp/1512930869357-1c24b6dc-d64c-4b83-8166-11edf1bfdad3-END.bin]
> [21:36:13,429][INFO][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager]
> Checking memory state [lastValidPos=FileWALPointer [idx=3582,
> fileOffset=59186076, len=9229, forceFlush=false], lastMarked=FileWALPointer
> [idx=3629, fileOffset=50829700, len=9229, forceFlush=false],
> lastCheckpointId=306c0895-1f5f-4237-bebf-8bf2b49682af]
> [21:36:13,429][WARNING][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager]
> Ignite node stopped in the middle of checkpoint. Will restore memory state
> and finish checkpoint on node start.
> [21:36:18,312][INFO][grid-nio-worker-tcp-comm-0-#41%statement_grid%][TcpCommunicationSpi]
> Accepted incoming communication connection [locAddr=/172.31.20.209:48100,
> rmtAddr=/172.31.17.115:57148]
> [21:36:21,619][INFO][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager]
> Found last checkpoint marker [cpId=306c0895-1f5f-4237-bebf-8bf2b49682af,
> pos=FileWALPointer [idx=3629, fileOffset=50829700, len=9229,
> forceFlush=false]]
> [21:36:21,620][INFO][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager]
> Finished applying memory changes [changesApplied=165103, time=8189ms]
> [21:36:22,403][INFO][grid-nio-worker-tcp-comm-1-#42%statement_grid%][TcpCommunicationSpi]
> Accepted incoming communication connection [locAddr=/172.31.20.209:48100,
> rmtAddr=/172.31.28.10:47964]
> [21:36:23,414][INFO][grid-nio-worker-tcp-comm-2-#43%statement_grid%][TcpCommunicationSpi]
> Accepted incoming communication connection [locAddr=/172.31.20.209:48100,
> rmtAddr=/172.31.27.101:46000]
> [21:36:33,019][WARNING][main][GridCachePartitionExchangeManager] Failed to
> wait for initial partition map exchange. Possible reasons are:
> ^-- Transactions in deadlock.
> ^-- Long running transactions (ignore if this is the case).
> ^-- Unreleased explicit locks.
> [21:36:53,021][WARNING][main][GridCachePartitionExchangeManager] Still
> waiting for initial partition map exchange
> [fut=GridDhtPartitionsExchangeFuture [firstDiscoEvt=DiscoveryEvent
>
[jira] [Commented] (IGNITE-9849) Remove invalid builds from the selection
[ https://issues.apache.org/jira/browse/IGNITE-9849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665099#comment-16665099 ] ASF GitHub Bot commented on IGNITE-9849: SomeFire commented on a change in pull request #38: IGNITE-9849 Remove invalid builds from the selection URL: https://github.com/apache/ignite-teamcity-bot/pull/38#discussion_r228495040 ## File path: ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/tcbot/condition/BuildCondition.java ## @@ -0,0 +1,91 @@ +/* + * Licensed to the Apache Software Foundation (ASF) under one or more + * contributor license agreements. See the NOTICE file distributed with + * this work for additional information regarding copyright ownership. + * The ASF licenses this file to You under the Apache License, Version 2.0 + * (the "License"); you may not use this file except in compliance with + * the License. You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, software + * distributed under the License is distributed on an "AS IS" BASIS, + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + * See the License for the specific language governing permissions and + * limitations under the License. + */ + +package org.apache.ignite.ci.tcbot.condition; + +import java.util.Date; +import java.util.Objects; + +/** + * Mark build as valid or invalid. Review comment: Clarify here: what is valid/invalid build? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Remove invalid builds from the selection > > > Key: IGNITE-9849 > URL: https://issues.apache.org/jira/browse/IGNITE-9849 > Project: Ignite > Issue Type: Sub-task >Reporter: Nikolai Kulagin >Assignee: Nikolai Kulagin >Priority: Minor > > In selection sometimes there are builds with abnormal values. For example, > the average number of failed tests is 25. But in the build [1953935] there > are 2939 failed tests. This is an anomalous value. Need to add the ability to > remove it from the selection. Build [1953935] - not valid. > In total, > 1. While clicking on a point on the chart, show a button that allows marking > a build invalid and excludes it from further selections. > 2. Reduce the number of erroneous exceptions. Compare the value with the > average, if the difference is small - ask for confirmation of the operation. > 3. Add the ability to return an excluded build to the selection. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9849) Remove invalid builds from the selection
[ https://issues.apache.org/jira/browse/IGNITE-9849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665100#comment-16665100 ] ASF GitHub Bot commented on IGNITE-9849: SomeFire commented on a change in pull request #38: IGNITE-9849 Remove invalid builds from the selection URL: https://github.com/apache/ignite-teamcity-bot/pull/38#discussion_r228498911 ## File path: ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/web/rest/build/GetBuildTestFailures.java ## @@ -210,10 +255,10 @@ public BuildsHistory getBuildsHistory( if (Boolean.valueOf(skipTests)) builder.skipTests(); -BuildsHistory buildsHistory = builder.build(); +BuildsHistory buildsHist = builder.build(); -buildsHistory.initialize(ICredentialsProv.get(req), ctx); +buildsHist.initialize(ICredentialsProv.get(req), ctx); Review comment: Move authorization check outside of `initialize`. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Remove invalid builds from the selection > > > Key: IGNITE-9849 > URL: https://issues.apache.org/jira/browse/IGNITE-9849 > Project: Ignite > Issue Type: Sub-task >Reporter: Nikolai Kulagin >Assignee: Nikolai Kulagin >Priority: Minor > > In selection sometimes there are builds with abnormal values. For example, > the average number of failed tests is 25. But in the build [1953935] there > are 2939 failed tests. This is an anomalous value. Need to add the ability to > remove it from the selection. Build [1953935] - not valid. > In total, > 1. While clicking on a point on the chart, show a button that allows marking > a build invalid and excludes it from further selections. > 2. Reduce the number of erroneous exceptions. Compare the value with the > average, if the difference is small - ask for confirmation of the operation. > 3. Add the ability to return an excluded build to the selection. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9849) Remove invalid builds from the selection
[
https://issues.apache.org/jira/browse/IGNITE-9849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665098#comment-16665098
]
ASF GitHub Bot commented on IGNITE-9849:
SomeFire commented on a change in pull request #38: IGNITE-9849 Remove invalid
builds from the selection
URL: https://github.com/apache/ignite-teamcity-bot/pull/38#discussion_r228497136
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/tcbot/condition/BuildConditionDao.java
##
@@ -0,0 +1,78 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.ignite.ci.tcbot.condition;
+
+import javax.inject.Inject;
+import javax.inject.Provider;
+import org.apache.ignite.Ignite;
+import org.apache.ignite.IgniteCache;
+import org.apache.ignite.ci.db.TcHelperDb;
+import org.apache.ignite.ci.teamcity.ignited.IStringCompactor;
+
+public class BuildConditionDao {
+/** Cache name*/
+public static final String BUILD_CONDITIONS_CACHE_NAME = "buildConditions";
+
+/** Ignite provider. */
+@Inject private Provider igniteProvider;
+
+/** Builds cache. */
+private IgniteCache buildsCache;
+
+/** Compactor. */
+@Inject private IStringCompactor compactor;
+
+/**
+ * Initialize
+ */
+public void init () {
+Ignite ignite = igniteProvider.get();
+buildsCache =
ignite.getOrCreateCache(TcHelperDb.getCacheV2Config(BUILD_CONDITIONS_CACHE_NAME));
+}
+
+/**
+ * @param srvIdMaskHigh Server id mask high.
+ * @param buildId Build id.
+ */
+private long buildIdToCacheKey(long srvIdMaskHigh, int buildId) {
+
Review comment:
Remove empty line.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Remove invalid builds from the selection
>
>
> Key: IGNITE-9849
> URL: https://issues.apache.org/jira/browse/IGNITE-9849
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Minor
>
> In selection sometimes there are builds with abnormal values. For example,
> the average number of failed tests is 25. But in the build [1953935] there
> are 2939 failed tests. This is an anomalous value. Need to add the ability to
> remove it from the selection. Build [1953935] - not valid.
> In total,
> 1. While clicking on a point on the chart, show a button that allows marking
> a build invalid and excludes it from further selections.
> 2. Reduce the number of erroneous exceptions. Compare the value with the
> average, if the difference is small - ask for confirmation of the operation.
> 3. Add the ability to return an excluded build to the selection.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9622) MVCC Cache API: prohibit non PESSIMISTIC REPEATABLE_READ transactions
[
https://issues.apache.org/jira/browse/IGNITE-9622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665125#comment-16665125
]
Ignite TC Bot commented on IGNITE-9622:
---
{panel:title=No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity Run All
Results|http://ci.ignite.apache.org/viewLog.html?buildId=2162726buildTypeId=IgniteTests24Java8_RunAll]
> MVCC Cache API: prohibit non PESSIMISTIC REPEATABLE_READ transactions
> -
>
> Key: IGNITE-9622
> URL: https://issues.apache.org/jira/browse/IGNITE-9622
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Ivan Pavlukhin
>Assignee: Ivan Pavlukhin
>Priority: Major
> Fix For: 2.8
>
>
> For cache with enabled mvcc we should allow running only PESSIMISTIC
> REPEATABLE_READ transactions. For other modes exception should be thrown
> (like is done for SQL API).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9991) thin clients: can't use array as cache key for PHP, JS and Python clients
[
https://issues.apache.org/jira/browse/IGNITE-9991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego updated IGNITE-9991:
Priority: Minor (was: Major)
> thin clients: can't use array as cache key for PHP, JS and Python clients
> -
>
> Key: IGNITE-9991
> URL: https://issues.apache.org/jira/browse/IGNITE-9991
> Project: Ignite
> Issue Type: Bug
> Components: thin client
>Affects Versions: 2.7
>Reporter: Stepan Pilschikov
>Priority: Minor
>
> Trying to put cache with key as values array
> Put Py code
> {code}
> cache = client.get_or_create_cache("PY_BOOLEAN_ARRAY")
> cache.put([True, False], 1, key_hint=BoolArrayObject, value_hint=IntObject)
> {code}
> Get
> {code}
> cache = client.get_or_create_cache("PY_BOOLEAN_ARRAY")
> print(cache.get([True, False] key_hint=BoolArrayObject))
> {code}
> output: null
> Same thing with PHP, JS clients and all others array data types
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9991) thin clients: can't use array as cache key for PHP, JS and Python clients
[
https://issues.apache.org/jira/browse/IGNITE-9991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665253#comment-16665253
]
Stepan Pilschikov commented on IGNITE-9991:
---
[~alexey.kosenchuk] [~Melnichuk]
Oh, ive tried. but used List, now understand that i was wrong, sorry
> thin clients: can't use array as cache key for PHP, JS and Python clients
> -
>
> Key: IGNITE-9991
> URL: https://issues.apache.org/jira/browse/IGNITE-9991
> Project: Ignite
> Issue Type: Bug
> Components: thin client
>Affects Versions: 2.7
>Reporter: Stepan Pilschikov
>Priority: Minor
>
> Trying to put cache with key as values array
> Put Py code
> {code}
> cache = client.get_or_create_cache("PY_BOOLEAN_ARRAY")
> cache.put([True, False], 1, key_hint=BoolArrayObject, value_hint=IntObject)
> {code}
> Get
> {code}
> cache = client.get_or_create_cache("PY_BOOLEAN_ARRAY")
> print(cache.get([True, False] key_hint=BoolArrayObject))
> {code}
> output: null
> Same thing with PHP, JS clients and all others array data types
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10026) [ML] Broken example: GaussianNaiveBayesTrainerExample
Yury Babak created IGNITE-10026: --- Summary: [ML] Broken example: GaussianNaiveBayesTrainerExample Key: IGNITE-10026 URL: https://issues.apache.org/jira/browse/IGNITE-10026 Project: Ignite Issue Type: Bug Components: ml Affects Versions: 2.8 Reporter: Yury Babak Assignee: Yury Babak Fix For: 2.8 Broken example: GaussianNaiveBayesTrainerExample -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-10024) MVCC TX: Stackoverflow during DhtEnlistFuture mapping
[
https://issues.apache.org/jira/browse/IGNITE-10024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Pavlukhin reassigned IGNITE-10024:
---
Assignee: Ivan Pavlukhin
> MVCC TX: Stackoverflow during DhtEnlistFuture mapping
> -
>
> Key: IGNITE-10024
> URL: https://issues.apache.org/jira/browse/IGNITE-10024
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Assignee: Ivan Pavlukhin
>Priority: Major
> Fix For: 2.7
>
>
> There is possible stack overflow error in {{GridNearTxAbstractEnlistFuture}}
> mapping. It should be investigated.
>
> {code:java}
> [16:19:22]W: [org.apache.ignite:ignite-core] [16:19:22] (err) Failed
> to notify listener:
> o.a.i.i.processors.timeout.GridTimeoutProcessor$2...@1f088f2cjava.lang.StackOverflowError
> [16:19:22]W: [org.apache.ignite:ignite-core]at
> java.lang.ThreadLocal.set(ThreadLocal.java:201)
> [16:19:22]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.GridCacheMvccManager.contextReset(GridCacheMvccManager.java:882)
> [16:19:22]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.GridCacheSharedContext.txContextReset(GridCacheSharedContext.java:1101)
> [16:19:22]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxAbstractEnlistFuture.lambda$mapOnTopology$23be56e8$1(GridNearTxAbstractEnlistFuture.java:342)
> [16:19:22]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.timeout.GridTimeoutProcessor.waitAsync(GridTimeoutProcessor.java:155)
> [16:19:22]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxAbstractEnlistFuture.mapOnTopology(GridNearTxAbstractEnlistFuture.java:334)
> [16:19:22]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxAbstractEnlistFuture.lambda$mapOnTopology$23be56e8$1(GridNearTxAbstractEnlistFuture.java:339)
> [16:19:22]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.timeout.GridTimeoutProcessor.waitAsync(GridTimeoutProcessor.java:155)
> [16:19:22]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxAbstractEnlistFuture.mapOnTopology(GridNearTxAbstractEnlistFuture.java:334)
> [16:19:22]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxAbstractEnlistFuture.lambda$mapOnTopology$23be56e8$1(GridNearTxAbstractEnlistFuture.java:339)
> [16:19:22]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.timeout.GridTimeoutProcessor.waitAsync(GridTimeoutProcessor.java:155)
> [16:19:22]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxAbstractEnlistFuture.mapOnTopology(GridNearTxAbstractEnlistFuture.java:334)
> [16:19:22]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxAbstractEnlistFuture.lambda$mapOnTopology$23be56e8$1(GridNearTxAbstractEnlistFuture.java:339)
> [16:19:22]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.timeout.GridTimeoutProcessor.waitAsync(GridTimeoutProcessor.java:155)
> [16:19:22]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxAbstractEnlistFuture.mapOnTopology(GridNearTxAbstractEnlistFuture.java:334)
> [16:19:22]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxAbstractEnlistFuture.lambda$mapOnTopology$23be56e8$1(GridNearTxAbstractEnlistFuture.java:339)
> [16:19:22]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.timeout.GridTimeoutProcessor.waitAsync(GridTimeoutProcessor.java:155)
> [16:19:22]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxAbstractEnlistFuture.mapOnTopology(GridNearTxAbstractEnlistFuture.java:334)
> [16:19:22]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxAbstractEnlistFuture.lambda$mapOnTopology$23be56e8$1(GridNearTxAbstractEnlistFuture.java:339)
> [16:19:22]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.timeout.GridTimeoutProcessor.waitAsync(GridTimeoutProcessor.java:155)
> [16:19:22]W:
[jira] [Commented] (IGNITE-10026) [ML] Broken example: GaussianNaiveBayesTrainerExample
[ https://issues.apache.org/jira/browse/IGNITE-10026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665268#comment-16665268 ] ASF GitHub Bot commented on IGNITE-10026: - GitHub user YuriBabak opened a pull request: https://github.com/apache/ignite/pull/5090 IGNITE-10026: [ML] Broken example: GaussianNaiveBayesTrainerExample fixed You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10026 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5090.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 #5090 commit 02da1edf7b8e90a307df374d45196b0b691c0e32 Author: YuriBabak Date: 2018-10-26T14:54:21Z IGNITE-10026: [ML] Broken example: GaussianNaiveBayesTrainerExample fixed > [ML] Broken example: GaussianNaiveBayesTrainerExample > -- > > Key: IGNITE-10026 > URL: https://issues.apache.org/jira/browse/IGNITE-10026 > Project: Ignite > Issue Type: Bug > Components: ml >Affects Versions: 2.8 >Reporter: Yury Babak >Assignee: Yury Babak >Priority: Major > Fix For: 2.8 > > > Broken example: GaussianNaiveBayesTrainerExample -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9849) Remove invalid builds from the selection
[
https://issues.apache.org/jira/browse/IGNITE-9849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665095#comment-16665095
]
ASF GitHub Bot commented on IGNITE-9849:
asfgit closed pull request #38: IGNITE-9849 Remove invalid builds from the
selection
URL: https://github.com/apache/ignite-teamcity-bot/pull/38
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git
a/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/tcbot/condition/BuildCondition.java
b/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/tcbot/condition/BuildCondition.java
new file mode 100644
index 000..6a1e0fa
--- /dev/null
+++
b/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/tcbot/condition/BuildCondition.java
@@ -0,0 +1,91 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.ignite.ci.tcbot.condition;
+
+import java.util.Date;
+import java.util.Objects;
+
+/**
+ * Mark build as valid or invalid.
+ */
+public class BuildCondition {
+/** Build id. */
+public int buildId;
+
+/** Username. */
+public String username;
+
+/** Is valid. */
+public boolean isValid;
+
+/** Date. */
+public Date date;
+
+/** Field, where build was marked. */
+public String field;
+
+/**
+ * Default constructor.
+ */
+public BuildCondition(){}
+
+/**
+ * @param buildId Build id.
+ * @param username Username.
+ * @param isValid Is valid.
+ * @param field Field.
+ */
+public BuildCondition(int buildId, String username, boolean isValid,
String field) {
+this.buildId = buildId;
+this.username = username;
+this.isValid = isValid;
+this.date = new Date();
+this.field = field;
+}
+
+/** {@inheritDoc} */
+@Override public String toString() {
+return "BuildCondition{" +
+"buildId=" + buildId +
+", username='" + username + '\'' +
+", isValid=" + isValid +
+", date=" + date +
+", field='" + field + '\'' +
+'}';
+}
+
+/** {@inheritDoc} */
+@Override public boolean equals(Object o) {
+if (this == o)
+return true;
+
+if (!(o instanceof BuildCondition))
+return false;
+
+BuildCondition that = (BuildCondition)o;
+
+return buildId == that.buildId &&
+isValid == that.isValid &&
+Objects.equals(username, that.username);
+}
+
+/** {@inheritDoc} */
+@Override public int hashCode() {
+return Objects.hash(buildId, username, isValid);
+}
+}
diff --git
a/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/tcbot/condition/BuildConditionCompacted.java
b/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/tcbot/condition/BuildConditionCompacted.java
new file mode 100644
index 000..83beee8
--- /dev/null
+++
b/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/tcbot/condition/BuildConditionCompacted.java
@@ -0,0 +1,71 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.ignite.ci.tcbot.condition;
+
+import java.util.Date;
+import
[jira] [Commented] (IGNITE-9753) Control.sh validate index work long and with errors
[ https://issues.apache.org/jira/browse/IGNITE-9753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665155#comment-16665155 ] Ilya Lantukh commented on IGNITE-9753: -- Looks good. > Control.sh validate index work long and with errors > --- > > Key: IGNITE-9753 > URL: https://issues.apache.org/jira/browse/IGNITE-9753 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 2.5 >Reporter: ARomantsov >Assignee: Ivan Daschinskiy >Priority: Major > Fix For: 2.8 > > > Errors - > [12:19:54][:666] IndexValidationIssue [key=null, cacheName=cache_name_1, > idxName=_key_PK_hash], class java.lang.NullPointerException: null > [12:19:54][:666] IndexValidationIssue [key=null, cacheName=cache_name_2, > idxName=_key_PK_hash], class java.lang.NullPointerException: null -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-9982) SQLLine: can't run with option --autoCommit=false or true
[
https://issues.apache.org/jira/browse/IGNITE-9982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665246#comment-16665246
]
Ivan Pavlukhin edited comment on IGNITE-9982 at 10/26/18 2:27 PM:
--
TC runs:
*SQL (failed tests were introduced by this ticket fixes, were fixed and rerun
locally)
https://ci.ignite.apache.org/viewLog.html?buildId=2166855=buildResultsDiv=IgniteTests24Java8_RunAllSql
* MVCC JDBC
https://ci.ignite.apache.org/viewLog.html?buildId=2166839=buildResultsDiv=IgniteTests24Java8_MvccCache
* MVCC Queries
https://ci.ignite.apache.org/viewLog.html?buildId=2167670=buildResultsDiv=IgniteTests24Java8_MvccQueries
* MVCC Cache
https://ci.ignite.apache.org/viewLog.html?buildId=2166843=buildResultsDiv=IgniteTests24Java8_MvccCache_2
All other failures seems flaky.
was (Author: pavlukhin):
TC runs:
SQL (failed tests were introduced by this ticket fixes, were fixed and rerun
locally)
https://ci.ignite.apache.org/viewLog.html?buildId=2166855=buildResultsDiv=IgniteTests24Java8_RunAllSql
MVCC JDBC
https://ci.ignite.apache.org/viewLog.html?buildId=2166839=buildResultsDiv=IgniteTests24Java8_MvccCache
> SQLLine: can't run with option --autoCommit=false or true
> -
>
> Key: IGNITE-9982
> URL: https://issues.apache.org/jira/browse/IGNITE-9982
> Project: Ignite
> Issue Type: Bug
> Components: mvcc, sql
>Affects Versions: 2.7
>Reporter: Stepan Pilschikov
>Assignee: Ivan Pavlukhin
>Priority: Major
> Fix For: 2.7
>
>
> Trying to run sqlline with additional options
> {code}
> $ /bin/sqlline.sh --autoCommit=false --color=true --outputFormat=csv
> --showNestedErrs=true --showWarnings=true --verbose=true -u
> jdbc:ignite:thin://127.0.0.1:10800
> {code}
> SQLline is working but with exception on start:
> {code}
> issuing: !connect jdbc:ignite:thin://127.0.0.1:10800 '' ''
> org.apache.ignite.IgniteJdbcThinDriver
> Connecting to jdbc:ignite:thin://127.0.0.1:10800
> Connected to: Apache Ignite (version 2.7.1#20181023-sha1:0ccde7c4)
> Driver: Apache Ignite Thin JDBC Driver (version 2.7.1#20181023-sha1:0ccde7c4)
> Error: MVCC must be enabled in order to invoke transactional operation:
> COMMIT (state=25000,code=5002)
> java.sql.SQLException: MVCC must be enabled in order to invoke transactional
> operation: COMMIT
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:750)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.doCommit(JdbcThinConnection.java:369)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.setAutoCommit(JdbcThinConnection.java:328)
> at sqlline.DatabaseConnection.connect(DatabaseConnection.java:178)
> at
> sqlline.DatabaseConnection.getConnection(DatabaseConnection.java:204)
> at sqlline.Commands.connect(Commands.java:1095)
> at sqlline.Commands.connect(Commands.java:1001)
> 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
> sqlline.ReflectiveCommandHandler.execute(ReflectiveCommandHandler.java:38)
> at sqlline.SqlLine.dispatch(SqlLine.java:791)
> at sqlline.SqlLine.initArgs(SqlLine.java:566)
> at sqlline.SqlLine.begin(SqlLine.java:643)
> at sqlline.SqlLine.start(SqlLine.java:373)
> at sqlline.SqlLine.main(SqlLine.java:265)
> Transaction isolation: TRANSACTION_REPEATABLE_READ
> {code}
> Without --autoCommit option sqlline running without this exception
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-9982) SQLLine: can't run with option --autoCommit=false or true
[
https://issues.apache.org/jira/browse/IGNITE-9982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665246#comment-16665246
]
Ivan Pavlukhin edited comment on IGNITE-9982 at 10/26/18 2:27 PM:
--
TC runs:
* SQL (failed tests were introduced by this ticket fixes, were fixed and rerun
locally)
https://ci.ignite.apache.org/viewLog.html?buildId=2166855=buildResultsDiv=IgniteTests24Java8_RunAllSql
* MVCC JDBC
https://ci.ignite.apache.org/viewLog.html?buildId=2166839=buildResultsDiv=IgniteTests24Java8_MvccCache
* MVCC Queries
https://ci.ignite.apache.org/viewLog.html?buildId=2167670=buildResultsDiv=IgniteTests24Java8_MvccQueries
* MVCC Cache
https://ci.ignite.apache.org/viewLog.html?buildId=2166843=buildResultsDiv=IgniteTests24Java8_MvccCache_2
All other failures seems flaky.
was (Author: pavlukhin):
TC runs:
*SQL (failed tests were introduced by this ticket fixes, were fixed and rerun
locally)
https://ci.ignite.apache.org/viewLog.html?buildId=2166855=buildResultsDiv=IgniteTests24Java8_RunAllSql
* MVCC JDBC
https://ci.ignite.apache.org/viewLog.html?buildId=2166839=buildResultsDiv=IgniteTests24Java8_MvccCache
* MVCC Queries
https://ci.ignite.apache.org/viewLog.html?buildId=2167670=buildResultsDiv=IgniteTests24Java8_MvccQueries
* MVCC Cache
https://ci.ignite.apache.org/viewLog.html?buildId=2166843=buildResultsDiv=IgniteTests24Java8_MvccCache_2
All other failures seems flaky.
> SQLLine: can't run with option --autoCommit=false or true
> -
>
> Key: IGNITE-9982
> URL: https://issues.apache.org/jira/browse/IGNITE-9982
> Project: Ignite
> Issue Type: Bug
> Components: mvcc, sql
>Affects Versions: 2.7
>Reporter: Stepan Pilschikov
>Assignee: Ivan Pavlukhin
>Priority: Major
> Fix For: 2.7
>
>
> Trying to run sqlline with additional options
> {code}
> $ /bin/sqlline.sh --autoCommit=false --color=true --outputFormat=csv
> --showNestedErrs=true --showWarnings=true --verbose=true -u
> jdbc:ignite:thin://127.0.0.1:10800
> {code}
> SQLline is working but with exception on start:
> {code}
> issuing: !connect jdbc:ignite:thin://127.0.0.1:10800 '' ''
> org.apache.ignite.IgniteJdbcThinDriver
> Connecting to jdbc:ignite:thin://127.0.0.1:10800
> Connected to: Apache Ignite (version 2.7.1#20181023-sha1:0ccde7c4)
> Driver: Apache Ignite Thin JDBC Driver (version 2.7.1#20181023-sha1:0ccde7c4)
> Error: MVCC must be enabled in order to invoke transactional operation:
> COMMIT (state=25000,code=5002)
> java.sql.SQLException: MVCC must be enabled in order to invoke transactional
> operation: COMMIT
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:750)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.doCommit(JdbcThinConnection.java:369)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.setAutoCommit(JdbcThinConnection.java:328)
> at sqlline.DatabaseConnection.connect(DatabaseConnection.java:178)
> at
> sqlline.DatabaseConnection.getConnection(DatabaseConnection.java:204)
> at sqlline.Commands.connect(Commands.java:1095)
> at sqlline.Commands.connect(Commands.java:1001)
> 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
> sqlline.ReflectiveCommandHandler.execute(ReflectiveCommandHandler.java:38)
> at sqlline.SqlLine.dispatch(SqlLine.java:791)
> at sqlline.SqlLine.initArgs(SqlLine.java:566)
> at sqlline.SqlLine.begin(SqlLine.java:643)
> at sqlline.SqlLine.start(SqlLine.java:373)
> at sqlline.SqlLine.main(SqlLine.java:265)
> Transaction isolation: TRANSACTION_REPEATABLE_READ
> {code}
> Without --autoCommit option sqlline running without this exception
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8902) GridDhtTxRemote sometimes not rolled back in one phase commit scenario.
[
https://issues.apache.org/jira/browse/IGNITE-8902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665260#comment-16665260
]
ASF GitHub Bot commented on IGNITE-8902:
GitHub user ascherbakoff opened a pull request:
https://github.com/apache/ignite/pull/5089
IGNITE-8902 One-phase commit race on tx timeout
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8902
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/5089.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 #5089
commit d0a48b4d31235637fd20fb6247f3ae897d6f0e24
Author: Aleksei Scherbakov
Date: 2018-10-23T16:32:04Z
IGNITE-8873 wip.
commit ae48293d567f3781d426db0e9eaaf641330e894b
Author: Aleksei Scherbakov
Date: 2018-10-24T09:18:45Z
Merge branch 'master' of https://github.com/apache/ignite into ignite-8902
commit 3d11cf7db66cbb5a7b4c31d63942e89514b4f27f
Author: Aleksei Scherbakov
Date: 2018-10-24T13:27:19Z
IGNITE-8873 wip.
commit 1a032c12704a0c31165f672f17bba3c18debb24e
Author: Aleksei Scherbakov
Date: 2018-10-24T13:44:01Z
IGNITE-8873 wip.
commit 97bceb290104245a4990e70e74c2aa06b9aad7b1
Author: Aleksei Scherbakov
Date: 2018-10-25T08:22:08Z
IGNITE-8873 wip.
commit 08ccf4b56ade0b6fcd758293e036f17daca82293
Author: Aleksei Scherbakov
Date: 2018-10-25T13:21:51Z
IGNITE-8902 wip.
commit 1c57f791bc4fe1e7965c66abcef157098ee8f74f
Author: Aleksei Scherbakov
Date: 2018-10-26T14:37:49Z
IGNITE-8902 wip.
commit a185c96cdd391296b57bc9acdd8ea76f7580f89e
Author: Aleksei Scherbakov
Date: 2018-10-26T14:38:30Z
Merge branch 'master' of https://github.com/apache/ignite into ignite-8902
> GridDhtTxRemote sometimes not rolled back in one phase commit scenario.
> ---
>
> Key: IGNITE-8902
> URL: https://issues.apache.org/jira/browse/IGNITE-8902
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexei Scherbakov
>Assignee: Alexei Scherbakov
>Priority: Major
> Fix For: 2.8
>
>
> Near node log:
> {noformat}
> 2018-06-28 18:37:14,541][WARN ][sys-#77] The transaction was forcibly rolled
> back because a timeout is reached:
> GridNearTxLocal[xid=c8c6b184461--0871-da69--0010,
> xidVersion=GridCacheVersion [topVer=141679209, order=1530218114188,
> nodeOrder=16], concurrency=PESSIMISTIC, isolation=REPEATABLE_READ,
> state=MARKED_ROLLBACK, invalidate=false, rollbackOnly=true,
> nodeId=36f1c741-dc02-417a-a27d-fcbc90dd8cf1, timeout=100, duration=101,
> label=null]
> {noformat}
> {noformat}
> [2018-06-28 18:37:14,560][ERROR][pool-356018-thread-1] Timeout (0 sec) is
> exceeded.
> org.apache.ignite.transactions.TransactionTimeoutException: Failed to acquire
> lock within provided timeout for transaction [timeout=100, tx=GridDhtTxLocal
> [nearNodeId=36f1c741-dc02-417a-a27d-fcbc90dd8cf1,
> nearFutId=a8563574461-ec96bd57-6a94-4303-8ff5-56eaac137f30, nearMiniId=1,
> nearFinFutId=null, nearFinMiniId=0, nearXidVer=GridCacheVersion
> [topVer=141679209, order=1530218114188, nodeOrder=16],
> super=GridDhtTxLocalAdapter [nearOnOriginatingNode=false, nearNodes=[],
> dhtNodes=[06630e42-1c4d-4011-a388-4ec1dd1824fd], explicitLock=false,
> super=IgniteTxLocalAdapter [completedBase=null, sndTransformedVals=false,
> depEnabled=false, txState=IgniteTxStateImpl
> [activeCacheIds=[117538306,117541069], recovery=false, txMap=[IgniteTxEntry
> [key=KeyCacheObjectImpl [part=779, val=5899, hasValBytes=true],
> cacheId=117541069, txKey=IgniteTxKey [key=KeyCacheObjectImpl [part=779,
> val=5899, hasValBytes=true], cacheId=117541069], val=[op=UPDATE,
> val=org.apache.ignite.scenario.internal.model.SampleObject
> [idHash=1226505441, hash=-1035741988, balance=100051, salary=1,
> fields=HashMap {field19=iiwxvrhxlpwqyixvpiregkuqpxuhtuir,
> field17=dyyxoefmichqvstteqjkbdpgmevifvmt,
> field18=iakcqzxcswsxncvztsotrjrlreuvpnsv,
> field22=wvewstllgkwvcxxujbkqkoihudgkkyve,
> field23=blgtxqcnwmexardyujbibiconowvyxvh,
> field20=mhvicfpnmptjreacgatiyobrmvvloxic,
> field21=bxajcavvwuhjvpugfoqohgulihzdbymr,
> field26=xceztfgnlpfoyciwnvhkorrgfllveocl,
> field27=sxzqvvckcgxgjctmygsibtouuzkfievo,
> field24=lsidfhurdjgjlmkrxyqbrdjzmbcicxie,
> field25=vfnmohbvezajifkqiwqbdqpulnynumfz,
> field28=zcewigkcryznakzsyzqzfdrbhklycjer,
> field29=vkctdybyrmtbitxuuqdlsrilxayorjjd,
> field11=lbwqnwwpwgewyjvlobyqwnvifuiggzio,
> field12=rmxclhojshtijttdjirppbkyudpvunht,
> field1=gvfrrpwkhmiziaortptiytwhviwjcpcr,
> field31=yktxbcjiyqfpaytacoajsiybtqocmezz,
> field0=vcorrbnevfunwssjzckdjlbvkynbogce,
>
[jira] [Commented] (IGNITE-8873) Optimize cache scans with enabled persistence.
[ https://issues.apache.org/jira/browse/IGNITE-8873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665269#comment-16665269 ] ASF GitHub Bot commented on IGNITE-8873: GitHub user ascherbakoff opened a pull request: https://github.com/apache/ignite/pull/5091 IGNITE-8873 Test fix You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8873 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5091.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 #5091 commit 67fa13bf4f5755aca5f43db0819b9cb19a197496 Author: Aleksei Scherbakov Date: 2018-09-26T09:00:26Z IGNITE-8873 wip. commit 5a9e712161578087f55895072e5d6fde53ab722d Author: Aleksei Scherbakov Date: 2018-09-26T17:13:09Z IGNITE-8873 wip. commit 3653b5e7f6687de34a70ae99988df2c8536d421f Author: ascherbakoff Date: 2018-09-26T21:08:28Z IGNITE-8873 wip. commit 390ab35492f3b54093025fd3bffc2a3798105fc3 Author: Aleksei Scherbakov Date: 2018-10-19T14:00:32Z Merge branch 'master' of https://github.com/apache/ignite into ignite-8873 commit 7ecdc9d01148ab4b2531e29a81250e6c918428a7 Author: Aleksei Scherbakov Date: 2018-10-19T16:16:13Z IGNITE-8873 wip. commit 7018264fae040f04f1eefcc144295047f3f20255 Author: Aleksei Scherbakov Date: 2018-10-19T16:18:24Z IGNITE-8873 wip. commit f3ff3499695643f1e319af64db5deb1198f9d7ad Author: Aleksei Scherbakov Date: 2018-10-19T16:21:50Z Merge branch 'ignite-8873' of https://github.com/gridgain/apache-ignite into ignite-8873 # Conflicts: # modules/core/src/main/java/org/apache/ignite/internal/processors/cache/GridCacheAdapter.java # modules/core/src/main/java/org/apache/ignite/internal/processors/cache/IgniteCacheOffheapManager.java # modules/core/src/main/java/org/apache/ignite/internal/processors/cache/IgniteCacheOffheapManagerImpl.java # modules/core/src/main/java/org/apache/ignite/internal/processors/cache/local/GridLocalCache.java # modules/core/src/main/java/org/apache/ignite/internal/processors/cache/persistence/GridCacheOffheapManager.java # modules/core/src/test/java/org/apache/ignite/internal/processors/cache/persistence/db/IgnitePdsPartitionPreloadTest.java commit 9b4180f35bc571484c4d07418dfaf4c83b165c99 Author: Aleksei Scherbakov Date: 2018-10-19T16:22:00Z Merge branch 'ignite-8873' of https://github.com/gridgain/apache-ignite into ignite-8873 # Conflicts: # modules/core/src/main/java/org/apache/ignite/internal/processors/cache/GridCacheAdapter.java # modules/core/src/main/java/org/apache/ignite/internal/processors/cache/IgniteCacheOffheapManager.java # modules/core/src/main/java/org/apache/ignite/internal/processors/cache/IgniteCacheOffheapManagerImpl.java # modules/core/src/main/java/org/apache/ignite/internal/processors/cache/local/GridLocalCache.java # modules/core/src/main/java/org/apache/ignite/internal/processors/cache/persistence/GridCacheOffheapManager.java # modules/core/src/test/java/org/apache/ignite/internal/processors/cache/persistence/db/IgnitePdsPartitionPreloadTest.java commit 3332500da74a37ca3cda4068683d7dba0c5c8bed Author: Aleksei Scherbakov Date: 2018-10-22T17:01:05Z IGNITE-8873 wip. commit 4c4b2050f8f005e101801d65db267ca14fdead6a Author: Aleksei Scherbakov Date: 2018-10-22T17:01:26Z IGNITE-8873 wip. commit c594dc8d85681ef88f7a2a73c9e5935ef742648a Author: Aleksei Scherbakov Date: 2018-10-22T17:02:12Z IGNITE-8873 wip. commit ee278751a3c1078277159e51fca24b3e167a3aca Author: Aleksei Scherbakov Date: 2018-10-23T09:36:31Z IGNITE-8873 wip. commit 5e25e88476adf43b0c2d5e8a2566ede9aef50fa3 Author: Aleksei Scherbakov Date: 2018-10-23T09:43:33Z Merge branch 'master' of https://github.com/apache/ignite into ignite-8873 commit 54e7fe1801f8a20036d6b665a5516aa6cddfa981 Author: Aleksei Scherbakov Date: 2018-10-23T09:59:41Z IGNITE-8873 wip. commit 5daab6029f0e54ba60162784e1e170f170c05d82 Author: Aleksei Scherbakov Date: 2018-10-24T08:56:40Z Merge branch 'master' of https://github.com/apache/ignite into ignite-8873 commit 68ba4496622bb71eb92811f7fec4e162ac5e94dd Author: Aleksei Scherbakov Date: 2018-10-24T09:13:32Z Merge branch 'master' of https://github.com/apache/ignite into ignite-8873 commit 538f199d9e82fb1810d57b466072200c3aec7d52 Author: Aleksei Scherbakov Date: 2018-10-25T09:07:12Z IGNITE-8873 wip. commit 2316ae10490c2910cf9b46abe1ba0feed9008011 Author: Aleksei Scherbakov Date: 2018-10-25T15:23:22Z IGNITE-8873 wip. commit 06a6f099e0613ceac1ad63c27df60d4afce8ae71 Author: Aleksei Scherbakov Date: 2018-10-25T15:46:08Z
[jira] [Commented] (IGNITE-10026) [ML] Broken example: GaussianNaiveBayesTrainerExample
[ https://issues.apache.org/jira/browse/IGNITE-10026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665300#comment-16665300 ] ASF GitHub Bot commented on IGNITE-10026: - Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5090 > [ML] Broken example: GaussianNaiveBayesTrainerExample > -- > > Key: IGNITE-10026 > URL: https://issues.apache.org/jira/browse/IGNITE-10026 > Project: Ignite > Issue Type: Bug > Components: ml >Affects Versions: 2.8 >Reporter: Yury Babak >Assignee: Yury Babak >Priority: Major > Fix For: 2.8 > > > Broken example: GaussianNaiveBayesTrainerExample -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-10028) Incorrect handling of page on replacement
[ https://issues.apache.org/jira/browse/IGNITE-10028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov reassigned IGNITE-10028: -- Assignee: Vladislav Pyatkov > Incorrect handling of page on replacement > - > > Key: IGNITE-10028 > URL: https://issues.apache.org/jira/browse/IGNITE-10028 > Project: Ignite > Issue Type: Bug >Reporter: Vladislav Pyatkov >Assignee: Vladislav Pyatkov >Priority: Major > > We can to pass incorrect page version to IgniteCacheSnapshotManager. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7196) Exchange can stuck and wait while new node restoring state from disk and starting caches
[
https://issues.apache.org/jira/browse/IGNITE-7196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665104#comment-16665104
]
ASF GitHub Bot commented on IGNITE-7196:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4520
> Exchange can stuck and wait while new node restoring state from disk and
> starting caches
>
>
> Key: IGNITE-7196
> URL: https://issues.apache.org/jira/browse/IGNITE-7196
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.3
>Reporter: Mikhail Cherkasov
>Assignee: Maxim Muzafarov
>Priority: Critical
> Fix For: 2.8
>
>
> Exchange can stuck and wait while new node restoring state from disk and
> starting caches, there's a log snippet from a just joined new node that shows
> the issue:
> {noformat}
> [21:36:13,023][INFO][exchange-worker-#62%statement_grid%][time] Started
> exchange init [topVer=AffinityTopologyVersion [topVer=57, minorTopVer=0],
> crd=false, evt=NODE_JOINED, evtNode=3ac1160e-0de4-41bc-a366-59292c9f03c1,
> customEvt=null, allowMerge=true]
> [21:36:13,023][INFO][exchange-worker-#62%statement_grid%][FilePageStoreManager]
> Resolved page store work directory:
> /mnt/store/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463
> [21:36:13,024][INFO][exchange-worker-#62%statement_grid%][FileWriteAheadLogManager]
> Resolved write ahead log work directory:
> /mnt/wal/WAL/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463
> [21:36:13,024][INFO][exchange-worker-#62%statement_grid%][FileWriteAheadLogManager]
> Resolved write ahead log archive directory:
> /mnt/wal/WAL_archive/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463
> [21:36:13,046][INFO][exchange-worker-#62%statement_grid%][FileWriteAheadLogManager]
> Started write-ahead log manager [mode=DEFAULT]
> [21:36:13,065][INFO][exchange-worker-#62%statement_grid%][PageMemoryImpl]
> Started page memory [memoryAllocated=100.0 MiB, pages=6352, tableSize=373.4
> KiB, checkpointBuffer=100.0 MiB]
> [21:36:13,105][INFO][exchange-worker-#62%statement_grid%][PageMemoryImpl]
> Started page memory [memoryAllocated=32.0 GiB, pages=2083376, tableSize=119.6
> MiB, checkpointBuffer=896.0 MiB]
> [21:36:13,428][INFO][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager]
> Read checkpoint status
> [startMarker=/mnt/store/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463/cp/1512930965253-306c0895-1f5f-4237-bebf-8bf2b49682af-START.bin,
>
> endMarker=/mnt/store/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463/cp/1512930869357-1c24b6dc-d64c-4b83-8166-11edf1bfdad3-END.bin]
> [21:36:13,429][INFO][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager]
> Checking memory state [lastValidPos=FileWALPointer [idx=3582,
> fileOffset=59186076, len=9229, forceFlush=false], lastMarked=FileWALPointer
> [idx=3629, fileOffset=50829700, len=9229, forceFlush=false],
> lastCheckpointId=306c0895-1f5f-4237-bebf-8bf2b49682af]
> [21:36:13,429][WARNING][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager]
> Ignite node stopped in the middle of checkpoint. Will restore memory state
> and finish checkpoint on node start.
> [21:36:18,312][INFO][grid-nio-worker-tcp-comm-0-#41%statement_grid%][TcpCommunicationSpi]
> Accepted incoming communication connection [locAddr=/172.31.20.209:48100,
> rmtAddr=/172.31.17.115:57148]
> [21:36:21,619][INFO][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager]
> Found last checkpoint marker [cpId=306c0895-1f5f-4237-bebf-8bf2b49682af,
> pos=FileWALPointer [idx=3629, fileOffset=50829700, len=9229,
> forceFlush=false]]
> [21:36:21,620][INFO][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager]
> Finished applying memory changes [changesApplied=165103, time=8189ms]
> [21:36:22,403][INFO][grid-nio-worker-tcp-comm-1-#42%statement_grid%][TcpCommunicationSpi]
> Accepted incoming communication connection [locAddr=/172.31.20.209:48100,
> rmtAddr=/172.31.28.10:47964]
> [21:36:23,414][INFO][grid-nio-worker-tcp-comm-2-#43%statement_grid%][TcpCommunicationSpi]
> Accepted incoming communication connection [locAddr=/172.31.20.209:48100,
> rmtAddr=/172.31.27.101:46000]
> [21:36:33,019][WARNING][main][GridCachePartitionExchangeManager] Failed to
> wait for initial partition map exchange. Possible reasons are:
> ^-- Transactions in deadlock.
> ^-- Long running transactions (ignore if this is the case).
> ^-- Unreleased explicit locks.
> [21:36:53,021][WARNING][main][GridCachePartitionExchangeManager] Still
> waiting for initial partition map exchange
> [fut=GridDhtPartitionsExchangeFuture [firstDiscoEvt=DiscoveryEvent
> [evtNode=TcpDiscoveryNode [id=3ac1160e-0de4-41bc-a366-59292c9f03c1,
> addrs=[0:0:0:0:0:0:0:1%lo, 127.0.0.1, 172.31.20.209],
[jira] [Created] (IGNITE-10024) MVCC TX: Stackoverflow during DhtEnlistFuture mapping
Roman Kondakov created IGNITE-10024:
---
Summary: MVCC TX: Stackoverflow during DhtEnlistFuture mapping
Key: IGNITE-10024
URL: https://issues.apache.org/jira/browse/IGNITE-10024
Project: Ignite
Issue Type: Bug
Components: mvcc
Reporter: Roman Kondakov
Fix For: 2.7
There is possible stack overflow error in {{GridNearTxAbstractEnlistFuture}}
mapping. It should be investigated.
{code:java}
[16:19:22]W: [org.apache.ignite:ignite-core] [16:19:22] (err) Failed to
notify listener:
o.a.i.i.processors.timeout.GridTimeoutProcessor$2...@1f088f2cjava.lang.StackOverflowError
[16:19:22]W: [org.apache.ignite:ignite-core]at
java.lang.ThreadLocal.set(ThreadLocal.java:201)
[16:19:22]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.internal.processors.cache.GridCacheMvccManager.contextReset(GridCacheMvccManager.java:882)
[16:19:22]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.internal.processors.cache.GridCacheSharedContext.txContextReset(GridCacheSharedContext.java:1101)
[16:19:22]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxAbstractEnlistFuture.lambda$mapOnTopology$23be56e8$1(GridNearTxAbstractEnlistFuture.java:342)
[16:19:22]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.internal.processors.timeout.GridTimeoutProcessor.waitAsync(GridTimeoutProcessor.java:155)
[16:19:22]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxAbstractEnlistFuture.mapOnTopology(GridNearTxAbstractEnlistFuture.java:334)
[16:19:22]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxAbstractEnlistFuture.lambda$mapOnTopology$23be56e8$1(GridNearTxAbstractEnlistFuture.java:339)
[16:19:22]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.internal.processors.timeout.GridTimeoutProcessor.waitAsync(GridTimeoutProcessor.java:155)
[16:19:22]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxAbstractEnlistFuture.mapOnTopology(GridNearTxAbstractEnlistFuture.java:334)
[16:19:22]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxAbstractEnlistFuture.lambda$mapOnTopology$23be56e8$1(GridNearTxAbstractEnlistFuture.java:339)
[16:19:22]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.internal.processors.timeout.GridTimeoutProcessor.waitAsync(GridTimeoutProcessor.java:155)
[16:19:22]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxAbstractEnlistFuture.mapOnTopology(GridNearTxAbstractEnlistFuture.java:334)
[16:19:22]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxAbstractEnlistFuture.lambda$mapOnTopology$23be56e8$1(GridNearTxAbstractEnlistFuture.java:339)
[16:19:22]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.internal.processors.timeout.GridTimeoutProcessor.waitAsync(GridTimeoutProcessor.java:155)
[16:19:22]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxAbstractEnlistFuture.mapOnTopology(GridNearTxAbstractEnlistFuture.java:334)
[16:19:22]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxAbstractEnlistFuture.lambda$mapOnTopology$23be56e8$1(GridNearTxAbstractEnlistFuture.java:339)
[16:19:22]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.internal.processors.timeout.GridTimeoutProcessor.waitAsync(GridTimeoutProcessor.java:155)
[16:19:22]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxAbstractEnlistFuture.mapOnTopology(GridNearTxAbstractEnlistFuture.java:334)
[16:19:22]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxAbstractEnlistFuture.lambda$mapOnTopology$23be56e8$1(GridNearTxAbstractEnlistFuture.java:339)
[16:19:22]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.internal.processors.timeout.GridTimeoutProcessor.waitAsync(GridTimeoutProcessor.java:155)
[16:19:22]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxAbstractEnlistFuture.mapOnTopology(GridNearTxAbstractEnlistFuture.java:334)
[16:19:22]W: [org.apache.ignite:ignite-core]at
[jira] [Created] (IGNITE-10027) Optimistic transaction doesn't throw TransactionTimeoutException on lock acquisition timeout.
Alexei Scherbakov created IGNITE-10027:
--
Summary: Optimistic transaction doesn't throw
TransactionTimeoutException on lock acquisition timeout.
Key: IGNITE-10027
URL: https://issues.apache.org/jira/browse/IGNITE-10027
Project: Ignite
Issue Type: Bug
Reporter: Alexei Scherbakov
Reproducer:
{noformat}
/*
* Licensed to the Apache Software Foundation (ASF) under one or more
* contributor license agreements. See the NOTICE file distributed with
* this work for additional information regarding copyright ownership.
* The ASF licenses this file to You under the Apache License, Version 2.0
* (the "License"); you may not use this file except in compliance with
* the License. You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/
package org.apache.ignite.internal.processors.cache.transactions;
import java.util.concurrent.CountDownLatch;
import java.util.concurrent.TimeUnit;
import org.apache.ignite.Ignite;
import org.apache.ignite.IgniteCheckedException;
import org.apache.ignite.configuration.CacheConfiguration;
import org.apache.ignite.configuration.IgniteConfiguration;
import org.apache.ignite.internal.IgniteEx;
import org.apache.ignite.internal.IgniteInternalFuture;
import org.apache.ignite.internal.IgniteInterruptedCheckedException;
import org.apache.ignite.internal.TestRecordingCommunicationSpi;
import
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareResponse;
import org.apache.ignite.internal.processors.cache.verify.IdleVerifyResultV2;
import org.apache.ignite.internal.util.typedef.X;
import org.apache.ignite.internal.util.typedef.internal.U;
import org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi;
import org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder;
import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;
import org.apache.ignite.transactions.Transaction;
import org.apache.ignite.transactions.TransactionConcurrency;
import org.apache.ignite.transactions.TransactionTimeoutException;
import static org.apache.ignite.cache.CacheAtomicityMode.TRANSACTIONAL;
import static org.apache.ignite.cache.CacheWriteSynchronizationMode.FULL_SYNC;
import static org.apache.ignite.testframework.GridTestUtils.runAsync;
import static org.apache.ignite.transactions.TransactionConcurrency.OPTIMISTIC;
import static org.apache.ignite.transactions.TransactionConcurrency.PESSIMISTIC;
import static
org.apache.ignite.transactions.TransactionIsolation.REPEATABLE_READ;
/**
* Tests rollback on timeout scenarios for one-phase commit protocol.
*/
public class TxRollbackOnTimeoutOnePhaseCommitTest extends
GridCommonAbstractTest {
/** IP finder. */
private static final TcpDiscoveryVmIpFinder IP_FINDER = new
TcpDiscoveryVmIpFinder(true);
/** */
private static final int GRID_CNT = 2;
/** {@inheritDoc} */
@Override protected IgniteConfiguration getConfiguration(String
igniteInstanceName) throws Exception {
IgniteConfiguration cfg = super.getConfiguration(igniteInstanceName);
((TcpDiscoverySpi)cfg.getDiscoverySpi()).setIpFinder(IP_FINDER);
cfg.setCommunicationSpi(new TestRecordingCommunicationSpi());
boolean client = igniteInstanceName.startsWith("client");
cfg.setClientMode(client);
if (!client) {
CacheConfiguration ccfg = new
CacheConfiguration(DEFAULT_CACHE_NAME);
ccfg.setAtomicityMode(TRANSACTIONAL);
ccfg.setBackups(1);
ccfg.setWriteSynchronizationMode(FULL_SYNC);
ccfg.setOnheapCacheEnabled(false);
cfg.setCacheConfiguration(ccfg);
}
return cfg;
}
/** {@inheritDoc} */
@Override protected void beforeTest() throws Exception {
super.beforeTest();
startGridsMultiThreaded(GRID_CNT);
startGrid("client");
}
/** */
public void testUnlockOptimistic() throws IgniteCheckedException {
IgniteEx client = grid("client");
assertNotNull(client.cache(DEFAULT_CACHE_NAME));
int key = 0;
CountDownLatch lock = new CountDownLatch(1);
CountDownLatch finish = new CountDownLatch(1);
IgniteInternalFuture fut = runAsync(() -> {
try (Transaction tx = client.transactions().txStart(PESSIMISTIC,
REPEATABLE_READ, 0, 1)) {
client.cache(DEFAULT_CACHE_NAME).put(key, key + 1);
lock.countDown();
try {
assertTrue(U.await(finish, 30, TimeUnit.SECONDS));
[jira] [Updated] (IGNITE-10027) Optimistic transaction doesn't throw TransactionTimeoutException on lock acquisition timeout.
[
https://issues.apache.org/jira/browse/IGNITE-10027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexei Scherbakov updated IGNITE-10027:
---
Fix Version/s: 2.8
> Optimistic transaction doesn't throw TransactionTimeoutException on lock
> acquisition timeout.
> -
>
> Key: IGNITE-10027
> URL: https://issues.apache.org/jira/browse/IGNITE-10027
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexei Scherbakov
>Priority: Major
> Fix For: 2.8
>
>
> Reproducer:
> {noformat}
> /*
> * Licensed to the Apache Software Foundation (ASF) under one or more
> * contributor license agreements. See the NOTICE file distributed with
> * this work for additional information regarding copyright ownership.
> * The ASF licenses this file to You under the Apache License, Version 2.0
> * (the "License"); you may not use this file except in compliance with
> * the License. You may obtain a copy of the License at
> *
> * http://www.apache.org/licenses/LICENSE-2.0
> *
> * Unless required by applicable law or agreed to in writing, software
> * distributed under the License is distributed on an "AS IS" BASIS,
> * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> * See the License for the specific language governing permissions and
> * limitations under the License.
> */
> package org.apache.ignite.internal.processors.cache.transactions;
> import java.util.concurrent.CountDownLatch;
> import java.util.concurrent.TimeUnit;
> import org.apache.ignite.Ignite;
> import org.apache.ignite.IgniteCheckedException;
> import org.apache.ignite.configuration.CacheConfiguration;
> import org.apache.ignite.configuration.IgniteConfiguration;
> import org.apache.ignite.internal.IgniteEx;
> import org.apache.ignite.internal.IgniteInternalFuture;
> import org.apache.ignite.internal.IgniteInterruptedCheckedException;
> import org.apache.ignite.internal.TestRecordingCommunicationSpi;
> import
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareResponse;
> import org.apache.ignite.internal.processors.cache.verify.IdleVerifyResultV2;
> import org.apache.ignite.internal.util.typedef.X;
> import org.apache.ignite.internal.util.typedef.internal.U;
> import org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi;
> import org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder;
> import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;
> import org.apache.ignite.transactions.Transaction;
> import org.apache.ignite.transactions.TransactionConcurrency;
> import org.apache.ignite.transactions.TransactionTimeoutException;
> import static org.apache.ignite.cache.CacheAtomicityMode.TRANSACTIONAL;
> import static org.apache.ignite.cache.CacheWriteSynchronizationMode.FULL_SYNC;
> import static org.apache.ignite.testframework.GridTestUtils.runAsync;
> import static
> org.apache.ignite.transactions.TransactionConcurrency.OPTIMISTIC;
> import static
> org.apache.ignite.transactions.TransactionConcurrency.PESSIMISTIC;
> import static
> org.apache.ignite.transactions.TransactionIsolation.REPEATABLE_READ;
> /**
> * Tests rollback on timeout scenarios for one-phase commit protocol.
> */
> public class TxRollbackOnTimeoutOnePhaseCommitTest extends
> GridCommonAbstractTest {
> /** IP finder. */
> private static final TcpDiscoveryVmIpFinder IP_FINDER = new
> TcpDiscoveryVmIpFinder(true);
> /** */
> private static final int GRID_CNT = 2;
> /** {@inheritDoc} */
> @Override protected IgniteConfiguration getConfiguration(String
> igniteInstanceName) throws Exception {
> IgniteConfiguration cfg = super.getConfiguration(igniteInstanceName);
> ((TcpDiscoverySpi)cfg.getDiscoverySpi()).setIpFinder(IP_FINDER);
> cfg.setCommunicationSpi(new TestRecordingCommunicationSpi());
> boolean client = igniteInstanceName.startsWith("client");
> cfg.setClientMode(client);
> if (!client) {
> CacheConfiguration ccfg = new
> CacheConfiguration(DEFAULT_CACHE_NAME);
> ccfg.setAtomicityMode(TRANSACTIONAL);
> ccfg.setBackups(1);
> ccfg.setWriteSynchronizationMode(FULL_SYNC);
> ccfg.setOnheapCacheEnabled(false);
> cfg.setCacheConfiguration(ccfg);
> }
> return cfg;
> }
> /** {@inheritDoc} */
> @Override protected void beforeTest() throws Exception {
> super.beforeTest();
> startGridsMultiThreaded(GRID_CNT);
> startGrid("client");
> }
> /** */
> public void testUnlockOptimistic() throws IgniteCheckedException {
> IgniteEx client = grid("client");
> assertNotNull(client.cache(DEFAULT_CACHE_NAME));
> int key = 0;
>
[jira] [Commented] (IGNITE-7165) Re-balancing is cancelled if client node joins
[ https://issues.apache.org/jira/browse/IGNITE-7165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665106#comment-16665106 ] ASF GitHub Bot commented on IGNITE-7165: Github user Mmuzaf closed the pull request at: https://github.com/apache/ignite/pull/4097 > Re-balancing is cancelled if client node joins > -- > > Key: IGNITE-7165 > URL: https://issues.apache.org/jira/browse/IGNITE-7165 > Project: Ignite > Issue Type: Bug >Reporter: Mikhail Cherkasov >Assignee: Maxim Muzafarov >Priority: Critical > Labels: rebalance > Fix For: 2.7 > > Attachments: GridCacheRebalancingCancelTestNoReproduce.java, > node-2-jstack.log, node-NO_REBALANCE-7165.log > > > Re-balancing is canceled if client node joins. Re-balancing can take hours > and each time when client node joins it starts again: > [15:10:05,700][INFO][disco-event-worker-#61%statement_grid%][GridDiscoveryManager] > Added new node to topology: TcpDiscoveryNode > [id=979cf868-1c37-424a-9ad1-12db501f32ef, addrs=[0:0:0:0:0:0:0:1, 127.0.0.1, > 172.31.16.213], sockAddrs=[/0:0:0:0:0:0:0:1:0, /127.0.0.1:0, > /172.31.16.213:0], discPort=0, order=36, intOrder=24, > lastExchangeTime=1512907805688, loc=false, ver=2.3.1#20171129-sha1:4b1ec0fe, > isClient=true] > [15:10:05,701][INFO][disco-event-worker-#61%statement_grid%][GridDiscoveryManager] > Topology snapshot [ver=36, servers=7, clients=5, CPUs=128, heap=160.0GB] > [15:10:05,702][INFO][exchange-worker-#62%statement_grid%][time] Started > exchange init [topVer=AffinityTopologyVersion [topVer=36, minorTopVer=0], > crd=false, evt=NODE_JOINED, evtNode=979cf868-1c37-424a-9ad1-12db501f32ef, > customEvt=null, allowMerge=true] > [15:10:05,702][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionsExchangeFuture] > Finish exchange future [startVer=AffinityTopologyVersion [topVer=36, > minorTopVer=0], resVer=AffinityTopologyVersion [topVer=36, minorTopVer=0], > err=null] > [15:10:05,702][INFO][exchange-worker-#62%statement_grid%][time] Finished > exchange init [topVer=AffinityTopologyVersion [topVer=36, minorTopVer=0], > crd=false] > [15:10:05,703][INFO][exchange-worker-#62%statement_grid%][GridCachePartitionExchangeManager] > Skipping rebalancing (nothing scheduled) [top=AffinityTopologyVersion > [topVer=36, minorTopVer=0], evt=NODE_JOINED, > node=979cf868-1c37-424a-9ad1-12db501f32ef] > [15:10:08,706][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander] > Cancelled rebalancing from all nodes [topology=AffinityTopologyVersion > [topVer=35, minorTopVer=0]] > [15:10:08,707][INFO][exchange-worker-#62%statement_grid%][GridCachePartitionExchangeManager] > Rebalancing scheduled [order=[statementp]] > [15:10:08,707][INFO][exchange-worker-#62%statement_grid%][GridCachePartitionExchangeManager] > Rebalancing started [top=null, evt=NODE_JOINED, > node=a8be3c14-9add-48c3-b099-3fd304cfdbf4] > [15:10:08,707][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander] > Starting rebalancing [mode=ASYNC, > fromNode=2f6bde48-ffb5-4815-bd32-df4e57dc13e0, partitionsCount=18, > topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], > updateSeq=-1754630006] > [15:10:08,707][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander] > Starting rebalancing [mode=ASYNC, > fromNode=35d01141-4dce-47dd-adf6-a4f3b2bb9da9, partitionsCount=15, > topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], > updateSeq=-1754630006] > [15:10:08,708][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander] > Starting rebalancing [mode=ASYNC, > fromNode=b3a8be53-e61f-4023-a906-a265923837ba, partitionsCount=15, > topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], > updateSeq=-1754630006] > [15:10:08,708][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander] > Starting rebalancing [mode=ASYNC, > fromNode=f825cb4e-7dcc-405f-a40d-c1dc1a3ade5a, partitionsCount=12, > topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], > updateSeq=-1754630006] > [15:10:08,708][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander] > Starting rebalancing [mode=ASYNC, > fromNode=4ae1db91-8b88-4180-a84b-127a303959e9, partitionsCount=11, > topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], > updateSeq=-1754630006] > [15:10:08,708][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander] > Starting rebalancing [mode=ASYNC, > fromNode=7c286481-7638-49e4-8c68-fa6aa65d8b76, partitionsCount=18, > topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], > updateSeq=-1754630006] > so in clusters with a big amount of data and the frequent client left/join > events this means that a new server will never receive its partitions. -- This message was sent by Atlassian JIRA
[jira] [Commented] (IGNITE-7165) Re-balancing is cancelled if client node joins
[ https://issues.apache.org/jira/browse/IGNITE-7165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665107#comment-16665107 ] ASF GitHub Bot commented on IGNITE-7165: Github user Mmuzaf closed the pull request at: https://github.com/apache/ignite/pull/4442 > Re-balancing is cancelled if client node joins > -- > > Key: IGNITE-7165 > URL: https://issues.apache.org/jira/browse/IGNITE-7165 > Project: Ignite > Issue Type: Bug >Reporter: Mikhail Cherkasov >Assignee: Maxim Muzafarov >Priority: Critical > Labels: rebalance > Fix For: 2.7 > > Attachments: GridCacheRebalancingCancelTestNoReproduce.java, > node-2-jstack.log, node-NO_REBALANCE-7165.log > > > Re-balancing is canceled if client node joins. Re-balancing can take hours > and each time when client node joins it starts again: > [15:10:05,700][INFO][disco-event-worker-#61%statement_grid%][GridDiscoveryManager] > Added new node to topology: TcpDiscoveryNode > [id=979cf868-1c37-424a-9ad1-12db501f32ef, addrs=[0:0:0:0:0:0:0:1, 127.0.0.1, > 172.31.16.213], sockAddrs=[/0:0:0:0:0:0:0:1:0, /127.0.0.1:0, > /172.31.16.213:0], discPort=0, order=36, intOrder=24, > lastExchangeTime=1512907805688, loc=false, ver=2.3.1#20171129-sha1:4b1ec0fe, > isClient=true] > [15:10:05,701][INFO][disco-event-worker-#61%statement_grid%][GridDiscoveryManager] > Topology snapshot [ver=36, servers=7, clients=5, CPUs=128, heap=160.0GB] > [15:10:05,702][INFO][exchange-worker-#62%statement_grid%][time] Started > exchange init [topVer=AffinityTopologyVersion [topVer=36, minorTopVer=0], > crd=false, evt=NODE_JOINED, evtNode=979cf868-1c37-424a-9ad1-12db501f32ef, > customEvt=null, allowMerge=true] > [15:10:05,702][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionsExchangeFuture] > Finish exchange future [startVer=AffinityTopologyVersion [topVer=36, > minorTopVer=0], resVer=AffinityTopologyVersion [topVer=36, minorTopVer=0], > err=null] > [15:10:05,702][INFO][exchange-worker-#62%statement_grid%][time] Finished > exchange init [topVer=AffinityTopologyVersion [topVer=36, minorTopVer=0], > crd=false] > [15:10:05,703][INFO][exchange-worker-#62%statement_grid%][GridCachePartitionExchangeManager] > Skipping rebalancing (nothing scheduled) [top=AffinityTopologyVersion > [topVer=36, minorTopVer=0], evt=NODE_JOINED, > node=979cf868-1c37-424a-9ad1-12db501f32ef] > [15:10:08,706][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander] > Cancelled rebalancing from all nodes [topology=AffinityTopologyVersion > [topVer=35, minorTopVer=0]] > [15:10:08,707][INFO][exchange-worker-#62%statement_grid%][GridCachePartitionExchangeManager] > Rebalancing scheduled [order=[statementp]] > [15:10:08,707][INFO][exchange-worker-#62%statement_grid%][GridCachePartitionExchangeManager] > Rebalancing started [top=null, evt=NODE_JOINED, > node=a8be3c14-9add-48c3-b099-3fd304cfdbf4] > [15:10:08,707][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander] > Starting rebalancing [mode=ASYNC, > fromNode=2f6bde48-ffb5-4815-bd32-df4e57dc13e0, partitionsCount=18, > topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], > updateSeq=-1754630006] > [15:10:08,707][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander] > Starting rebalancing [mode=ASYNC, > fromNode=35d01141-4dce-47dd-adf6-a4f3b2bb9da9, partitionsCount=15, > topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], > updateSeq=-1754630006] > [15:10:08,708][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander] > Starting rebalancing [mode=ASYNC, > fromNode=b3a8be53-e61f-4023-a906-a265923837ba, partitionsCount=15, > topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], > updateSeq=-1754630006] > [15:10:08,708][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander] > Starting rebalancing [mode=ASYNC, > fromNode=f825cb4e-7dcc-405f-a40d-c1dc1a3ade5a, partitionsCount=12, > topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], > updateSeq=-1754630006] > [15:10:08,708][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander] > Starting rebalancing [mode=ASYNC, > fromNode=4ae1db91-8b88-4180-a84b-127a303959e9, partitionsCount=11, > topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], > updateSeq=-1754630006] > [15:10:08,708][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander] > Starting rebalancing [mode=ASYNC, > fromNode=7c286481-7638-49e4-8c68-fa6aa65d8b76, partitionsCount=18, > topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], > updateSeq=-1754630006] > so in clusters with a big amount of data and the frequent client left/join > events this means that a new server will never receive its partitions. -- This message was sent by Atlassian JIRA
[jira] [Commented] (IGNITE-9091) IEP-25: creating documentation
[ https://issues.apache.org/jira/browse/IGNITE-9091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665182#comment-16665182 ] Ilya Lantukh commented on IGNITE-9091: -- [~agoncharuk], yes, everything is correct. > IEP-25: creating documentation > -- > > Key: IGNITE-9091 > URL: https://issues.apache.org/jira/browse/IGNITE-9091 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Alex Volkov >Assignee: Alexey Goncharuk >Priority: Major > Labels: iep-25 > Fix For: 2.8 > > > It would be great to have proper documentation for IEP-25: > [https://cwiki.apache.org/confluence/display/IGNITE/IEP-25:+Partition+Map+Exchange+hangs+resolving] > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9991) thin clients: can't use array as cache key for PHP, JS and Python clients
[
https://issues.apache.org/jira/browse/IGNITE-9991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Kosenchuk reassigned IGNITE-9991:
Assignee: (was: Alexey Kosenchuk)
> thin clients: can't use array as cache key for PHP, JS and Python clients
> -
>
> Key: IGNITE-9991
> URL: https://issues.apache.org/jira/browse/IGNITE-9991
> Project: Ignite
> Issue Type: Bug
> Components: thin client
>Affects Versions: 2.7
>Reporter: Stepan Pilschikov
>Priority: Major
>
> Trying to put cache with key as values array
> Put Py code
> {code}
> cache = client.get_or_create_cache("PY_BOOLEAN_ARRAY")
> cache.put([True, False], 1, key_hint=BoolArrayObject, value_hint=IntObject)
> {code}
> Get
> {code}
> cache = client.get_or_create_cache("PY_BOOLEAN_ARRAY")
> print(cache.get([True, False] key_hint=BoolArrayObject))
> {code}
> output: null
> Same thing with PHP, JS clients and all others array data types
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9991) thin clients: can't use array as cache key for PHP, JS and Python clients
[
https://issues.apache.org/jira/browse/IGNITE-9991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665218#comment-16665218
]
Alexey Kosenchuk commented on IGNITE-9991:
--
Reproduced with NodeJS and PHP clients.
Reproduced with Java thin client as well.
This seems the server's issue.
Put operation works fine. It's possible to see the new entry (eg. using scan
query operation).
But after that, get and containsKey operations do not return anything for the
array-key.
> thin clients: can't use array as cache key for PHP, JS and Python clients
> -
>
> Key: IGNITE-9991
> URL: https://issues.apache.org/jira/browse/IGNITE-9991
> Project: Ignite
> Issue Type: Bug
> Components: thin client
>Affects Versions: 2.7
>Reporter: Stepan Pilschikov
>Priority: Major
>
> Trying to put cache with key as values array
> Put Py code
> {code}
> cache = client.get_or_create_cache("PY_BOOLEAN_ARRAY")
> cache.put([True, False], 1, key_hint=BoolArrayObject, value_hint=IntObject)
> {code}
> Get
> {code}
> cache = client.get_or_create_cache("PY_BOOLEAN_ARRAY")
> print(cache.get([True, False] key_hint=BoolArrayObject))
> {code}
> output: null
> Same thing with PHP, JS clients and all others array data types
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7072) IgniteCache.replace(k, v, nv) does not work in binary mode without classes
[
https://issues.apache.org/jira/browse/IGNITE-7072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665252#comment-16665252
]
Ignite TC Bot commented on IGNITE-7072:
---
{panel:title=Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Queries (Binary Objects Simple Mapper){color} [[tests 0 Exit
Code |https://ci.ignite.apache.org/viewLog.html?buildId=2166798]]
{panel}
[TeamCity Run All
Results|http://ci.ignite.apache.org/viewLog.html?buildId=2167553buildTypeId=IgniteTests24Java8_BinaryObjectsSimpleMapperQueries]
> IgniteCache.replace(k, v, nv) does not work in binary mode without classes
> --
>
> Key: IGNITE-7072
> URL: https://issues.apache.org/jira/browse/IGNITE-7072
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Reporter: Pavel Tupitsyn
>Assignee: Igor Sapego
>Priority: Major
> Fix For: 2.8
>
>
> {{IgniteCache.replace(K key, V oldVal, V newVal)}} method deserializes cache
> values in order to compare them, which causes exception when classes are not
> present on server:
> {code}
> class org.apache.ignite.IgniteCheckedException: Unknown pair [platformId=0,
> typeId=-1690383137]
> at
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7260)
> at
> org.apache.ignite.internal.processors.cache.GridCacheContext.isAll(GridCacheContext.java:1242)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.onEntriesLocked(GridDhtTxPrepareFuture.java:464)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.prepare0(GridDhtTxPrepareFuture.java:1223)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.mapIfLocked(GridDhtTxPrepareFuture.java:666)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.prepare(GridDhtTxPrepareFuture.java:1040)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.prepareAsyncLocal(GridNearTxLocal.java:3452)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.prepareColocatedTx(IgniteTxHandler.java:257)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearOptimisticTxPrepareFuture.proceedPrepare(GridNearOptimisticTxPrepareFuture.java:574)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearOptimisticTxPrepareFuture.prepareSingle(GridNearOptimisticTxPrepareFuture.java:401)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearOptimisticTxPrepareFuture.prepare0(GridNearOptimisticTxPrepareFuture.java:344)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearOptimisticTxPrepareFutureAdapter.prepareOnTopology(GridNearOptimisticTxPrepareFutureAdapter.java:137)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearOptimisticTxPrepareFutureAdapter.prepare(GridNearOptimisticTxPrepareFutureAdapter.java:74)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.prepareNearTxLocal(GridNearTxLocal.java:3161)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.commitNearTxLocalAsync(GridNearTxLocal.java:3221)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.optimisticPutFuture(GridNearTxLocal.java:2391)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.putAsync0(GridNearTxLocal.java:622)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.putAsync(GridNearTxLocal.java:385)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter$34.op(GridCacheAdapter.java:2707)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter$AsyncOp.op(GridCacheAdapter.java:5120)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.asyncOp(GridCacheAdapter.java:4260)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter$AsyncOpRetryFuture.execute(GridCacheAdapter.java:4841)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.asyncOp(GridCacheAdapter.java:4173)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.putAsync0(GridCacheAdapter.java:2705)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.putAsync(GridCacheAdapter.java:2689)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.replaceAsync(GridCacheAdapter.java:2776)
> at
>
[jira] [Commented] (IGNITE-10026) [ML] Broken example: GaussianNaiveBayesTrainerExample
[ https://issues.apache.org/jira/browse/IGNITE-10026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665297#comment-16665297 ] Yury Babak commented on IGNITE-10026: - This bug caused by this issue > [ML] Broken example: GaussianNaiveBayesTrainerExample > -- > > Key: IGNITE-10026 > URL: https://issues.apache.org/jira/browse/IGNITE-10026 > Project: Ignite > Issue Type: Bug > Components: ml >Affects Versions: 2.8 >Reporter: Yury Babak >Assignee: Yury Babak >Priority: Major > Fix For: 2.8 > > > Broken example: GaussianNaiveBayesTrainerExample -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-10026) [ML] Broken example: GaussianNaiveBayesTrainerExample
[ https://issues.apache.org/jira/browse/IGNITE-10026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Babak resolved IGNITE-10026. - Resolution: Fixed merged. > [ML] Broken example: GaussianNaiveBayesTrainerExample > -- > > Key: IGNITE-10026 > URL: https://issues.apache.org/jira/browse/IGNITE-10026 > Project: Ignite > Issue Type: Bug > Components: ml >Affects Versions: 2.8 >Reporter: Yury Babak >Assignee: Yury Babak >Priority: Major > Fix For: 2.8 > > > Broken example: GaussianNaiveBayesTrainerExample -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10020) control.sh error: Comparison method violates its general contract!
[ https://issues.apache.org/jira/browse/IGNITE-10020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665075#comment-16665075 ] ASF GitHub Bot commented on IGNITE-10020: - 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 > 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 >Priority: Major > > ./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)
[jira] [Commented] (IGNITE-7196) Exchange can stuck and wait while new node restoring state from disk and starting caches
[
https://issues.apache.org/jira/browse/IGNITE-7196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665096#comment-16665096
]
Dmitriy Govorukhin commented on IGNITE-7196:
[~Mmuzaf] Thanks for great work, merged changes to master.
> Exchange can stuck and wait while new node restoring state from disk and
> starting caches
>
>
> Key: IGNITE-7196
> URL: https://issues.apache.org/jira/browse/IGNITE-7196
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.3
>Reporter: Mikhail Cherkasov
>Assignee: Maxim Muzafarov
>Priority: Critical
> Fix For: 2.8
>
>
> Exchange can stuck and wait while new node restoring state from disk and
> starting caches, there's a log snippet from a just joined new node that shows
> the issue:
> {noformat}
> [21:36:13,023][INFO][exchange-worker-#62%statement_grid%][time] Started
> exchange init [topVer=AffinityTopologyVersion [topVer=57, minorTopVer=0],
> crd=false, evt=NODE_JOINED, evtNode=3ac1160e-0de4-41bc-a366-59292c9f03c1,
> customEvt=null, allowMerge=true]
> [21:36:13,023][INFO][exchange-worker-#62%statement_grid%][FilePageStoreManager]
> Resolved page store work directory:
> /mnt/store/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463
> [21:36:13,024][INFO][exchange-worker-#62%statement_grid%][FileWriteAheadLogManager]
> Resolved write ahead log work directory:
> /mnt/wal/WAL/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463
> [21:36:13,024][INFO][exchange-worker-#62%statement_grid%][FileWriteAheadLogManager]
> Resolved write ahead log archive directory:
> /mnt/wal/WAL_archive/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463
> [21:36:13,046][INFO][exchange-worker-#62%statement_grid%][FileWriteAheadLogManager]
> Started write-ahead log manager [mode=DEFAULT]
> [21:36:13,065][INFO][exchange-worker-#62%statement_grid%][PageMemoryImpl]
> Started page memory [memoryAllocated=100.0 MiB, pages=6352, tableSize=373.4
> KiB, checkpointBuffer=100.0 MiB]
> [21:36:13,105][INFO][exchange-worker-#62%statement_grid%][PageMemoryImpl]
> Started page memory [memoryAllocated=32.0 GiB, pages=2083376, tableSize=119.6
> MiB, checkpointBuffer=896.0 MiB]
> [21:36:13,428][INFO][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager]
> Read checkpoint status
> [startMarker=/mnt/store/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463/cp/1512930965253-306c0895-1f5f-4237-bebf-8bf2b49682af-START.bin,
>
> endMarker=/mnt/store/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463/cp/1512930869357-1c24b6dc-d64c-4b83-8166-11edf1bfdad3-END.bin]
> [21:36:13,429][INFO][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager]
> Checking memory state [lastValidPos=FileWALPointer [idx=3582,
> fileOffset=59186076, len=9229, forceFlush=false], lastMarked=FileWALPointer
> [idx=3629, fileOffset=50829700, len=9229, forceFlush=false],
> lastCheckpointId=306c0895-1f5f-4237-bebf-8bf2b49682af]
> [21:36:13,429][WARNING][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager]
> Ignite node stopped in the middle of checkpoint. Will restore memory state
> and finish checkpoint on node start.
> [21:36:18,312][INFO][grid-nio-worker-tcp-comm-0-#41%statement_grid%][TcpCommunicationSpi]
> Accepted incoming communication connection [locAddr=/172.31.20.209:48100,
> rmtAddr=/172.31.17.115:57148]
> [21:36:21,619][INFO][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager]
> Found last checkpoint marker [cpId=306c0895-1f5f-4237-bebf-8bf2b49682af,
> pos=FileWALPointer [idx=3629, fileOffset=50829700, len=9229,
> forceFlush=false]]
> [21:36:21,620][INFO][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager]
> Finished applying memory changes [changesApplied=165103, time=8189ms]
> [21:36:22,403][INFO][grid-nio-worker-tcp-comm-1-#42%statement_grid%][TcpCommunicationSpi]
> Accepted incoming communication connection [locAddr=/172.31.20.209:48100,
> rmtAddr=/172.31.28.10:47964]
> [21:36:23,414][INFO][grid-nio-worker-tcp-comm-2-#43%statement_grid%][TcpCommunicationSpi]
> Accepted incoming communication connection [locAddr=/172.31.20.209:48100,
> rmtAddr=/172.31.27.101:46000]
> [21:36:33,019][WARNING][main][GridCachePartitionExchangeManager] Failed to
> wait for initial partition map exchange. Possible reasons are:
> ^-- Transactions in deadlock.
> ^-- Long running transactions (ignore if this is the case).
> ^-- Unreleased explicit locks.
> [21:36:53,021][WARNING][main][GridCachePartitionExchangeManager] Still
> waiting for initial partition map exchange
> [fut=GridDhtPartitionsExchangeFuture [firstDiscoEvt=DiscoveryEvent
> [evtNode=TcpDiscoveryNode [id=3ac1160e-0de4-41bc-a366-59292c9f03c1,
> addrs=[0:0:0:0:0:0:0:1%lo, 127.0.0.1, 172.31.20.209],
>
[jira] [Commented] (IGNITE-9435) Document MVCC
[ https://issues.apache.org/jira/browse/IGNITE-9435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665097#comment-16665097 ] Artem Budnikov commented on IGNITE-9435: [~gvvinblade], I created a first version of the page describing MVCC: [https://apacheignite-sql.readme.io/v2.6/docs/multiversion-concurrency-control] Please review. > Document MVCC > - > > Key: IGNITE-9435 > URL: https://issues.apache.org/jira/browse/IGNITE-9435 > Project: Ignite > Issue Type: Task > Components: documentation, mvcc >Reporter: Vladimir Ozerov >Assignee: Artem Budnikov >Priority: Major > Fix For: 2.7 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9435) Document MVCC
[ https://issues.apache.org/jira/browse/IGNITE-9435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Budnikov reassigned IGNITE-9435: -- Assignee: Igor Seliverstov (was: Artem Budnikov) > Document MVCC > - > > Key: IGNITE-9435 > URL: https://issues.apache.org/jira/browse/IGNITE-9435 > Project: Ignite > Issue Type: Task > Components: documentation, mvcc >Reporter: Vladimir Ozerov >Assignee: Igor Seliverstov >Priority: Major > Fix For: 2.7 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10021) IgniteInterruptedCheckedException: sleep interrupted in GridServiceProcessorBatchDeploySelfTest#testCancelAllTopologyChange
[
https://issues.apache.org/jira/browse/IGNITE-10021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Ignatenko updated IGNITE-10021:
Attachment: GridServiceProcessorBatchDeploySelfTest.java
> IgniteInterruptedCheckedException: sleep interrupted in
> GridServiceProcessorBatchDeploySelfTest#testCancelAllTopologyChange
> ---
>
> Key: IGNITE-10021
> URL: https://issues.apache.org/jira/browse/IGNITE-10021
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Oleg Ignatenko
>Priority: Major
> Attachments: GridServiceProcessorBatchDeploySelfTest.java,
> GridServiceProcessorBatchDeploySelfTest.testCancelAllTopologyChange.log
>
>
> Test {{GridServiceProcessorBatchDeploySelfTest#testCancelAllTopologyChange}}
> failed at TC (couldn't reproduce locally), error message:
> {noformat}
> [2018-10-23
> 15:40:25,651][ERROR][srvc-deploy-#121506%extra-node-1%][TcpCommunicationSpi]
> Failed to send message to remote node [node=TcpDiscoveryNode
> [id=ce88f2ef-5c88-46f1-83d4-50dd8163, addrs=ArrayList [127.0.0.1],
> sockAddrs=HashSet [/127.0.0.1:47503], discPort=47503, order=4, intOrder=4,
> lastExchangeTime=1540309225078, loc=false, ver=2.7.0#20181023-sha1:d09f1d47,
> isClient=false], msg=GridIoMessage [plc=5, topic=TOPIC_CACHE, topicOrd=8,
> ordered=false, timeout=0, skipOnTimeout=false, msg=GridCacheIdMessage
> [cacheId=0]GridDistributedBaseMessage [ver=GridCacheVersion
> [topVer=151789232, order=1540309225927, nodeOrder=7], committedVers=null,
> rolledbackVers=null, cnt=0, super=]GridDistributedTxPrepareRequest
> [threadId=133839, concurrency=OPTIMISTIC, isolation=READ_COMMITTED,
> writeVer=GridCacheVersion [topVer=151789232, order=1540309225928,
> nodeOrder=7], timeout=0, reads=null, writes=PredicateCollectionView
> [IgniteTxEntry [key=KeyCacheObjectImpl [part=9, val=GridServiceAssignmentsKey
> [name=testService-175], hasValBytes=true], cacheId=-2100569601,
> txKey=IgniteTxKey [key=KeyCacheObjectImpl [part=9,
> val=GridServiceAssignmentsKey [name=testService-175], hasValBytes=true],
> cacheId=-2100569601], val=[op=DELETE, val=null], prevVal=[op=NOOP, val=null],
> oldVal=[op=NOOP, val=null], entryProcessorsCol=null, ttl=-1,
> conflictExpireTime=-1, conflictVer=null, explicitVer=null, dhtVer=null,
> filters=CacheEntryPredicate[] [], filtersPassed=false, filtersSet=true,
> entry=GridCacheMapEntry [key=KeyCacheObjectImpl [part=9,
> val=GridServiceAssignmentsKey [name=testService-175], hasValBytes=true],
> val=CacheObjectImpl [val=GridServiceAssignments
> [nodeId=bdeeb063-5558-4dab-90c3-b61b91b338f0, topVer=6,
> cfg=LazyServiceConfiguration
> [srvcClsName=org.apache.ignite.internal.processors.service.DummyService,
> svcCls=, nodeFilterCls=AttributeFilter], assigns=HashMap
> {0069f119-2516-48ee-866c-8a3ba55f8000=0,
> dcf0a942-d7d0-4574-870a-6b251740=0,
> ce88f2ef-5c88-46f1-83d4-50dd8163=1,
> 3264d65e-695f-433c-b028-7bff8b82=0,
> 4427ca0c-24c1-4e61-9f04-bbd37d11=0}], hasValBytes=true],
> ver=GridCacheVersion [topVer=151789229, order=1540309225560, nodeOrder=1],
> hash=1705888709, extras=GridCacheMvccEntryExtras [mvcc=GridCacheMvcc
> [locs=LinkedList [GridCacheMvccCandidate
> [nodeId=100f5b42-d915-409b-980c-726f1945a001, ver=GridCacheVersion
> [topVer=151789232, order=1540309225927, nodeOrder=7], threadId=133839,
> id=335933, topVer=AffinityTopologyVersion [topVer=9, minorTopVer=0],
> reentry=null, otherNodeId=100f5b42-d915-409b-980c-726f1945a001,
> otherVer=GridCacheVersion [topVer=151789232, order=1540309225927,
> nodeOrder=7], mappedDhtNodes=null, mappedNearNodes=null, ownerVer=null,
> serOrder=null, key=KeyCacheObjectImpl [part=9, val=GridServiceAssignmentsKey
> [name=testService-175], hasValBytes=true],
> masks=local=1|owner=1|ready=1|reentry=0|used=0|tx=1|single_implicit=1|dht_local=1|near_local=0|removed=0|read=0,
> prevVer=null, nextVer=null]], rmts=null]], flags=2]GridDistributedCacheEntry
> [super=]GridDhtCacheEntry [rdrs=ReaderId[] [], part=9, super=], prepared=1,
> locked=false, nodeId=100f5b42-d915-409b-980c-726f1945a001, locMapped=false,
> expiryPlc=null, transferExpiryPlc=false, flags=0, partUpdateCntr=0,
> serReadVer=null, xidVer=GridCacheVersion [topVer=151789232,
> order=1540309225927, nodeOrder=7]]], dhtVers=null, txSize=0, plc=5,
> txState=null, flags=retVal|last|sys, super=]GridDhtTxPrepareRequest
> [nearNodeId=100f5b42-d915-409b-980c-726f1945a001,
> futId=f0a1fb1a661-0ff0152a-8da5-4117-8c29-4ba138e30072, miniId=1,
> topVer=AffinityTopologyVersion [topVer=9, minorTopVer=0],
> invalidateNearEntries={}, nearWrites=null, owned=null,
> nearXidVer=GridCacheVersion [topVer=151789232, order=1540309225927,
> nodeOrder=7],
[jira] [Updated] (IGNITE-9558) Avoid changing AffinityTopologyVersion on client connect when possible
[ https://issues.apache.org/jira/browse/IGNITE-9558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Lantukh updated IGNITE-9558: - Fix Version/s: 2.8 > Avoid changing AffinityTopologyVersion on client connect when possible > -- > > Key: IGNITE-9558 > URL: https://issues.apache.org/jira/browse/IGNITE-9558 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.0 >Reporter: Alexey Goncharuk >Assignee: Ilya Lantukh >Priority: Major > Fix For: 2.8 > > > Currently a client join event changes discovery topology version which, in > turn, changes AffinityTopologyVersion. > When a client maps transaction on new AffinityTopologyVersion, corresponding > message is not processed on remote node until remote node receives the > corresponding discovery event. If discovery event delivery is delayed for > some reason, this will result in transaction stalls on client joins. > Since the client node does not change partition affinity, we can safely map > transactions on the previous topology version and do not change the affinity > topology version at all. > Some cases need special care and probably do not qualify for this > optimization, such as when client has near cache or client hosts partition > for REPLICATED cache. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9558) Avoid changing AffinityTopologyVersion on client connect when possible
[ https://issues.apache.org/jira/browse/IGNITE-9558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Govorukhin updated IGNITE-9558: --- Ignite Flags: (was: Docs Required) > Avoid changing AffinityTopologyVersion on client connect when possible > -- > > Key: IGNITE-9558 > URL: https://issues.apache.org/jira/browse/IGNITE-9558 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.0 >Reporter: Alexey Goncharuk >Assignee: Ilya Lantukh >Priority: Major > Fix For: 2.8 > > > Currently a client join event changes discovery topology version which, in > turn, changes AffinityTopologyVersion. > When a client maps transaction on new AffinityTopologyVersion, corresponding > message is not processed on remote node until remote node receives the > corresponding discovery event. If discovery event delivery is delayed for > some reason, this will result in transaction stalls on client joins. > Since the client node does not change partition affinity, we can safely map > transactions on the previous topology version and do not change the affinity > topology version at all. > Some cases need special care and probably do not qualify for this > optimization, such as when client has near cache or client hosts partition > for REPLICATED cache. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9673) Timeout in Java Client suite.
[
https://issues.apache.org/jira/browse/IGNITE-9673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665142#comment-16665142
]
Sergey Chugunov commented on IGNITE-9673:
-
[~NSAmelchev],
Changes look good to me, thank you for contribution!
[~dpavlov], could you please assist with merging this patch?
> Timeout in Java Client suite.
> -
>
> Key: IGNITE-9673
> URL: https://issues.apache.org/jira/browse/IGNITE-9673
> Project: Ignite
> Issue Type: Bug
>Reporter: Amelchev Nikita
>Assignee: Amelchev Nikita
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
> Attachments: ThreadDump.txt
>
>
> Example of timeout: [TC
> build|[https://ci.ignite.apache.org/viewLog.html?buildId=1919405=buildResultsDiv=IgniteTests24Java8_JavaClient].]
> The possible reason is non-interruptable future and starvation in stripped
> pool:
> {noformat}
> "test-runner-#2440%redis.RedisProtocolStringSelfTest%" #3843 prio=5 os_prio=0
> tid=0x7f8f053fb000 nid=0x7b19 waiting on condition [0x7f8d74f8f000]
>java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:304)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:177)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:140)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter$22.op(GridCacheAdapter.java:2465)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter$22.op(GridCacheAdapter.java:2463)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.syncOp(GridCacheAdapter.java:4228)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.put0(GridCacheAdapter.java:2463)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:2444)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:2421)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.put(IgniteCacheProxyImpl.java:1089)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.put(GatewayProtectedCacheProxy.java:820)
> at
> org.apache.ignite.internal.processors.rest.protocols.tcp.redis.RedisProtocolStringSelfTest.testStrlen(RedisProtocolStringSelfTest.java:310)
> 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 junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2177)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:143)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:2092)
> at java.lang.Thread.run(Thread.java:748)
> [grid-timeout-worker-#2323%redis.RedisProtocolStringSelfTest0%][G] >>>
> Possible starvation in striped pool.
> Thread name: sys-stripe-3-#2304%redis.RedisProtocolStringSelfTest0%
> Queue: [Message closure [msg=GridIoMessage [plc=2, topic=TOPIC_CACHE,
> topicOrd=8, ordered=false, timeout=0, skipOnTimeout=false,
> msg=GridCacheIdMessage [cacheId=1481046058]GridDistributedBaseMessage
> [ver=GridCacheVersion [topVer=148979816, order=1537499815759, nodeOrder=1],
> committedVers=ArrayList [], rolledbackVers=ArrayList [], cnt=0,
> super=]GridDistributedLockResponse
> [futId=e739f1af561-9bc10183-74c7-4b9a-a525-aef32c002efc, err=null,
> vals=ArrayList [null], super=]GridNearLockResponse [pending=ArrayList [],
> miniId=1, dhtVers=GridCacheVersion[] [GridCacheVersion [topVer=0, order=0,
> nodeOrder=0]], mappedVers=GridCacheVersion[] [GridCacheVersion
> [topVer=148979816, order=1537499815760, nodeOrder=2]], clientRemapVer=null,
> super=]]], Message closure [msg=GridIoMessage [plc=2, topic=TOPIC_CACHE,
> topicOrd=8, ordered=false, timeout=0, skipOnTimeout=false,
> msg=GridDistributedTxFinishResponse [txId=GridCacheVersion [topVer=148979816,
> order=1537499815765, nodeOrder=1],
> futId=e849f1af561-9bc10183-74c7-4b9a-a525-aef32c002efc,
> part=-1]GridNearTxFinishResponse [err=null, miniId=1, nearThreadId=3843,
> super=
> Deadlock: false
> Completed: 5
> "sys-stripe-3-#2304%redis.RedisProtocolStringSelfTest0%" #3628 prio=5
> os_prio=0 tid=0x7f8f054e1800 nid=0x7a41 waiting on condition
> [0x7f8ed2ef]
> java.lang.Thread.State: WAITING
[jira] [Commented] (IGNITE-10004) Parse error leads to leave the transaction
[
https://issues.apache.org/jira/browse/IGNITE-10004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665174#comment-16665174
]
ASF GitHub Bot commented on IGNITE-10004:
-
GitHub user AMashenkov opened a pull request:
https://github.com/apache/ignite/pull/5088
IGNITE-10004: Add test.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-10004
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/5088.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 #5088
commit 4222322e8c5381db458a41d0f1a73791bf067c66
Author: Andrey V. Mashenkov
Date: 2018-10-26T13:21:59Z
IGNITE-10004: Add test.
> Parse error leads to leave the transaction
> --
>
> Key: IGNITE-10004
> URL: https://issues.apache.org/jira/browse/IGNITE-10004
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Affects Versions: 2.7
>Reporter: Sergey Kozlov
>Assignee: Andrew Mashenkov
>Priority: Major
> Fix For: 2.7
>
>
> 1. Start 2 nodes + connect sqlline
> 2. Execute following queries:
> {noformat}
> create table t10 (a int, b varchar, primary key(a)) with
> "ATOMICITY=TRANSACTIONAL_SNAPSHOT,backups=1";
> begin;
> insert into t10 values(1); <- worng set
> insert into t10 values(2, '2'); <- coorect set
> commit;
> {noformat}
> The output:
> {noformat}
> 0: jdbc:ignite:thin://127.0.0.1/> create table t10 (a int, b varchar, primary
> key(a)) with "ATOMICITY=TRANSACTIONAL_SNAP
> SHOT,backups=1";
> No rows affected (0,032 seconds)
> 0: jdbc:ignite:thin://127.0.0.1/> begin;
> No rows affected (0 seconds)
> 0: jdbc:ignite:thin://127.0.0.1/> insert into t10 values(1);
> Error: Failed to parse query. ═хтхЁэюх ъюышўхёЄтю ёЄюысЎют
> Column count does not match; SQL statement:
> insert into t10 values(1) [21002-197] (state=42000,code=1001)
> java.sql.SQLException: Failed to parse query. Неверное количество столбцов
> Column count does not match; SQL statement:
> insert into t10 values(1) [21002-197]
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:750)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
> at sqlline.Commands.execute(Commands.java:823)
> at sqlline.Commands.sql(Commands.java:733)
> at sqlline.SqlLine.dispatch(SqlLine.java:795)
> at sqlline.SqlLine.begin(SqlLine.java:668)
> at sqlline.SqlLine.start(SqlLine.java:373)
> at sqlline.SqlLine.main(SqlLine.java:265)
> 0: jdbc:ignite:thin://127.0.0.1/> insert into t10 values(2, '2');
> Error: Transaction is already completed. (state=25000,code=5004)
> java.sql.SQLException: Transaction is already completed.
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:750)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
> at sqlline.Commands.execute(Commands.java:823)
> at sqlline.Commands.sql(Commands.java:733)
> at sqlline.SqlLine.dispatch(SqlLine.java:795)
> at sqlline.SqlLine.begin(SqlLine.java:668)
> at sqlline.SqlLine.start(SqlLine.java:373)
> at sqlline.SqlLine.main(SqlLine.java:265)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7164) SQL TX: Remap protocol
[
https://issues.apache.org/jira/browse/IGNITE-7164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665175#comment-16665175
]
Ignite TC Bot commented on IGNITE-7164:
---
{panel:title=Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Queries (Binary Objects Simple Mapper){color} [[tests 0 TIMEOUT
, Exit Code |https://ci.ignite.apache.org/viewLog.html?buildId=2166774]]
* IgniteSqlSplitterSelfTest.testIndexSegmentationPartitionedReplicated (last
started)
{color:#d04437}MVCC Queries{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2163369]]
* CacheMvccTxNodeMappingTest.testAllTxNodesAreTrackedSrv (last started)
{color:#d04437}MVCC Cache{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2163367]]
* CacheMvccTransactionsTest.testUpdate_N_Objects_ClientServer_Backups1_Scan
(last started)
{color:#d04437}Continuous Query 1{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2163325]]
* CacheContinuousQueryRandomOperationsTest.testMvccTxExplicit (last started)
{panel}
[TeamCity Run All
Results|http://ci.ignite.apache.org/viewLog.html?buildId=2163421buildTypeId=IgniteTests24Java8_RunAll]
> SQL TX: Remap protocol
> --
>
> Key: IGNITE-7164
> URL: https://issues.apache.org/jira/browse/IGNITE-7164
> Project: Ignite
> Issue Type: Task
> Components: mvcc, sql
>Reporter: Igor Seliverstov
>Assignee: Andrew Mashenkov
>Priority: Major
>
> We need to provide remap protocol on topology changes
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9558) Avoid changing AffinityTopologyVersion on client connect when possible
[
https://issues.apache.org/jira/browse/IGNITE-9558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665211#comment-16665211
]
Ignite TC Bot commented on IGNITE-9558:
---
{panel:title=Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}SPI{color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=2167237]]
* IgniteSpiTestSuite:
GridTcpCommunicationSpiRecoveryNoPairedConnectionsTest.testBlockRead2 - 0,0%
fails in last 100 master runs.
* IgniteSpiTestSuite: TcpDiscoverySslSelfTest.testMulticastIpFinder - 0,0%
fails in last 100 master runs.
{color:#d04437}Platform .NET{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2167298]]
* exe: ServicesTest.TestWithKeepBinaryClient - 0,0% fails in last 100 master
runs.
{color:#d04437}Queries 2{color} [[tests
3|https://ci.ignite.apache.org/viewLog.html?buildId=2167232]]
* IgniteBinaryCacheQueryTestSuite2:
IgniteCacheQueryStopOnCancelOrTimeoutDistributedJoinSelfTest.testTimeout2 -
0,0% fails in last 100 master runs.
{color:#d04437}Cache 7 (With Persistence){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2167279]]
* IgniteCacheTestSuite7:
TransactionIntegrityWithPrimaryIndexCorruptionTest.testPrimaryIndexCorruptionDuringCommitPrimaryNonColocatedThrowsChecked
- 0,0% fails in last 100 master runs.
{color:#d04437}Cache 2{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2167274]]
* IgniteCacheTestSuite2:
IgniteCacheClientNodeChangingTopologyTest.testPessimisticTx2 - 0,0% fails in
last 100 master runs.
{color:#d04437}Cache 6{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2167278]]
* IgniteCacheTestSuite6: CacheExchangeMergeTest.testMergeServerAndClientJoin1 -
0,0% fails in last 100 master runs.
{color:#d04437}JDBC Driver{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2167229]]
{panel}
[TeamCity Run All
Results|http://ci.ignite.apache.org/viewLog.html?buildId=2162502buildTypeId=IgniteTests24Java8_RunAll]
> Avoid changing AffinityTopologyVersion on client connect when possible
> --
>
> Key: IGNITE-9558
> URL: https://issues.apache.org/jira/browse/IGNITE-9558
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 2.0
>Reporter: Alexey Goncharuk
>Assignee: Ilya Lantukh
>Priority: Major
> Fix For: 2.8
>
>
> Currently a client join event changes discovery topology version which, in
> turn, changes AffinityTopologyVersion.
> When a client maps transaction on new AffinityTopologyVersion, corresponding
> message is not processed on remote node until remote node receives the
> corresponding discovery event. If discovery event delivery is delayed for
> some reason, this will result in transaction stalls on client joins.
> Since the client node does not change partition affinity, we can safely map
> transactions on the previous topology version and do not change the affinity
> topology version at all.
> Some cases need special care and probably do not qualify for this
> optimization, such as when client has near cache or client hosts partition
> for REPLICATED cache.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9982) SQLLine: can't run with option --autoCommit=false or true
[
https://issues.apache.org/jira/browse/IGNITE-9982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665246#comment-16665246
]
Ivan Pavlukhin commented on IGNITE-9982:
TC runs:
SQL (failed tests were introduced by this ticket fixes, were fixed and rerun
locally)
https://ci.ignite.apache.org/viewLog.html?buildId=2166855=buildResultsDiv=IgniteTests24Java8_RunAllSql
MVCC JDBC
https://ci.ignite.apache.org/viewLog.html?buildId=2166839=buildResultsDiv=IgniteTests24Java8_MvccCache
> SQLLine: can't run with option --autoCommit=false or true
> -
>
> Key: IGNITE-9982
> URL: https://issues.apache.org/jira/browse/IGNITE-9982
> Project: Ignite
> Issue Type: Bug
> Components: mvcc, sql
>Affects Versions: 2.7
>Reporter: Stepan Pilschikov
>Assignee: Ivan Pavlukhin
>Priority: Major
> Fix For: 2.7
>
>
> Trying to run sqlline with additional options
> {code}
> $ /bin/sqlline.sh --autoCommit=false --color=true --outputFormat=csv
> --showNestedErrs=true --showWarnings=true --verbose=true -u
> jdbc:ignite:thin://127.0.0.1:10800
> {code}
> SQLline is working but with exception on start:
> {code}
> issuing: !connect jdbc:ignite:thin://127.0.0.1:10800 '' ''
> org.apache.ignite.IgniteJdbcThinDriver
> Connecting to jdbc:ignite:thin://127.0.0.1:10800
> Connected to: Apache Ignite (version 2.7.1#20181023-sha1:0ccde7c4)
> Driver: Apache Ignite Thin JDBC Driver (version 2.7.1#20181023-sha1:0ccde7c4)
> Error: MVCC must be enabled in order to invoke transactional operation:
> COMMIT (state=25000,code=5002)
> java.sql.SQLException: MVCC must be enabled in order to invoke transactional
> operation: COMMIT
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:750)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.doCommit(JdbcThinConnection.java:369)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.setAutoCommit(JdbcThinConnection.java:328)
> at sqlline.DatabaseConnection.connect(DatabaseConnection.java:178)
> at
> sqlline.DatabaseConnection.getConnection(DatabaseConnection.java:204)
> at sqlline.Commands.connect(Commands.java:1095)
> at sqlline.Commands.connect(Commands.java:1001)
> 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
> sqlline.ReflectiveCommandHandler.execute(ReflectiveCommandHandler.java:38)
> at sqlline.SqlLine.dispatch(SqlLine.java:791)
> at sqlline.SqlLine.initArgs(SqlLine.java:566)
> at sqlline.SqlLine.begin(SqlLine.java:643)
> at sqlline.SqlLine.start(SqlLine.java:373)
> at sqlline.SqlLine.main(SqlLine.java:265)
> Transaction isolation: TRANSACTION_REPEATABLE_READ
> {code}
> Without --autoCommit option sqlline running without this exception
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10026) [ML] Broken example: GaussianNaiveBayesTrainerExample
[ https://issues.apache.org/jira/browse/IGNITE-10026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Babak updated IGNITE-10026: Ignite Flags: (was: Docs Required) > [ML] Broken example: GaussianNaiveBayesTrainerExample > -- > > Key: IGNITE-10026 > URL: https://issues.apache.org/jira/browse/IGNITE-10026 > Project: Ignite > Issue Type: Bug > Components: ml >Affects Versions: 2.8 >Reporter: Yury Babak >Assignee: Yury Babak >Priority: Major > Fix For: 2.8 > > > Broken example: GaussianNaiveBayesTrainerExample -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10028) Incorrect handling of page on replacement
Vladislav Pyatkov created IGNITE-10028: -- Summary: Incorrect handling of page on replacement Key: IGNITE-10028 URL: https://issues.apache.org/jira/browse/IGNITE-10028 Project: Ignite Issue Type: Bug Reporter: Vladislav Pyatkov We can to pass incorrect page version to IgniteCacheSnapshotManager. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10021) IgniteInterruptedCheckedException: sleep interrupted in GridServiceProcessorBatchDeploySelfTest#testCancelAllTopologyChange
[
https://issues.apache.org/jira/browse/IGNITE-10021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Ignatenko updated IGNITE-10021:
Attachment:
GridServiceProcessorBatchDeploySelfTest.testCancelAllTopologyChange.log
> IgniteInterruptedCheckedException: sleep interrupted in
> GridServiceProcessorBatchDeploySelfTest#testCancelAllTopologyChange
> ---
>
> Key: IGNITE-10021
> URL: https://issues.apache.org/jira/browse/IGNITE-10021
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Oleg Ignatenko
>Priority: Major
> Attachments:
> GridServiceProcessorBatchDeploySelfTest.testCancelAllTopologyChange.log
>
>
> Test {{GridServiceProcessorBatchDeploySelfTest#testCancelAllTopologyChange}}
> failed at TC (couldn't reproduce locally), error message:
> {noformat}
> [2018-10-23
> 15:40:25,651][ERROR][srvc-deploy-#121506%extra-node-1%][TcpCommunicationSpi]
> Failed to send message to remote node [node=TcpDiscoveryNode
> [id=ce88f2ef-5c88-46f1-83d4-50dd8163, addrs=ArrayList [127.0.0.1],
> sockAddrs=HashSet [/127.0.0.1:47503], discPort=47503, order=4, intOrder=4,
> lastExchangeTime=1540309225078, loc=false, ver=2.7.0#20181023-sha1:d09f1d47,
> isClient=false], msg=GridIoMessage [plc=5, topic=TOPIC_CACHE, topicOrd=8,
> ordered=false, timeout=0, skipOnTimeout=false, msg=GridCacheIdMessage
> [cacheId=0]GridDistributedBaseMessage [ver=GridCacheVersion
> [topVer=151789232, order=1540309225927, nodeOrder=7], committedVers=null,
> rolledbackVers=null, cnt=0, super=]GridDistributedTxPrepareRequest
> [threadId=133839, concurrency=OPTIMISTIC, isolation=READ_COMMITTED,
> writeVer=GridCacheVersion [topVer=151789232, order=1540309225928,
> nodeOrder=7], timeout=0, reads=null, writes=PredicateCollectionView
> [IgniteTxEntry [key=KeyCacheObjectImpl [part=9, val=GridServiceAssignmentsKey
> [name=testService-175], hasValBytes=true], cacheId=-2100569601,
> txKey=IgniteTxKey [key=KeyCacheObjectImpl [part=9,
> val=GridServiceAssignmentsKey [name=testService-175], hasValBytes=true],
> cacheId=-2100569601], val=[op=DELETE, val=null], prevVal=[op=NOOP, val=null],
> oldVal=[op=NOOP, val=null], entryProcessorsCol=null, ttl=-1,
> conflictExpireTime=-1, conflictVer=null, explicitVer=null, dhtVer=null,
> filters=CacheEntryPredicate[] [], filtersPassed=false, filtersSet=true,
> entry=GridCacheMapEntry [key=KeyCacheObjectImpl [part=9,
> val=GridServiceAssignmentsKey [name=testService-175], hasValBytes=true],
> val=CacheObjectImpl [val=GridServiceAssignments
> [nodeId=bdeeb063-5558-4dab-90c3-b61b91b338f0, topVer=6,
> cfg=LazyServiceConfiguration
> [srvcClsName=org.apache.ignite.internal.processors.service.DummyService,
> svcCls=, nodeFilterCls=AttributeFilter], assigns=HashMap
> {0069f119-2516-48ee-866c-8a3ba55f8000=0,
> dcf0a942-d7d0-4574-870a-6b251740=0,
> ce88f2ef-5c88-46f1-83d4-50dd8163=1,
> 3264d65e-695f-433c-b028-7bff8b82=0,
> 4427ca0c-24c1-4e61-9f04-bbd37d11=0}], hasValBytes=true],
> ver=GridCacheVersion [topVer=151789229, order=1540309225560, nodeOrder=1],
> hash=1705888709, extras=GridCacheMvccEntryExtras [mvcc=GridCacheMvcc
> [locs=LinkedList [GridCacheMvccCandidate
> [nodeId=100f5b42-d915-409b-980c-726f1945a001, ver=GridCacheVersion
> [topVer=151789232, order=1540309225927, nodeOrder=7], threadId=133839,
> id=335933, topVer=AffinityTopologyVersion [topVer=9, minorTopVer=0],
> reentry=null, otherNodeId=100f5b42-d915-409b-980c-726f1945a001,
> otherVer=GridCacheVersion [topVer=151789232, order=1540309225927,
> nodeOrder=7], mappedDhtNodes=null, mappedNearNodes=null, ownerVer=null,
> serOrder=null, key=KeyCacheObjectImpl [part=9, val=GridServiceAssignmentsKey
> [name=testService-175], hasValBytes=true],
> masks=local=1|owner=1|ready=1|reentry=0|used=0|tx=1|single_implicit=1|dht_local=1|near_local=0|removed=0|read=0,
> prevVer=null, nextVer=null]], rmts=null]], flags=2]GridDistributedCacheEntry
> [super=]GridDhtCacheEntry [rdrs=ReaderId[] [], part=9, super=], prepared=1,
> locked=false, nodeId=100f5b42-d915-409b-980c-726f1945a001, locMapped=false,
> expiryPlc=null, transferExpiryPlc=false, flags=0, partUpdateCntr=0,
> serReadVer=null, xidVer=GridCacheVersion [topVer=151789232,
> order=1540309225927, nodeOrder=7]]], dhtVers=null, txSize=0, plc=5,
> txState=null, flags=retVal|last|sys, super=]GridDhtTxPrepareRequest
> [nearNodeId=100f5b42-d915-409b-980c-726f1945a001,
> futId=f0a1fb1a661-0ff0152a-8da5-4117-8c29-4ba138e30072, miniId=1,
> topVer=AffinityTopologyVersion [topVer=9, minorTopVer=0],
> invalidateNearEntries={}, nearWrites=null, owned=null,
> nearXidVer=GridCacheVersion [topVer=151789232, order=1540309225927,
> nodeOrder=7],
[jira] [Created] (IGNITE-10021) IgniteInterruptedCheckedException: sleep interrupted in GridServiceProcessorBatchDeploySelfTest#testCancelAllTopologyChange
Oleg Ignatenko created IGNITE-10021:
---
Summary: IgniteInterruptedCheckedException: sleep interrupted in
GridServiceProcessorBatchDeploySelfTest#testCancelAllTopologyChange
Key: IGNITE-10021
URL: https://issues.apache.org/jira/browse/IGNITE-10021
Project: Ignite
Issue Type: Bug
Affects Versions: 2.6
Reporter: Oleg Ignatenko
Attachments:
GridServiceProcessorBatchDeploySelfTest.testCancelAllTopologyChange.log
Test {{GridServiceProcessorBatchDeploySelfTest#testCancelAllTopologyChange}}
failed at TC (couldn't reproduce locally), error message:
{noformat}
[2018-10-23
15:40:25,651][ERROR][srvc-deploy-#121506%extra-node-1%][TcpCommunicationSpi]
Failed to send message to remote node [node=TcpDiscoveryNode
[id=ce88f2ef-5c88-46f1-83d4-50dd8163, addrs=ArrayList [127.0.0.1],
sockAddrs=HashSet [/127.0.0.1:47503], discPort=47503, order=4, intOrder=4,
lastExchangeTime=1540309225078, loc=false, ver=2.7.0#20181023-sha1:d09f1d47,
isClient=false], msg=GridIoMessage [plc=5, topic=TOPIC_CACHE, topicOrd=8,
ordered=false, timeout=0, skipOnTimeout=false, msg=GridCacheIdMessage
[cacheId=0]GridDistributedBaseMessage [ver=GridCacheVersion [topVer=151789232,
order=1540309225927, nodeOrder=7], committedVers=null, rolledbackVers=null,
cnt=0, super=]GridDistributedTxPrepareRequest [threadId=133839,
concurrency=OPTIMISTIC, isolation=READ_COMMITTED, writeVer=GridCacheVersion
[topVer=151789232, order=1540309225928, nodeOrder=7], timeout=0, reads=null,
writes=PredicateCollectionView [IgniteTxEntry [key=KeyCacheObjectImpl [part=9,
val=GridServiceAssignmentsKey [name=testService-175], hasValBytes=true],
cacheId=-2100569601, txKey=IgniteTxKey [key=KeyCacheObjectImpl [part=9,
val=GridServiceAssignmentsKey [name=testService-175], hasValBytes=true],
cacheId=-2100569601], val=[op=DELETE, val=null], prevVal=[op=NOOP, val=null],
oldVal=[op=NOOP, val=null], entryProcessorsCol=null, ttl=-1,
conflictExpireTime=-1, conflictVer=null, explicitVer=null, dhtVer=null,
filters=CacheEntryPredicate[] [], filtersPassed=false, filtersSet=true,
entry=GridCacheMapEntry [key=KeyCacheObjectImpl [part=9,
val=GridServiceAssignmentsKey [name=testService-175], hasValBytes=true],
val=CacheObjectImpl [val=GridServiceAssignments
[nodeId=bdeeb063-5558-4dab-90c3-b61b91b338f0, topVer=6,
cfg=LazyServiceConfiguration
[srvcClsName=org.apache.ignite.internal.processors.service.DummyService,
svcCls=, nodeFilterCls=AttributeFilter], assigns=HashMap
{0069f119-2516-48ee-866c-8a3ba55f8000=0,
dcf0a942-d7d0-4574-870a-6b251740=0, ce88f2ef-5c88-46f1-83d4-50dd8163=1,
3264d65e-695f-433c-b028-7bff8b82=0,
4427ca0c-24c1-4e61-9f04-bbd37d11=0}], hasValBytes=true],
ver=GridCacheVersion [topVer=151789229, order=1540309225560, nodeOrder=1],
hash=1705888709, extras=GridCacheMvccEntryExtras [mvcc=GridCacheMvcc
[locs=LinkedList [GridCacheMvccCandidate
[nodeId=100f5b42-d915-409b-980c-726f1945a001, ver=GridCacheVersion
[topVer=151789232, order=1540309225927, nodeOrder=7], threadId=133839,
id=335933, topVer=AffinityTopologyVersion [topVer=9, minorTopVer=0],
reentry=null, otherNodeId=100f5b42-d915-409b-980c-726f1945a001,
otherVer=GridCacheVersion [topVer=151789232, order=1540309225927, nodeOrder=7],
mappedDhtNodes=null, mappedNearNodes=null, ownerVer=null, serOrder=null,
key=KeyCacheObjectImpl [part=9, val=GridServiceAssignmentsKey
[name=testService-175], hasValBytes=true],
masks=local=1|owner=1|ready=1|reentry=0|used=0|tx=1|single_implicit=1|dht_local=1|near_local=0|removed=0|read=0,
prevVer=null, nextVer=null]], rmts=null]], flags=2]GridDistributedCacheEntry
[super=]GridDhtCacheEntry [rdrs=ReaderId[] [], part=9, super=], prepared=1,
locked=false, nodeId=100f5b42-d915-409b-980c-726f1945a001, locMapped=false,
expiryPlc=null, transferExpiryPlc=false, flags=0, partUpdateCntr=0,
serReadVer=null, xidVer=GridCacheVersion [topVer=151789232,
order=1540309225927, nodeOrder=7]]], dhtVers=null, txSize=0, plc=5,
txState=null, flags=retVal|last|sys, super=]GridDhtTxPrepareRequest
[nearNodeId=100f5b42-d915-409b-980c-726f1945a001,
futId=f0a1fb1a661-0ff0152a-8da5-4117-8c29-4ba138e30072, miniId=1,
topVer=AffinityTopologyVersion [topVer=9, minorTopVer=0],
invalidateNearEntries={}, nearWrites=null, owned=null,
nearXidVer=GridCacheVersion [topVer=151789232, order=1540309225927,
nodeOrder=7], subjId=100f5b42-d915-409b-980c-726f1945a001, taskNameHash=0,
preloadKeys=null, mvccSnapshot=null, skipCompletedVers=true, super=]]]
class org.apache.ignite.internal.IgniteInterruptedCheckedException: sleep
interrupted
at org.apache.ignite.internal.util.IgniteUtils.sleep(IgniteUtils.java:7782)
at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.reserveClient(TcpCommunicationSpi.java:2888)
at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage0(TcpCommunicationSpi.java:2713)
at
[jira] [Updated] (IGNITE-10007) Deactivation hangs if an open transaction exists
[
https://issues.apache.org/jira/browse/IGNITE-10007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov updated IGNITE-10007:
---
Attachment: stacktrace_18308.txt
stacktrace_7808.txt
> Deactivation hangs if an open transaction exists
>
>
> Key: IGNITE-10007
> URL: https://issues.apache.org/jira/browse/IGNITE-10007
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Affects Versions: 2.7
>Reporter: Sergey Kozlov
>Assignee: Sergey Kozlov
>Priority: Major
> Fix For: 2.7
>
> Attachments:
> PersistenceDeactivationWIthActiveMvccTransactionSelfTest.java,
> stacktrace_18308.txt, stacktrace_7808.txt
>
>
> 1. Start 2 node with PDS
> 2. Activate cluster
> 3. Connect sqlline
> 4. Create table {{create table t1(a int, b varchar, primary key(a)) with
> "ATOMICITY=TRANSACTIONAL_SNAPSHOT,backups=1";}}
> 3.Start TX and execute a DML commnd:
> {noformat}
> begin;
> insert into t1 values (1, '1');
> {noformat}
> 4. Try deactivate cluster {{bin/control.bat --deactivate}}. The scripts
> doesn't return control.
> 5. Show LRT:
> {noformat}
> c:\Work\apache-ignite-2.7.0-SNAPSHOT-bin>bin\control.bat --tx
> Control utility [ver. 2.7.0-SNAPSHOT#19700101-sha1:DEV]
> 2018 Copyright(C) Apache Software Foundation
> User:
>
> Matching transactions:
> TcpDiscoveryNode [id=5d3e8936-174d-42e2-a47f-c70ec02bccab, addrs=[127.0.0.1],
> order=1, ver=2.7.0#19700101-sha1:,
> isClient=false, consistentId=1]
> Tx: [xid=74bc1aba661--090e-b121--0001, label=null,
> state=ACTIVE, startTime=2018-10-25 17:34:35.5
> 22, duration=352, isolation=REPEATABLE_READ, concurrency=PESSIMISTIC,
> topVer=AffinityTopologyVersion [topVer=2, minorTop
> Ver=6], timeout=0, size=0, dhtNodes=[41ff88d2],
> nearXid=74bc1aba661--090e-b121--0001, parentNodeIds=
> [5d3e8936]]
> {noformat}
> 6. Complete TX:
> {noformat}
> 0: jdbc:ignite:thin://127.0.0.1/> commit;
> Error: class org.apache.ignite.IgniteException: Can not perform the operation
> because the cluster is inactive. Note, tha
> t the cluster is considered inactive by default if Ignite Persistent Store is
> used to let all the nodes join the cluster
> . To activate the cluster call Ignite.active(true). (state=5,code=1)
> java.sql.SQLException: class org.apache.ignite.IgniteException: Can not
> perform the operation because the cluster is ina
> ctive. Note, that the cluster is considered inactive by default if Ignite
> Persistent Store is used to let all the nodes
> join the cluster. To activate the cluster call Ignite.active(true).
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:750)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
> at sqlline.Commands.execute(Commands.java:823)
> at sqlline.Commands.sql(Commands.java:733)
> at sqlline.SqlLine.dispatch(SqlLine.java:795)
> at sqlline.SqlLine.begin(SqlLine.java:668)
> at sqlline.SqlLine.start(SqlLine.java:373)
> at sqlline.SqlLine.main(SqlLine.java:265)
> 0: jdbc:ignite:thin://127.0.0.1/>
> {noformat}
> It.s ok but LRT is still presented and deactivation script doesn't return
> control back to user:
> {noformat}
> c:\Work\apache-ignite-2.7.0-SNAPSHOT-bin>bin\control.bat --tx
> Control utility [ver. 2.7.0-SNAPSHOT#19700101-sha1:DEV]
> 2018 Copyright(C) Apache Software Foundation
> User:
>
> Matching transactions:
> TcpDiscoveryNode [id=5d3e8936-174d-42e2-a47f-c70ec02bccab, addrs=[127.0.0.1],
> order=1, ver=2.7.0#19700101-sha1:,
> isClient=false, consistentId=1]
> Tx: [xid=74bc1aba661--090e-b121--0001, label=null,
> state=ACTIVE, startTime=2018-10-25 17:34:35.5
> 22, duration=510, isolation=REPEATABLE_READ, concurrency=PESSIMISTIC,
> topVer=AffinityTopologyVersion [topVer=2, minorTop
> Ver=6], timeout=0, size=0, dhtNodes=[41ff88d2],
> nearXid=74bc1aba661--090e-b121--0001, parentNodeIds=
> [5d3e8936]]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10004) Parse error leads to leave the transaction
[
https://issues.apache.org/jira/browse/IGNITE-10004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Mashenkov updated IGNITE-10004:
--
Component/s: sql
> Parse error leads to leave the transaction
> --
>
> Key: IGNITE-10004
> URL: https://issues.apache.org/jira/browse/IGNITE-10004
> Project: Ignite
> Issue Type: Bug
> Components: mvcc, sql
>Affects Versions: 2.7
>Reporter: Sergey Kozlov
>Assignee: Andrew Mashenkov
>Priority: Major
> Fix For: 2.7
>
>
> 1. Start 2 nodes + connect sqlline
> 2. Execute following queries:
> {noformat}
> create table t10 (a int, b varchar, primary key(a)) with
> "ATOMICITY=TRANSACTIONAL_SNAPSHOT,backups=1";
> begin;
> insert into t10 values(1); <- worng set
> insert into t10 values(2, '2'); <- coorect set
> commit;
> {noformat}
> The output:
> {noformat}
> 0: jdbc:ignite:thin://127.0.0.1/> create table t10 (a int, b varchar, primary
> key(a)) with "ATOMICITY=TRANSACTIONAL_SNAP
> SHOT,backups=1";
> No rows affected (0,032 seconds)
> 0: jdbc:ignite:thin://127.0.0.1/> begin;
> No rows affected (0 seconds)
> 0: jdbc:ignite:thin://127.0.0.1/> insert into t10 values(1);
> Error: Failed to parse query. ═хтхЁэюх ъюышўхёЄтю ёЄюысЎют
> Column count does not match; SQL statement:
> insert into t10 values(1) [21002-197] (state=42000,code=1001)
> java.sql.SQLException: Failed to parse query. Неверное количество столбцов
> Column count does not match; SQL statement:
> insert into t10 values(1) [21002-197]
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:750)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
> at sqlline.Commands.execute(Commands.java:823)
> at sqlline.Commands.sql(Commands.java:733)
> at sqlline.SqlLine.dispatch(SqlLine.java:795)
> at sqlline.SqlLine.begin(SqlLine.java:668)
> at sqlline.SqlLine.start(SqlLine.java:373)
> at sqlline.SqlLine.main(SqlLine.java:265)
> 0: jdbc:ignite:thin://127.0.0.1/> insert into t10 values(2, '2');
> Error: Transaction is already completed. (state=25000,code=5004)
> java.sql.SQLException: Transaction is already completed.
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:750)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
> at sqlline.Commands.execute(Commands.java:823)
> at sqlline.Commands.sql(Commands.java:733)
> at sqlline.SqlLine.dispatch(SqlLine.java:795)
> at sqlline.SqlLine.begin(SqlLine.java:668)
> at sqlline.SqlLine.start(SqlLine.java:373)
> at sqlline.SqlLine.main(SqlLine.java:265)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10023) Improve ListeningTestLogger for wait conditions.
Amelchev Nikita created IGNITE-10023:
Summary: Improve ListeningTestLogger for wait conditions.
Key: IGNITE-10023
URL: https://issues.apache.org/jira/browse/IGNITE-10023
Project: Ignite
Issue Type: Improvement
Reporter: Amelchev Nikita
Assignee: Amelchev Nikita
Fix For: 2.8
[Dev-list
discussion.|http://apache-ignite-developers.2346864.n4.nabble.com/Unreliable-checks-in-tests-for-string-presence-in-GridStringLogger-contents-td30802.html]
Method LogListener.check() should be boolean type.
It'll be useful for wait for conditions and code readability:
For now:
{code:java}
waitForCondition(() -> {
try {
lsnr.check();
return true;
}
catch (AssertionError ignored) {
return false;
}
}, timeout);
{code}
After improvement:
{code:java}
waitForCondition(lsnr::check, timeout);
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9991) thin clients: can't use array as cache key for PHP, JS and Python clients
[
https://issues.apache.org/jira/browse/IGNITE-9991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665238#comment-16665238
]
Igor Sapego commented on IGNITE-9991:
-
Changed priority to minor. Usage of an array as a key does not seem like a
production use case to me.
> thin clients: can't use array as cache key for PHP, JS and Python clients
> -
>
> Key: IGNITE-9991
> URL: https://issues.apache.org/jira/browse/IGNITE-9991
> Project: Ignite
> Issue Type: Bug
> Components: thin client
>Affects Versions: 2.7
>Reporter: Stepan Pilschikov
>Priority: Minor
>
> Trying to put cache with key as values array
> Put Py code
> {code}
> cache = client.get_or_create_cache("PY_BOOLEAN_ARRAY")
> cache.put([True, False], 1, key_hint=BoolArrayObject, value_hint=IntObject)
> {code}
> Get
> {code}
> cache = client.get_or_create_cache("PY_BOOLEAN_ARRAY")
> print(cache.get([True, False] key_hint=BoolArrayObject))
> {code}
> output: null
> Same thing with PHP, JS clients and all others array data types
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9991) thin clients: can't use array as cache key for PHP, JS and Python clients
[
https://issues.apache.org/jira/browse/IGNITE-9991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665258#comment-16665258
]
Alexey Kosenchuk commented on IGNITE-9991:
--
[~spilschikov] no problem at all! You've found an issue anyway. Thanks for
scrupulous testing!
> thin clients: can't use array as cache key for PHP, JS and Python clients
> -
>
> Key: IGNITE-9991
> URL: https://issues.apache.org/jira/browse/IGNITE-9991
> Project: Ignite
> Issue Type: Bug
> Components: thin client
>Affects Versions: 2.7
>Reporter: Stepan Pilschikov
>Priority: Minor
>
> Trying to put cache with key as values array
> Put Py code
> {code}
> cache = client.get_or_create_cache("PY_BOOLEAN_ARRAY")
> cache.put([True, False], 1, key_hint=BoolArrayObject, value_hint=IntObject)
> {code}
> Get
> {code}
> cache = client.get_or_create_cache("PY_BOOLEAN_ARRAY")
> print(cache.get([True, False] key_hint=BoolArrayObject))
> {code}
> output: null
> Same thing with PHP, JS clients and all others array data types
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10025) CPP: Runtime code deployment
Igor Sapego created IGNITE-10025: Summary: CPP: Runtime code deployment Key: IGNITE-10025 URL: https://issues.apache.org/jira/browse/IGNITE-10025 Project: Ignite Issue Type: New Feature Components: platforms Reporter: Igor Sapego Fix For: 2.8 It would be useful for a user to have an ability to deploy code (dll, so, etc) in cluster on a selected subset of nodes. This task can be split in a 3 steps: 1. Uploading module to selected subset of nodes. 2. Loading module dynamically on the whole subset. 3. Initializing of a module (i.e. registering callables, declared in the module within Ignite) This also may require partial implementation of a Cluster API - IGNITE-5708 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-10025) CPP: Runtime code deployment
[ https://issues.apache.org/jira/browse/IGNITE-10025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego reassigned IGNITE-10025: Assignee: Igor Sapego > CPP: Runtime code deployment > > > Key: IGNITE-10025 > URL: https://issues.apache.org/jira/browse/IGNITE-10025 > Project: Ignite > Issue Type: New Feature > Components: platforms >Reporter: Igor Sapego >Assignee: Igor Sapego >Priority: Major > Labels: cpp > Fix For: 2.8 > > > It would be useful for a user to have an ability to deploy code (dll, so, > etc) in cluster on a selected subset of nodes. > This task can be split in a 3 steps: > 1. Uploading module to selected subset of nodes. > 2. Loading module dynamically on the whole subset. > 3. Initializing of a module (i.e. registering callables, declared in the > module within Ignite) > This also may require partial implementation of a Cluster API - IGNITE-5708 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10004) Parse error leads to leave the transaction
[
https://issues.apache.org/jira/browse/IGNITE-10004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Mashenkov updated IGNITE-10004:
--
Ignite Flags: (was: Docs Required)
> Parse error leads to leave the transaction
> --
>
> Key: IGNITE-10004
> URL: https://issues.apache.org/jira/browse/IGNITE-10004
> Project: Ignite
> Issue Type: Bug
> Components: mvcc, sql
>Affects Versions: 2.7
>Reporter: Sergey Kozlov
>Assignee: Andrew Mashenkov
>Priority: Major
> Fix For: 2.7
>
>
> 1. Start 2 nodes + connect sqlline
> 2. Execute following queries:
> {noformat}
> create table t10 (a int, b varchar, primary key(a)) with
> "ATOMICITY=TRANSACTIONAL_SNAPSHOT,backups=1";
> begin;
> insert into t10 values(1); <- wrong set
> insert into t10 values(2, '2'); <- correct set
> commit;
> {noformat}
> The output:
> {noformat}
> 0: jdbc:ignite:thin://127.0.0.1/> create table t10 (a int, b varchar, primary
> key(a)) with "ATOMICITY=TRANSACTIONAL_SNAP
> SHOT,backups=1";
> No rows affected (0,032 seconds)
> 0: jdbc:ignite:thin://127.0.0.1/> begin;
> No rows affected (0 seconds)
> 0: jdbc:ignite:thin://127.0.0.1/> insert into t10 values(1);
> Error: Failed to parse query. ═хтхЁэюх ъюышўхёЄтю ёЄюысЎют
> Column count does not match; SQL statement:
> insert into t10 values(1) [21002-197] (state=42000,code=1001)
> java.sql.SQLException: Failed to parse query. Неверное количество столбцов
> Column count does not match; SQL statement:
> insert into t10 values(1) [21002-197]
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:750)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
> at sqlline.Commands.execute(Commands.java:823)
> at sqlline.Commands.sql(Commands.java:733)
> at sqlline.SqlLine.dispatch(SqlLine.java:795)
> at sqlline.SqlLine.begin(SqlLine.java:668)
> at sqlline.SqlLine.start(SqlLine.java:373)
> at sqlline.SqlLine.main(SqlLine.java:265)
> 0: jdbc:ignite:thin://127.0.0.1/> insert into t10 values(2, '2');
> Error: Transaction is already completed. (state=25000,code=5004)
> java.sql.SQLException: Transaction is already completed.
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:750)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
> at sqlline.Commands.execute(Commands.java:823)
> at sqlline.Commands.sql(Commands.java:733)
> at sqlline.SqlLine.dispatch(SqlLine.java:795)
> at sqlline.SqlLine.begin(SqlLine.java:668)
> at sqlline.SqlLine.start(SqlLine.java:373)
> at sqlline.SqlLine.main(SqlLine.java:265)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-3467) jdbc getTables() returns catalog as null
[ https://issues.apache.org/jira/browse/IGNITE-3467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665440#comment-16665440 ] Pavel Kuznetsov commented on IGNITE-3467: - [~vozerov] Thank you, I've updated pull request. RunAll https://ci.ignite.apache.org/viewQueued.html?itemId=2170131 > jdbc getTables() returns catalog as null > > > Key: IGNITE-3467 > URL: https://issues.apache.org/jira/browse/IGNITE-3467 > Project: Ignite > Issue Type: Bug > Components: jdbc >Affects Versions: 1.6 >Reporter: Alexandre Boudnik >Assignee: Pavel Kuznetsov >Priority: Major > Labels: usability > > Then some jdbc query tool uses null values as catalog name. An H2 database > returns word "DATABASE" in CATALOG column, and then correctly resolves a > fully-qualified name. I would recommend to do the same for these metadata. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9903) Copy only actual amount of data during archiving of WAL segment
[
https://issues.apache.org/jira/browse/IGNITE-9903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Stelmak reassigned IGNITE-9903:
--
Assignee: Alexey Stelmak (was: Andrey Gura)
> Copy only actual amount of data during archiving of WAL segment
> ---
>
> Key: IGNITE-9903
> URL: https://issues.apache.org/jira/browse/IGNITE-9903
> Project: Ignite
> Issue Type: Improvement
>Reporter: Andrey Gura
>Assignee: Alexey Stelmak
>Priority: Major
> Fix For: 2.8
>
>
> Current WAL archiver implementation copies full WAL segment to the archive
> while actual size of the segment can be significantly less then
> {{maxWalSegmentSize}} (segment files are preallocated for max possible
> segment size).
> In order to reduce disk space consuming we need copy only actual data of
> segment using {{SWITCH_SEGMENT_RECORD}} as marker. It will require some kind
> of WAL iterator implementation that will just copy WAL records using
> information about record size without records deserialization.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9976) [Test Failed] BinaryMetadataUpdatesFlowTest.testFlowNoConflicts flaky fails on TC.
[
https://issues.apache.org/jira/browse/IGNITE-9976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin updated IGNITE-9976:
-
Description:
Test {{BinaryMetadataUpdatesFlowTest.testFlowNoConflicts}} fails sometimes on
master branch.
Example of recent failure:
https://ci.ignite.apache.org/viewLog.html?buildId=2136137=buildResultsDiv=IgniteTests24Java8_BinaryObjects#testNameId-3561618975502992496
Typical failure 1:
{noformat}
[2018-10-20 16:26:55,321][ERROR][main][root] Test failed.
junit.framework.AssertionFailedError: There are less than expected entries,
data loss occurred; expected:<5000> but was:<4108>
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.Assert.failNotEquals(Assert.java:329)
at junit.framework.Assert.assertEquals(Assert.java:78)
at junit.framework.Assert.assertEquals(Assert.java:234)
at junit.framework.TestCase.assertEquals(TestCase.java:401)
at
org.apache.ignite.internal.processors.cache.binary.BinaryMetadataUpdatesFlowTest.testFlowNoConflicts(BinaryMetadataUpdatesFlowTest.java:309)
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 junit.framework.TestCase.runTest(TestCase.java:176)
at
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2176)
at
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:142)
at
org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:2091)
at java.lang.Thread.run(Thread.java:748)
{noformat}
Suggested solution - await {{PME}} before call {{IgniteCache#size()}}.
Typical failure 2:
{noformat}
java.lang.AssertionError: Error occurred on grid stop (see log for more
details).
...
[ERROR][node-killer-thread][root] Failed to stop grid
[igniteInstanceName=binary.BinaryMetadataUpdatesFlowTest2, cancel=false]
class org.apache.ignite.internal.IgniteInterruptedCheckedException: sleep
interrupted
at org.apache.ignite.internal.util.IgniteUtils.sleep(IgniteUtils.java:7783)
at
org.apache.ignite.testframework.GridTestUtils.waitForCondition(GridTestUtils.java:1737)
at
org.apache.ignite.testframework.junits.GridAbstractTest.awaitTopologyChange(GridAbstractTest.java:2325)
at
org.apache.ignite.testframework.junits.GridAbstractTest.stopGrid(GridAbstractTest.java:1187)
at
org.apache.ignite.testframework.junits.GridAbstractTest.stopGrid(GridAbstractTest.java:1162)
at
org.apache.ignite.testframework.junits.GridAbstractTest.stopGrid(GridAbstractTest.java:1462)
at
org.apache.ignite.internal.processors.cache.binary.BinaryMetadataUpdatesFlowTest.access$900(BinaryMetadataUpdatesFlowTest.java:65)
at
org.apache.ignite.internal.processors.cache.binary.BinaryMetadataUpdatesFlowTest$ServerNodeKiller.run(BinaryMetadataUpdatesFlowTest.java:444)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.InterruptedException: sleep interrupted
at java.lang.Thread.sleep(Native Method)
at org.apache.ignite.internal.util.IgniteUtils.sleep(IgniteUtils.java:7778)
... 8 more
{noformat}
Suggested solution - in test framework don't interrupt thread from which we
call the {{stopGrid}}.
was:
Test {{BinaryMetadataUpdatesFlowTest.testFlowNoConflicts}} fails sometimes on
master branch.
Example of recent failure:
https://ci.ignite.apache.org/viewLog.html?buildId=2136137=buildResultsDiv=IgniteTests24Java8_BinaryObjects#testNameId-3561618975502992496
Typical failure 1:
{noformat}
[2018-10-20 16:26:55,321][ERROR][main][root] Test failed.
junit.framework.AssertionFailedError: There are less than expected entries,
data loss occurred; expected:<5000> but was:<4108>
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.Assert.failNotEquals(Assert.java:329)
at junit.framework.Assert.assertEquals(Assert.java:78)
at junit.framework.Assert.assertEquals(Assert.java:234)
at junit.framework.TestCase.assertEquals(TestCase.java:401)
at
org.apache.ignite.internal.processors.cache.binary.BinaryMetadataUpdatesFlowTest.testFlowNoConflicts(BinaryMetadataUpdatesFlowTest.java:309)
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 junit.framework.TestCase.runTest(TestCase.java:176)
at
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2176)
at
[jira] [Closed] (IGNITE-6784) Document cluster activation via REST protocol
[
https://issues.apache.org/jira/browse/IGNITE-6784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda closed IGNITE-6784.
---
> Document cluster activation via REST protocol
> -
>
> Key: IGNITE-6784
> URL: https://issues.apache.org/jira/browse/IGNITE-6784
> Project: Ignite
> Issue Type: Task
> Components: documentation
>Affects Versions: 2.4
>Reporter: Denis Magda
>Assignee: Denis Magda
>Priority: Major
> Fix For: 2.7
>
>
> Starting Ignite 2.3 cluster can be activated with REST protocol. The
> following commands are supported:
> - {{activate}} - actives the cluster.
> - {{deactivate}} - deactivates the cluster.
> - {{currentstate}} - checks current cluster state.
> Update both pages below:
> https://apacheignite.readme.io/docs/rest-api
> https://apacheignite.readme.io/v2.2/docs/cluster-activation
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-6784) Document cluster activation via REST protocol
[
https://issues.apache.org/jira/browse/IGNITE-6784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665548#comment-16665548
]
Denis Magda commented on IGNITE-6784:
-
[~pgarg], thanks a lot, looks good to me!
> Document cluster activation via REST protocol
> -
>
> Key: IGNITE-6784
> URL: https://issues.apache.org/jira/browse/IGNITE-6784
> Project: Ignite
> Issue Type: Task
> Components: documentation
>Affects Versions: 2.4
>Reporter: Denis Magda
>Assignee: Denis Magda
>Priority: Major
> Fix For: 2.7
>
>
> Starting Ignite 2.3 cluster can be activated with REST protocol. The
> following commands are supported:
> - {{activate}} - actives the cluster.
> - {{deactivate}} - deactivates the cluster.
> - {{currentstate}} - checks current cluster state.
> Update both pages below:
> https://apacheignite.readme.io/docs/rest-api
> https://apacheignite.readme.io/v2.2/docs/cluster-activation
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IGNITE-9848) [TC Bot] Background upload of all builds from TC to the bot DB
[ https://issues.apache.org/jira/browse/IGNITE-9848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov resolved IGNITE-9848. Resolution: Fixed Done in V20181026, additional entities to be loaded in a separate issue. > [TC Bot] Background upload of all builds from TC to the bot DB > --- > > Key: IGNITE-9848 > URL: https://issues.apache.org/jira/browse/IGNITE-9848 > Project: Ignite > Issue Type: Task >Reporter: Dmitriy Pavlov >Assignee: Dmitriy Pavlov >Priority: Major > > To fix slow loading of PR report and Master trends page. > Upload all tracked and observed branches related builds into TC Bot's Ignite > DB. > Prepare compacted entities to reduce storage size. > Implement idea of having fat build, which will represent replies from a > number of REST services. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10019) Documentation: partition preloading
[ https://issues.apache.org/jira/browse/IGNITE-10019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-10019: -- Component/s: documentation > Documentation: partition preloading > --- > > Key: IGNITE-10019 > URL: https://issues.apache.org/jira/browse/IGNITE-10019 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Alexei Scherbakov >Assignee: Artem Budnikov >Priority: Major > Fix For: 2.8 > > > We have to add documentation for partition preloading feature: > IgniteCache.preloadPartition -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8873) Optimize cache scans with enabled persistence.
[ https://issues.apache.org/jira/browse/IGNITE-8873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-8873: - Ignite Flags: Docs Required > Optimize cache scans with enabled persistence. > -- > > Key: IGNITE-8873 > URL: https://issues.apache.org/jira/browse/IGNITE-8873 > Project: Ignite > Issue Type: Improvement >Reporter: Alexei Scherbakov >Assignee: Alexei Scherbakov >Priority: Major > Fix For: 2.8 > > > Currently cache scans with enabled persistence involve link resolution, which > can lead to radom disk access resulting in bad performace on SAS disks. > One possibility is to preload cache data pages to remove slow random disk > access. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10021) IgniteInterruptedCheckedException: sleep interrupted in GridServiceProcessorBatchDeploySelfTest#testCancelAllTopologyChange
[
https://issues.apache.org/jira/browse/IGNITE-10021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Ignatenko updated IGNITE-10021:
Ignite Flags: (was: Docs Required)
> IgniteInterruptedCheckedException: sleep interrupted in
> GridServiceProcessorBatchDeploySelfTest#testCancelAllTopologyChange
> ---
>
> Key: IGNITE-10021
> URL: https://issues.apache.org/jira/browse/IGNITE-10021
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Oleg Ignatenko
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Attachments: GridServiceProcessorBatchDeploySelfTest.java,
> GridServiceProcessorBatchDeploySelfTest.testCancelAllTopologyChange.log
>
>
> Test {{GridServiceProcessorBatchDeploySelfTest#testCancelAllTopologyChange}}
> failed at TC (couldn't reproduce locally), error message:
> {noformat}
> [2018-10-23
> 15:40:25,651][ERROR][srvc-deploy-#121506%extra-node-1%][TcpCommunicationSpi]
> Failed to send message to remote node [node=TcpDiscoveryNode
> [id=ce88f2ef-5c88-46f1-83d4-50dd8163, addrs=ArrayList [127.0.0.1],
> sockAddrs=HashSet [/127.0.0.1:47503], discPort=47503, order=4, intOrder=4,
> lastExchangeTime=1540309225078, loc=false, ver=2.7.0#20181023-sha1:d09f1d47,
> isClient=false], msg=GridIoMessage [plc=5, topic=TOPIC_CACHE, topicOrd=8,
> ordered=false, timeout=0, skipOnTimeout=false, msg=GridCacheIdMessage
> [cacheId=0]GridDistributedBaseMessage [ver=GridCacheVersion
> [topVer=151789232, order=1540309225927, nodeOrder=7], committedVers=null,
> rolledbackVers=null, cnt=0, super=]GridDistributedTxPrepareRequest
> [threadId=133839, concurrency=OPTIMISTIC, isolation=READ_COMMITTED,
> writeVer=GridCacheVersion [topVer=151789232, order=1540309225928,
> nodeOrder=7], timeout=0, reads=null, writes=PredicateCollectionView
> [IgniteTxEntry [key=KeyCacheObjectImpl [part=9, val=GridServiceAssignmentsKey
> [name=testService-175], hasValBytes=true], cacheId=-2100569601,
> txKey=IgniteTxKey [key=KeyCacheObjectImpl [part=9,
> val=GridServiceAssignmentsKey [name=testService-175], hasValBytes=true],
> cacheId=-2100569601], val=[op=DELETE, val=null], prevVal=[op=NOOP, val=null],
> oldVal=[op=NOOP, val=null], entryProcessorsCol=null, ttl=-1,
> conflictExpireTime=-1, conflictVer=null, explicitVer=null, dhtVer=null,
> filters=CacheEntryPredicate[] [], filtersPassed=false, filtersSet=true,
> entry=GridCacheMapEntry [key=KeyCacheObjectImpl [part=9,
> val=GridServiceAssignmentsKey [name=testService-175], hasValBytes=true],
> val=CacheObjectImpl [val=GridServiceAssignments
> [nodeId=bdeeb063-5558-4dab-90c3-b61b91b338f0, topVer=6,
> cfg=LazyServiceConfiguration
> [srvcClsName=org.apache.ignite.internal.processors.service.DummyService,
> svcCls=, nodeFilterCls=AttributeFilter], assigns=HashMap
> {0069f119-2516-48ee-866c-8a3ba55f8000=0,
> dcf0a942-d7d0-4574-870a-6b251740=0,
> ce88f2ef-5c88-46f1-83d4-50dd8163=1,
> 3264d65e-695f-433c-b028-7bff8b82=0,
> 4427ca0c-24c1-4e61-9f04-bbd37d11=0}], hasValBytes=true],
> ver=GridCacheVersion [topVer=151789229, order=1540309225560, nodeOrder=1],
> hash=1705888709, extras=GridCacheMvccEntryExtras [mvcc=GridCacheMvcc
> [locs=LinkedList [GridCacheMvccCandidate
> [nodeId=100f5b42-d915-409b-980c-726f1945a001, ver=GridCacheVersion
> [topVer=151789232, order=1540309225927, nodeOrder=7], threadId=133839,
> id=335933, topVer=AffinityTopologyVersion [topVer=9, minorTopVer=0],
> reentry=null, otherNodeId=100f5b42-d915-409b-980c-726f1945a001,
> otherVer=GridCacheVersion [topVer=151789232, order=1540309225927,
> nodeOrder=7], mappedDhtNodes=null, mappedNearNodes=null, ownerVer=null,
> serOrder=null, key=KeyCacheObjectImpl [part=9, val=GridServiceAssignmentsKey
> [name=testService-175], hasValBytes=true],
> masks=local=1|owner=1|ready=1|reentry=0|used=0|tx=1|single_implicit=1|dht_local=1|near_local=0|removed=0|read=0,
> prevVer=null, nextVer=null]], rmts=null]], flags=2]GridDistributedCacheEntry
> [super=]GridDhtCacheEntry [rdrs=ReaderId[] [], part=9, super=], prepared=1,
> locked=false, nodeId=100f5b42-d915-409b-980c-726f1945a001, locMapped=false,
> expiryPlc=null, transferExpiryPlc=false, flags=0, partUpdateCntr=0,
> serReadVer=null, xidVer=GridCacheVersion [topVer=151789232,
> order=1540309225927, nodeOrder=7]]], dhtVers=null, txSize=0, plc=5,
> txState=null, flags=retVal|last|sys, super=]GridDhtTxPrepareRequest
> [nearNodeId=100f5b42-d915-409b-980c-726f1945a001,
> futId=f0a1fb1a661-0ff0152a-8da5-4117-8c29-4ba138e30072, miniId=1,
> topVer=AffinityTopologyVersion [topVer=9, minorTopVer=0],
> invalidateNearEntries={}, nearWrites=null, owned=null,
> nearXidVer=GridCacheVersion [topVer=151789232, order=1540309225927,
>
[jira] [Updated] (IGNITE-10021) IgniteInterruptedCheckedException: sleep interrupted in GridServiceProcessorBatchDeploySelfTest#testCancelAllTopologyChange
[
https://issues.apache.org/jira/browse/IGNITE-10021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Ignatenko updated IGNITE-10021:
Labels: MakeTeamcityGreenAgain (was: )
> IgniteInterruptedCheckedException: sleep interrupted in
> GridServiceProcessorBatchDeploySelfTest#testCancelAllTopologyChange
> ---
>
> Key: IGNITE-10021
> URL: https://issues.apache.org/jira/browse/IGNITE-10021
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Oleg Ignatenko
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Attachments: GridServiceProcessorBatchDeploySelfTest.java,
> GridServiceProcessorBatchDeploySelfTest.testCancelAllTopologyChange.log
>
>
> Test {{GridServiceProcessorBatchDeploySelfTest#testCancelAllTopologyChange}}
> failed at TC (couldn't reproduce locally), error message:
> {noformat}
> [2018-10-23
> 15:40:25,651][ERROR][srvc-deploy-#121506%extra-node-1%][TcpCommunicationSpi]
> Failed to send message to remote node [node=TcpDiscoveryNode
> [id=ce88f2ef-5c88-46f1-83d4-50dd8163, addrs=ArrayList [127.0.0.1],
> sockAddrs=HashSet [/127.0.0.1:47503], discPort=47503, order=4, intOrder=4,
> lastExchangeTime=1540309225078, loc=false, ver=2.7.0#20181023-sha1:d09f1d47,
> isClient=false], msg=GridIoMessage [plc=5, topic=TOPIC_CACHE, topicOrd=8,
> ordered=false, timeout=0, skipOnTimeout=false, msg=GridCacheIdMessage
> [cacheId=0]GridDistributedBaseMessage [ver=GridCacheVersion
> [topVer=151789232, order=1540309225927, nodeOrder=7], committedVers=null,
> rolledbackVers=null, cnt=0, super=]GridDistributedTxPrepareRequest
> [threadId=133839, concurrency=OPTIMISTIC, isolation=READ_COMMITTED,
> writeVer=GridCacheVersion [topVer=151789232, order=1540309225928,
> nodeOrder=7], timeout=0, reads=null, writes=PredicateCollectionView
> [IgniteTxEntry [key=KeyCacheObjectImpl [part=9, val=GridServiceAssignmentsKey
> [name=testService-175], hasValBytes=true], cacheId=-2100569601,
> txKey=IgniteTxKey [key=KeyCacheObjectImpl [part=9,
> val=GridServiceAssignmentsKey [name=testService-175], hasValBytes=true],
> cacheId=-2100569601], val=[op=DELETE, val=null], prevVal=[op=NOOP, val=null],
> oldVal=[op=NOOP, val=null], entryProcessorsCol=null, ttl=-1,
> conflictExpireTime=-1, conflictVer=null, explicitVer=null, dhtVer=null,
> filters=CacheEntryPredicate[] [], filtersPassed=false, filtersSet=true,
> entry=GridCacheMapEntry [key=KeyCacheObjectImpl [part=9,
> val=GridServiceAssignmentsKey [name=testService-175], hasValBytes=true],
> val=CacheObjectImpl [val=GridServiceAssignments
> [nodeId=bdeeb063-5558-4dab-90c3-b61b91b338f0, topVer=6,
> cfg=LazyServiceConfiguration
> [srvcClsName=org.apache.ignite.internal.processors.service.DummyService,
> svcCls=, nodeFilterCls=AttributeFilter], assigns=HashMap
> {0069f119-2516-48ee-866c-8a3ba55f8000=0,
> dcf0a942-d7d0-4574-870a-6b251740=0,
> ce88f2ef-5c88-46f1-83d4-50dd8163=1,
> 3264d65e-695f-433c-b028-7bff8b82=0,
> 4427ca0c-24c1-4e61-9f04-bbd37d11=0}], hasValBytes=true],
> ver=GridCacheVersion [topVer=151789229, order=1540309225560, nodeOrder=1],
> hash=1705888709, extras=GridCacheMvccEntryExtras [mvcc=GridCacheMvcc
> [locs=LinkedList [GridCacheMvccCandidate
> [nodeId=100f5b42-d915-409b-980c-726f1945a001, ver=GridCacheVersion
> [topVer=151789232, order=1540309225927, nodeOrder=7], threadId=133839,
> id=335933, topVer=AffinityTopologyVersion [topVer=9, minorTopVer=0],
> reentry=null, otherNodeId=100f5b42-d915-409b-980c-726f1945a001,
> otherVer=GridCacheVersion [topVer=151789232, order=1540309225927,
> nodeOrder=7], mappedDhtNodes=null, mappedNearNodes=null, ownerVer=null,
> serOrder=null, key=KeyCacheObjectImpl [part=9, val=GridServiceAssignmentsKey
> [name=testService-175], hasValBytes=true],
> masks=local=1|owner=1|ready=1|reentry=0|used=0|tx=1|single_implicit=1|dht_local=1|near_local=0|removed=0|read=0,
> prevVer=null, nextVer=null]], rmts=null]], flags=2]GridDistributedCacheEntry
> [super=]GridDhtCacheEntry [rdrs=ReaderId[] [], part=9, super=], prepared=1,
> locked=false, nodeId=100f5b42-d915-409b-980c-726f1945a001, locMapped=false,
> expiryPlc=null, transferExpiryPlc=false, flags=0, partUpdateCntr=0,
> serReadVer=null, xidVer=GridCacheVersion [topVer=151789232,
> order=1540309225927, nodeOrder=7]]], dhtVers=null, txSize=0, plc=5,
> txState=null, flags=retVal|last|sys, super=]GridDhtTxPrepareRequest
> [nearNodeId=100f5b42-d915-409b-980c-726f1945a001,
> futId=f0a1fb1a661-0ff0152a-8da5-4117-8c29-4ba138e30072, miniId=1,
> topVer=AffinityTopologyVersion [topVer=9, minorTopVer=0],
> invalidateNearEntries={}, nearWrites=null, owned=null,
> nearXidVer=GridCacheVersion [topVer=151789232, order=1540309225927,
>
[jira] [Updated] (IGNITE-10021) IgniteInterruptedCheckedException: sleep interrupted in GridServiceProcessorBatchDeploySelfTest#testCancelAllTopologyChange
[
https://issues.apache.org/jira/browse/IGNITE-10021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Ignatenko updated IGNITE-10021:
Description:
Test {{GridServiceProcessorBatchDeploySelfTest#testCancelAllTopologyChange}}
failed at TC (couldn't reproduce locally), error message:
{noformat}
[2018-10-23
15:40:25,651][ERROR][srvc-deploy-#121506%extra-node-1%][TcpCommunicationSpi]
Failed to send message to remote node [node=TcpDiscoveryNode
[id=ce88f2ef-5c88-46f1-83d4-50dd8163, addrs=ArrayList [127.0.0.1],
sockAddrs=HashSet [/127.0.0.1:47503], discPort=47503, order=4, intOrder=4,
lastExchangeTime=1540309225078, loc=false, ver=2.7.0#20181023-sha1:d09f1d47,
isClient=false], msg=GridIoMessage [plc=5, topic=TOPIC_CACHE, topicOrd=8,
ordered=false, timeout=0, skipOnTimeout=false, msg=GridCacheIdMessage
[cacheId=0]GridDistributedBaseMessage [ver=GridCacheVersion [topVer=151789232,
order=1540309225927, nodeOrder=7], committedVers=null, rolledbackVers=null,
cnt=0, super=]GridDistributedTxPrepareRequest [threadId=133839,
concurrency=OPTIMISTIC, isolation=READ_COMMITTED, writeVer=GridCacheVersion
[topVer=151789232, order=1540309225928, nodeOrder=7], timeout=0, reads=null,
writes=PredicateCollectionView [IgniteTxEntry [key=KeyCacheObjectImpl [part=9,
val=GridServiceAssignmentsKey [name=testService-175], hasValBytes=true],
cacheId=-2100569601, txKey=IgniteTxKey [key=KeyCacheObjectImpl [part=9,
val=GridServiceAssignmentsKey [name=testService-175], hasValBytes=true],
cacheId=-2100569601], val=[op=DELETE, val=null], prevVal=[op=NOOP, val=null],
oldVal=[op=NOOP, val=null], entryProcessorsCol=null, ttl=-1,
conflictExpireTime=-1, conflictVer=null, explicitVer=null, dhtVer=null,
filters=CacheEntryPredicate[] [], filtersPassed=false, filtersSet=true,
entry=GridCacheMapEntry [key=KeyCacheObjectImpl [part=9,
val=GridServiceAssignmentsKey [name=testService-175], hasValBytes=true],
val=CacheObjectImpl [val=GridServiceAssignments
[nodeId=bdeeb063-5558-4dab-90c3-b61b91b338f0, topVer=6,
cfg=LazyServiceConfiguration
[srvcClsName=org.apache.ignite.internal.processors.service.DummyService,
svcCls=, nodeFilterCls=AttributeFilter], assigns=HashMap
{0069f119-2516-48ee-866c-8a3ba55f8000=0,
dcf0a942-d7d0-4574-870a-6b251740=0, ce88f2ef-5c88-46f1-83d4-50dd8163=1,
3264d65e-695f-433c-b028-7bff8b82=0,
4427ca0c-24c1-4e61-9f04-bbd37d11=0}], hasValBytes=true],
ver=GridCacheVersion [topVer=151789229, order=1540309225560, nodeOrder=1],
hash=1705888709, extras=GridCacheMvccEntryExtras [mvcc=GridCacheMvcc
[locs=LinkedList [GridCacheMvccCandidate
[nodeId=100f5b42-d915-409b-980c-726f1945a001, ver=GridCacheVersion
[topVer=151789232, order=1540309225927, nodeOrder=7], threadId=133839,
id=335933, topVer=AffinityTopologyVersion [topVer=9, minorTopVer=0],
reentry=null, otherNodeId=100f5b42-d915-409b-980c-726f1945a001,
otherVer=GridCacheVersion [topVer=151789232, order=1540309225927, nodeOrder=7],
mappedDhtNodes=null, mappedNearNodes=null, ownerVer=null, serOrder=null,
key=KeyCacheObjectImpl [part=9, val=GridServiceAssignmentsKey
[name=testService-175], hasValBytes=true],
masks=local=1|owner=1|ready=1|reentry=0|used=0|tx=1|single_implicit=1|dht_local=1|near_local=0|removed=0|read=0,
prevVer=null, nextVer=null]], rmts=null]], flags=2]GridDistributedCacheEntry
[super=]GridDhtCacheEntry [rdrs=ReaderId[] [], part=9, super=], prepared=1,
locked=false, nodeId=100f5b42-d915-409b-980c-726f1945a001, locMapped=false,
expiryPlc=null, transferExpiryPlc=false, flags=0, partUpdateCntr=0,
serReadVer=null, xidVer=GridCacheVersion [topVer=151789232,
order=1540309225927, nodeOrder=7]]], dhtVers=null, txSize=0, plc=5,
txState=null, flags=retVal|last|sys, super=]GridDhtTxPrepareRequest
[nearNodeId=100f5b42-d915-409b-980c-726f1945a001,
futId=f0a1fb1a661-0ff0152a-8da5-4117-8c29-4ba138e30072, miniId=1,
topVer=AffinityTopologyVersion [topVer=9, minorTopVer=0],
invalidateNearEntries={}, nearWrites=null, owned=null,
nearXidVer=GridCacheVersion [topVer=151789232, order=1540309225927,
nodeOrder=7], subjId=100f5b42-d915-409b-980c-726f1945a001, taskNameHash=0,
preloadKeys=null, mvccSnapshot=null, skipCompletedVers=true, super=]]]
class org.apache.ignite.internal.IgniteInterruptedCheckedException: sleep
interrupted
at org.apache.ignite.internal.util.IgniteUtils.sleep(IgniteUtils.java:7782)
at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.reserveClient(TcpCommunicationSpi.java:2888)
at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage0(TcpCommunicationSpi.java:2713)
at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage(TcpCommunicationSpi.java:2672)
at
org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1656)
at
org.apache.ignite.internal.managers.communication.GridIoManager.sendToGridTopic(GridIoManager.java:1731)
[jira] [Commented] (IGNITE-10004) Parse error leads to leave the transaction
[
https://issues.apache.org/jira/browse/IGNITE-10004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665160#comment-16665160
]
Andrew Mashenkov commented on IGNITE-10004:
---
I've create a simple repro (where I try to catch Exception and ignore parsing
exception) and see we have same issue with SQL API queries.
Tx is closed before certain exception has been catched.
> Parse error leads to leave the transaction
> --
>
> Key: IGNITE-10004
> URL: https://issues.apache.org/jira/browse/IGNITE-10004
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Affects Versions: 2.7
>Reporter: Sergey Kozlov
>Assignee: Andrew Mashenkov
>Priority: Major
> Fix For: 2.7
>
>
> 1. Start 2 nodes + connect sqlline
> 2. Execute following queries:
> {noformat}
> create table t10 (a int, b varchar, primary key(a)) with
> "ATOMICITY=TRANSACTIONAL_SNAPSHOT,backups=1";
> begin;
> insert into t10 values(1); <- worng set
> insert into t10 values(2, '2'); <- coorect set
> commit;
> {noformat}
> The output:
> {noformat}
> 0: jdbc:ignite:thin://127.0.0.1/> create table t10 (a int, b varchar, primary
> key(a)) with "ATOMICITY=TRANSACTIONAL_SNAP
> SHOT,backups=1";
> No rows affected (0,032 seconds)
> 0: jdbc:ignite:thin://127.0.0.1/> begin;
> No rows affected (0 seconds)
> 0: jdbc:ignite:thin://127.0.0.1/> insert into t10 values(1);
> Error: Failed to parse query. ═хтхЁэюх ъюышўхёЄтю ёЄюысЎют
> Column count does not match; SQL statement:
> insert into t10 values(1) [21002-197] (state=42000,code=1001)
> java.sql.SQLException: Failed to parse query. Неверное количество столбцов
> Column count does not match; SQL statement:
> insert into t10 values(1) [21002-197]
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:750)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
> at sqlline.Commands.execute(Commands.java:823)
> at sqlline.Commands.sql(Commands.java:733)
> at sqlline.SqlLine.dispatch(SqlLine.java:795)
> at sqlline.SqlLine.begin(SqlLine.java:668)
> at sqlline.SqlLine.start(SqlLine.java:373)
> at sqlline.SqlLine.main(SqlLine.java:265)
> 0: jdbc:ignite:thin://127.0.0.1/> insert into t10 values(2, '2');
> Error: Transaction is already completed. (state=25000,code=5004)
> java.sql.SQLException: Transaction is already completed.
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:750)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
> at sqlline.Commands.execute(Commands.java:823)
> at sqlline.Commands.sql(Commands.java:733)
> at sqlline.SqlLine.dispatch(SqlLine.java:795)
> at sqlline.SqlLine.begin(SqlLine.java:668)
> at sqlline.SqlLine.start(SqlLine.java:373)
> at sqlline.SqlLine.main(SqlLine.java:265)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10007) Deactivation hangs if an open transaction exists
[
https://issues.apache.org/jira/browse/IGNITE-10007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665158#comment-16665158
]
Sergey Kozlov commented on IGNITE-10007:
More details:
The issue is reproduced for one node as well.
LRT is still presented if sqlline is running (even commit has been executed)
> Deactivation hangs if an open transaction exists
>
>
> Key: IGNITE-10007
> URL: https://issues.apache.org/jira/browse/IGNITE-10007
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Affects Versions: 2.7
>Reporter: Sergey Kozlov
>Assignee: Sergey Kozlov
>Priority: Major
> Fix For: 2.7
>
> Attachments:
> PersistenceDeactivationWIthActiveMvccTransactionSelfTest.java,
> stacktrace_18308.txt, stacktrace_7808.txt
>
>
> 1. Start 2 node with PDS
> 2. Activate cluster
> 3. Connect sqlline
> 4. Create table {{create table t1(a int, b varchar, primary key(a)) with
> "ATOMICITY=TRANSACTIONAL_SNAPSHOT,backups=1";}}
> 3.Start TX and execute a DML commnd:
> {noformat}
> begin;
> insert into t1 values (1, '1');
> {noformat}
> 4. Try deactivate cluster {{bin/control.bat --deactivate}}. The scripts
> doesn't return control.
> 5. Show LRT:
> {noformat}
> c:\Work\apache-ignite-2.7.0-SNAPSHOT-bin>bin\control.bat --tx
> Control utility [ver. 2.7.0-SNAPSHOT#19700101-sha1:DEV]
> 2018 Copyright(C) Apache Software Foundation
> User:
>
> Matching transactions:
> TcpDiscoveryNode [id=5d3e8936-174d-42e2-a47f-c70ec02bccab, addrs=[127.0.0.1],
> order=1, ver=2.7.0#19700101-sha1:,
> isClient=false, consistentId=1]
> Tx: [xid=74bc1aba661--090e-b121--0001, label=null,
> state=ACTIVE, startTime=2018-10-25 17:34:35.5
> 22, duration=352, isolation=REPEATABLE_READ, concurrency=PESSIMISTIC,
> topVer=AffinityTopologyVersion [topVer=2, minorTop
> Ver=6], timeout=0, size=0, dhtNodes=[41ff88d2],
> nearXid=74bc1aba661--090e-b121--0001, parentNodeIds=
> [5d3e8936]]
> {noformat}
> 6. Complete TX:
> {noformat}
> 0: jdbc:ignite:thin://127.0.0.1/> commit;
> Error: class org.apache.ignite.IgniteException: Can not perform the operation
> because the cluster is inactive. Note, tha
> t the cluster is considered inactive by default if Ignite Persistent Store is
> used to let all the nodes join the cluster
> . To activate the cluster call Ignite.active(true). (state=5,code=1)
> java.sql.SQLException: class org.apache.ignite.IgniteException: Can not
> perform the operation because the cluster is ina
> ctive. Note, that the cluster is considered inactive by default if Ignite
> Persistent Store is used to let all the nodes
> join the cluster. To activate the cluster call Ignite.active(true).
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:750)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
> at sqlline.Commands.execute(Commands.java:823)
> at sqlline.Commands.sql(Commands.java:733)
> at sqlline.SqlLine.dispatch(SqlLine.java:795)
> at sqlline.SqlLine.begin(SqlLine.java:668)
> at sqlline.SqlLine.start(SqlLine.java:373)
> at sqlline.SqlLine.main(SqlLine.java:265)
> 0: jdbc:ignite:thin://127.0.0.1/>
> {noformat}
> It.s ok but LRT is still presented and deactivation script doesn't return
> control back to user:
> {noformat}
> c:\Work\apache-ignite-2.7.0-SNAPSHOT-bin>bin\control.bat --tx
> Control utility [ver. 2.7.0-SNAPSHOT#19700101-sha1:DEV]
> 2018 Copyright(C) Apache Software Foundation
> User:
>
> Matching transactions:
> TcpDiscoveryNode [id=5d3e8936-174d-42e2-a47f-c70ec02bccab, addrs=[127.0.0.1],
> order=1, ver=2.7.0#19700101-sha1:,
> isClient=false, consistentId=1]
> Tx: [xid=74bc1aba661--090e-b121--0001, label=null,
> state=ACTIVE, startTime=2018-10-25 17:34:35.5
> 22, duration=510, isolation=REPEATABLE_READ, concurrency=PESSIMISTIC,
> topVer=AffinityTopologyVersion [topVer=2, minorTop
> Ver=6], timeout=0, size=0, dhtNodes=[41ff88d2],
> nearXid=74bc1aba661--090e-b121--0001, parentNodeIds=
> [5d3e8936]]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10029) Node attributes are not restored from metastore after node restart.
Alexei Scherbakov created IGNITE-10029: -- Summary: Node attributes are not restored from metastore after node restart. Key: IGNITE-10029 URL: https://issues.apache.org/jira/browse/IGNITE-10029 Project: Ignite Issue Type: Bug Reporter: Alexei Scherbakov Fix For: 2.8 Scenario: 1. Start node with enabled persistence, configure some user attributes. 2. Restart node without directly setting node attributes again. 3. Read any user attribute and observe NULL value. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9714) Document ODBC streaming mode
[
https://issues.apache.org/jira/browse/IGNITE-9714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665541#comment-16665541
]
Denis Magda commented on IGNITE-9714:
-
[~pgarg], [~Artem Budnikov], thanks, looks good to me!
> Document ODBC streaming mode
>
>
> Key: IGNITE-9714
> URL: https://issues.apache.org/jira/browse/IGNITE-9714
> Project: Ignite
> Issue Type: Task
> Components: documentation
>Reporter: Vladimir Ozerov
>Assignee: Denis Magda
>Priority: Major
> Fix For: 2.7
>
>
> Need to document ODBC streaming mode introduced in IGNITE-7855.
> Need to mention that ODBC supports streaming mode now and give a link to a
> {{SET}} command description, pretty much the same way it's done for JDBC:
> https://apacheignite-sql.readme.io/docs/jdbc-driver#section-streaming
> Maybe it makes sense to mention that "array of parameters" feature and
> "data-on-execution" are not supported in the streaming mode.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (IGNITE-9714) Document ODBC streaming mode
[
https://issues.apache.org/jira/browse/IGNITE-9714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda closed IGNITE-9714.
---
> Document ODBC streaming mode
>
>
> Key: IGNITE-9714
> URL: https://issues.apache.org/jira/browse/IGNITE-9714
> Project: Ignite
> Issue Type: Task
> Components: documentation
>Reporter: Vladimir Ozerov
>Assignee: Denis Magda
>Priority: Major
> Fix For: 2.7
>
>
> Need to document ODBC streaming mode introduced in IGNITE-7855.
> Need to mention that ODBC supports streaming mode now and give a link to a
> {{SET}} command description, pretty much the same way it's done for JDBC:
> https://apacheignite-sql.readme.io/docs/jdbc-driver#section-streaming
> Maybe it makes sense to mention that "array of parameters" feature and
> "data-on-execution" are not supported in the streaming mode.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9848) [TC Bot] Background upload of all builds from TC to the bot DB
[ https://issues.apache.org/jira/browse/IGNITE-9848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665510#comment-16665510 ] ASF GitHub Bot commented on IGNITE-9848: asfgit closed pull request #43: IGNITE-9848 load all builds URL: https://github.com/apache/ignite-teamcity-bot/pull/43 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > [TC Bot] Background upload of all builds from TC to the bot DB > --- > > Key: IGNITE-9848 > URL: https://issues.apache.org/jira/browse/IGNITE-9848 > Project: Ignite > Issue Type: Task >Reporter: Dmitriy Pavlov >Assignee: Dmitriy Pavlov >Priority: Major > > To fix slow loading of PR report and Master trends page. > Upload all tracked and observed branches related builds into TC Bot's Ignite > DB. > Prepare compacted entities to reduce storage size. > Implement idea of having fat build, which will represent replies from a > number of REST services. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10030) [TC Bot] Background upload of changes, problems, and statistics
Dmitriy Pavlov created IGNITE-10030: --- Summary: [TC Bot] Background upload of changes, problems, and statistics Key: IGNITE-10030 URL: https://issues.apache.org/jira/browse/IGNITE-10030 Project: Ignite Issue Type: Task Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov After the implementation of [IGNITE-9848] load time is still long because of statistics and changes requires significant time to be loaded Refs: BuildChainProcessor#loadTestsAndProblems TeamcityIgnitedImpl#reloadBuild -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8871) TDE - Phase-1. Documentation
[ https://issues.apache.org/jira/browse/IGNITE-8871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665544#comment-16665544 ] Denis Magda commented on IGNITE-8871: - [~Artem Budnikov], could you please review the documentation first and enhance it if needed? > TDE - Phase-1. Documentation > > > Key: IGNITE-8871 > URL: https://issues.apache.org/jira/browse/IGNITE-8871 > Project: Ignite > Issue Type: Sub-task > Components: documentation >Affects Versions: 2.5 >Reporter: Nikolay Izhikov >Assignee: Denis Magda >Priority: Major > Labels: documentation > Fix For: 2.7 > > > TDE feature should be documented. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-8871) TDE - Phase-1. Documentation
[ https://issues.apache.org/jira/browse/IGNITE-8871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda reassigned IGNITE-8871: --- Assignee: Artem Budnikov (was: Denis Magda) > TDE - Phase-1. Documentation > > > Key: IGNITE-8871 > URL: https://issues.apache.org/jira/browse/IGNITE-8871 > Project: Ignite > Issue Type: Sub-task > Components: documentation >Affects Versions: 2.5 >Reporter: Nikolay Izhikov >Assignee: Artem Budnikov >Priority: Major > Labels: documentation > Fix For: 2.7 > > > TDE feature should be documented. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9345) Document custom SQL schemas
[
https://issues.apache.org/jira/browse/IGNITE-9345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665563#comment-16665563
]
Denis Magda commented on IGNITE-9345:
-
[~Artem Budnikov], I placed the page under "Architecture" section. The rest
looks good.
> Document custom SQL schemas
> ---
>
> Key: IGNITE-9345
> URL: https://issues.apache.org/jira/browse/IGNITE-9345
> Project: Ignite
> Issue Type: Task
> Components: documentation, sql
>Reporter: Vladimir Ozerov
>Assignee: Denis Magda
>Priority: Critical
> Fix For: 2.7
>
>
> Key highlights:
> 1) DDL operations \{{CREATE TABLE}} and \{{DROP TABLE}} are no longer tied to
> \{{PUBLIC}} schema. They can be executed on any schema. Need to remove this
> from docs (if there is such paragraph)
> 2) Added a property \{{IgniteConfiguration.sqlSchemas}} which creates local
> schemas with provided names.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IGNITE-9345) Document custom SQL schemas
[
https://issues.apache.org/jira/browse/IGNITE-9345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda resolved IGNITE-9345.
-
Resolution: Fixed
> Document custom SQL schemas
> ---
>
> Key: IGNITE-9345
> URL: https://issues.apache.org/jira/browse/IGNITE-9345
> Project: Ignite
> Issue Type: Task
> Components: documentation, sql
>Reporter: Vladimir Ozerov
>Assignee: Denis Magda
>Priority: Critical
> Fix For: 2.7
>
>
> Key highlights:
> 1) DDL operations \{{CREATE TABLE}} and \{{DROP TABLE}} are no longer tied to
> \{{PUBLIC}} schema. They can be executed on any schema. Need to remove this
> from docs (if there is such paragraph)
> 2) Added a property \{{IgniteConfiguration.sqlSchemas}} which creates local
> schemas with provided names.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (IGNITE-9345) Document custom SQL schemas
[
https://issues.apache.org/jira/browse/IGNITE-9345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda closed IGNITE-9345.
---
> Document custom SQL schemas
> ---
>
> Key: IGNITE-9345
> URL: https://issues.apache.org/jira/browse/IGNITE-9345
> Project: Ignite
> Issue Type: Task
> Components: documentation, sql
>Reporter: Vladimir Ozerov
>Assignee: Denis Magda
>Priority: Critical
> Fix For: 2.7
>
>
> Key highlights:
> 1) DDL operations \{{CREATE TABLE}} and \{{DROP TABLE}} are no longer tied to
> \{{PUBLIC}} schema. They can be executed on any schema. Need to remove this
> from docs (if there is such paragraph)
> 2) Added a property \{{IgniteConfiguration.sqlSchemas}} which creates local
> schemas with provided names.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-9817) Update documentation and examples for Spark SQL Table Specification
[ https://issues.apache.org/jira/browse/IGNITE-9817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda reassigned IGNITE-9817: --- Assignee: Prachi Garg > Update documentation and examples for Spark SQL Table Specification > --- > > Key: IGNITE-9817 > URL: https://issues.apache.org/jira/browse/IGNITE-9817 > Project: Ignite > Issue Type: Sub-task > Components: documentation >Reporter: Nikolay Izhikov >Assignee: Prachi Garg >Priority: Major > Fix For: 2.7 > > > We should update documentation and examples according to the results of > IGNITE-9228. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9817) Update documentation and examples for Spark SQL Table Specification
[ https://issues.apache.org/jira/browse/IGNITE-9817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-9817: Component/s: documentation > Update documentation and examples for Spark SQL Table Specification > --- > > Key: IGNITE-9817 > URL: https://issues.apache.org/jira/browse/IGNITE-9817 > Project: Ignite > Issue Type: Sub-task > Components: documentation >Reporter: Nikolay Izhikov >Assignee: Prachi Garg >Priority: Major > Fix For: 2.7 > > > We should update documentation and examples according to the results of > IGNITE-9228. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9817) Update documentation and examples for Spark SQL Table Specification
[ https://issues.apache.org/jira/browse/IGNITE-9817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-9817: Fix Version/s: 2.7 > Update documentation and examples for Spark SQL Table Specification > --- > > Key: IGNITE-9817 > URL: https://issues.apache.org/jira/browse/IGNITE-9817 > Project: Ignite > Issue Type: Sub-task > Components: documentation >Reporter: Nikolay Izhikov >Assignee: Prachi Garg >Priority: Major > Fix For: 2.7 > > > We should update documentation and examples according to the results of > IGNITE-9228. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9817) Update documentation and examples for Spark SQL Table Specification
[ https://issues.apache.org/jira/browse/IGNITE-9817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665573#comment-16665573 ] Denis Magda commented on IGNITE-9817: - [~NIzhikov], looks good to me, thanks! [~pgarg] please do a final editorial review. > Update documentation and examples for Spark SQL Table Specification > --- > > Key: IGNITE-9817 > URL: https://issues.apache.org/jira/browse/IGNITE-9817 > Project: Ignite > Issue Type: Sub-task > Components: documentation >Reporter: Nikolay Izhikov >Priority: Major > Fix For: 2.7 > > > We should update documentation and examples according to the results of > IGNITE-9228. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9009) Local continuous query listeners may be called on partition reassignment
[ https://issues.apache.org/jira/browse/IGNITE-9009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Mekhanikov updated IGNITE-9009: - Ignite Flags: (was: Docs Required) > Local continuous query listeners may be called on partition reassignment > > > Key: IGNITE-9009 > URL: https://issues.apache.org/jira/browse/IGNITE-9009 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.5 >Reporter: Denis Mekhanikov >Assignee: Denis Mekhanikov >Priority: Major > Fix For: 2.8 > > Attachments: ContinuousQueryReassignmentTest.java > > > When a node becomes primary for some partitions, then local continuous query > listeners receive updates on entries from that partitions. Such invocations > shouldn't happen. > Attached test class demonstrates this behaviour. > Dev list discussion: > http://apache-ignite-developers.2346864.n4.nabble.com/Backup-queue-for-local-continuous-query-td33391.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9355) Document new system views (nodes, node attributes, baseline nodes, node metrics)
[
https://issues.apache.org/jira/browse/IGNITE-9355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665553#comment-16665553
]
Denis Magda commented on IGNITE-9355:
-
[~Artem Budnikov], please consider the following:
* Let's create Metrics section and put this page there. Presently it's under
some Guides
* Show a code example (SQL) that accesses these metrics
* System Views sound like a better page title
> Document new system views (nodes, node attributes, baseline nodes, node
> metrics)
>
>
> Key: IGNITE-9355
> URL: https://issues.apache.org/jira/browse/IGNITE-9355
> Project: Ignite
> Issue Type: Task
> Components: documentation, sql
>Reporter: Vladimir Ozerov
>Assignee: Denis Magda
>Priority: Major
> Fix For: 2.7
>
>
> We need to document three new SQL system views.
> # Explain users that new system SQL schema appeared, named "IGNITE", where
> all views are stored
> # System view NODES - list of current nodes in topology. Columns: ID,
> CONSISTENT_ID, VERSION, IS_LOCAL, IS_CLIENT, IS_DAEMON, NODE_ORDER,
> ADDRESSES, HOSTNAMES
> # System view NODE_ATTRIBUTES - attributes for all nodes. Columns: NODE_ID,
> NAME, VALUE
> # System view BASELINE_NODES - list of baseline topology nodes. Columns:
> CONSISTENT_ID, ONLINE (whether node is up and running at the moment)
> # System view NODE_METRICS - node metrics. Columns - see
> \{{org.apache.ignite.internal.processors.query.h2.sys.view.SqlSystemViewNodeMetrics}}
> class
> # Explain limitations: views cannot be joined with user tables; it is not
> allowed to create other objects (tables, indexes) in "IGNITE" schema.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-9355) Document new system views (nodes, node attributes, baseline nodes, node metrics)
[
https://issues.apache.org/jira/browse/IGNITE-9355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda reassigned IGNITE-9355:
---
Assignee: Artem Budnikov (was: Denis Magda)
> Document new system views (nodes, node attributes, baseline nodes, node
> metrics)
>
>
> Key: IGNITE-9355
> URL: https://issues.apache.org/jira/browse/IGNITE-9355
> Project: Ignite
> Issue Type: Task
> Components: documentation, sql
>Reporter: Vladimir Ozerov
>Assignee: Artem Budnikov
>Priority: Major
> Fix For: 2.7
>
>
> We need to document three new SQL system views.
> # Explain users that new system SQL schema appeared, named "IGNITE", where
> all views are stored
> # System view NODES - list of current nodes in topology. Columns: ID,
> CONSISTENT_ID, VERSION, IS_LOCAL, IS_CLIENT, IS_DAEMON, NODE_ORDER,
> ADDRESSES, HOSTNAMES
> # System view NODE_ATTRIBUTES - attributes for all nodes. Columns: NODE_ID,
> NAME, VALUE
> # System view BASELINE_NODES - list of baseline topology nodes. Columns:
> CONSISTENT_ID, ONLINE (whether node is up and running at the moment)
> # System view NODE_METRICS - node metrics. Columns - see
> \{{org.apache.ignite.internal.processors.query.h2.sys.view.SqlSystemViewNodeMetrics}}
> class
> # Explain limitations: views cannot be joined with user tables; it is not
> allowed to create other objects (tables, indexes) in "IGNITE" schema.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (IGNITE-9546) Document GROUP_CONCAT aggregate function
[
https://issues.apache.org/jira/browse/IGNITE-9546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda closed IGNITE-9546.
---
> Document GROUP_CONCAT aggregate function
>
>
> Key: IGNITE-9546
> URL: https://issues.apache.org/jira/browse/IGNITE-9546
> Project: Ignite
> Issue Type: Task
> Components: documentation, sql
>Affects Versions: 2.6
>Reporter: Taras Ledkov
>Assignee: Denis Magda
>Priority: Major
> Fix For: 2.7
>
>
> We need to document GROUP_CONCAT aggregate function.
> # Explain users that {{DISTINCT}} and {{ORDER BY}} is supported only for
> collocated {{GROUP BY}};
> # String concatenation expressions are separated by {{||}} (not by comma as
> described at the
> [draft|https://dash.readme.io/project/apacheignite-sql/v2.6/docs/group_concat]);
> e.g.: {{GROUP_CONCAT(valueId || '=' || value SEPARATOR '; ')}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9546) Document GROUP_CONCAT aggregate function
[
https://issues.apache.org/jira/browse/IGNITE-9546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665570#comment-16665570
]
Denis Magda commented on IGNITE-9546:
-
[~Artem Budnikov], perfect, thanks a lot for the contribution!
> Document GROUP_CONCAT aggregate function
>
>
> Key: IGNITE-9546
> URL: https://issues.apache.org/jira/browse/IGNITE-9546
> Project: Ignite
> Issue Type: Task
> Components: documentation, sql
>Affects Versions: 2.6
>Reporter: Taras Ledkov
>Assignee: Denis Magda
>Priority: Major
> Fix For: 2.7
>
>
> We need to document GROUP_CONCAT aggregate function.
> # Explain users that {{DISTINCT}} and {{ORDER BY}} is supported only for
> collocated {{GROUP BY}};
> # String concatenation expressions are separated by {{||}} (not by comma as
> described at the
> [draft|https://dash.readme.io/project/apacheignite-sql/v2.6/docs/group_concat]);
> e.g.: {{GROUP_CONCAT(valueId || '=' || value SEPARATOR '; ')}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9884) Some tests are incorrectly muted
[
https://issues.apache.org/jira/browse/IGNITE-9884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665586#comment-16665586
]
Ignite TC Bot commented on IGNITE-9884:
---
{panel:title=Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Queries (Binary Objects Simple Mapper){color} [[tests 0 TIMEOUT
, Exit Code |https://ci.ignite.apache.org/viewLog.html?buildId=2170018]]
* IgniteSqlSplitterSelfTest.testPushDownLeftJoin (last started)
{panel}
[TeamCity Run All
Results|http://ci.ignite.apache.org/viewLog.html?buildId=2167668buildTypeId=IgniteTests24Java8_RunAll]
> Some tests are incorrectly muted
>
>
> Key: IGNITE-9884
> URL: https://issues.apache.org/jira/browse/IGNITE-9884
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
>
> The following tests pass when unmuted. It looks like the reasons that made
> them fail in the past were somehow resolved by later code changes but tests
> were forgotten to unmute:
> {panel}
> GridCacheStoreManagerDeserializationTest#_testBinaryStream
> IgniteCacheConfigVariationsFullApiTest#_testDeletedEntriesFlag
> IgniteCacheConfigVariationsFullApiTest#_testEvictExpired
> PageIdDistributionTest#_testRealHistory
> GridEventConsumeSelfTest#_testMultithreadedWithNodeRestart
> BPlusTreeSelfTest#_testBenchInvoke
> IgniteClientReconnectMassiveShutdownTest#_testMassiveServersShutdown1
> IgniteClientReconnectMassiveShutdownTest#_testMassiveServersShutdown3
> TcpDiscoveryMultiThreadedTest#_testMultiThreadedServersRestart
> GridServiceProcessorBatchDeploySelfTest#_testDeployAllTopologyChange
> GridServiceProcessorBatchDeploySelfTest#_testDeployAllTopologyChangeFail
> GridServiceProcessorBatchDeploySelfTest#_testCancelAllTopologyChange
> {panel}
> The following tests are muted by renaming (prefixing with underscore,
> {{_test...}}, should use standard muting by known JIRA tickets instead:
> {panel}
> - CacheMvccTransactionsTest#_testNodesRestartNoHang
> should fail with the reference to IGNITE-5935
> - GridCacheAbstractFullApiSelfTest#_testInvokeAllMultithreaded
> should fail with the reference to IGNITE-4380{panel}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10031) REST: Introduce "caches" param for "top" command.
Alexey Kuznetsov created IGNITE-10031: - Summary: REST: Introduce "caches" param for "top" command. Key: IGNITE-10031 URL: https://issues.apache.org/jira/browse/IGNITE-10031 Project: Ignite Issue Type: Improvement Components: rest Reporter: Alexey Kuznetsov Assignee: Alexey Kuznetsov Fix For: 2.8 We have top command on REST API: https://apacheignite.readme.io/docs/rest-api#topology And result of this command also contains short caches info (name, mode & SQL Schema). But in situation when node contains thousand caches and hundred nodes and caches have long names - that will result in a HUGE JSON. For example, I get 88Mb JSON for cluster of 128 nodes and 6000 caches. And my application do not need that info about caches, I just need a list of node IDs. Lets add one more flag "caches" as we already have "attr" & "mtr". For compatibility reasons I will preserve current behaviour if "caches" flag will not be specified. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9884) Some tests are incorrectly muted
[
https://issues.apache.org/jira/browse/IGNITE-9884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665592#comment-16665592
]
Oleg Ignatenko commented on IGNITE-9884:
Note regarding [Ignite TC Bot
results|https://issues.apache.org/jira/browse/IGNITE-9884?focusedCommentId=16665586=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16665586]
above:
{{Queries (Binary Objects Simple Mapper)}} - I honestly have no idea how to
handle this warning. It kept timing out at all my attempts to re-run. I also
could not find how it can even be related to changes I made because checking
code of involved test suite
([IgniteBinaryObjectsSimpleNameMapperComputeGridTestSuite|https://github.com/apache/ignite/blob/master/modules/core/src/test/java/org/apache/ignite/testsuites/IgniteBinaryObjectsSimpleNameMapperComputeGridTestSuite.java]
and {{IgniteComputeGridTestSuite}} invoked from it) didn't show using any of
the tests I modified in my changes. [~dmitry.pavlov] I would appreciate if you
can advise how to handle that.
> Some tests are incorrectly muted
>
>
> Key: IGNITE-9884
> URL: https://issues.apache.org/jira/browse/IGNITE-9884
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
>
> The following tests pass when unmuted. It looks like the reasons that made
> them fail in the past were somehow resolved by later code changes but tests
> were forgotten to unmute:
> {panel}
> GridCacheStoreManagerDeserializationTest#_testBinaryStream
> IgniteCacheConfigVariationsFullApiTest#_testDeletedEntriesFlag
> IgniteCacheConfigVariationsFullApiTest#_testEvictExpired
> PageIdDistributionTest#_testRealHistory
> GridEventConsumeSelfTest#_testMultithreadedWithNodeRestart
> BPlusTreeSelfTest#_testBenchInvoke
> IgniteClientReconnectMassiveShutdownTest#_testMassiveServersShutdown1
> IgniteClientReconnectMassiveShutdownTest#_testMassiveServersShutdown3
> TcpDiscoveryMultiThreadedTest#_testMultiThreadedServersRestart
> GridServiceProcessorBatchDeploySelfTest#_testDeployAllTopologyChange
> GridServiceProcessorBatchDeploySelfTest#_testDeployAllTopologyChangeFail
> GridServiceProcessorBatchDeploySelfTest#_testCancelAllTopologyChange
> {panel}
> The following tests are muted by renaming (prefixing with underscore,
> {{_test...}}, should use standard muting by known JIRA tickets instead:
> {panel}
> - CacheMvccTransactionsTest#_testNodesRestartNoHang
> should fail with the reference to IGNITE-5935
> - GridCacheAbstractFullApiSelfTest#_testInvokeAllMultithreaded
> should fail with the reference to IGNITE-4380{panel}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IGNITE-9819) SQL: document recomendation to use TIMESTAMP instead of DATE
[ https://issues.apache.org/jira/browse/IGNITE-9819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Budnikov resolved IGNITE-9819. Resolution: Fixed > SQL: document recomendation to use TIMESTAMP instead of DATE > > > Key: IGNITE-9819 > URL: https://issues.apache.org/jira/browse/IGNITE-9819 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Vladimir Ozerov >Assignee: Artem Budnikov >Priority: Major > Fix For: 2.7 > > > We support both DATE (date only) and TIMESTAMP (date + time) data types. > Unfortunately, DATE data type is serialized/deserialized very inefficiently, > what leads to performance degradation. > We need to warn users in documentation, that it is better to use TIMESTAMP > than DATE. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9819) SQL: document recomendation to use TIMESTAMP instead of DATE
[ https://issues.apache.org/jira/browse/IGNITE-9819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16664820#comment-16664820 ] Artem Budnikov commented on IGNITE-9819: Added this info to the Date data type section. > SQL: document recomendation to use TIMESTAMP instead of DATE > > > Key: IGNITE-9819 > URL: https://issues.apache.org/jira/browse/IGNITE-9819 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Vladimir Ozerov >Assignee: Artem Budnikov >Priority: Major > Fix For: 2.7 > > > We support both DATE (date only) and TIMESTAMP (date + time) data types. > Unfortunately, DATE data type is serialized/deserialized very inefficiently, > what leads to performance degradation. > We need to warn users in documentation, that it is better to use TIMESTAMP > than DATE. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
