[jira] [Updated] (IGNITE-9235) Transitivity violation in GridMergeIndex Comparator
[
https://issues.apache.org/jira/browse/IGNITE-9235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Evgenii Zagumennov updated IGNITE-9235:
---
Fix Version/s: 2.5
> Transitivity violation in GridMergeIndex Comparator
> ---
>
> Key: IGNITE-9235
> URL: https://issues.apache.org/jira/browse/IGNITE-9235
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Andrew Medvedev
>Assignee: Andrew Medvedev
>Priority: Major
> Fix For: 2.5
>
>
> Currently comparator in
> org.apache.ignite.internal.processors.query.h2.twostep.GridMergeIndex is:
>
> Private final Comparator streamCmp = new Comparator() {
> @Override public int compare(RowStream o1, RowStream o2) {
> // Nulls at the beginning.
> if (o1 == null)
> return -1;
> if (o2 == null)
> return 1;
> return compareRows(o1.get(), o2.get());
> }
> };
> --
>
> This comparator violates transitivity when o1 and o2 are null. Thus we get
> exception in JDK1.8:
>
>
> {color:#d04437}Caused by: java.lang.IllegalArgumentException: Comparison
> method violates its general contract!{color}
> {color:#d04437} at java.util.TimSort.mergeHi(TimSort.java:899){color}
> {color:#d04437} at java.util.TimSort.mergeAt(TimSort.java:516){color}
> {color:#d04437} at java.util.TimSort.mergeCollapse(TimSort.java:441){color}
> {color:#d04437} at java.util.TimSort.sort(TimSort.java:245){color}
> {color:#d04437} at java.util.Arrays.sort(Arrays.java:1438){color}
> {color:#d04437} at
> org.apache.ignite.internal.processors.query.h2.twostep.GridMergeIndexSorted$MergeStreamIterator.goFirst(GridMergeIndexSorted.java:248){color}
> {color:#d04437} at
> org.apache.ignite.internal.processors.query.h2.twostep.GridMergeIndexSorted$MergeStreamIterator.hasNext(GridMergeIndexSorted.java:270){color}
> {color:#d04437} at
> org.apache.ignite.internal.processors.query.h2.twostep.GridMergeIndex$FetchingCursor.fetchRows(GridMergeIndex.java:614){color}
> {color:#d04437} at
> org.apache.ignite.internal.processors.query.h2.twostep.GridMergeIndex$FetchingCursor.next(GridMergeIndex.java:658){color}
> {color:#d04437} at org.h2.index.IndexCursor.next(IndexCursor.java:305){color}
> {color:#d04437} at org.h2.table.TableFilter.next(TableFilter.java:499){color}
> {color:#d04437} at
> org.h2.command.dml.Select$LazyResultQueryFlat.fetchNextRow(Select.java:1452){color}
> {color:#d04437} at
> org.h2.result.LazyResult.hasNext(LazyResult.java:79){color}
> {color:#d04437} at org.h2.result.LazyResult.next(LazyResult.java:59){color}
> {color:#d04437} at
> org.h2.command.dml.Select.queryFlat(Select.java:519){color}
> {color:#d04437} at
> org.h2.command.dml.Select.queryWithoutCache(Select.java:625){color}
> {color:#d04437} at
> org.h2.command.dml.Query.queryWithoutCacheLazyCheck(Query.java:114){color}
> {color:#d04437} at org.h2.command.dml.Query.query(Query.java:352){color}
> {color:#d04437} at org.h2.command.dml.Query.query(Query.java:333){color}
> {color:#d04437} at
> org.h2.command.CommandContainer.query(CommandContainer.java:113){color}
> {color:#d04437} at
> org.h2.command.Command.executeQuery(Command.java:201){color}
> {color:#d04437} ... 44 more{color}
>
> WA: use -Djava.util.Arrays.useLegacyMergeSort=true
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9144) A client node leaving a grid may trigger the wrong message about coordinator change in the logs
[
https://issues.apache.org/jira/browse/IGNITE-9144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16565115#comment-16565115
]
Evgenii Zagumennov commented on IGNITE-9144:
https://ci.ignite.apache.org/viewLog.html?buildId=1572242=buildResultsDiv=IgniteTests24Java8_RunAll
> A client node leaving a grid may trigger the wrong message about coordinator
> change in the logs
> ---
>
> Key: IGNITE-9144
> URL: https://issues.apache.org/jira/browse/IGNITE-9144
> Project: Ignite
> Issue Type: Bug
>Reporter: Ivan Artukhov
>Assignee: Evgenii Zagumennov
>Priority: Major
>
> The issue was introduced by https://issues.apache.org/jira/browse/IGNITE-8738.
> Suppose we have a grid with X server nodes and Y client nodes. Server nodes
> are restarted periodically while client nodes are left untouched. In this
> case *order* of current coordinator might be greater than *order* of any
> client node. Then when some client node leaves the grid, we will erroneously
> print the *Coordinator changed* message with *client* node being the previous
> coordinator. E.g.:
> {noformat}
> [2018-07-19 14:55:28,897][INFO ][disco-event-worker-#61] Node left topology:
> TcpDiscoveryNode [id=7240957f-a51b-452d-bfc8-420e8ef9ea68, addrs=[127.0.0.1,
> 172.17.0.1, 172.25.1.15], sockAddrs=[/172.17.0.1:0, /127.0.0.1:0,
> lab15.gridgain.local/172.25.1.15:0], discPort=0, order=16, intOrder=11,
> lastExchangeTime=1532001260398, loc=false, ver=2.5.1#20180717-sha1:80e51c80,
> isClient=true]
> [2018-07-19 14:55:28,899][INFO ][disco-event-worker-#61] Topology snapshot
> [ver=27, servers=3, clients=4, CPUs=96, offheap=260.0GB, heap=56.0GB]
> [2018-07-19 14:55:28,899][INFO ][disco-event-worker-#61] Coordinator changed
> [prev=TcpDiscoveryNode [id=7240957f-a51b-452d-bfc8-420e8ef9ea68,
> addrs=[127.0.0.1, 172.17.0.1, 172.25.1.15], sockAddrs=[/172.17.0.1:0,
> /127.0.0.1:0, lab15.gridgain.local/172.25.1.15:0], discPort=0, order=16,
> intOrder=11, lastExchangeTime=1532001260398, loc=false,
> ver=2.5.1#20180717-sha1:80e51c80, isClient=true], cur=TcpDiscoveryNode
> [id=760fd8f2-b9d7-4953-aa86-3954c05c9feb, addrs=[127.0.0.1, 172.17.0.1,
> 172.25.1.21], sockAddrs=[/172.17.0.1:47500,
> lab21.gridgain.local/172.25.1.21:47500, /127.0.0.1:47500], discPort=47500,
> order=21, intOrder=15, lastExchangeTime=1532001260428, loc=false,
> ver=2.5.1#20180717-sha1:80e51c80, isClient=false]]
> [2018-07-19 14:55:28,899][INFO ][disco-event-worker-#61] ^-- Node
> [id=22B15E97-9944-48B5-A473-5C64E75A4D5A, clusterState=ACTIVE]
> [2018-07-19 14:55:28,899][INFO ][disco-event-worker-#61] ^-- Baseline
> [id=6, size=3, online=3, offline=0]
> [2018-07-19 14:55:28,899][INFO ][disco-event-worker-#61] Data Regions
> Configured:
> [2018-07-19 14:55:28,900][INFO ][disco-event-worker-#61] ^-- default
> [initSize=256.0 MiB, maxSize=60.0 GiB, persistenceEnabled=true]
> {noformat}
> The *Coordinator changed* message should not be here because in fact the
> coordinator was not changed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-9144) A client node leaving a grid may trigger the wrong message about coordinator change in the logs
[
https://issues.apache.org/jira/browse/IGNITE-9144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Evgenii Zagumennov reassigned IGNITE-9144:
--
Assignee: Evgenii Zagumennov
> A client node leaving a grid may trigger the wrong message about coordinator
> change in the logs
> ---
>
> Key: IGNITE-9144
> URL: https://issues.apache.org/jira/browse/IGNITE-9144
> Project: Ignite
> Issue Type: Bug
>Reporter: Ivan Artukhov
>Assignee: Evgenii Zagumennov
>Priority: Major
>
> The issue was introduced by https://issues.apache.org/jira/browse/IGNITE-8738.
> Suppose we have a grid with X server nodes and Y client nodes. Server nodes
> are restarted periodically while client nodes are left untouched. In this
> case *order* of current coordinator might be greater than *order* of any
> client node. Then when some client node leaves the grid, we will erroneously
> print the *Coordinator changed* message with *client* node being the previous
> coordinator. E.g.:
> {noformat}
> [2018-07-19 14:55:28,897][INFO ][disco-event-worker-#61] Node left topology:
> TcpDiscoveryNode [id=7240957f-a51b-452d-bfc8-420e8ef9ea68, addrs=[127.0.0.1,
> 172.17.0.1, 172.25.1.15], sockAddrs=[/172.17.0.1:0, /127.0.0.1:0,
> lab15.gridgain.local/172.25.1.15:0], discPort=0, order=16, intOrder=11,
> lastExchangeTime=1532001260398, loc=false, ver=2.5.1#20180717-sha1:80e51c80,
> isClient=true]
> [2018-07-19 14:55:28,899][INFO ][disco-event-worker-#61] Topology snapshot
> [ver=27, servers=3, clients=4, CPUs=96, offheap=260.0GB, heap=56.0GB]
> [2018-07-19 14:55:28,899][INFO ][disco-event-worker-#61] Coordinator changed
> [prev=TcpDiscoveryNode [id=7240957f-a51b-452d-bfc8-420e8ef9ea68,
> addrs=[127.0.0.1, 172.17.0.1, 172.25.1.15], sockAddrs=[/172.17.0.1:0,
> /127.0.0.1:0, lab15.gridgain.local/172.25.1.15:0], discPort=0, order=16,
> intOrder=11, lastExchangeTime=1532001260398, loc=false,
> ver=2.5.1#20180717-sha1:80e51c80, isClient=true], cur=TcpDiscoveryNode
> [id=760fd8f2-b9d7-4953-aa86-3954c05c9feb, addrs=[127.0.0.1, 172.17.0.1,
> 172.25.1.21], sockAddrs=[/172.17.0.1:47500,
> lab21.gridgain.local/172.25.1.21:47500, /127.0.0.1:47500], discPort=47500,
> order=21, intOrder=15, lastExchangeTime=1532001260428, loc=false,
> ver=2.5.1#20180717-sha1:80e51c80, isClient=false]]
> [2018-07-19 14:55:28,899][INFO ][disco-event-worker-#61] ^-- Node
> [id=22B15E97-9944-48B5-A473-5C64E75A4D5A, clusterState=ACTIVE]
> [2018-07-19 14:55:28,899][INFO ][disco-event-worker-#61] ^-- Baseline
> [id=6, size=3, online=3, offline=0]
> [2018-07-19 14:55:28,899][INFO ][disco-event-worker-#61] Data Regions
> Configured:
> [2018-07-19 14:55:28,900][INFO ][disco-event-worker-#61] ^-- default
> [initSize=256.0 MiB, maxSize=60.0 GiB, persistenceEnabled=true]
> {noformat}
> The *Coordinator changed* message should not be here because in fact the
> coordinator was not changed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IGNITE-9117) Need to log GridReduceQueryExecutor#query long execution
[ https://issues.apache.org/jira/browse/IGNITE-9117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgenii Zagumennov resolved IGNITE-9117. Resolution: Duplicate > Need to log GridReduceQueryExecutor#query long execution > > > Key: IGNITE-9117 > URL: https://issues.apache.org/jira/browse/IGNITE-9117 > Project: Ignite > Issue Type: Improvement > Components: compute, sql >Reporter: Evgenii Zagumennov >Priority: Major > > In case of long query execution *GridReduceQueryExecutor.query()* should log > the root cause and throw an exception by timeout. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9117) Need to log GridReduceQueryExecutor#query long execution
Evgenii Zagumennov created IGNITE-9117: -- Summary: Need to log GridReduceQueryExecutor#query long execution Key: IGNITE-9117 URL: https://issues.apache.org/jira/browse/IGNITE-9117 Project: Ignite Issue Type: Improvement Components: compute, sql Reporter: Evgenii Zagumennov In case of long query execution *GridReduceQueryExecutor.query()* should log the root cause and throw an exception by timeout. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-8939) Transaction string reprsentation unhandled exception
[
https://issues.apache.org/jira/browse/IGNITE-8939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Evgenii Zagumennov reassigned IGNITE-8939:
--
Assignee: Stanilovsky Evgeny (was: Evgenii Zagumennov)
> Transaction string reprsentation unhandled exception
>
>
> Key: IGNITE-8939
> URL: https://issues.apache.org/jira/browse/IGNITE-8939
> Project: Ignite
> Issue Type: Bug
> Components: binary
>Reporter: Evgenii Zagumennov
>Assignee: Stanilovsky Evgeny
>Priority: Major
>
> IgniteTxHandler.finishDhtLocal() (IgniteTxHandler.java:957)
> {code:java}
> U.error(log, "Failed completing transaction [commit=" + req.commit() + ",
> tx=" + *tx* + ']', e);{code}
> tx.toString() can lead to excepion (in GridToStringBuilder.toStringImpl()),
> and original exception in transaction will be lost. We need to log original
> exception and catch probable tx.toString() exception.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-8939) Transaction string reprsentation unhandled exception
[
https://issues.apache.org/jira/browse/IGNITE-8939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Evgenii Zagumennov reassigned IGNITE-8939:
--
Assignee: Evgenii Zagumennov
> Transaction string reprsentation unhandled exception
>
>
> Key: IGNITE-8939
> URL: https://issues.apache.org/jira/browse/IGNITE-8939
> Project: Ignite
> Issue Type: Bug
> Components: binary
>Reporter: Evgenii Zagumennov
>Assignee: Evgenii Zagumennov
>Priority: Major
>
> IgniteTxHandler.finishDhtLocal() (IgniteTxHandler.java:957)
> {code:java}
> U.error(log, "Failed completing transaction [commit=" + req.commit() + ",
> tx=" + *tx* + ']', e);{code}
> tx.toString() can lead to excepion (in GridToStringBuilder.toStringImpl()),
> and original exception in transaction will be lost. We need to log original
> exception and catch probable tx.toString() exception.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8866) Need attempt to upload class until node leave or fail topology by discovery SPI
[
https://issues.apache.org/jira/browse/IGNITE-8866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Evgenii Zagumennov updated IGNITE-8866:
---
Description:
After one fail attempt to upload a class, client code getting exception:
{noformat}
10:04:46,253 INFO [stdout] (Thread-732) java.lang.NoClassDefFoundError:
com/company/deposit_pf_api/core/utils/DplUtils
10:04:46,253 INFO [stdout] (Thread-732) at
com.company.deposit_pf_api.comparators.CommonPredicate.nodeIdIgnite(CommonPredicate.java:225)
10:04:46,253 INFO [stdout] (Thread-732) at
com.company.deposit_pf_api.comparators.CommonPredicate.cacheEntities(CommonPredicate.java:191)
10:04:46,253 INFO [stdout] (Thread-732) at
com.company.deposit_pf_api.comparators.CommonPredicate.(CommonPredicate.java:116)
{noformat}
And log contains some related warnings:
{noformat}
018-06-19 10:04:18.459 [WARN
][pub-#3308%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDeploymentCommunication]
Failed to receive peer response from node within duration
[node=5861d763-a552-463e-817a-0742f7aad114, duration=5008]
2018-06-19 10:04:18.459 [WARN
][pub-#3308%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDeploymentPerVersionStore]
Failed to send class-loading request to node (is node alive?)
[node=5861d763-a552-463e-817a-0742f7aad114,
clsName=com.company.deposit_pf_api.core.utils.DplUtils,
clsPath=com/company/deposit_pf_api/core/utils/DplUtils.class,
clsLdrId=370f1361461-5861d763-a552-463e-817a-0742f7aad114,
parentClsLdr=com.company.dpl.gridgain.ignite.NodeClassLoader@1ce4a752]
{noformat}
I think should to upload class through p2p until node present in topology.
Look at the [^P2PClassDeploymentDelay.java] reproducer.
was:
After one fail attempt to upload a class, client code getting exception:
{noformat}
10:04:46,253 INFO [stdout] (Thread-732) java.lang.NoClassDefFoundError:
ru/sbt/deposit_pf_api/core/utils/DplUtils
10:04:46,253 INFO [stdout] (Thread-732) at
ru.sbt.deposit_pf_api.comparators.CommonPredicate.nodeIdIgnite(CommonPredicate.java:225)
10:04:46,253 INFO [stdout] (Thread-732) at
ru.sbt.deposit_pf_api.comparators.CommonPredicate.cacheEntities(CommonPredicate.java:191)
10:04:46,253 INFO [stdout] (Thread-732) at
ru.sbt.deposit_pf_api.comparators.CommonPredicate.(CommonPredicate.java:116)
{noformat}
And log contains some related warnings:
{noformat}
018-06-19 10:04:18.459 [WARN
][pub-#3308%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDeploymentCommunication]
Failed to receive peer response from node within duration
[node=5861d763-a552-463e-817a-0742f7aad114, duration=5008]
2018-06-19 10:04:18.459 [WARN
][pub-#3308%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDeploymentPerVersionStore]
Failed to send class-loading request to node (is node alive?)
[node=5861d763-a552-463e-817a-0742f7aad114,
clsName=ru.sbt.deposit_pf_api.core.utils.DplUtils,
clsPath=ru/sbt/deposit_pf_api/core/utils/DplUtils.class,
clsLdrId=370f1361461-5861d763-a552-463e-817a-0742f7aad114,
parentClsLdr=com.sbt.dpl.gridgain.ignite.NodeClassLoader@1ce4a752]
{noformat}
I think should to upload class through p2p until node present in topology.
Look at the [^P2PClassDeploymentDelay.java] reproducer.
> Need attempt to upload class until node leave or fail topology by discovery
> SPI
> ---
>
> Key: IGNITE-8866
> URL: https://issues.apache.org/jira/browse/IGNITE-8866
> Project: Ignite
> Issue Type: Bug
>Reporter: Vladislav Pyatkov
>Assignee: Evgenii Zagumennov
>Priority: Major
> Attachments: P2PClassDeploymentDelay.java
>
>
> After one fail attempt to upload a class, client code getting exception:
> {noformat}
> 10:04:46,253 INFO [stdout] (Thread-732) java.lang.NoClassDefFoundError:
> com/company/deposit_pf_api/core/utils/DplUtils
> 10:04:46,253 INFO [stdout] (Thread-732) at
> com.company.deposit_pf_api.comparators.CommonPredicate.nodeIdIgnite(CommonPredicate.java:225)
> 10:04:46,253 INFO [stdout] (Thread-732) at
> com.company.deposit_pf_api.comparators.CommonPredicate.cacheEntities(CommonPredicate.java:191)
> 10:04:46,253 INFO [stdout] (Thread-732) at
> com.company.deposit_pf_api.comparators.CommonPredicate.(CommonPredicate.java:116)
> {noformat}
> And log contains some related warnings:
> {noformat}
> 018-06-19 10:04:18.459 [WARN
> ][pub-#3308%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDeploymentCommunication]
> Failed to receive peer response from node within duration
> [node=5861d763-a552-463e-817a-0742f7aad114, duration=5008]
> 2018-06-19 10:04:18.459 [WARN
> ][pub-#3308%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDeploymentPerVersionStore]
> Failed to send class-loading request to node (is node alive?)
> [node=5861d763-a552-463e-817a-0742f7aad114,
> clsName=com.company.deposit_pf_api.core.utils.DplUtils,
>
[jira] [Commented] (IGNITE-8866) Need attempt to upload class until node leave or fail topology by discovery SPI
[
https://issues.apache.org/jira/browse/IGNITE-8866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16554252#comment-16554252
]
Evgenii Zagumennov commented on IGNITE-8866:
https://ci.ignite.apache.org/viewLog.html?buildId=1534268=buildResultsDiv=IgniteTests24Java8_RunAll
> Need attempt to upload class until node leave or fail topology by discovery
> SPI
> ---
>
> Key: IGNITE-8866
> URL: https://issues.apache.org/jira/browse/IGNITE-8866
> Project: Ignite
> Issue Type: Bug
>Reporter: Vladislav Pyatkov
>Assignee: Evgenii Zagumennov
>Priority: Major
> Attachments: P2PClassDeploymentDelay.java
>
>
> After one fail attempt to upload a class, client code getting exception:
> {noformat}
> 10:04:46,253 INFO [stdout] (Thread-732) java.lang.NoClassDefFoundError:
> ru/sbt/deposit_pf_api/core/utils/DplUtils
> 10:04:46,253 INFO [stdout] (Thread-732) at
> ru.sbt.deposit_pf_api.comparators.CommonPredicate.nodeIdIgnite(CommonPredicate.java:225)
> 10:04:46,253 INFO [stdout] (Thread-732) at
> ru.sbt.deposit_pf_api.comparators.CommonPredicate.cacheEntities(CommonPredicate.java:191)
> 10:04:46,253 INFO [stdout] (Thread-732) at
> ru.sbt.deposit_pf_api.comparators.CommonPredicate.(CommonPredicate.java:116)
> {noformat}
> And log contains some related warnings:
> {noformat}
> 018-06-19 10:04:18.459 [WARN
> ][pub-#3308%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDeploymentCommunication]
> Failed to receive peer response from node within duration
> [node=5861d763-a552-463e-817a-0742f7aad114, duration=5008]
> 2018-06-19 10:04:18.459 [WARN
> ][pub-#3308%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDeploymentPerVersionStore]
> Failed to send class-loading request to node (is node alive?)
> [node=5861d763-a552-463e-817a-0742f7aad114,
> clsName=ru.sbt.deposit_pf_api.core.utils.DplUtils,
> clsPath=ru/sbt/deposit_pf_api/core/utils/DplUtils.class,
> clsLdrId=370f1361461-5861d763-a552-463e-817a-0742f7aad114,
> parentClsLdr=com.sbt.dpl.gridgain.ignite.NodeClassLoader@1ce4a752]
> {noformat}
> I think should to upload class through p2p until node present in topology.
> Look at the [^P2PClassDeploymentDelay.java] reproducer.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9048) Local SqlFieldsQuery on client leads to exception
[
https://issues.apache.org/jira/browse/IGNITE-9048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Evgenii Zagumennov updated IGNITE-9048:
---
Description:
SqlFieldsQuery with setLocal(true) on client node throws exception
{code:java}
Caused by: java.lang.NullPointerException
at
org.apache.ignite.internal.processors.query.h2.database.H2TreeIndex.segmentsCount(H2TreeIndex.java:187)
at
org.apache.ignite.internal.processors.query.h2.opt.GridH2IndexBase.threadLocalSegment(GridH2IndexBase.java:182)
at
org.apache.ignite.internal.processors.query.h2.database.H2TreeIndex.find(H2TreeIndex.java:195)
at org.h2.index.BaseIndex.find(BaseIndex.java:128)
at org.h2.index.IndexCursor.find(IndexCursor.java:169)
at org.h2.table.TableFilter.next(TableFilter.java:468)
at
org.h2.command.dml.Select$LazyResultQueryFlat.fetchNextRow(Select.java:1452)
at org.h2.result.LazyResult.hasNext(LazyResult.java:79)
at org.h2.result.LazyResult.next(LazyResult.java:59)
at org.h2.command.dml.Select.queryFlat(Select.java:519)
at org.h2.command.dml.Select.queryWithoutCache(Select.java:625)
at org.h2.command.dml.Query.queryWithoutCacheLazyCheck(Query.java:114)
at org.h2.command.dml.Query.query(Query.java:352)
at org.h2.command.dml.Query.query(Query.java:333)
at org.h2.command.CommandContainer.query(CommandContainer.java:113)
at org.h2.command.Command.executeQuery(Command.java:201)
... 18 more{code}
*Reproducer "LocalSqlFieldsQueryOnClientFailTest.java" is in the attachement*
was:
SqlFieldsQuery with setLocal(true) on client node throws exception
{code:java}
Caused by: java.lang.NullPointerException
at
org.apache.ignite.internal.processors.query.h2.database.H2TreeIndex.segmentsCount(H2TreeIndex.java:187)
at
org.apache.ignite.internal.processors.query.h2.opt.GridH2IndexBase.threadLocalSegment(GridH2IndexBase.java:182)
at
org.apache.ignite.internal.processors.query.h2.database.H2TreeIndex.find(H2TreeIndex.java:195)
at org.h2.index.BaseIndex.find(BaseIndex.java:128)
at org.h2.index.IndexCursor.find(IndexCursor.java:169)
at org.h2.table.TableFilter.next(TableFilter.java:468)
at
org.h2.command.dml.Select$LazyResultQueryFlat.fetchNextRow(Select.java:1452)
at org.h2.result.LazyResult.hasNext(LazyResult.java:79)
at org.h2.result.LazyResult.next(LazyResult.java:59)
at org.h2.command.dml.Select.queryFlat(Select.java:519)
at org.h2.command.dml.Select.queryWithoutCache(Select.java:625)
at org.h2.command.dml.Query.queryWithoutCacheLazyCheck(Query.java:114)
at org.h2.command.dml.Query.query(Query.java:352)
at org.h2.command.dml.Query.query(Query.java:333)
at org.h2.command.CommandContainer.query(CommandContainer.java:113)
at org.h2.command.Command.executeQuery(Command.java:201)
... 18 more{code}
Reproducer "LocalSqlFieldsQueryOnClientFailTest.java" is in the attachement
> Local SqlFieldsQuery on client leads to exception
> -
>
> Key: IGNITE-9048
> URL: https://issues.apache.org/jira/browse/IGNITE-9048
> Project: Ignite
> Issue Type: Bug
> Components: cache, clients, sql
>Reporter: Evgenii Zagumennov
>Priority: Major
> Attachments: LocalSqlFieldsQueryOnClientFailTest.java
>
>
> SqlFieldsQuery with setLocal(true) on client node throws exception
>
> {code:java}
> Caused by: java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.query.h2.database.H2TreeIndex.segmentsCount(H2TreeIndex.java:187)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2IndexBase.threadLocalSegment(GridH2IndexBase.java:182)
> at
> org.apache.ignite.internal.processors.query.h2.database.H2TreeIndex.find(H2TreeIndex.java:195)
> at org.h2.index.BaseIndex.find(BaseIndex.java:128)
> at org.h2.index.IndexCursor.find(IndexCursor.java:169)
> at org.h2.table.TableFilter.next(TableFilter.java:468)
> at
> org.h2.command.dml.Select$LazyResultQueryFlat.fetchNextRow(Select.java:1452)
> at org.h2.result.LazyResult.hasNext(LazyResult.java:79)
> at org.h2.result.LazyResult.next(LazyResult.java:59)
> at org.h2.command.dml.Select.queryFlat(Select.java:519)
> at org.h2.command.dml.Select.queryWithoutCache(Select.java:625)
> at org.h2.command.dml.Query.queryWithoutCacheLazyCheck(Query.java:114)
> at org.h2.command.dml.Query.query(Query.java:352)
> at org.h2.command.dml.Query.query(Query.java:333)
> at org.h2.command.CommandContainer.query(CommandContainer.java:113)
> at org.h2.command.Command.executeQuery(Command.java:201)
> ... 18 more{code}
>
> *Reproducer "LocalSqlFieldsQueryOnClientFailTest.java" is in the attachement*
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9048) Local SqlFieldsQuery on client leads to exception
Evgenii Zagumennov created IGNITE-9048:
--
Summary: Local SqlFieldsQuery on client leads to exception
Key: IGNITE-9048
URL: https://issues.apache.org/jira/browse/IGNITE-9048
Project: Ignite
Issue Type: Bug
Components: cache, clients, sql
Reporter: Evgenii Zagumennov
Attachments: LocalSqlFieldsQueryOnClientFailTest.java
SqlFieldsQuery with setLocal(true) on client node throws exception
{code:java}
Caused by: java.lang.NullPointerException
at
org.apache.ignite.internal.processors.query.h2.database.H2TreeIndex.segmentsCount(H2TreeIndex.java:187)
at
org.apache.ignite.internal.processors.query.h2.opt.GridH2IndexBase.threadLocalSegment(GridH2IndexBase.java:182)
at
org.apache.ignite.internal.processors.query.h2.database.H2TreeIndex.find(H2TreeIndex.java:195)
at org.h2.index.BaseIndex.find(BaseIndex.java:128)
at org.h2.index.IndexCursor.find(IndexCursor.java:169)
at org.h2.table.TableFilter.next(TableFilter.java:468)
at
org.h2.command.dml.Select$LazyResultQueryFlat.fetchNextRow(Select.java:1452)
at org.h2.result.LazyResult.hasNext(LazyResult.java:79)
at org.h2.result.LazyResult.next(LazyResult.java:59)
at org.h2.command.dml.Select.queryFlat(Select.java:519)
at org.h2.command.dml.Select.queryWithoutCache(Select.java:625)
at org.h2.command.dml.Query.queryWithoutCacheLazyCheck(Query.java:114)
at org.h2.command.dml.Query.query(Query.java:352)
at org.h2.command.dml.Query.query(Query.java:333)
at org.h2.command.CommandContainer.query(CommandContainer.java:113)
at org.h2.command.Command.executeQuery(Command.java:201)
... 18 more{code}
Reproducer "LocalSqlFieldsQueryOnClientFailTest.java" is in the attachement
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8866) Need attempt to upload class until node leave or fail topology by discovery SPI
[
https://issues.apache.org/jira/browse/IGNITE-8866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16550744#comment-16550744
]
Evgenii Zagumennov commented on IGNITE-8866:
I guess, sending requests untill a node leave the topology is a wrong way.
Resource node may not respond because of GC-pause or another reason, but number
of requests will grow. I've added to
GridDeploymentCommunication#sendResourceRequest ability to retry to send
request. Number of retries is definable.
> Need attempt to upload class until node leave or fail topology by discovery
> SPI
> ---
>
> Key: IGNITE-8866
> URL: https://issues.apache.org/jira/browse/IGNITE-8866
> Project: Ignite
> Issue Type: Bug
>Reporter: Vladislav Pyatkov
>Assignee: Evgenii Zagumennov
>Priority: Major
> Attachments: P2PClassDeploymentDelay.java
>
>
> After one fail attempt to upload a class, client code getting exception:
> {noformat}
> 10:04:46,253 INFO [stdout] (Thread-732) java.lang.NoClassDefFoundError:
> ru/sbt/deposit_pf_api/core/utils/DplUtils
> 10:04:46,253 INFO [stdout] (Thread-732) at
> ru.sbt.deposit_pf_api.comparators.CommonPredicate.nodeIdIgnite(CommonPredicate.java:225)
> 10:04:46,253 INFO [stdout] (Thread-732) at
> ru.sbt.deposit_pf_api.comparators.CommonPredicate.cacheEntities(CommonPredicate.java:191)
> 10:04:46,253 INFO [stdout] (Thread-732) at
> ru.sbt.deposit_pf_api.comparators.CommonPredicate.(CommonPredicate.java:116)
> {noformat}
> And log contains some related warnings:
> {noformat}
> 018-06-19 10:04:18.459 [WARN
> ][pub-#3308%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDeploymentCommunication]
> Failed to receive peer response from node within duration
> [node=5861d763-a552-463e-817a-0742f7aad114, duration=5008]
> 2018-06-19 10:04:18.459 [WARN
> ][pub-#3308%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDeploymentPerVersionStore]
> Failed to send class-loading request to node (is node alive?)
> [node=5861d763-a552-463e-817a-0742f7aad114,
> clsName=ru.sbt.deposit_pf_api.core.utils.DplUtils,
> clsPath=ru/sbt/deposit_pf_api/core/utils/DplUtils.class,
> clsLdrId=370f1361461-5861d763-a552-463e-817a-0742f7aad114,
> parentClsLdr=com.sbt.dpl.gridgain.ignite.NodeClassLoader@1ce4a752]
> {noformat}
> I think should to upload class through p2p until node present in topology.
> Look at the [^P2PClassDeploymentDelay.java] reproducer.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8738) Improve coordinator change information
[
https://issues.apache.org/jira/browse/IGNITE-8738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16536602#comment-16536602
]
Evgenii Zagumennov commented on IGNITE-8738:
[~agoncharuk], I've implemented your suggestion.
> Improve coordinator change information
> --
>
> Key: IGNITE-8738
> URL: https://issues.apache.org/jira/browse/IGNITE-8738
> Project: Ignite
> Issue Type: Improvement
>Reporter: Alexey Goncharuk
>Assignee: Evgenii Zagumennov
>Priority: Major
> Time Spent: 16h
> Remaining Estimate: 0h
>
> When topology changes and coordinator is also changed, we need to print out
> this alongside with topology information.
> An example of such message:
> {{Coordinator changed [prev=node.tostring(), cur=node.tostr()]}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8939) Transaction string reprsentation unhandled exception
[
https://issues.apache.org/jira/browse/IGNITE-8939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Evgenii Zagumennov updated IGNITE-8939:
---
Description:
IgniteTxHandler.finishDhtLocal() (IgniteTxHandler.java:957)
{code:java}
U.error(log, "Failed completing transaction [commit=" + req.commit() + ", tx="
+ *tx* + ']', e);{code}
tx.toString() can lead to excepion (in GridToStringBuilder.toStringImpl()), and
original exception in transaction will be lost. We need to log original
exception and catch probable tx.toString() exception.
was:
IgniteTxHandler.finishDhtLocal() (IgniteTxHandler.java:957)
U.error(log, "Failed completing transaction [commit=" + req.commit() + ", tx="
+ *tx* + ']', e);
tx.toString() can lead to excepion (because of errors in metadata), and
original exception in transaction will be lost. We need to log original
exception and catch probable tx.toString() exception.
> Transaction string reprsentation unhandled exception
>
>
> Key: IGNITE-8939
> URL: https://issues.apache.org/jira/browse/IGNITE-8939
> Project: Ignite
> Issue Type: Bug
> Components: binary
>Reporter: Evgenii Zagumennov
>Priority: Major
>
> IgniteTxHandler.finishDhtLocal() (IgniteTxHandler.java:957)
> {code:java}
> U.error(log, "Failed completing transaction [commit=" + req.commit() + ",
> tx=" + *tx* + ']', e);{code}
> tx.toString() can lead to excepion (in GridToStringBuilder.toStringImpl()),
> and original exception in transaction will be lost. We need to log original
> exception and catch probable tx.toString() exception.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8939) Transaction string reprsentation unhandled exception
[ https://issues.apache.org/jira/browse/IGNITE-8939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgenii Zagumennov updated IGNITE-8939: --- Description: IgniteTxHandler.finishDhtLocal() (IgniteTxHandler.java:957) U.error(log, "Failed completing transaction [commit=" + req.commit() + ", tx=" + *tx* + ']', e); tx.toString() can lead to excepion (because of errors in metadata), and original exception in transaction will be lost. We need to log original exception and catch probable tx.toString() exception. > Transaction string reprsentation unhandled exception > > > Key: IGNITE-8939 > URL: https://issues.apache.org/jira/browse/IGNITE-8939 > Project: Ignite > Issue Type: Bug > Components: binary >Reporter: Evgenii Zagumennov >Priority: Major > > IgniteTxHandler.finishDhtLocal() (IgniteTxHandler.java:957) > U.error(log, "Failed completing transaction [commit=" + req.commit() + ", > tx=" + *tx* + ']', e); > tx.toString() can lead to excepion (because of errors in metadata), and > original exception in transaction will be lost. We need to log original > exception and catch probable tx.toString() exception. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8939) Transaction string reprsentation unhandled exception
[ https://issues.apache.org/jira/browse/IGNITE-8939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgenii Zagumennov updated IGNITE-8939: --- Summary: Transaction string reprsentation unhandled exception (was: Error in binary meta data after RESTORE with wal_compaction) > Transaction string reprsentation unhandled exception > > > Key: IGNITE-8939 > URL: https://issues.apache.org/jira/browse/IGNITE-8939 > Project: Ignite > Issue Type: Bug > Components: binary >Reporter: Evgenii Zagumennov >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8939) Error in binary meta data after RESTORE with wal_compaction
[ https://issues.apache.org/jira/browse/IGNITE-8939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgenii Zagumennov updated IGNITE-8939: --- Description: (was: Steps to reproduce: # CREATE snapshot # RESTORE from snapshot # CHECK snapshot # Restart client nodes # Run some jobs on grid Node fails with exception: org.apache.ignite.binary.BinaryObjectException: Cannot find schema for object with compact footer [typeName=...] at org.apache.ignite.internal.binary.BinaryReaderExImpl.getOrCreateSchema(BinaryReaderExImpl.java:2033) at org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:286) at org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:185) at org.apache.ignite.internal.binary.BinaryObjectImpl.reader(BinaryObjectImpl.java:832) at org.apache.ignite.internal.binary.BinaryObjectImpl.reader(BinaryObjectImpl.java:846) at org.apache.ignite.internal.binary.BinaryObjectImpl.field(BinaryObjectImpl.java:626) at org.apache.ignite.internal.binary.BinaryObjectExImpl.toString(BinaryObjectExImpl.java:225) at org.apache.ignite.internal.binary.BinaryObjectExImpl.appendValue(BinaryObjectExImpl.java:280) at org.apache.ignite.internal.binary.BinaryObjectExImpl.toString(BinaryObjectExImpl.java:229) at org.apache.ignite.internal.binary.BinaryObjectExImpl.toString(BinaryObjectExImpl.java:186) *wlaModeEnabled = true*) > Error in binary meta data after RESTORE with wal_compaction > --- > > Key: IGNITE-8939 > URL: https://issues.apache.org/jira/browse/IGNITE-8939 > Project: Ignite > Issue Type: Bug > Components: binary >Reporter: Evgenii Zagumennov >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8939) Error in binary meta data after RESTORE with wal_compaction
[ https://issues.apache.org/jira/browse/IGNITE-8939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgenii Zagumennov updated IGNITE-8939: --- Description: Steps to reproduce: # CREATE snapshot # RESTORE from snapshot # CHECK snapshot # Restart client nodes # Run some jobs on grid Node fails with exception: org.apache.ignite.binary.BinaryObjectException: Cannot find schema for object with compact footer [typeName=...] at org.apache.ignite.internal.binary.BinaryReaderExImpl.getOrCreateSchema(BinaryReaderExImpl.java:2033) at org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:286) at org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:185) at org.apache.ignite.internal.binary.BinaryObjectImpl.reader(BinaryObjectImpl.java:832) at org.apache.ignite.internal.binary.BinaryObjectImpl.reader(BinaryObjectImpl.java:846) at org.apache.ignite.internal.binary.BinaryObjectImpl.field(BinaryObjectImpl.java:626) at org.apache.ignite.internal.binary.BinaryObjectExImpl.toString(BinaryObjectExImpl.java:225) at org.apache.ignite.internal.binary.BinaryObjectExImpl.appendValue(BinaryObjectExImpl.java:280) at org.apache.ignite.internal.binary.BinaryObjectExImpl.toString(BinaryObjectExImpl.java:229) at org.apache.ignite.internal.binary.BinaryObjectExImpl.toString(BinaryObjectExImpl.java:186) *wlaModeEnabled = true* was: Steps to reproduce: # CREATE snapshot # RESTORE from snapshot # CHECK snapshot # Restart client nodes # Run some jobs on grid Node fails with exception: org.apache.ignite.binary.BinaryObjectException: Cannot find schema for object with compact footer [typeName=...] at org.apache.ignite.internal.binary.BinaryReaderExImpl.getOrCreateSchema(BinaryReaderExImpl.java:2033) at org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:286) at org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:185) at org.apache.ignite.internal.binary.BinaryObjectImpl.reader(BinaryObjectImpl.java:832) at org.apache.ignite.internal.binary.BinaryObjectImpl.reader(BinaryObjectImpl.java:846) at org.apache.ignite.internal.binary.BinaryObjectImpl.field(BinaryObjectImpl.java:626) at org.apache.ignite.internal.binary.BinaryObjectExImpl.toString(BinaryObjectExImpl.java:225) at org.apache.ignite.internal.binary.BinaryObjectExImpl.appendValue(BinaryObjectExImpl.java:280) at org.apache.ignite.internal.binary.BinaryObjectExImpl.toString(BinaryObjectExImpl.java:229) at org.apache.ignite.internal.binary.BinaryObjectExImpl.toString(BinaryObjectExImpl.java:186) > Error in binary meta data after RESTORE with wal_compaction > --- > > Key: IGNITE-8939 > URL: https://issues.apache.org/jira/browse/IGNITE-8939 > Project: Ignite > Issue Type: Bug > Components: binary >Reporter: Evgenii Zagumennov >Priority: Major > > Steps to reproduce: > # CREATE snapshot > # RESTORE from snapshot > # CHECK snapshot > # Restart client nodes > # Run some jobs on grid > Node fails with exception: > > org.apache.ignite.binary.BinaryObjectException: Cannot find schema for > object with compact footer [typeName=...] > at > org.apache.ignite.internal.binary.BinaryReaderExImpl.getOrCreateSchema(BinaryReaderExImpl.java:2033) > at > org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:286) > at > org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:185) > at > org.apache.ignite.internal.binary.BinaryObjectImpl.reader(BinaryObjectImpl.java:832) > at > org.apache.ignite.internal.binary.BinaryObjectImpl.reader(BinaryObjectImpl.java:846) > at > org.apache.ignite.internal.binary.BinaryObjectImpl.field(BinaryObjectImpl.java:626) > at > org.apache.ignite.internal.binary.BinaryObjectExImpl.toString(BinaryObjectExImpl.java:225) > at > org.apache.ignite.internal.binary.BinaryObjectExImpl.appendValue(BinaryObjectExImpl.java:280) > at > org.apache.ignite.internal.binary.BinaryObjectExImpl.toString(BinaryObjectExImpl.java:229) > at > org.apache.ignite.internal.binary.BinaryObjectExImpl.toString(BinaryObjectExImpl.java:186) > > *wlaModeEnabled = true* -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8939) Error in binary meta data after RESTORE with wal_compaction
Evgenii Zagumennov created IGNITE-8939: -- Summary: Error in binary meta data after RESTORE with wal_compaction Key: IGNITE-8939 URL: https://issues.apache.org/jira/browse/IGNITE-8939 Project: Ignite Issue Type: Bug Components: binary Reporter: Evgenii Zagumennov Steps to reproduce: # CREATE snapshot # RESTORE from snapshot # CHECK snapshot # Restart client nodes # Run some jobs on grid Node fails with exception: org.apache.ignite.binary.BinaryObjectException: Cannot find schema for object with compact footer [typeName=...] at org.apache.ignite.internal.binary.BinaryReaderExImpl.getOrCreateSchema(BinaryReaderExImpl.java:2033) at org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:286) at org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:185) at org.apache.ignite.internal.binary.BinaryObjectImpl.reader(BinaryObjectImpl.java:832) at org.apache.ignite.internal.binary.BinaryObjectImpl.reader(BinaryObjectImpl.java:846) at org.apache.ignite.internal.binary.BinaryObjectImpl.field(BinaryObjectImpl.java:626) at org.apache.ignite.internal.binary.BinaryObjectExImpl.toString(BinaryObjectExImpl.java:225) at org.apache.ignite.internal.binary.BinaryObjectExImpl.appendValue(BinaryObjectExImpl.java:280) at org.apache.ignite.internal.binary.BinaryObjectExImpl.toString(BinaryObjectExImpl.java:229) at org.apache.ignite.internal.binary.BinaryObjectExImpl.toString(BinaryObjectExImpl.java:186) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-8866) Need attempt to upload class until node leave or fail topology by discovery SPI
[
https://issues.apache.org/jira/browse/IGNITE-8866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Evgenii Zagumennov reassigned IGNITE-8866:
--
Assignee: Evgenii Zagumennov
> Need attempt to upload class until node leave or fail topology by discovery
> SPI
> ---
>
> Key: IGNITE-8866
> URL: https://issues.apache.org/jira/browse/IGNITE-8866
> Project: Ignite
> Issue Type: Bug
>Reporter: Vladislav Pyatkov
>Assignee: Evgenii Zagumennov
>Priority: Major
> Attachments: P2PClassDeploymentDelay.java
>
>
> After one fail attempt to upload a class, client code getting exception:
> {noformat}
> 10:04:46,253 INFO [stdout] (Thread-732) java.lang.NoClassDefFoundError:
> ru/sbt/deposit_pf_api/core/utils/DplUtils
> 10:04:46,253 INFO [stdout] (Thread-732) at
> ru.sbt.deposit_pf_api.comparators.CommonPredicate.nodeIdIgnite(CommonPredicate.java:225)
> 10:04:46,253 INFO [stdout] (Thread-732) at
> ru.sbt.deposit_pf_api.comparators.CommonPredicate.cacheEntities(CommonPredicate.java:191)
> 10:04:46,253 INFO [stdout] (Thread-732) at
> ru.sbt.deposit_pf_api.comparators.CommonPredicate.(CommonPredicate.java:116)
> {noformat}
> And log contains some related warnings:
> {noformat}
> 018-06-19 10:04:18.459 [WARN
> ][pub-#3308%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDeploymentCommunication]
> Failed to receive peer response from node within duration
> [node=5861d763-a552-463e-817a-0742f7aad114, duration=5008]
> 2018-06-19 10:04:18.459 [WARN
> ][pub-#3308%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDeploymentPerVersionStore]
> Failed to send class-loading request to node (is node alive?)
> [node=5861d763-a552-463e-817a-0742f7aad114,
> clsName=ru.sbt.deposit_pf_api.core.utils.DplUtils,
> clsPath=ru/sbt/deposit_pf_api/core/utils/DplUtils.class,
> clsLdrId=370f1361461-5861d763-a552-463e-817a-0742f7aad114,
> parentClsLdr=com.sbt.dpl.gridgain.ignite.NodeClassLoader@1ce4a752]
> {noformat}
> I think should to upload class through p2p until node present in topology.
> Look at the [^P2PClassDeploymentDelay.java] reproducer.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8738) Improve coordinator change information
[
https://issues.apache.org/jira/browse/IGNITE-8738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524987#comment-16524987
]
Evgenii Zagumennov commented on IGNITE-8738:
After discussion with [~ivandasch], removed filed currCrd and used
DiscoCache#oldestAliveServerNode. That should prevent race conditions.
> Improve coordinator change information
> --
>
> Key: IGNITE-8738
> URL: https://issues.apache.org/jira/browse/IGNITE-8738
> Project: Ignite
> Issue Type: Improvement
>Reporter: Alexey Goncharuk
>Assignee: Evgenii Zagumennov
>Priority: Major
>
> When topology changes and coordinator is also changed, we need to print out
> this alongside with topology information.
> An example of such message:
> {{Coordinator changed [prev=node.tostring(), cur=node.tostr()]}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8798) Move transaction recovery logging to INFO level
[
https://issues.apache.org/jira/browse/IGNITE-8798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16514113#comment-16514113
]
Evgenii Zagumennov commented on IGNITE-8798:
[~ascherbakov],
I've implemented your remarks and squashed commits.
> Move transaction recovery logging to INFO level
> ---
>
> Key: IGNITE-8798
> URL: https://issues.apache.org/jira/browse/IGNITE-8798
> Project: Ignite
> Issue Type: Improvement
>Reporter: Alexey Goncharuk
>Assignee: Evgenii Zagumennov
>Priority: Major
>
> Currently we log transaction recovery state changes to {{DEBUG}}, however,
> this information is critically important for production deployment and
> incident analysis. I suggest to move corresponding logging
> ({{GridCacheTxRecoveryFuture}} and surrounding code) to {{INFO}} level.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-8798) Move transaction recovery logging to INFO level
[
https://issues.apache.org/jira/browse/IGNITE-8798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Evgenii Zagumennov reassigned IGNITE-8798:
--
Assignee: Evgenii Zagumennov
> Move transaction recovery logging to INFO level
> ---
>
> Key: IGNITE-8798
> URL: https://issues.apache.org/jira/browse/IGNITE-8798
> Project: Ignite
> Issue Type: Improvement
>Reporter: Alexey Goncharuk
>Assignee: Evgenii Zagumennov
>Priority: Major
>
> Currently we log transaction recovery state changes to {{DEBUG}}, however,
> this information is critically important for production deployment and
> incident analysis. I suggest to move corresponding logging
> ({{GridCacheTxRecoveryFuture}} and surrounding code) to {{INFO}} level.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-8738) Improve coordinator change information
[
https://issues.apache.org/jira/browse/IGNITE-8738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Evgenii Zagumennov reassigned IGNITE-8738:
--
Assignee: Evgenii Zagumennov
> Improve coordinator change information
> --
>
> Key: IGNITE-8738
> URL: https://issues.apache.org/jira/browse/IGNITE-8738
> Project: Ignite
> Issue Type: Improvement
>Reporter: Alexey Goncharuk
>Assignee: Evgenii Zagumennov
>Priority: Major
>
> When topology changes and coordinator is also changed, we need to print out
> this alongside with topology information.
> An example of such message:
> {{Coordinator changed [prev=node.tostring(), cur=node.tostr()]}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-8745) Add ability to monitor TCP discovery ring information
[ https://issues.apache.org/jira/browse/IGNITE-8745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgenii Zagumennov reassigned IGNITE-8745: -- Assignee: Evgenii Zagumennov > Add ability to monitor TCP discovery ring information > - > > Key: IGNITE-8745 > URL: https://issues.apache.org/jira/browse/IGNITE-8745 > Project: Ignite > Issue Type: Improvement >Reporter: Alexey Goncharuk >Assignee: Evgenii Zagumennov >Priority: Major > > We should add the following modifications: > 1) Add a method on TCP discovery MBean to dump the ring structure on local > node and on all nodes in the grid > 2) Make tcp-disco-worker thread name reflect the node to which the local node > is connected > 3) Add a method on TCP discovery MBean to return current topology version -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-7766) Ignite Queries 2: Test always failed IgniteCacheQueryNodeRestartTxSelfTest.testRestarts
[ https://issues.apache.org/jira/browse/IGNITE-7766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16497766#comment-16497766 ] Evgenii Zagumennov edited comment on IGNITE-7766 at 6/1/18 9:15 AM: [~ilantukh], [~dpavlov], i've implemented fix. Now, if the first cache in the cacheIds collection is not partitioned, we find it (if it is in cacheIds) and move to the index 0. was (Author: ezagumennov): [~ilantukh], i've implemented your advice. Now, if the first cache in the cacheIds collection is not partitioned, we find it (if it is in cacheIds) and move to the index 0. > Ignite Queries 2: Test always failed > IgniteCacheQueryNodeRestartTxSelfTest.testRestarts > --- > > Key: IGNITE-7766 > URL: https://issues.apache.org/jira/browse/IGNITE-7766 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Dmitriy Pavlov >Assignee: Evgenii Zagumennov >Priority: Major > Labels: MakeTeamcityGreenAgain > > Ignite Queries 2 > IgniteBinaryCacheQueryTestSuite2: > IgniteCacheQueryNodeRestartTxSelfTest.testRestarts (fail rate 76,1%) > IgniteCacheQueryNodeRestartTxSelfTest.testRestarts > Current failure: refs/heads/master #345 No changes 11 Feb 18 03:03 > junit.framework.AssertionFailedError: On large page size must retry. > Last runs fails with 100% probability. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7766) Ignite Queries 2: Test always failed IgniteCacheQueryNodeRestartTxSelfTest.testRestarts
[ https://issues.apache.org/jira/browse/IGNITE-7766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16497766#comment-16497766 ] Evgenii Zagumennov commented on IGNITE-7766: [~ilantukh], i've implemented your advice. Now, if the first cache in the cacheIds collection is not partitioned, we find it (if it is in cacheIds) and move to the index 0. > Ignite Queries 2: Test always failed > IgniteCacheQueryNodeRestartTxSelfTest.testRestarts > --- > > Key: IGNITE-7766 > URL: https://issues.apache.org/jira/browse/IGNITE-7766 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Dmitriy Pavlov >Assignee: Evgenii Zagumennov >Priority: Major > Labels: MakeTeamcityGreenAgain > > Ignite Queries 2 > IgniteBinaryCacheQueryTestSuite2: > IgniteCacheQueryNodeRestartTxSelfTest.testRestarts (fail rate 76,1%) > IgniteCacheQueryNodeRestartTxSelfTest.testRestarts > Current failure: refs/heads/master #345 No changes 11 Feb 18 03:03 > junit.framework.AssertionFailedError: On large page size must retry. > Last runs fails with 100% probability. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7766) Ignite Queries 2: Test always failed IgniteCacheQueryNodeRestartTxSelfTest.testRestarts
[ https://issues.apache.org/jira/browse/IGNITE-7766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493235#comment-16493235 ] Evgenii Zagumennov commented on IGNITE-7766: Hi, [~dpavlov]. Ok, got it. Moved to *Patch Available* > Ignite Queries 2: Test always failed > IgniteCacheQueryNodeRestartTxSelfTest.testRestarts > --- > > Key: IGNITE-7766 > URL: https://issues.apache.org/jira/browse/IGNITE-7766 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Dmitriy Pavlov >Assignee: Evgenii Zagumennov >Priority: Major > Labels: MakeTeamcityGreenAgain > >Ignite Queries 2 > IgniteBinaryCacheQueryTestSuite2: > IgniteCacheQueryNodeRestartTxSelfTest.testRestarts (fail rate 76,1%) > IgniteCacheQueryNodeRestartTxSelfTest.testRestarts > Current failure:refs/heads/master #345No changes > 11 Feb 18 03:03 > > junit.framework.AssertionFailedError: On large page size must retry. > > Last runs fails with 100% probability. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (IGNITE-7766) Ignite Queries 2: Test always failed IgniteCacheQueryNodeRestartTxSelfTest.testRestarts
[ https://issues.apache.org/jira/browse/IGNITE-7766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgenii Zagumennov reopened IGNITE-7766: > Ignite Queries 2: Test always failed > IgniteCacheQueryNodeRestartTxSelfTest.testRestarts > --- > > Key: IGNITE-7766 > URL: https://issues.apache.org/jira/browse/IGNITE-7766 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Dmitriy Pavlov >Assignee: Evgenii Zagumennov >Priority: Major > Labels: MakeTeamcityGreenAgain > >Ignite Queries 2 > IgniteBinaryCacheQueryTestSuite2: > IgniteCacheQueryNodeRestartTxSelfTest.testRestarts (fail rate 76,1%) > IgniteCacheQueryNodeRestartTxSelfTest.testRestarts > Current failure:refs/heads/master #345No changes > 11 Feb 18 03:03 > > junit.framework.AssertionFailedError: On large page size must retry. > > Last runs fails with 100% probability. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (IGNITE-7766) Ignite Queries 2: Test always failed IgniteCacheQueryNodeRestartTxSelfTest.testRestarts
[ https://issues.apache.org/jira/browse/IGNITE-7766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgenii Zagumennov updated IGNITE-7766: --- Comment: was deleted (was: I've investigated the issue (with "git bisect"). This test started to fail after [IGNITE-7195|https://issues.apache.org/jira/browse/IGNITE-7195] was fixed. I think, the subject test (IgniteCacheQueryNodeRestartTxSelfTest.testRestarts) is not actual anymore.) > Ignite Queries 2: Test always failed > IgniteCacheQueryNodeRestartTxSelfTest.testRestarts > --- > > Key: IGNITE-7766 > URL: https://issues.apache.org/jira/browse/IGNITE-7766 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Dmitriy Pavlov >Assignee: Evgenii Zagumennov >Priority: Major > Labels: MakeTeamcityGreenAgain > >Ignite Queries 2 > IgniteBinaryCacheQueryTestSuite2: > IgniteCacheQueryNodeRestartTxSelfTest.testRestarts (fail rate 76,1%) > IgniteCacheQueryNodeRestartTxSelfTest.testRestarts > Current failure:refs/heads/master #345No changes > 11 Feb 18 03:03 > > junit.framework.AssertionFailedError: On large page size must retry. > > Last runs fails with 100% probability. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7766) Ignite Queries 2: Test always failed IgniteCacheQueryNodeRestartTxSelfTest.testRestarts
[ https://issues.apache.org/jira/browse/IGNITE-7766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16465066#comment-16465066 ] Evgenii Zagumennov commented on IGNITE-7766: I've investigated the issue (with "git bisect"). This test started to fail after [IGNITE-7195|https://issues.apache.org/jira/browse/IGNITE-7195] was fixed. I think, the subject test (IgniteCacheQueryNodeRestartTxSelfTest.testRestarts) is not actual anymore. > Ignite Queries 2: Test always failed > IgniteCacheQueryNodeRestartTxSelfTest.testRestarts > --- > > Key: IGNITE-7766 > URL: https://issues.apache.org/jira/browse/IGNITE-7766 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Dmitriy Pavlov >Assignee: Evgenii Zagumennov >Priority: Major > Labels: MakeTeamcityGreenAgain > >Ignite Queries 2 > IgniteBinaryCacheQueryTestSuite2: > IgniteCacheQueryNodeRestartTxSelfTest.testRestarts (fail rate 76,1%) > IgniteCacheQueryNodeRestartTxSelfTest.testRestarts > Current failure:refs/heads/master #345No changes > 11 Feb 18 03:03 > > junit.framework.AssertionFailedError: On large page size must retry. > > Last runs fails with 100% probability. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-7766) Ignite Queries 2: Test always failed IgniteCacheQueryNodeRestartTxSelfTest.testRestarts
[ https://issues.apache.org/jira/browse/IGNITE-7766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgenii Zagumennov reassigned IGNITE-7766: -- Assignee: Evgenii Zagumennov (was: Alexei Scherbakov) > Ignite Queries 2: Test always failed > IgniteCacheQueryNodeRestartTxSelfTest.testRestarts > --- > > Key: IGNITE-7766 > URL: https://issues.apache.org/jira/browse/IGNITE-7766 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Dmitriy Pavlov >Assignee: Evgenii Zagumennov >Priority: Major > Labels: MakeTeamcityGreenAgain > >Ignite Queries 2 > IgniteBinaryCacheQueryTestSuite2: > IgniteCacheQueryNodeRestartTxSelfTest.testRestarts (fail rate 76,1%) > IgniteCacheQueryNodeRestartTxSelfTest.testRestarts > Current failure:refs/heads/master #345No changes > 11 Feb 18 03:03 > > junit.framework.AssertionFailedError: On large page size must retry. > > Last runs fails with 100% probability. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-8185) There is deadlock when client tries to reconnect and node stop was initiated simultaneously
[
https://issues.apache.org/jira/browse/IGNITE-8185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Evgenii Zagumennov reassigned IGNITE-8185:
--
Assignee: Evgenii Zagumennov
> There is deadlock when client tries to reconnect and node stop was initiated
> simultaneously
> ---
>
> Key: IGNITE-8185
> URL: https://issues.apache.org/jira/browse/IGNITE-8185
> Project: Ignite
> Issue Type: Bug
>Reporter: Eduard Shangareev
>Assignee: Evgenii Zagumennov
>Priority: Critical
> Labels: MakeTeamcityGreenAgain
>
> Stack traces of these 2 activities which deadlock:
> {code}
> "tcp-client-disco-msg-worker-#493%client%" #7712 prio=5 os_prio=0
> tid=0x7f5e06731000 nid=0x520f waiting for monitor entry
> [0x7f5c7adeb000]
>java.lang.Thread.State: BLOCKED (on object monitor)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2519)
> - waiting to lock <0x0007a5fe6138> (a
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2511)
> at org.apache.ignite.internal.IgnitionEx.stop(IgnitionEx.java:368)
> at org.apache.ignite.Ignition.stop(Ignition.java:224)
> at org.apache.ignite.internal.IgniteKernal.close(IgniteKernal.java:3439)
> at
> org.apache.ignite.internal.IgniteKernal.onReconnected(IgniteKernal.java:3926)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:812)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery(GridDiscoveryManager.java:578)
> - locked <0x0007a5fe6358> (a java.lang.Object)
> at
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.notifyDiscovery(ClientImpl.java:2425)
> at
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.notifyDiscovery(ClientImpl.java:2404)
> at
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processNodeAddFinishedMessage(ClientImpl.java:2049)
> at
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processDiscoveryMessage(ClientImpl.java:1898)
> at
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.body(ClientImpl.java:1792)
> at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> {code}
> {code}
> "main" #1 prio=5 os_prio=0 tid=0x7f5e0400e800 nid=0x340c in Object.wait()
> [0x7f5e09fbb000]
>java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> at java.lang.Thread.join(Thread.java:1252)
> - locked <0x0007a5fe5f98> (a
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker)
> at java.lang.Thread.join(Thread.java:1326)
> at
> org.apache.ignite.internal.util.IgniteUtils.join(IgniteUtils.java:4603)
> at
> org.apache.ignite.spi.discovery.tcp.ClientImpl.spiStop(ClientImpl.java:313)
> at
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.spiStop(TcpDiscoverySpi.java:2061)
> at
> org.apache.ignite.internal.managers.GridManagerAdapter.stopSpi(GridManagerAdapter.java:330)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.stop(GridDiscoveryManager.java:1612)
> at org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:2238)
> at org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:2116)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2548)
> - locked <0x0007a5fe6138> (a
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2511)
> at org.apache.ignite.internal.IgnitionEx.stop(IgnitionEx.java:368)
> at org.apache.ignite.Ignition.stop(Ignition.java:224)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.stopGrid(GridAbstractTest.java:1027)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.stopAllGrids(GridAbstractTest.java:1067)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.stopAllGrids(GridAbstractTest.java:1048)
> at
> org.gridgain.grid.internal.processors.cache.database.IgniteDbSnapshotNotStableTopologiesTest.afterTest(IgniteDbSnapshotNotStableTopologiesTest.java:241)
> at
> org.gridgain.grid.internal.processors.cache.database.IgniteDbSnapshotNotStableTopologiesMultiNodeTest.afterTest(IgniteDbSnapshotNotStableTopologiesMultiNodeTest.java:83)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.tearDown(GridAbstractTest.java:1624)
> at
>
