[jira] [Commented] (IGNITE-9719) Extra rebalanceThreadPoolSize check on client node.
[ https://issues.apache.org/jira/browse/IGNITE-9719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16637790#comment-16637790 ] ASF GitHub Bot commented on IGNITE-9719: GitHub user luchnikovbsk opened a pull request: https://github.com/apache/ignite/pull/4911 IGNITE-9719 Extra rebalanceThreadPoolSize check on client node You can merge this pull request into a Git repository by running: $ git pull https://github.com/luchnikovbsk/ignite ignite-9719 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4911.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 #4911 commit 2ca69aeb2e2e8a8df09a5091f1395f0cf92f Author: luchnikovnsk Date: 2018-10-04T04:07:25Z IGNITE-9719 Extra rebalanceThreadPoolSize check on client node > Extra rebalanceThreadPoolSize check on client node. > --- > > Key: IGNITE-9719 > URL: https://issues.apache.org/jira/browse/IGNITE-9719 > Project: Ignite > Issue Type: Bug > Components: clients >Affects Versions: 2.6 >Reporter: Stanilovsky Evgeny >Assignee: Luchnikov Alexander >Priority: Minor > Fix For: 2.8 > > > No need to check rebalance thread pool size on client side in > IgniteKernal#ackRebalanceConfiguration method. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9719) Extra rebalanceThreadPoolSize check on client node.
[ https://issues.apache.org/jira/browse/IGNITE-9719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16637784#comment-16637784 ] ASF GitHub Bot commented on IGNITE-9719: Github user luchnikovbsk closed the pull request at: https://github.com/apache/ignite/pull/4905 > Extra rebalanceThreadPoolSize check on client node. > --- > > Key: IGNITE-9719 > URL: https://issues.apache.org/jira/browse/IGNITE-9719 > Project: Ignite > Issue Type: Bug > Components: clients >Affects Versions: 2.6 >Reporter: Stanilovsky Evgeny >Assignee: Luchnikov Alexander >Priority: Minor > Fix For: 2.8 > > > No need to check rebalance thread pool size on client side in > IgniteKernal#ackRebalanceConfiguration method. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-7460) Web console: revise inputs with step for correct validation
[ https://issues.apache.org/jira/browse/IGNITE-7460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov closed IGNITE-7460. -- > Web console: revise inputs with step for correct validation > --- > > Key: IGNITE-7460 > URL: https://issues.apache.org/jira/browse/IGNITE-7460 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Pavel Konstantinov >Priority: Minor > Fix For: 2.7 > > > For example Cluster-Data storage configuration-Default data region. > 'Eviction threshold' input become invalid if value = 0.89 due to it's step=0.5 > So you need to enter the value multiple of 0.5 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7460) Web console: revise inputs with step for correct validation
[ https://issues.apache.org/jira/browse/IGNITE-7460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16637783#comment-16637783 ] Pavel Konstantinov commented on IGNITE-7460: Re-tested. > Web console: revise inputs with step for correct validation > --- > > Key: IGNITE-7460 > URL: https://issues.apache.org/jira/browse/IGNITE-7460 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Pavel Konstantinov >Priority: Minor > Fix For: 2.7 > > > For example Cluster-Data storage configuration-Default data region. > 'Eviction threshold' input become invalid if value = 0.89 due to it's step=0.5 > So you need to enter the value multiple of 0.5 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-8842) Web console: Wrong start screen on start of demo mode
[ https://issues.apache.org/jira/browse/IGNITE-8842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov closed IGNITE-8842. -- > Web console: Wrong start screen on start of demo mode > - > > Key: IGNITE-8842 > URL: https://issues.apache.org/jira/browse/IGNITE-8842 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Vasiliy Sisko >Assignee: Pavel Konstantinov >Priority: Minor > Fix For: 2.7 > > > On start of demo mode screen with "SQL demo" notebook should be opened. > Also on "Notebooks" screen "SQL demo" notebook should be available. > On demo start "SQL demo" should be recreated if needed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8842) Web console: Wrong start screen on start of demo mode
[ https://issues.apache.org/jira/browse/IGNITE-8842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16637773#comment-16637773 ] Pavel Konstantinov commented on IGNITE-8842: Tested. > Web console: Wrong start screen on start of demo mode > - > > Key: IGNITE-8842 > URL: https://issues.apache.org/jira/browse/IGNITE-8842 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Vasiliy Sisko >Assignee: Pavel Konstantinov >Priority: Minor > Fix For: 2.7 > > > On start of demo mode screen with "SQL demo" notebook should be opened. > Also on "Notebooks" screen "SQL demo" notebook should be available. > On demo start "SQL demo" should be recreated if needed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7926) Web console: demo faled to start under java >= 9
[ https://issues.apache.org/jira/browse/IGNITE-7926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16637752#comment-16637752 ] Vasiliy Sisko commented on IGNITE-7926: --- Merged last changes from Ignite run files. > Web console: demo faled to start under java >= 9 > > > Key: IGNITE-7926 > URL: https://issues.apache.org/jira/browse/IGNITE-7926 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.4 >Reporter: Pavel Konstantinov >Assignee: Vasiliy Sisko >Priority: Minor > Fix For: 2.7 > > > We need to add support for Java 9 to web console demo. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-7926) Web console: demo faled to start under java >= 9
[ https://issues.apache.org/jira/browse/IGNITE-7926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko reassigned IGNITE-7926: - Assignee: Pavel Konstantinov (was: Vasiliy Sisko) > Web console: demo faled to start under java >= 9 > > > Key: IGNITE-7926 > URL: https://issues.apache.org/jira/browse/IGNITE-7926 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.4 >Reporter: Pavel Konstantinov >Assignee: Pavel Konstantinov >Priority: Minor > Fix For: 2.7 > > > We need to add support for Java 9 to web console demo. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-9552) Web console: add TypeScript support
[ https://issues.apache.org/jira/browse/IGNITE-9552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov closed IGNITE-9552. -- > Web console: add TypeScript support > --- > > Key: IGNITE-9552 > URL: https://issues.apache.org/jira/browse/IGNITE-9552 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Ilya Borisov >Assignee: Pavel Konstantinov >Priority: Minor > Fix For: 2.8 > > Original Estimate: 48h > Time Spent: 3.5h > Remaining Estimate: 13.75h > > What to do: > 1. ✔ Add TypeScript preset to babel config. > 2. ✔ Update webpack configs to load .ts files with babel-loader. > 3. ✔ Make sure eslint lint .ts files -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9552) Web console: add TypeScript support
[ https://issues.apache.org/jira/browse/IGNITE-9552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16637750#comment-16637750 ] Pavel Konstantinov commented on IGNITE-9552: Done. > Web console: add TypeScript support > --- > > Key: IGNITE-9552 > URL: https://issues.apache.org/jira/browse/IGNITE-9552 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Ilya Borisov >Assignee: Pavel Konstantinov >Priority: Minor > Fix For: 2.8 > > Original Estimate: 48h > Time Spent: 3.5h > Remaining Estimate: 13.75h > > What to do: > 1. ✔ Add TypeScript preset to babel config. > 2. ✔ Update webpack configs to load .ts files with babel-loader. > 3. ✔ Make sure eslint lint .ts files -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9609) Web console: update to AngularJS 1.7.4
[ https://issues.apache.org/jira/browse/IGNITE-9609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16637747#comment-16637747 ] Pavel Konstantinov commented on IGNITE-9609: Re-tested. > Web console: update to AngularJS 1.7.4 > -- > > Key: IGNITE-9609 > URL: https://issues.apache.org/jira/browse/IGNITE-9609 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Ilya Borisov >Assignee: Pavel Konstantinov >Priority: Minor > Fix For: 2.7 > > Time Spent: 56m > Remaining Estimate: 0h > > Let's update package-.json to use AngularJS 1.7.4, the 1.7.3 release > introduced some interesting new feature we might use (like extra form methods > and arbitrary event/property bindings). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-9609) Web console: update to AngularJS 1.7.4
[ https://issues.apache.org/jira/browse/IGNITE-9609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov closed IGNITE-9609. -- > Web console: update to AngularJS 1.7.4 > -- > > Key: IGNITE-9609 > URL: https://issues.apache.org/jira/browse/IGNITE-9609 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Ilya Borisov >Assignee: Pavel Konstantinov >Priority: Minor > Fix For: 2.7 > > Time Spent: 56m > Remaining Estimate: 0h > > Let's update package-.json to use AngularJS 1.7.4, the 1.7.3 release > introduced some interesting new feature we might use (like extra form methods > and arbitrary event/property bindings). -- 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=16637601#comment-16637601
]
Roman Shtykh commented on IGNITE-6784:
--
[~pgarg] when you issue "activate/deactivate," you just issue the command.
Hence `"activate started"`
It's not instant, and to check the topology status you can issue `currentstate`.
> 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: Prachi Garg
>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] [Comment Edited] (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=16637528#comment-16637528
]
Prachi Garg edited comment on IGNITE-6784 at 10/3/18 9:39 PM:
--
[~roman_s], the response from "activate" command is
{"successStatus":0,"error":null,"sessionToken":null,"response":"activate
started"}
Here, does "activate started" mean that the process to activate the cluster is
started, or does it mean that the cluster is now active?
Also, the response from "currentstate" command is
{"successStatus":0,"error":null,"sessionToken":null,"response":true}
This response does not give me much information. I think instead of
"response":true/false, it should be- "response":active / inactive based on
the state of the cluster.
was (Author: pgarg):
[~roman_s], the response from "activate" command is
{"successStatus":0,"error":null,"sessionToken":null,"response":"activate
started"}
Here, does "activate started" mean that the process to activate the cluster is
started, or does it mean that the cluster is now active?
> 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: Prachi Garg
>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=16637528#comment-16637528
]
Prachi Garg commented on IGNITE-6784:
-
[~roman_s], the response from "activate" command is
{"successStatus":0,"error":null,"sessionToken":null,"response":"activate
started"}
Here, does "activate started" mean that the process to activate the cluster is
started, or does it mean that the cluster is now active?
> 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: Prachi Garg
>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-9298) control.sh does not support SSL (org.apache.ignite.internal.commandline.CommandHandler)
[ https://issues.apache.org/jira/browse/IGNITE-9298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16637510#comment-16637510 ] Dmitriy Pavlov commented on IGNITE-9298: Hi [~vozerov], I wanted to ask the same, but you were first :) [~deviljelly] I would like you could continue with the fix, so would you like to contribute tests? Or if you would like we can ask Alex P to finish this ticket? > control.sh does not support SSL > (org.apache.ignite.internal.commandline.CommandHandler) > --- > > Key: IGNITE-9298 > URL: https://issues.apache.org/jira/browse/IGNITE-9298 > Project: Ignite > Issue Type: Bug > Components: clients >Affects Versions: 2.6 >Reporter: Paul Anderson >Assignee: Paul Anderson >Priority: Major > Fix For: 2.7 > > Attachments: Arguments.patch, CommandHandler.patch > > > We required SSL on the connector port and to use control.sh to work with the > baseline configuration. > This morning I added support, see attached patches against 2.6.0 for > org/apache/ignite/internal/commandline/CommandHandler.java > org/apache/ignite/internal/commandline/Arguments.java > No tests, no docs. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9390) MVCC: add MVCC support to .NET configuration.
[ https://issues.apache.org/jira/browse/IGNITE-9390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16637504#comment-16637504 ] ASF GitHub Bot commented on IGNITE-9390: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4910 > MVCC: add MVCC support to .NET configuration. > - > > Key: IGNITE-9390 > URL: https://issues.apache.org/jira/browse/IGNITE-9390 > Project: Ignite > Issue Type: Task > Components: mvcc, platforms >Reporter: Andrew Mashenkov >Assignee: Vladimir Ozerov >Priority: Blocker > Fix For: 2.7 > > > We should make MVCC configurable from .NET client. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9390) MVCC: add MVCC support to .NET configuration.
[ https://issues.apache.org/jira/browse/IGNITE-9390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16637505#comment-16637505 ] Dmitriy Pavlov commented on IGNITE-9390: Additional fix 95b6597638a5a6b0348d6919507db3f534841eaa merged to master and cherry-picked to 2.7 beb7eb0b26b647c221157e0f734202981eb47ff5. [~rkondakov] thank you for contribution. > MVCC: add MVCC support to .NET configuration. > - > > Key: IGNITE-9390 > URL: https://issues.apache.org/jira/browse/IGNITE-9390 > Project: Ignite > Issue Type: Task > Components: mvcc, platforms >Reporter: Andrew Mashenkov >Assignee: Vladimir Ozerov >Priority: Blocker > Fix For: 2.7 > > > We should make MVCC configurable from .NET client. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9390) MVCC: add MVCC support to .NET configuration.
[ https://issues.apache.org/jira/browse/IGNITE-9390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16637410#comment-16637410 ] Roman Kondakov commented on IGNITE-9390: [~vozerov], [~dpavlov], I've made a [PR|https://github.com/apache/ignite/pull/4910] the fix of these tests. Fix is trivial - these tests didn't take into account one extra memory region for TxLog. [Tests are OK.|https://ci.ignite.apache.org/viewLog.html?buildId=1999429=queuedBuildOverviewTab] Please review and merge if needed. > MVCC: add MVCC support to .NET configuration. > - > > Key: IGNITE-9390 > URL: https://issues.apache.org/jira/browse/IGNITE-9390 > Project: Ignite > Issue Type: Task > Components: mvcc, platforms >Reporter: Andrew Mashenkov >Assignee: Vladimir Ozerov >Priority: Blocker > Fix For: 2.7 > > > We should make MVCC configurable from .NET client. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9749) Assertion error in JdbcThinTransactionsServerAutoCommitComplexSelfTest leading to JDBC MVCC suite hang
[
https://issues.apache.org/jira/browse/IGNITE-9749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16637383#comment-16637383
]
Vladimir Ozerov commented on IGNITE-9749:
-
First of all, we should not continue our enlist loop in exchange thread. Next,
we observe that returned list of affintiy nodes doesn't have local node as
primary. As exchange was in progress, most probably some node was added or
removed, and TX topology version was not updated accordingly.
> Assertion error in JdbcThinTransactionsServerAutoCommitComplexSelfTest
> leading to JDBC MVCC suite hang
> --
>
> Key: IGNITE-9749
> URL: https://issues.apache.org/jira/browse/IGNITE-9749
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Alexey Goncharuk
>Priority: Critical
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.7
>
>
> The following assertion can be observed in master
> {code}
> [10:34:12]W: [org.apache.ignite:ignite-clients] [07:34:12] (err)
> Failed to notify listener:
> o.a.i.i.util.future.GridEmbeddedFuture$2...@4e56da7bjava.lang.AssertionError:
> localNode = 14353600-ea43-42ae-bf7c-4b467800, dhtNodes =
> [TcpDiscoveryNode [id=04134719-3eb1-4969-99dc-f520f982, addrs=ArrayList
> [127.0.0.1], sockAddrs=HashSet [/127.0.0.1:47501], discPort=47501, order=3,
> intOrder=3, lastExchangeTime=1538379249752, loc=false,
> ver=2.7.0#20181001-sha1:9ab8ebd7, isClient=false]]
> [10:34:12]W: [org.apache.ignite:ignite-clients] at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxAbstractEnlistFuture.backupNodes(GridDhtTxAbstractEnlistFuture.java:867)
> [10:34:12]W: [org.apache.ignite:ignite-clients] at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxAbstractEnlistFuture.addToBatch(GridDhtTxAbstractEnlistFuture.java:627)
> [10:34:12]W: [org.apache.ignite:ignite-clients] at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxAbstractEnlistFuture.processEntry(GridDhtTxAbstractEnlistFuture.java:614)
> [10:34:12]W: [org.apache.ignite:ignite-clients] at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxAbstractEnlistFuture.continueLoop(GridDhtTxAbstractEnlistFuture.java:501)
> [10:34:12]W: [org.apache.ignite:ignite-clients] at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxAbstractEnlistFuture.init(GridDhtTxAbstractEnlistFuture.java:363)
> [10:34:12]W: [org.apache.ignite:ignite-clients] at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxQueryEnlistFuture.map(GridNearTxQueryEnlistFuture.java:212)
> [10:34:12]W: [org.apache.ignite:ignite-clients] at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxAbstractEnlistFuture.mapOnTopology(GridNearTxAbstractEnlistFuture.java:332)
> [10:34:12] : [Step 4/5] [2018-10-01 07:34:12,762][INFO
> ][exchange-worker-#2510%thin.JdbcThinTransactionsServerAutoCommitComplexSelfTest2%][GridCachePartitionExchangeManager]
> Skipping rebalancing (nothing scheduled) [top=AffinityTopologyVersion
> [topVer=4, minorTopVer=16], force=false, evt=DISCOVERY_CUSTOM_EVT,
> node=14353600-ea43-42ae-bf7c-4b467800]
> [10:34:12]W: [org.apache.ignite:ignite-clients] at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxAbstractEnlistFuture.access$000(GridNearTxAbstractEnlistFuture.java:56)
> [10:34:12]W: [org.apache.ignite:ignite-clients] at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxAbstractEnlistFuture$2.apply(GridNearTxAbstractEnlistFuture.java:340)
> [10:34:12]W: [org.apache.ignite:ignite-clients] at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxAbstractEnlistFuture$2.apply(GridNearTxAbstractEnlistFuture.java:335)
> [10:34:12]W: [org.apache.ignite:ignite-clients] at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:385)
> [10:34:12]W: [org.apache.ignite:ignite-clients] at
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblock(GridFutureAdapter.java:349)
> [10:34:12]W: [org.apache.ignite:ignite-clients] at
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblockAll(GridFutureAdapter.java:337)
> [10:34:12]W: [org.apache.ignite:ignite-clients] at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:497)
> [10:34:12]W: [org.apache.ignite:ignite-clients] at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:476)
> [10:34:12]W:
[jira] [Assigned] (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:all-tabpanel ] Vladimir Ozerov reassigned IGNITE-9622: --- Assignee: (was: Vladimir Ozerov) > 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 >Priority: Major > Fix For: 2.7 > > > 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] [Commented] (IGNITE-9676) Ignite as storage in Spring Session
[ https://issues.apache.org/jira/browse/IGNITE-9676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16637379#comment-16637379 ] Vladimir Ozerov commented on IGNITE-9676: - [~antkr], what is current state of the ticket? > Ignite as storage in Spring Session > --- > > Key: IGNITE-9676 > URL: https://issues.apache.org/jira/browse/IGNITE-9676 > Project: Ignite > Issue Type: New Feature > Components: spring >Reporter: Anton Kurbanov >Assignee: Anton Kurbanov >Priority: Minor > Fix For: 2.7 > > > Implement repository backed with Ignite for sessions clustering with Spring > Session. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (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:all-tabpanel ] Vladimir Ozerov reassigned IGNITE-9622: --- Assignee: Vladimir Ozerov > 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: Vladimir Ozerov >Priority: Major > Fix For: 2.7 > > > 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-9676) Ignite as storage in Spring Session
[ https://issues.apache.org/jira/browse/IGNITE-9676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-9676: Component/s: spring > Ignite as storage in Spring Session > --- > > Key: IGNITE-9676 > URL: https://issues.apache.org/jira/browse/IGNITE-9676 > Project: Ignite > Issue Type: New Feature > Components: spring >Reporter: Anton Kurbanov >Assignee: Anton Kurbanov >Priority: Minor > Fix For: 2.7 > > > Implement repository backed with Ignite for sessions clustering with Spring > Session. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8518) Web Console: Auto focus "Confirm" button in Confirmation dialog
[ https://issues.apache.org/jira/browse/IGNITE-8518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-8518: Fix Version/s: (was: 2.7) 2.8 > Web Console: Auto focus "Confirm" button in Confirmation dialog > --- > > Key: IGNITE-8518 > URL: https://issues.apache.org/jira/browse/IGNITE-8518 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Pavel Konstantinov >Priority: Major > Fix For: 2.8 > > > This will allow to confirm from keyboard. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9298) control.sh does not support SSL (org.apache.ignite.internal.commandline.CommandHandler)
[ https://issues.apache.org/jira/browse/IGNITE-9298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16637374#comment-16637374 ] Vladimir Ozerov commented on IGNITE-9298: - [~ilyak], [~dpavlov], [~deviljelly], Igniters, Any new on this ticket? Looks like acitivies are stopped. Should we move it to AI 2.8? > control.sh does not support SSL > (org.apache.ignite.internal.commandline.CommandHandler) > --- > > Key: IGNITE-9298 > URL: https://issues.apache.org/jira/browse/IGNITE-9298 > Project: Ignite > Issue Type: Bug > Components: clients >Affects Versions: 2.6 >Reporter: Paul Anderson >Assignee: Paul Anderson >Priority: Major > Fix For: 2.7 > > Attachments: Arguments.patch, CommandHandler.patch > > > We required SSL on the connector port and to use control.sh to work with the > baseline configuration. > This morning I added support, see attached patches against 2.6.0 for > org/apache/ignite/internal/commandline/CommandHandler.java > org/apache/ignite/internal/commandline/Arguments.java > No tests, no docs. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8518) Web Console: Auto focus "Confirm" button in Confirmation dialog
[ https://issues.apache.org/jira/browse/IGNITE-8518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16637377#comment-16637377 ] Vladimir Ozerov commented on IGNITE-8518: - Moving to AI 2.8 scope due to long inactivity. > Web Console: Auto focus "Confirm" button in Confirmation dialog > --- > > Key: IGNITE-8518 > URL: https://issues.apache.org/jira/browse/IGNITE-8518 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Pavel Konstantinov >Priority: Major > Fix For: 2.7 > > > This will allow to confirm from keyboard. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9228) Spark SQL Table Schema Specification
[ https://issues.apache.org/jira/browse/IGNITE-9228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16637372#comment-16637372 ] Vladimir Ozerov commented on IGNITE-9228: - [~stuartmacd], [~NIzhikov], [~dpavlov], Igniters, Any news on this ticket? Should we merge it or move to AI 2.8? > Spark SQL Table Schema Specification > > > Key: IGNITE-9228 > URL: https://issues.apache.org/jira/browse/IGNITE-9228 > Project: Ignite > Issue Type: Improvement > Components: spark >Affects Versions: 2.6 >Reporter: Stuart Macdonald >Assignee: Stuart Macdonald >Priority: Major > Fix For: 2.7 > > > The Ignite Spark SQL interface currently takes just “table name” as a > parameter which it uses to supply a Spark dataset with data from the > underlying Ignite SQL table with that name. > To do this it loops through each cache and finds the first one with the > given table name [1]. This causes issues if there are multiple tables > registered in different schema with the same table name as you can only > access one of those from Spark. We could either: > 1. Pass an extra parameter through the Ignite Spark data source which > optionally specifies the schema name. > 2. Support namespacing in the existing table name parameter, ie > “schemaName.tableName” > [1 > ]https://github.com/apache/ignite/blob/ca973ad99c6112160a305df05be9458e29f88307/modules/spark/src/main/scala/org/apache/ignite/spark/impl/package.scala#L119 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9082) Throwing checked exception during tx commit without node stopping leads to data corruption
[ https://issues.apache.org/jira/browse/IGNITE-9082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16637370#comment-16637370 ] Vladimir Ozerov commented on IGNITE-9082: - [~ascherbakov], [~Jokser], [~agoncharuk], Igniters, Do we have any progress with this ticket? Should we move it to AI 2.8? > Throwing checked exception during tx commit without node stopping leads to > data corruption > -- > > Key: IGNITE-9082 > URL: https://issues.apache.org/jira/browse/IGNITE-9082 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.4, 2.5, 2.6 >Reporter: Pavel Kovalenko >Assignee: Alexei Scherbakov >Priority: Major > Fix For: 2.7 > > > If we get checked exception during tx commit on a primary node and this > exception is not supposed to be handled as NodeStopping OR doesn't lead to > node stop using Failure Handler, in this case, we may get data loss on a node > which is a backup node for this tx. > Possible solution: > If we get any checked or unchecked exception during tx commit we should stop > this node after that to prevent further data loss. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9784) Performance drop on sql yardstick benchmarks
[ https://issues.apache.org/jira/browse/IGNITE-9784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-9784: Fix Version/s: 2.7 > Performance drop on sql yardstick benchmarks > > > Key: IGNITE-9784 > URL: https://issues.apache.org/jira/browse/IGNITE-9784 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.7 >Reporter: Ilya Suntsov >Priority: Blocker > Fix For: 2.7 > > Attachments: Screen Shot 2018-10-03 at 4.52.22 PM.png > > > Please take a look at the attachment. > Grid configuration: > * 4 servers / 8 clients > * java 8 > * 64 threads, 60s warmup, 180s duration -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9722) MVCC: Test CacheMvccTransactionTest.testMvccCoordinatorChangeSimple fails.
[ https://issues.apache.org/jira/browse/IGNITE-9722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16637360#comment-16637360 ] ASF GitHub Bot commented on IGNITE-9722: Github user devozerov closed the pull request at: https://github.com/apache/ignite/pull/4903 > MVCC: Test CacheMvccTransactionTest.testMvccCoordinatorChangeSimple fails. > -- > > Key: IGNITE-9722 > URL: https://issues.apache.org/jira/browse/IGNITE-9722 > Project: Ignite > Issue Type: Bug > Components: cache, mvcc >Reporter: Andrew Mashenkov >Assignee: Vladimir Ozerov >Priority: Critical > Fix For: 2.7 > > > The test make transactional putAll() and then check data with Scan query and > getAll(). > ScanQuery can miss some results on unstable topology which is expected as it > doesn't lock topology. > But getAll() can unexpectedly return stale results. > To reproduce the issue, one can change read mode SCAN->GET (passed to > checkAndGetAll() call) in checkPutGet() method. > > It looks like rebalance can overwrite local backup entries or remap is broken > and we read local partition in moving state. Disabling fastLocGet in > GridPartitionedGetFuture.map() resolves the issue. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9390) MVCC: add MVCC support to .NET configuration.
[ https://issues.apache.org/jira/browse/IGNITE-9390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16637334#comment-16637334 ] ASF GitHub Bot commented on IGNITE-9390: GitHub user rkondakov opened a pull request: https://github.com/apache/ignite/pull/4910 IGNITE-9390: Fixed memory metrics tests. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9390 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4910.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 #4910 commit dce38c4a2bd1a075ae78ebe59e8b43bfb50f3306 Author: rkondakov Date: 2018-10-03T18:17:57Z IGNITE-9390: Fixed memory metrics tests. > MVCC: add MVCC support to .NET configuration. > - > > Key: IGNITE-9390 > URL: https://issues.apache.org/jira/browse/IGNITE-9390 > Project: Ignite > Issue Type: Task > Components: mvcc, platforms >Reporter: Andrew Mashenkov >Assignee: Vladimir Ozerov >Priority: Blocker > Fix For: 2.7 > > > We should make MVCC configurable from .NET client. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9449) Lazy unmarshalling of discovery events in TcpDiscovery
[
https://issues.apache.org/jira/browse/IGNITE-9449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16637331#comment-16637331
]
Nikolay Izhikov commented on IGNITE-9449:
-
Hello, [~Jokser].
I want to investigate this issue. Can you help me with it?
If I understand you correctly, you described following a piece of code
ServerImpl line 3234
{code:java}
spi.writeToSocket(sock, out, pendingMsg, timeoutHelper.nextTimeoutChunk(
spi.getSocketTimeout()));
{code}
which internally serialize `pendingMsg` with a configured marshaller.
Do you have some numbers showing an impact of this marshalling?
Do you have a benchmark or similar that we can use as an indicator of an issue?
> Lazy unmarshalling of discovery events in TcpDiscovery
> --
>
> Key: IGNITE-9449
> URL: https://issues.apache.org/jira/browse/IGNITE-9449
> Project: Ignite
> Issue Type: Improvement
> Components: cache
>Affects Versions: 2.4, 2.5, 2.6
>Reporter: Pavel Kovalenko
>Assignee: Nikolay Izhikov
>Priority: Major
> Fix For: 2.8
>
>
> Currently disco-msg-worker thread spend major part of time on disocvery
> message unmarshalling before send it to the next node. In most cases this is
> unnecessary and message can be send immediately after receiving and notyfing
> discovery-event-worker.
> Responsibility of unmarshalling should moved to discovery-event-worker thread
> and this improvement will significantly reduce latency of sending custom
> messages across ring.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9775) IgniteCache.lostPartitions() is empty with single node remaining in the cluster
[ https://issues.apache.org/jira/browse/IGNITE-9775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Novichenok updated IGNITE-9775: - Summary: IgniteCache.lostPartitions() is empty with single node remaining in the cluster (was: Cache.lostPartitions() is empty with single node remaining in the cluster) > IgniteCache.lostPartitions() is empty with single node remaining in the > cluster > --- > > Key: IGNITE-9775 > URL: https://issues.apache.org/jira/browse/IGNITE-9775 > Project: Ignite > Issue Type: Bug > Components: persistence >Affects Versions: 2.5, 2.6 >Reporter: Roman Novichenok >Priority: Major > > When only one node remains in the cluster, cache.lostPartitions() is empty. > Pull request: [https://github.com/novicr/ignite/pull/1] contains a test to > show the issue. > To reproduce: > # Turn on native persistence > # Create partitioned cache with 1 backup, sync replication, READ_ONLY_SAFE > loss policy > # Start 4 nodes > # Persist enough data to make sure all nodes participate > # Stop 3 nodes > Expected behavior: > * cache.lostPartitions().size() > 0 > Actual: > * cache.lostPartitions().size() == 0 > > Note, if more than one node is operational, the lostPartitions() will contain > some number of partitions. Don't know if the list it contains is complete. > > The issue seems to be in the > GridDhtPartitionTopologyImpl.detectLostPartitions() > With a single node left in the cluster, the coordinator node is also the only > one that contains any data, but localNode is skipped when examining node2Part > maps to look for any partitions that should be marked LOST. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9652) Fix `Missorted modifiers' according inspections profile`
[
https://issues.apache.org/jira/browse/IGNITE-9652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16637282#comment-16637282
]
Ignite TC Bot commented on IGNITE-9652:
---
{panel:title=No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity Run
All|http://ci.ignite.apache.org/viewLog.html?buildId=1995776buildTypeId=IgniteTests24Java8_RunAll]
> Fix `Missorted modifiers' according inspections profile`
>
>
> Key: IGNITE-9652
> URL: https://issues.apache.org/jira/browse/IGNITE-9652
> Project: Ignite
> Issue Type: Bug
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Minor
> Labels: inspections
> Fix For: 2.8
>
>
> New `Code Inspections` profile can be found
> \idea\ignite_inspections.xml.
> We need to fix rule `Missorted modifiers` in ignite-core module.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9752) Fix ODBC documentation
[ https://issues.apache.org/jira/browse/IGNITE-9752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16637274#comment-16637274 ] Prachi Garg commented on IGNITE-9752: - [~dmagda], [~qvad], What needs to be done here? Please provide some more information. > Fix ODBC documentation > -- > > Key: IGNITE-9752 > URL: https://issues.apache.org/jira/browse/IGNITE-9752 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Dmitry Sherstobitov >Assignee: Prachi Garg >Priority: Blocker > Fix For: 2.7 > > Attachments: image-2018-10-01-17-12-21-555.png > > > See screen shot. > There is no matching between default values and values in example > host in default - 0.0.0.0 > port in default - 10800 > host in example 127.0.0.1 (does it visible inside machine?) > port - 12345 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9756) [Test Failed] IgniteCacheIncrementTxTest.testIncrementTxTopologyChange2 fails sometimes in master.
[
https://issues.apache.org/jira/browse/IGNITE-9756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin updated IGNITE-9756:
-
Description:
IgniteCacheIncrementTxTest.testIncrementTxTopologyChange2 fails sometimes in
master with timeout.
Example of such failure:
[https://ci.ignite.apache.org/viewLog.html?buildId=1977579=buildResultsDiv=IgniteTests24Java8_Cache2#testNameId-613377372188362920]
Typical log output:
{noformat}
[2018-10-03 19:40:32,654][INFO
][sys-#438%cache.IgniteCacheIncrementTxTest1%][GridDhtPartitionDemander]
Started rebalance routine [default,
supplier=67fdbd60-24fe-4810-a6a6-41a949b3, topic=0, fullPartitions=[28, 31,
33, 40, 43, 56, 61, 63, 70, 86, 93, 107, 115, 129, 149, 153, 167, 187, 207,
215, 218, 224, 247, 279, 284, 290, 329, 332, 342, 373, 377, 383, 385-386, 423,
435, 469, 478, 494, 515, 525, 528, 537, 565, 603, 607, 610, 624, 654, 686, 707,
718, 738, 741, 746, 766, 775, 777, 797, 807, 809, 814, 822, 849, 856, 872, 876,
909, 911, 914, 925, 940, 943, 962, 983, 991, 1005, 1014], histPartitions=[]]
[2018-10-03 19:40:32,654][INFO
][sys-#175%cache.IgniteCacheIncrementTxTest0%][GridDhtPartitionSupplier]
Finished supplying rebalancing [grp=default,
demander=688062dd-508d-4ebc-9458-a48e1ba2, topVer=AffinityTopologyVersion
[topVer=45, minorTopVer=0], topic=0]
[2018-10-03 19:40:32,654][INFO
][sys-#185%cache.IgniteCacheIncrementTxTest3%][GridDhtPartitionSupplier]
Finished supplying rebalancing [grp=default,
demander=3f09a855-390b-40ce-b3e0-8b411db1, topVer=AffinityTopologyVersion
[topVer=45, minorTopVer=0], topic=0]
[2018-10-03 19:40:32,654][INFO
][sys-#179%cache.IgniteCacheIncrementTxTest0%][GridDhtPartitionSupplier]
Finished supplying rebalancing [grp=default,
demander=67fdbd60-24fe-4810-a6a6-41a949b3, topVer=AffinityTopologyVersion
[topVer=45, minorTopVer=0], topic=0]
[2018-10-03 19:40:32,654][INFO
][sys-#234%cache.IgniteCacheIncrementTxTest1%][GridDhtPartitionDemander]
Completed rebalancing [grp=default,
supplier=67fdbd60-24fe-4810-a6a6-41a949b3, topVer=AffinityTopologyVersion
[topVer=45, minorTopVer=0], progress=1/2, time=0 ms]
[2018-10-03 19:40:32,654][INFO
][sys-#237%cache.IgniteCacheIncrementTxTest3%][GridDhtPartitionDemander]
Completed (final) rebalancing [grp=default,
supplier=4b3e5c6e-cec4-4fb6-b1b2-47fd7190, topVer=AffinityTopologyVersion
[topVer=45, minorTopVer=0], progress=2/2, time=0 ms]
[2018-10-03 19:40:32,654][INFO
][sys-#237%cache.IgniteCacheIncrementTxTest3%][GridDhtPartitionDemander]
Completed rebalance future: RebalanceFuture [grp=CacheGroupContext
[grp=default], topVer=AffinityTopologyVersion [topVer=45, minorTopVer=0],
rebalanceId=96, routines=2]
[2018-10-03 19:40:32,655][INFO
][sys-#162%cache.IgniteCacheIncrementTxTest2%][GridDhtPartitionDemander]
Completed (final) rebalancing [grp=default,
supplier=4b3e5c6e-cec4-4fb6-b1b2-47fd7190, topVer=AffinityTopologyVersion
[topVer=45, minorTopVer=0], progress=2/2, time=0 ms]
[2018-10-03 19:40:32,655][INFO
][sys-#162%cache.IgniteCacheIncrementTxTest2%][GridDhtPartitionDemander]
Completed rebalance future: RebalanceFuture [grp=CacheGroupContext
[grp=default], topVer=AffinityTopologyVersion [topVer=45, minorTopVer=0],
rebalanceId=96, routines=2]
[2018-10-03 19:40:33,260][INFO
][exchange-worker-#38%cache.IgniteCacheIncrementTxTest0%][GridCachePartitionExchangeManager]
Skipping rebalancing (nothing scheduled) [top=AffinityTopologyVersion
[topVer=45, minorTopVer=0], force=true, evt=NODE_LEFT,
node=f675cf49-5db3-45b3-83fb-7a778849]
[2018-10-03 19:40:33,261][INFO
][exchange-worker-#151%cache.IgniteCacheIncrementTxTest1%][GridDhtPartitionDemander]
Cancelled rebalancing from all nodes [grp=default,
topVer=AffinityTopologyVersion [topVer=45, minorTopVer=0]]
[2018-10-03 19:40:33,261][INFO
][exchange-worker-#151%cache.IgniteCacheIncrementTxTest1%][GridDhtPartitionDemander]
Completed rebalance future: RebalanceFuture [grp=CacheGroupContext
[grp=default], topVer=AffinityTopologyVersion [topVer=45, minorTopVer=0],
rebalanceId=96, routines=2]
[2018-10-03 19:40:33,261][INFO
][exchange-worker-#151%cache.IgniteCacheIncrementTxTest1%][GridCachePartitionExchangeManager]
Rebalancing scheduled [order=[default], top=AffinityTopologyVersion
[topVer=45, minorTopVer=0], force=true, evt=NODE_LEFT,
node=f675cf49-5db3-45b3-83fb-7a778849]
[2018-10-03 19:40:33,262][INFO
][exchange-worker-#151%cache.IgniteCacheIncrementTxTest1%][GridDhtPartitionDemander]
Prepared rebalancing [grp=default, mode=ASYNC,
supplier=4b3e5c6e-cec4-4fb6-b1b2-47fd7190, partitionsCount=97,
topVer=AffinityTopologyVersion [topVer=45, minorTopVer=0], parallelism=1]
[2018-10-03 19:40:33,899][INFO
][sys-#155%cache.IgniteCacheIncrementTxTest0%][GridCachePartitionExchangeManager]
Full Message creating for AffinityTopologyVersion [topVer=45, minorTopVer=0]
performed in 1 ms.
[2018-10-03 19:40:33,903][INFO
[jira] [Updated] (IGNITE-9756) [Test Failed] IgniteCacheIncrementTxTest.testIncrementTxTopologyChange2 fails sometimes in master.
[
https://issues.apache.org/jira/browse/IGNITE-9756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin updated IGNITE-9756:
-
Description:
IgniteCacheIncrementTxTest.testIncrementTxTopologyChange2 fails sometimes in
master with timeout.
Example of such failure:
[https://ci.ignite.apache.org/viewLog.html?buildId=1977579=buildResultsDiv=IgniteTests24Java8_Cache2#testNameId-613377372188362920]
Typical log output:
{noformat}
[2018-10-03 19:40:32,654][INFO
][sys-#438%cache.IgniteCacheIncrementTxTest1%][GridDhtPartitionDemander]
Started rebalance routine [default,
supplier=67fdbd60-24fe-4810-a6a6-41a949b3, topic=0, fullPartitions=[28, 31,
33, 40, 43, 56, 61, 63, 70, 86, 93, 107, 115, 129, 149, 153, 167, 187, 207,
215, 218, 224, 247, 279, 284, 290, 329, 332, 342, 373, 377, 383, 385-386, 423,
435, 469, 478, 494, 515, 525, 528, 537, 565, 603, 607, 610, 624, 654, 686, 707,
718, 738, 741, 746, 766, 775, 777, 797, 807, 809, 814, 822, 849, 856, 872, 876,
909, 911, 914, 925, 940, 943, 962, 983, 991, 1005, 1014], histPartitions=[]]
[2018-10-03 19:40:32,654][INFO
][sys-#175%cache.IgniteCacheIncrementTxTest0%][GridDhtPartitionSupplier]
Finished supplying rebalancing [grp=default,
demander=688062dd-508d-4ebc-9458-a48e1ba2, topVer=AffinityTopologyVersion
[topVer=45, minorTopVer=0], topic=0]
[2018-10-03 19:40:32,654][INFO
][sys-#185%cache.IgniteCacheIncrementTxTest3%][GridDhtPartitionSupplier]
Finished supplying rebalancing [grp=default,
demander=3f09a855-390b-40ce-b3e0-8b411db1, topVer=AffinityTopologyVersion
[topVer=45, minorTopVer=0], topic=0]
[2018-10-03 19:40:32,654][INFO
][sys-#179%cache.IgniteCacheIncrementTxTest0%][GridDhtPartitionSupplier]
Finished supplying rebalancing [grp=default,
demander=67fdbd60-24fe-4810-a6a6-41a949b3, topVer=AffinityTopologyVersion
[topVer=45, minorTopVer=0], topic=0]
[2018-10-03 19:40:32,654][INFO
][sys-#234%cache.IgniteCacheIncrementTxTest1%][GridDhtPartitionDemander]
Completed rebalancing [grp=default,
supplier=67fdbd60-24fe-4810-a6a6-41a949b3, topVer=AffinityTopologyVersion
[topVer=45, minorTopVer=0], progress=1/2, time=0 ms]
[2018-10-03 19:40:32,654][INFO
][sys-#237%cache.IgniteCacheIncrementTxTest3%][GridDhtPartitionDemander]
Completed (final) rebalancing [grp=default,
supplier=4b3e5c6e-cec4-4fb6-b1b2-47fd7190, topVer=AffinityTopologyVersion
[topVer=45, minorTopVer=0], progress=2/2, time=0 ms]
[2018-10-03 19:40:32,654][INFO
][sys-#237%cache.IgniteCacheIncrementTxTest3%][GridDhtPartitionDemander]
Completed rebalance future: RebalanceFuture [grp=CacheGroupContext
[grp=default], topVer=AffinityTopologyVersion [topVer=45, minorTopVer=0],
rebalanceId=96, routines=2]
[2018-10-03 19:40:32,655][INFO
][sys-#162%cache.IgniteCacheIncrementTxTest2%][GridDhtPartitionDemander]
Completed (final) rebalancing [grp=default,
supplier=4b3e5c6e-cec4-4fb6-b1b2-47fd7190, topVer=AffinityTopologyVersion
[topVer=45, minorTopVer=0], progress=2/2, time=0 ms]
[2018-10-03 19:40:32,655][INFO
][sys-#162%cache.IgniteCacheIncrementTxTest2%][GridDhtPartitionDemander]
Completed rebalance future: RebalanceFuture [grp=CacheGroupContext
[grp=default], topVer=AffinityTopologyVersion [topVer=45, minorTopVer=0],
rebalanceId=96, routines=2]
[2018-10-03 19:40:33,260][INFO
][exchange-worker-#38%cache.IgniteCacheIncrementTxTest0%][GridCachePartitionExchangeManager]
Skipping rebalancing (nothing scheduled) [top=AffinityTopologyVersion
[topVer=45, minorTopVer=0], force=true, evt=NODE_LEFT,
node=f675cf49-5db3-45b3-83fb-7a778849]
[2018-10-03 19:40:33,261][INFO
][exchange-worker-#151%cache.IgniteCacheIncrementTxTest1%][GridDhtPartitionDemander]
Cancelled rebalancing from all nodes [grp=default,
topVer=AffinityTopologyVersion [topVer=45, minorTopVer=0]]
[2018-10-03 19:40:33,261][INFO
][exchange-worker-#151%cache.IgniteCacheIncrementTxTest1%][GridDhtPartitionDemander]
Completed rebalance future: RebalanceFuture [grp=CacheGroupContext
[grp=default], topVer=AffinityTopologyVersion [topVer=45, minorTopVer=0],
rebalanceId=96, routines=2]
[2018-10-03 19:40:33,261][INFO
][exchange-worker-#151%cache.IgniteCacheIncrementTxTest1%][GridCachePartitionExchangeManager]
Rebalancing scheduled [order=[default], top=AffinityTopologyVersion
[topVer=45, minorTopVer=0], force=true, evt=NODE_LEFT,
node=f675cf49-5db3-45b3-83fb-7a778849]
[2018-10-03 19:40:33,262][INFO
][exchange-worker-#151%cache.IgniteCacheIncrementTxTest1%][GridDhtPartitionDemander]
Prepared rebalancing [grp=default, mode=ASYNC,
supplier=4b3e5c6e-cec4-4fb6-b1b2-47fd7190, partitionsCount=97,
topVer=AffinityTopologyVersion [topVer=45, minorTopVer=0], parallelism=1]
[2018-10-03 19:40:33,899][INFO
][sys-#155%cache.IgniteCacheIncrementTxTest0%][GridCachePartitionExchangeManager]
Full Message creating for AffinityTopologyVersion [topVer=45, minorTopVer=0]
performed in 1 ms.
[2018-10-03 19:40:33,903][INFO
[jira] [Commented] (IGNITE-9705) GridCacheDatabaseSharedManager#createPageMemory flushes invalid byte buffer into snapshot manager
[ https://issues.apache.org/jira/browse/IGNITE-9705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16637191#comment-16637191 ] Eduard Shangareev commented on IGNITE-9705: --- Looks good. [~DmitriyGovorukhin], please help with merge. > GridCacheDatabaseSharedManager#createPageMemory flushes invalid byte buffer > into snapshot manager > - > > Key: IGNITE-9705 > URL: https://issues.apache.org/jira/browse/IGNITE-9705 > Project: Ignite > Issue Type: Improvement >Reporter: Ivan Bessonov >Assignee: Ivan Bessonov >Priority: Major > > org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager#createPageMemory > executes two consecutive operations with the same byte buffer bot doesn't > rewind it in between which may lead to inconsistent data. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9697) [TC Bot] Autocomplete branch for TC field
[
https://issues.apache.org/jira/browse/IGNITE-9697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16637178#comment-16637178
]
ASF GitHub Bot commented on IGNITE-9697:
asfgit closed pull request #24: IGNITE-9697 Autocomplete branch for TC field
URL: https://github.com/apache/ignite-teamcity-bot/pull/24
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/HelperConfig.java
b/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/HelperConfig.java
index 67be102..c39fd1e 100644
--- a/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/HelperConfig.java
+++ b/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/HelperConfig.java
@@ -54,6 +54,12 @@
/** JIRA authorization token property name. */
public static final String JIRA_AUTH_TOKEN = "jira.auth_token";
+/** JIRA authorization token property name. */
+public static final String GIT_API_URL = "git.api_url";
+
+/** JIRA authorization token property name. */
+public static final String JIRA_API_URL = "jira.api_url";
+
/** Slack authorization token property name. */
public static final String SLACK_AUTH_TOKEN = "slack.auth_token";
public static final String SLACK_CHANNEL = "slack.channel";
diff --git
a/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/ITeamcity.java
b/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/ITeamcity.java
index 3193ea8..8f58657 100644
--- a/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/ITeamcity.java
+++ b/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/ITeamcity.java
@@ -319,6 +319,25 @@ default SingleBuildRunCtx loadTestsAndProblems(@Nonnull
Build build, @Deprecated
*/
boolean sendJiraComment(String ticket, String comment);
+/**
+ * @param url URL for git integration.
+ */
+void setGitApiUrl(String url);
+
+/**
+ * @return URL for git integration.
+ */
+String getGitApiUrl();
+
+/**
+ * @param url URL for JIRA integration.
+ */
+void setJiraApiUrl(String url);
+
+/**
+ * @return URL for JIRA integration.
+ */
+String getJiraApiUrl();
default void setAuthData(String user, String password) {
setAuthToken(
diff --git
a/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/IgnitePersistentTeamcity.java
b/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/IgnitePersistentTeamcity.java
index ec53d9b..2e9f873 100644
---
a/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/IgnitePersistentTeamcity.java
+++
b/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/IgnitePersistentTeamcity.java
@@ -1168,6 +1168,26 @@ public void setExecutor(ExecutorService executor) {
return teamcity.sendJiraComment(ticket, comment);
}
+/** {@inheritDoc} */
+@Override public void setGitApiUrl(String url) {
+teamcity.setGitApiUrl(url);
+}
+
+/** {@inheritDoc} */
+@Override public String getGitApiUrl() {
+return teamcity.getGitApiUrl();
+}
+
+/** {@inheritDoc} */
+@Override public void setJiraApiUrl(String url) {
+teamcity.setJiraApiUrl(url);
+}
+
+/** {@inheritDoc} */
+@Override public String getJiraApiUrl() {
+return teamcity.getJiraApiUrl();
+}
+
/** {@inheritDoc} */
@Override public PullRequest getPullRequest(String branchForTc) {
return teamcity.getPullRequest(branchForTc);
diff --git
a/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/IgniteTeamcityConnection.java
b/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/IgniteTeamcityConnection.java
index 6b63f1b..3d68ccb 100644
---
a/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/IgniteTeamcityConnection.java
+++
b/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/IgniteTeamcityConnection.java
@@ -104,6 +104,12 @@
/** JIRA authorization token. */
private String jiraBasicAuthTok;
+/** URL for git integration. */
+private String gitApiUrl;
+
+/** URL for JIRA integration. */
+private String jiraApiUrl;
+
private String configName; //main properties file name
private String tcName;
@@ -130,8 +136,10 @@ public void init(@Nullable String tcName) {
}
setGitToken(HelperConfig.prepareGithubHttpAuthToken(props));
+setGitApiUrl(props.getProperty(HelperConfig.GIT_API_URL));
setJiraToken(HelperConfig.prepareJiraHttpAuthToken(props));
+setJiraApiUrl(props.getProperty(HelperConfig.JIRA_API_URL));
final File logsDirFile = HelperConfig.resolveLogs(workDir, props);
@@ -173,8 +181,14 @@ public void init(@Nullable String tcName) {
[jira] [Commented] (IGNITE-9126) Update Apache Kafka dependency
[ https://issues.apache.org/jira/browse/IGNITE-9126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16637175#comment-16637175 ] ASF GitHub Bot commented on IGNITE-9126: GitHub user Max-Pudov opened a pull request: https://github.com/apache/ignite/pull/4909 IGNITE-9126 Update Apache Kafka dependency You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9126 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4909.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 #4909 commit e81883de88965435e878fe60ddd5f933c05fe312 Author: Max-Pudov Date: 2018-10-03T16:39:21Z IGNITE-9126 Update Apache Kafka dependency > Update Apache Kafka dependency > -- > > Key: IGNITE-9126 > URL: https://issues.apache.org/jira/browse/IGNITE-9126 > Project: Ignite > Issue Type: Task >Reporter: Dmitriy Pavlov >Assignee: Maxim Pudov >Priority: Major > Fix For: 2.7 > > > It is suggested to update kafka in accordance with scala update, e.g. to > https://mvnrepository.com/artifact/org.apache.kafka/kafka_2.11/1.0.2 > or to Kafka 1.1.1 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9541) Add the comparison for two general statistics "RunAll" for master in the date interval
[
https://issues.apache.org/jira/browse/IGNITE-9541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16637148#comment-16637148
]
ASF GitHub Bot commented on IGNITE-9541:
asfgit closed pull request #23: IGNITE-9541 Add row highlight for 'failed', add
title for columns, re…
URL: https://github.com/apache/ignite-teamcity-bot/pull/23
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/webapp/comparison.html
b/ignite-tc-helper-web/src/main/webapp/comparison.html
index 5efe4e3..7868f64 100644
--- a/ignite-tc-helper-web/src/main/webapp/comparison.html
+++ b/ignite-tc-helper-web/src/main/webapp/comparison.html
@@ -29,11 +29,11 @@
-TESTS
+TESTS
COUNT
-
-
+
+
@@ -42,8 +42,8 @@
PASSED
-
-
+
+
@@ -52,8 +52,8 @@
FAILED
-
-
+
+
@@ -62,8 +62,8 @@
IGNORED
-
-
+
+
@@ -72,19 +72,19 @@
MUTED
-
-
+
+
-PROBLEMS
+PROBLEMS
TOTAL
-
-
+
+
@@ -92,8 +92,8 @@
EXECUTION TIMEOUT
-
-
+
+
@@ -102,8 +102,8 @@
JVM CRASH
-
-
+
+
@@ -112,8 +112,8 @@
OOME
-
-
+
+
@@ -122,8 +122,8 @@
EXIT CODE
-
-
+
+
@@ -200,6 +200,7 @@
if (dates.length === 0) {
printImportantMessage(num, "#ff", "No data for the selected
period");
fillAllDataCells(num, "");
+$('.title' + num).html("");
return;
} else {
@@ -211,37 +212,47 @@
(firstDate === lastDate ? firstDate : ("the period from "
+ firstDate + " to " + lastDate)) + "");
} else {
$("#info" + num).html("");
-if (document.getElementById("info" + anotherNum).innerHTML ===
"") {
-document.getElementById("showInfo").style.display = "none";
+if ($('#info' + anotherNum).text() === ''){
+$('#showInfo').css('display', 'none')
}
}
}
-let anotherMedian;
-let result = {};
+$('.title' + num).html('min - median - max');
for (let i = 0; i < prOcc.length; i++) {
-result = getMinMaxMedian(statistics[prOcc[i]]);
-anotherMedian = parseMedian(document.getElementById(prOcc[i] +
anotherNum).innerHTML);
-
-$('#' + prOcc[i] + num).html(result.min + " - " + result.median +
" - " + result.max);
-
-if (!isNaN(anotherMedian)){
-if (result.median > anotherMedian){
-document.getElementById(prOcc[i] +
num).style.backgroundColor = "#ffeee9";
-document.getElementById(prOcc[i] +
anotherNum).style.backgroundColor = "#e5ffe8";
-} else if (result.median < anotherMedian){
-document.getElementById(prOcc[i] +
anotherNum).style.backgroundColor = "#ffeee9";
-document.getElementById(prOcc[i] +
num).style.backgroundColor = "#e5ffe8";
-}
-}
+fillCellWithStatistics(prOcc[i], num, statistics, dates);
+fillCellWithStatistics(tOcc[i], num, statistics, dates);
+}
+}
+
+function fillCellWithStatistics(prefix, num, statistics, dates) {
+let result = getMinMaxMedian(statistics[prefix]);
-result = getMinMaxMedian(statistics[tOcc[i]]);
+$('#' + prefix + num).html(result.min + " - " + result.median + " - "
+ result.max);
-$('#' + tOcc[i] + num).html(result.min + " - " + result.median + "
- " + result.max);
+compareAndHighlight(prefix, num, result.median);
+
+drawGraph(prefix, num, dates, statistics[prefix], prefix);
+}
-drawGraph(prOcc[i], num, dates, statistics[prOcc[i]], prOcc[i]);
-drawGraph(tOcc[i], num, dates, statistics[tOcc[i]], tOcc[i]);
+function compareAndHighlight(prefix, thisNum, thisMedian){
+let anotherNum = (thisNum === 1) ? 2 : 1;
+
+let thisElement = $('#' + prefix + thisNum);
+let
[jira] [Closed] (IGNITE-9346) md5 should be removed from release
[ https://issues.apache.org/jira/browse/IGNITE-9346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Ivanov closed IGNITE-9346. > md5 should be removed from release > -- > > Key: IGNITE-9346 > URL: https://issues.apache.org/jira/browse/IGNITE-9346 > Project: Ignite > Issue Type: Task >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Major > Fix For: 2.7 > > > The board communicated the following release policy changes: > -- for new releases : > -- you MUST supply a SHA-256 and/or SHA-512 file > -- you SHOULD NOT supply MD5 or SHA-1 files > So, we should get rid of md5 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-9346) md5 should be removed from release
[ https://issues.apache.org/jira/browse/IGNITE-9346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Ivanov resolved IGNITE-9346. -- Resolution: Done > md5 should be removed from release > -- > > Key: IGNITE-9346 > URL: https://issues.apache.org/jira/browse/IGNITE-9346 > Project: Ignite > Issue Type: Task >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Major > Fix For: 2.7 > > > The board communicated the following release policy changes: > -- for new releases : > -- you MUST supply a SHA-256 and/or SHA-512 file > -- you SHOULD NOT supply MD5 or SHA-1 files > So, we should get rid of md5 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9346) md5 should be removed from release
[ https://issues.apache.org/jira/browse/IGNITE-9346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Ivanov updated IGNITE-9346: - Ignite Flags: (was: Docs Required) > md5 should be removed from release > -- > > Key: IGNITE-9346 > URL: https://issues.apache.org/jira/browse/IGNITE-9346 > Project: Ignite > Issue Type: Task >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Major > Fix For: 2.7 > > > The board communicated the following release policy changes: > -- for new releases : > -- you MUST supply a SHA-256 and/or SHA-512 file > -- you SHOULD NOT supply MD5 or SHA-1 files > So, we should get rid of md5 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9785) Introduce read-only state in local node context
[ https://issues.apache.org/jira/browse/IGNITE-9785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Rakov updated IGNITE-9785: --- Description: It would be useful to have option to switch "read-only" state on Ignite node. Under read-only state: 1) Any attempt to update data via Cache API should throw exception 2) Any attempt to update data via DataStreamer should throw exception 3) Any attempt to update data via SQL API should fail Local read-only state may be helpful in further implementing global read-only cluster state, which can be switched via user API. was: It would be useful to have option to switch "read-only" state on Ignite node. Under read-only state: 1) Any attempt to update data via Cache API should throw exception 2) Any attempt to update data via DataStreamer should throw exception Local read-only state may be helpful in further implementing global read-only cluster state, which can be switched via user API. > Introduce read-only state in local node context > --- > > Key: IGNITE-9785 > URL: https://issues.apache.org/jira/browse/IGNITE-9785 > Project: Ignite > Issue Type: New Feature >Reporter: Ivan Rakov >Assignee: Aleksey Plekhanov >Priority: Major > Fix For: 2.8 > > > It would be useful to have option to switch "read-only" state on Ignite node. > Under read-only state: > 1) Any attempt to update data via Cache API should throw exception > 2) Any attempt to update data via DataStreamer should throw exception > 3) Any attempt to update data via SQL API should fail > Local read-only state may be helpful in further implementing global read-only > cluster state, which can be switched via user API. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9346) md5 should be removed from release
[
https://issues.apache.org/jira/browse/IGNITE-9346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16637115#comment-16637115
]
Peter Ivanov commented on IGNITE-9346:
--
Latest 2.7.0-RC build contains:
{code}
/svn/vote# ls -l
total 401356
-rw-rw-r-- 1 root root 308884443 Oct 2 12:43 apache-ignite-2.7.0-bin.zip
-rw-r--r-- 1 root root 833 Oct 2 15:10 apache-ignite-2.7.0-bin.zip.asc
-rw-rw-r-- 1 root root 158 Oct 2 12:43 apache-ignite-2.7.0-bin.zip.sha512
-rw-rw-r-- 1 root root 28681634 Oct 2 12:27 apache-ignite-2.7.0-src.zip
-rw-r--r-- 1 root root 833 Oct 2 15:10 apache-ignite-2.7.0-src.zip.asc
-rw-rw-r-- 1 root root 158 Oct 2 12:43 apache-ignite-2.7.0-src.zip.sha512
-rw-rw-r-- 1 root root 73388610 Oct 2 12:43 apache-ignite-hadoop-2.7.0-bin.zip
-rw-r--r-- 1 root root 833 Oct 2 15:10
apache-ignite-hadoop-2.7.0-bin.zip.asc
-rw-rw-r-- 1 root root 165 Oct 2 12:43
apache-ignite-hadoop-2.7.0-bin.zip.sha512
{code}
Everything is OK.
> md5 should be removed from release
> --
>
> Key: IGNITE-9346
> URL: https://issues.apache.org/jira/browse/IGNITE-9346
> Project: Ignite
> Issue Type: Task
>Reporter: Anton Vinogradov
>Assignee: Anton Vinogradov
>Priority: Major
> Fix For: 2.7
>
>
> The board communicated the following release policy changes:
> -- for new releases :
> -- you MUST supply a SHA-256 and/or SHA-512 file
> -- you SHOULD NOT supply MD5 or SHA-1 files
> So, we should get rid of md5
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9428) MVCC TX: MvccQueryTrackerImpl.onDone() semantic is broken.
[
https://issues.apache.org/jira/browse/IGNITE-9428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-9428:
Fix Version/s: (was: 2.7)
2.8
> MVCC TX: MvccQueryTrackerImpl.onDone() semantic is broken.
> --
>
> Key: IGNITE-9428
> URL: https://issues.apache.org/jira/browse/IGNITE-9428
> Project: Ignite
> Issue Type: Bug
> Components: mvcc, sql
>Reporter: Roman Kondakov
>Assignee: Andrew Mashenkov
>Priority: Major
> Fix For: 2.8
>
>
> Due to IGNITE-9256 patch, multiple {{H2ResultSetIterator#onClose}} invocation
> becomes possible. This can be considered as a {{Closable}} contract violation
> and should be fixed.
> Also this case revealed a bug in {{MvccQueryTrackerImpl}} when multiple
> {{onDone()}} call leads to multiple query finished acks sent back to the
> {{MvccCoordinator}} which leads to the problems with the query tracking and
> assertion errors.
> Reproducer:
> {{CacheMvccSqlTxQueriesAbstractTest#testAccountsTxDmlSumSql_WithRemoves_SingleNode}}
>
>
> Upd: test was fixed in IGNITE-9373. But MvccQueryTrackerImpl.onDone() issue
> is still actual.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9787) Local Continuous Query skips rows during initial rebalance of REPLICATED cache
Ilya Kasnacheev created IGNITE-9787: --- Summary: Local Continuous Query skips rows during initial rebalance of REPLICATED cache Key: IGNITE-9787 URL: https://issues.apache.org/jira/browse/IGNITE-9787 Project: Ignite Issue Type: Bug Affects Versions: 2.4 Reporter: Ilya Kasnacheev Attachments: IgniteRepro2.zip This is observer under .Net but I assume will affect Java too: If you have a partitioned cache with non-local continuous query, continuous query will iterate every entry in REPLICATED cache. If you have a replicated cache with non-local continuous query, it works. If you have a replicated cache with local continuous query and synchronous rebalancing, it also works. But if you have replicated cache with local continuous query and non-synchronous rebalancing , you will see the gap in data - newly written entries while rebalance is underway may not be passed to callback or scan query. Please see the ML thread and reproducer. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9786) MVCC: simplify TX wait list management
[ https://issues.apache.org/jira/browse/IGNITE-9786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16637097#comment-16637097 ] Vladimir Ozerov commented on IGNITE-9786: - Test run: https://ci.ignite.apache.org/viewQueued.html?itemId=1998703=queuedBuildOverviewTab > MVCC: simplify TX wait list management > -- > > Key: IGNITE-9786 > URL: https://issues.apache.org/jira/browse/IGNITE-9786 > Project: Ignite > Issue Type: Task > Components: mvcc >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Major > Fix For: 2.8 > > > It seems that instead of having a lot of classes and complex synchronization > mechanics for MvccProcessorImpl.waitMap, we can use single wrapper with a > list of waiters. > Resulting code will be much more simpler and less prone to concurrency issues. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9126) Update Apache Kafka dependency
[ https://issues.apache.org/jira/browse/IGNITE-9126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16637096#comment-16637096 ] ASF GitHub Bot commented on IGNITE-9126: Github user Max-Pudov closed the pull request at: https://github.com/apache/ignite/pull/4880 > Update Apache Kafka dependency > -- > > Key: IGNITE-9126 > URL: https://issues.apache.org/jira/browse/IGNITE-9126 > Project: Ignite > Issue Type: Task >Reporter: Dmitriy Pavlov >Assignee: Maxim Pudov >Priority: Major > Fix For: 2.7 > > > It is suggested to update kafka in accordance with scala update, e.g. to > https://mvnrepository.com/artifact/org.apache.kafka/kafka_2.11/1.0.2 > or to Kafka 1.1.1 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9786) MVCC: simplify TX wait list management
[ https://issues.apache.org/jira/browse/IGNITE-9786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16637093#comment-16637093 ] ASF GitHub Bot commented on IGNITE-9786: GitHub user devozerov opened a pull request: https://github.com/apache/ignite/pull/4908 IGNITE-9786 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9786 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4908.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 #4908 commit 9200568fb830c93c7d98c74c14d4006bbdac8797 Author: devozerov Date: 2018-10-03T14:37:59Z WIP. commit 88ef985156c42ffeef564b7a1a2a54e5efaa7989 Author: devozerov Date: 2018-10-03T15:41:59Z Done. > MVCC: simplify TX wait list management > -- > > Key: IGNITE-9786 > URL: https://issues.apache.org/jira/browse/IGNITE-9786 > Project: Ignite > Issue Type: Task > Components: mvcc >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Major > Fix For: 2.8 > > > It seems that instead of having a lot of classes and complex synchronization > mechanics for MvccProcessorImpl.waitMap, we can use single wrapper with a > list of waiters. > Resulting code will be much more simpler and less prone to concurrency issues. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9786) MVCC: simplify TX wait list management
Vladimir Ozerov created IGNITE-9786: --- Summary: MVCC: simplify TX wait list management Key: IGNITE-9786 URL: https://issues.apache.org/jira/browse/IGNITE-9786 Project: Ignite Issue Type: Task Components: mvcc Reporter: Vladimir Ozerov Assignee: Vladimir Ozerov Fix For: 2.8 It seems that instead of having a lot of classes and complex synchronization mechanics for MvccProcessorImpl.waitMap, we can use single wrapper with a list of waiters. Resulting code will be much more simpler and less prone to concurrency issues. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9431) Documentation for zk paths used by ZookeeperDiscovery.
[ https://issues.apache.org/jira/browse/IGNITE-9431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Budnikov reassigned IGNITE-9431: -- Assignee: Stanilovsky Evgeny (was: Artem Budnikov) > Documentation for zk paths used by ZookeeperDiscovery. > -- > > Key: IGNITE-9431 > URL: https://issues.apache.org/jira/browse/IGNITE-9431 > Project: Ignite > Issue Type: Improvement > Components: documentation >Affects Versions: 2.6 >Reporter: Stanilovsky Evgeny >Assignee: Stanilovsky Evgeny >Priority: Major > > I found that under /apacheIgnite zk directory, there are also: > /jd, /ce, /cp, /ca and some other dirs, from source i found that they take > place from : org.apache.ignite.spi.discovery.zk.internal.ZkIgnitePaths. Plz > document this paths purpose. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9431) Documentation for zk paths used by ZookeeperDiscovery.
[ https://issues.apache.org/jira/browse/IGNITE-9431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16637085#comment-16637085 ] Artem Budnikov commented on IGNITE-9431: [~zstan], I think users do not need to know low-level implementation details. Advanced users can find documentation on these directories in the source code. Feel free to ask the developers to provide details in the Ignite's wiki, i.e., here: https://cwiki.apache.org/confluence/display/IGNITE/IEP-15%3A+Discovery+SPI+by+ZooKeeper. > Documentation for zk paths used by ZookeeperDiscovery. > -- > > Key: IGNITE-9431 > URL: https://issues.apache.org/jira/browse/IGNITE-9431 > Project: Ignite > Issue Type: Improvement > Components: documentation >Affects Versions: 2.6 >Reporter: Stanilovsky Evgeny >Assignee: Artem Budnikov >Priority: Major > > I found that under /apacheIgnite zk directory, there are also: > /jd, /ce, /cp, /ca and some other dirs, from source i found that they take > place from : org.apache.ignite.spi.discovery.zk.internal.ZkIgnitePaths. Plz > document this paths purpose. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9606) JDBC getPrimaryKeys() returns wrong value for COLUMN_NAME
[
https://issues.apache.org/jira/browse/IGNITE-9606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-9606:
-
Ignite Flags: (was: Docs Required)
> JDBC getPrimaryKeys() returns wrong value for COLUMN_NAME
> -
>
> Key: IGNITE-9606
> URL: https://issues.apache.org/jira/browse/IGNITE-9606
> Project: Ignite
> Issue Type: Bug
> Components: jdbc
>Affects Versions: 2.6
>Reporter: Pat Patterson
>Assignee: Pavel Kuznetsov
>Priority: Major
> Fix For: 2.8
>
>
> JDBC {{getPrimaryKeys()}} method returns {{_KEY}} as column name rather than
> actual column name. This breaks apps that expect a valid column name as the
> primary key.
> Trivially reproducible:
> {noformat}
> public static void main(String[] args) throws Exception {
> // Register JDBC driver.
> Class.forName("org.apache.ignite.IgniteJdbcThinDriver");
> // Open JDBC connection.
> try (Connection conn =
> DriverManager.getConnection("jdbc:ignite:thin://127.0.0.1/")) {
> // Create database tables.
> try (Statement stmt = conn.createStatement()) {
> stmt.executeUpdate("CREATE TABLE TESTER (" + " ID LONG PRIMARY KEY,
> NAME VARCHAR) " + " WITH \"template=replicated\"");
> }
> // Get database metadata
> DatabaseMetaData md = conn.getMetaData();
> // Get primary keys
> ResultSet rs = md.getPrimaryKeys(conn.getCatalog(), "", "TESTER");
> //
> while (rs.next()) {
> // Column 4 is COLUMN_NAME
> System.out.println("Primary key column is " + rs.getString(4));
> }
> }
> }
> {noformat}
> Expected output is:
> {noformat}
> Primary key column is ID
> {noformat}
> Actual output is:
> {noformat}
> Primary key column is _KEY
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9606) JDBC getPrimaryKeys() returns wrong value for COLUMN_NAME
[
https://issues.apache.org/jira/browse/IGNITE-9606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16637079#comment-16637079
]
Taras Ledkov commented on IGNITE-9606:
--
[~pkouznet], please provide TC tests results for SQL suites.
> JDBC getPrimaryKeys() returns wrong value for COLUMN_NAME
> -
>
> Key: IGNITE-9606
> URL: https://issues.apache.org/jira/browse/IGNITE-9606
> Project: Ignite
> Issue Type: Bug
> Components: jdbc
>Affects Versions: 2.6
>Reporter: Pat Patterson
>Assignee: Pavel Kuznetsov
>Priority: Major
> Fix For: 2.8
>
>
> JDBC {{getPrimaryKeys()}} method returns {{_KEY}} as column name rather than
> actual column name. This breaks apps that expect a valid column name as the
> primary key.
> Trivially reproducible:
> {noformat}
> public static void main(String[] args) throws Exception {
> // Register JDBC driver.
> Class.forName("org.apache.ignite.IgniteJdbcThinDriver");
> // Open JDBC connection.
> try (Connection conn =
> DriverManager.getConnection("jdbc:ignite:thin://127.0.0.1/")) {
> // Create database tables.
> try (Statement stmt = conn.createStatement()) {
> stmt.executeUpdate("CREATE TABLE TESTER (" + " ID LONG PRIMARY KEY,
> NAME VARCHAR) " + " WITH \"template=replicated\"");
> }
> // Get database metadata
> DatabaseMetaData md = conn.getMetaData();
> // Get primary keys
> ResultSet rs = md.getPrimaryKeys(conn.getCatalog(), "", "TESTER");
> //
> while (rs.next()) {
> // Column 4 is COLUMN_NAME
> System.out.println("Primary key column is " + rs.getString(4));
> }
> }
> }
> {noformat}
> Expected output is:
> {noformat}
> Primary key column is ID
> {noformat}
> Actual output is:
> {noformat}
> Primary key column is _KEY
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9785) Introduce read-only state in local node context
[ https://issues.apache.org/jira/browse/IGNITE-9785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16637074#comment-16637074 ] Ivan Rakov commented on IGNITE-9785: TC run: https://ci.ignite.apache.org/viewQueued.html?itemId=1998594 > Introduce read-only state in local node context > --- > > Key: IGNITE-9785 > URL: https://issues.apache.org/jira/browse/IGNITE-9785 > Project: Ignite > Issue Type: New Feature >Reporter: Ivan Rakov >Assignee: Aleksey Plekhanov >Priority: Major > Fix For: 2.8 > > > It would be useful to have option to switch "read-only" state on Ignite node. > Under read-only state: > 1) Any attempt to update data via Cache API should throw exception > 2) Any attempt to update data via DataStreamer should throw exception > Local read-only state may be helpful in further implementing global read-only > cluster state, which can be switched via user API. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (IGNITE-9785) Introduce read-only state in local node context
[ https://issues.apache.org/jira/browse/IGNITE-9785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Rakov updated IGNITE-9785: --- Comment: was deleted (was: PR: https://github.com/apache/ignite/pull/4895 TC run: https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8_IgniteTests24Java8=pull%2F4895%2Fhead) > Introduce read-only state in local node context > --- > > Key: IGNITE-9785 > URL: https://issues.apache.org/jira/browse/IGNITE-9785 > Project: Ignite > Issue Type: New Feature >Reporter: Ivan Rakov >Assignee: Aleksey Plekhanov >Priority: Major > Fix For: 2.8 > > > It would be useful to have option to switch "read-only" state on Ignite node. > Under read-only state: > 1) Any attempt to update data via Cache API should throw exception > 2) Any attempt to update data via DataStreamer should throw exception > Local read-only state may be helpful in further implementing global read-only > cluster state, which can be switched via user API. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9785) Introduce read-only state in local node context
[ https://issues.apache.org/jira/browse/IGNITE-9785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16637070#comment-16637070 ] ASF GitHub Bot commented on IGNITE-9785: GitHub user glukos opened a pull request: https://github.com/apache/ignite/pull/4907 IGNITE-9785 Introduce read-only state in local node context You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9785 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4907.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 #4907 commit 9a40d52662a115755d3e89931ff24c55ca4b377c Author: Aleksey Plekhanov Date: 2018-10-03T15:11:08Z TDR-18 Read-only mode Signed-off-by: Ivan Rakov > Introduce read-only state in local node context > --- > > Key: IGNITE-9785 > URL: https://issues.apache.org/jira/browse/IGNITE-9785 > Project: Ignite > Issue Type: New Feature >Reporter: Ivan Rakov >Assignee: Aleksey Plekhanov >Priority: Major > Fix For: 2.8 > > > It would be useful to have option to switch "read-only" state on Ignite node. > Under read-only state: > 1) Any attempt to update data via Cache API should throw exception > 2) Any attempt to update data via DataStreamer should throw exception > Local read-only state may be helpful in further implementing global read-only > cluster state, which can be switched via user API. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9785) Introduce read-only state in local node context
[ https://issues.apache.org/jira/browse/IGNITE-9785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16637048#comment-16637048 ] Ivan Rakov commented on IGNITE-9785: PR: https://github.com/apache/ignite/pull/4895 TC run: https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8_IgniteTests24Java8=pull%2F4895%2Fhead > Introduce read-only state in local node context > --- > > Key: IGNITE-9785 > URL: https://issues.apache.org/jira/browse/IGNITE-9785 > Project: Ignite > Issue Type: New Feature >Reporter: Ivan Rakov >Assignee: Aleksey Plekhanov >Priority: Major > Fix For: 2.8 > > > It would be useful to have option to switch "read-only" state on Ignite node. > Under read-only state: > 1) Any attempt to update data via Cache API should throw exception > 2) Any attempt to update data via DataStreamer should throw exception > Local read-only state may be helpful in further implementing global read-only > cluster state, which can be switched via user API. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9785) Introduce read-only state in local node context
Ivan Rakov created IGNITE-9785: -- Summary: Introduce read-only state in local node context Key: IGNITE-9785 URL: https://issues.apache.org/jira/browse/IGNITE-9785 Project: Ignite Issue Type: New Feature Reporter: Ivan Rakov Assignee: Aleksey Plekhanov Fix For: 2.8 It would be useful to have option to switch "read-only" state on Ignite node. Under read-only state: 1) Any attempt to update data via Cache API should throw exception 2) Any attempt to update data via DataStreamer should throw exception Local read-only state may be helpful in further implementing global read-only cluster state, which can be switched via user API. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7616) GridDataStreamExecutor and GridCallbackExecutor JMX beans return incorrect values due to invalid interface registration.
[ https://issues.apache.org/jira/browse/IGNITE-7616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16637028#comment-16637028 ] David Harvey commented on IGNITE-7616: -- The purpose of this change, as I understand it, to implement what is effectively a "toString" function that humans can use during analysis. There was a request for additional unit tests, but it is unclear what such tests would accomplish. Without this patch, DataStreamExecutor and StripedExecutor were returning "-1" > GridDataStreamExecutor and GridCallbackExecutor JMX beans return incorrect > values due to invalid interface registration. > > > Key: IGNITE-7616 > URL: https://issues.apache.org/jira/browse/IGNITE-7616 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.4 >Reporter: Max Shonichev >Assignee: David Harvey >Priority: Major > Labels: jmx > Fix For: 2.7 > > Attachments: image-2018-10-03-10-23-24-676.png, > image-2018-10-03-10-24-12-459.png, master_1b3742f4d7_mxbeans_threads2.patch > > > Two of newly added management beans as a result of implementing feature > request https://issues.apache.org/jira/browse/IGNITE-7217 have bugs: > # GridDataStreamExecutor is registered as conforming to ThreadPoolMXBean > interface, though actually it is an incompatible StripedExecutor. > # GridCallbackExecutor is registered as conforming to ThreadPoolMXBean > interface, though actually it is an incompatible > IgniteStripedThreadPoolExecutor. > # ThreadPoolMXBeanAdapter checks whether adapted instance is > ThreadPoolExecutor, and as interfaces are incompatible, most of the JMX > attributes of GridCallbackExecutor and GridDataStreamExecutor are returned as > -1 or null. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7616) GridDataStreamExecutor and GridCallbackExecutor JMX beans return incorrect values due to invalid interface registration.
[ https://issues.apache.org/jira/browse/IGNITE-7616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Harvey updated IGNITE-7616: - Attachment: image-2018-10-03-10-24-12-459.png > GridDataStreamExecutor and GridCallbackExecutor JMX beans return incorrect > values due to invalid interface registration. > > > Key: IGNITE-7616 > URL: https://issues.apache.org/jira/browse/IGNITE-7616 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.4 >Reporter: Max Shonichev >Assignee: David Harvey >Priority: Major > Labels: jmx > Fix For: 2.7 > > Attachments: image-2018-10-03-10-23-24-676.png, > image-2018-10-03-10-24-12-459.png, master_1b3742f4d7_mxbeans_threads2.patch > > > Two of newly added management beans as a result of implementing feature > request https://issues.apache.org/jira/browse/IGNITE-7217 have bugs: > # GridDataStreamExecutor is registered as conforming to ThreadPoolMXBean > interface, though actually it is an incompatible StripedExecutor. > # GridCallbackExecutor is registered as conforming to ThreadPoolMXBean > interface, though actually it is an incompatible > IgniteStripedThreadPoolExecutor. > # ThreadPoolMXBeanAdapter checks whether adapted instance is > ThreadPoolExecutor, and as interfaces are incompatible, most of the JMX > attributes of GridCallbackExecutor and GridDataStreamExecutor are returned as > -1 or null. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7616) GridDataStreamExecutor and GridCallbackExecutor JMX beans return incorrect values due to invalid interface registration.
[ https://issues.apache.org/jira/browse/IGNITE-7616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16637024#comment-16637024 ] David Harvey commented on IGNITE-7616: -- !image-2018-10-03-10-24-12-459.png! > GridDataStreamExecutor and GridCallbackExecutor JMX beans return incorrect > values due to invalid interface registration. > > > Key: IGNITE-7616 > URL: https://issues.apache.org/jira/browse/IGNITE-7616 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.4 >Reporter: Max Shonichev >Assignee: David Harvey >Priority: Major > Labels: jmx > Fix For: 2.7 > > Attachments: image-2018-10-03-10-23-24-676.png, > image-2018-10-03-10-24-12-459.png, master_1b3742f4d7_mxbeans_threads2.patch > > > Two of newly added management beans as a result of implementing feature > request https://issues.apache.org/jira/browse/IGNITE-7217 have bugs: > # GridDataStreamExecutor is registered as conforming to ThreadPoolMXBean > interface, though actually it is an incompatible StripedExecutor. > # GridCallbackExecutor is registered as conforming to ThreadPoolMXBean > interface, though actually it is an incompatible > IgniteStripedThreadPoolExecutor. > # ThreadPoolMXBeanAdapter checks whether adapted instance is > ThreadPoolExecutor, and as interfaces are incompatible, most of the JMX > attributes of GridCallbackExecutor and GridDataStreamExecutor are returned as > -1 or null. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7616) GridDataStreamExecutor and GridCallbackExecutor JMX beans return incorrect values due to invalid interface registration.
[ https://issues.apache.org/jira/browse/IGNITE-7616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Harvey updated IGNITE-7616: - Attachment: image-2018-10-03-10-23-24-676.png > GridDataStreamExecutor and GridCallbackExecutor JMX beans return incorrect > values due to invalid interface registration. > > > Key: IGNITE-7616 > URL: https://issues.apache.org/jira/browse/IGNITE-7616 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.4 >Reporter: Max Shonichev >Assignee: David Harvey >Priority: Major > Labels: jmx > Fix For: 2.7 > > Attachments: image-2018-10-03-10-23-24-676.png, > master_1b3742f4d7_mxbeans_threads2.patch > > > Two of newly added management beans as a result of implementing feature > request https://issues.apache.org/jira/browse/IGNITE-7217 have bugs: > # GridDataStreamExecutor is registered as conforming to ThreadPoolMXBean > interface, though actually it is an incompatible StripedExecutor. > # GridCallbackExecutor is registered as conforming to ThreadPoolMXBean > interface, though actually it is an incompatible > IgniteStripedThreadPoolExecutor. > # ThreadPoolMXBeanAdapter checks whether adapted instance is > ThreadPoolExecutor, and as interfaces are incompatible, most of the JMX > attributes of GridCallbackExecutor and GridDataStreamExecutor are returned as > -1 or null. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7616) GridDataStreamExecutor and GridCallbackExecutor JMX beans return incorrect values due to invalid interface registration.
[ https://issues.apache.org/jira/browse/IGNITE-7616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16637023#comment-16637023 ] David Harvey commented on IGNITE-7616: -- !image-2018-10-03-10-23-24-676.png! > GridDataStreamExecutor and GridCallbackExecutor JMX beans return incorrect > values due to invalid interface registration. > > > Key: IGNITE-7616 > URL: https://issues.apache.org/jira/browse/IGNITE-7616 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.4 >Reporter: Max Shonichev >Assignee: David Harvey >Priority: Major > Labels: jmx > Fix For: 2.7 > > Attachments: image-2018-10-03-10-23-24-676.png, > master_1b3742f4d7_mxbeans_threads2.patch > > > Two of newly added management beans as a result of implementing feature > request https://issues.apache.org/jira/browse/IGNITE-7217 have bugs: > # GridDataStreamExecutor is registered as conforming to ThreadPoolMXBean > interface, though actually it is an incompatible StripedExecutor. > # GridCallbackExecutor is registered as conforming to ThreadPoolMXBean > interface, though actually it is an incompatible > IgniteStripedThreadPoolExecutor. > # ThreadPoolMXBeanAdapter checks whether adapted instance is > ThreadPoolExecutor, and as interfaces are incompatible, most of the JMX > attributes of GridCallbackExecutor and GridDataStreamExecutor are returned as > -1 or null. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9673) Timeout in Java Client suite.
[
https://issues.apache.org/jira/browse/IGNITE-9673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amelchev Nikita updated IGNITE-9673:
Labels: MakeTeamcityGreenAgain (was: )
> 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 (parking)
> at sun.misc.Unsafe.park(Native Method)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:304)
> at
[jira] [Updated] (IGNITE-9673) Timeout in Java Client suite.
[
https://issues.apache.org/jira/browse/IGNITE-9673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amelchev Nikita updated IGNITE-9673:
Fix Version/s: 2.8
> 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 (parking)
> at sun.misc.Unsafe.park(Native Method)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:304)
> at
>
[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=16636998#comment-16636998
]
Amelchev Nikita commented on IGNITE-9673:
-
I have prepared PR to fix the issue.
The problem was that it happens deadlock between system threads. I added
reproducer to tests. I dragged the method "makeResponse" that call AtomicLong
to the system pool. TC tests look good.
[~ilantukh], could you review, please?
> 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
> 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
[jira] [Created] (IGNITE-9784) Performance drop on sql yardstick benchmarks
Ilya Suntsov created IGNITE-9784: Summary: Performance drop on sql yardstick benchmarks Key: IGNITE-9784 URL: https://issues.apache.org/jira/browse/IGNITE-9784 Project: Ignite Issue Type: Bug Components: sql Affects Versions: 2.7 Reporter: Ilya Suntsov Attachments: Screen Shot 2018-10-03 at 4.52.22 PM.png Please take a look at the attachment. Grid configuration: * 4 servers / 8 clients * java 8 * 64 threads, 60s warmup, 180s duration -- 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=16636988#comment-16636988
]
Ignite TC Bot commented on IGNITE-9673:
---
{panel:title=Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Activate | Deactivate Cluster{color} [[tests 0 TIMEOUT , Exit
Code |https://ci.ignite.apache.org/viewLog.html?buildId=1996522]]
* IgniteClusterActivateDeactivateTest.testConcurrentJoinAndActivate (last
started)
{color:#d04437}MVCC Queries{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=1996620]]
* IgniteCacheMvccSqlTestSuite:
CacheMvccReplicatedSelectForUpdateQueryTest.testSelectForUpdateOutsideTxLocal -
0,0% fails in last 100 master runs.
{color:#d04437}Client Nodes{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=1996524]]
* IgniteClientNodesTestSuite:
IgniteClientReconnectContinuousProcessorTest.testMessageListenerReconnectAndStopFromClient
- 0,0% fails in last 100 master runs.
{panel}
[TeamCity Run
All|http://ci.ignite.apache.org/viewLog.html?buildId=1996621buildTypeId=IgniteTests24Java8_RunAll]
> 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
> 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]],
[jira] [Commented] (IGNITE-9645) [TC Bot] Add comparison of failed tests lists in two date intervals
[
https://issues.apache.org/jira/browse/IGNITE-9645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16636978#comment-16636978
]
ASF GitHub Bot commented on IGNITE-9645:
SomeFire commented on a change in pull request #25: IGNITE-9645 [TC Bot] Add
comparison of failed tests lists in two date intervals
URL: https://github.com/apache/ignite-teamcity-bot/pull/25#discussion_r79867
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/web/rest/build/GetBuildTestFailures.java
##
@@ -159,75 +156,59 @@ public TestFailuresSummary getBuildTestFails(
}
@GET
-@Path("history")
-public List getBuildsHistory(
-@Nullable @QueryParam("server") String srv,
-@Nullable @QueryParam("buildType") String buildType,
-@Nullable @QueryParam("branch") String branch,
-@Nullable @QueryParam("sinceDate") String sinceDate,
-@Nullable @QueryParam("untilDate") String untilDate)
-throws ServiceUnauthorizedException {
-String srvId = isNullOrEmpty(srv) ? "apache" : srv;
-String buildTypeId = isNullOrEmpty(buildType) ?
"IgniteTests24Java8_RunAll" : buildType;
-String branchName = isNullOrEmpty(branch) ? "refs/heads/master" :
branch;
-Date sinceDateFilter = isNullOrEmpty(sinceDate) ? null :
dateParse(sinceDate);
-Date untilDateFilter = isNullOrEmpty(untilDate) ? null :
dateParse(untilDate);
-
-final BackgroundUpdater updater =
CtxListener.getBackgroundUpdater(ctx);
-
-final ITcHelper tcHelper = CtxListener.getTcHelper(ctx);
+@Produces(MediaType.TEXT_PLAIN)
+@Path("testRef")
+public String getTestRef(
+@NotNull @QueryParam("testName") String name,
+@Nullable @QueryParam("server") String server,
+@Nullable @QueryParam("projectId") String projectId)
+throws InterruptedException, ExecutionException {
+final ITcHelper helper = CtxListener.getTcHelper(ctx);
final ICredentialsProv prov = ICredentialsProv.get(req);
-IAnalyticsEnabledTeamcity teamcity = tcHelper.server(srvId, prov);
-
-int[] finishedBuilds =
teamcity.getBuildNumbersFromHistory(buildTypeId, branchName, sinceDateFilter,
untilDateFilter);
+String project = projectId == null ? "IgniteTests24Java8" : projectId;
-List buildsStatistics = new ArrayList<>();
+String serverId = server == null ? "apache" : server;
-for (int i = 0; i < finishedBuilds.length; i++) {
-int buildId = finishedBuilds[i];
+IAnalyticsEnabledTeamcity teamcity = helper.server(serverId, prov);
-FullQueryParams param = new FullQueryParams();
-param.setBuildId(buildId);
-param.setBranch(branchName);
-param.setServerId(srvId);
+FullQueryParams key = new FullQueryParams();
-BuildStatisticsSummary buildsStatistic = updater.get(
-BUILDS_STATISTICS_SUMMARY_CACHE_NAME, prov, param,
-(k) -> getBuildStatisticsSummaryNoCache(srvId, buildId),
false);
+key.setTestName(name);
-if (!buildsStatistic.isFakeStub)
-buildsStatistics.add(buildsStatistic);
-}
+key.setProjectId(project);
-return buildsStatistics;
-}
+key.setServerId(serverId);
-private Date dateParse(String date){
-DateFormat dateFormat = new SimpleDateFormat("ddMMHHmmss");
+CompletableFuture ref = teamcity.getTestRef(key);
-try {
-return dateFormat.parse(date);
-}
-catch (ParseException e) {
-return null;
-}
+return ref.isDone() ? teamcity.host() + "project.html?"
++ "projectId=" + project
++ "=" + ref.get().id
++ "=testDetails" : null;
}
-private BuildStatisticsSummary getBuildStatisticsSummaryNoCache(String
server, int buildId) {
-String srvId = isNullOrEmpty(server) ? "apache" : server;
-
-final ITcHelper tcHelper = CtxListener.getTcHelper(ctx);
-
-final ICredentialsProv creds = ICredentialsProv.get(req);
-
-IAnalyticsEnabledTeamcity teamcity = tcHelper.server(srvId, creds);
+@GET
+@Path("history")
+public BuildsHistory getBuildsHistory(
+@Nullable @QueryParam("server") String server,
+@Nullable @QueryParam("buildType") String buildType,
+@Nullable @QueryParam("branch") String branch,
+@Nullable @QueryParam("sinceDate") String sinceDate,
+@Nullable @QueryParam("untilDate") String untilDate) throws
ParseException {
+BuildsHistory buildsHistory = new BuildsHistory.Builder()
+.branch(branch)
+.server(server)
+.buildType(buildType)
+.sinceDate(sinceDate)
+.untilDate(untilDate)
+.build();
-BuildStatisticsSummary
[jira] [Commented] (IGNITE-9645) [TC Bot] Add comparison of failed tests lists in two date intervals
[
https://issues.apache.org/jira/browse/IGNITE-9645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16636980#comment-16636980
]
ASF GitHub Bot commented on IGNITE-9645:
SomeFire commented on a change in pull request #25: IGNITE-9645 [TC Bot] Add
comparison of failed tests lists in two date intervals
URL: https://github.com/apache/ignite-teamcity-bot/pull/25#discussion_r72279
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/web/model/hist/BuildsHistory.java
##
@@ -0,0 +1,209 @@
+package org.apache.ignite.ci.web.model.hist;
+
+import com.fasterxml.jackson.core.JsonProcessingException;
+import com.fasterxml.jackson.databind.ObjectMapper;
+import java.text.DateFormat;
+import java.text.ParseException;
+import java.text.SimpleDateFormat;
+import java.util.ArrayList;
+import java.util.Date;
+import java.util.HashMap;
+import java.util.HashSet;
+import java.util.List;
+import java.util.Map;
+import java.util.Set;
+import javax.servlet.ServletContext;
+import org.apache.ignite.ci.IAnalyticsEnabledTeamcity;
+import org.apache.ignite.ci.ITcHelper;
+import org.apache.ignite.ci.IgnitePersistentTeamcity;
+import org.apache.ignite.ci.chain.BuildChainProcessor;
+import org.apache.ignite.ci.tcmodel.result.Build;
+import org.apache.ignite.ci.tcmodel.result.tests.TestOccurrence;
+import org.apache.ignite.ci.tcmodel.result.tests.TestOccurrences;
+import org.apache.ignite.ci.user.ICredentialsProv;
+import org.apache.ignite.ci.web.CtxListener;
+import org.apache.ignite.ci.web.model.current.BuildStatisticsSummary;
+import org.apache.ignite.ci.web.rest.parms.FullQueryParams;
+
+import static com.google.common.base.Strings.isNullOrEmpty;
+import static
org.apache.ignite.ci.web.rest.build.GetBuildTestFailures.BUILDS_STATISTICS_SUMMARY_CACHE_NAME;
+
+public class BuildsHistory {
+private String srvId;
+
+private String projectId;
+
+private String buildTypeId;
+
+private String branchName;
+
+private Date sinceDateFilter;
+
+private Date untilDateFilter;
+
+private ObjectMapper objectMapper = new ObjectMapper();
+
+private Map> mergedTestsBySuites = new HashMap<>();
+
+private Set mergedTests = new HashSet<>();
+
+public List buildsStatistics = new ArrayList<>();
+
+public String mergedTestsResult;
+
+public void initialize(ICredentialsProv prov, ServletContext context) {
+ITcHelper tcHelper = CtxListener.getTcHelper(context);
+
+IAnalyticsEnabledTeamcity teamcity = tcHelper.server(srvId, prov);
+
+
Review comment:
Remove double 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
> [TC Bot] Add comparison of failed tests lists in two date intervals
> ---
>
> Key: IGNITE-9645
> URL: https://issues.apache.org/jira/browse/IGNITE-9645
> Project: Ignite
> Issue Type: Task
>Reporter: PetrovMikhail
>Assignee: PetrovMikhail
>Priority: Major
>
> Based on [IGNITE-9541|https://issues.apache.org/jira/browse/IGNITE-9541] It's
> needed to add comparison of failed tests lists in two date intervals
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9645) [TC Bot] Add comparison of failed tests lists in two date intervals
[
https://issues.apache.org/jira/browse/IGNITE-9645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16636976#comment-16636976
]
ASF GitHub Bot commented on IGNITE-9645:
SomeFire commented on a change in pull request #25: IGNITE-9645 [TC Bot] Add
comparison of failed tests lists in two date intervals
URL: https://github.com/apache/ignite-teamcity-bot/pull/25#discussion_r89864
##
File path: ignite-tc-helper-web/src/main/webapp/comparison.html
##
@@ -173,6 +178,176 @@
return parseFloat(string.substring(string.indexOf("-") + 2,
string.lastIndexOf("-") - 1));
}
+var ch_disp = function(id) {
+let el = document.getElementById(id);
+
+el.style.display = el.style.display == 'block' ? 'none' : 'block';
+}
+
+function printTests(num, result) {
+let obj = {};
+
+try {
+obj = JSON.parse(result);
+} catch (e) {
+showErrInLoadStatus
+
+return;
+}
+
+if (obj == null)
+return;
+
+let tests = getTests(obj, num);
+
+window.sessionStorage.setItem('tests' + num, tests);
+
+$('#MT' + num).html(tests);
+}
+
+function compareHandler() {
+var compareMode = window.sessionStorage.compareMode;
+
+var needTestsUpdate = window.sessionStorage.needTestsUpdate;
+
+if (needTestsUpdate == 'true') {
+let result1 = window.sessionStorage.result1;
+
+let result2 = window.sessionStorage.result2;
+
+if (result1 == null || result2 == null) {
+alert("Two columns should be loaded for compareMode!");
+
+return;
+}
+
+let obj1 = {};
+
+let obj2 = {};
+
+try {
+obj1 = JSON.parse(result1);
+
+obj2 = JSON.parse(result2);
+} catch (e) {
+showErrInLoadStatus
+}
+
+window.sessionStorage.uniqTests1 = getUniqueTests(obj1, obj2, 1);
+
+window.sessionStorage.uniqTests2 = getUniqueTests(obj2, obj1, 2);
+
+window.sessionStorage.needTestsUpdate = 'false';
+}
+
+if (compareMode == 'true') {
+$('#btt').html("CompareMode");
+
+$('#MT1').html(window.sessionStorage.tests1);
+
+$('#MT2').html(window.sessionStorage.tests2);
+
+window.sessionStorage.compareMode = 'false';
+} else {
+$('#btt').html("FullMode");
+
+$('#MT1').html(window.sessionStorage.uniqTests1);
+
+$('#MT2').html(window.sessionStorage.uniqTests2);
+
+window.sessionStorage.compareMode = 'true';
+}
+
+}
+
+function getUniqueTests(obj1, obj2, num) {
+let uniqObj = {};
+
+let suites = Object.keys(obj1);
+
+for (let suite of suites) {
+if (!obj2.hasOwnProperty(suite)) {
+uniqObj[suite] = obj1[suite];
+
+continue;
+}
+
+let tests = obj2[suite];
+
+let uniqTests = [];
+
+for (let v of obj1[suite])
+if (!tests.includes(v, 0))
+uniqTests.push(v);
+
+if (uniqTests.length != 0)
+uniqObj[suite] = uniqTests;
+}
+
+return getTests(uniqObj, num);
+}
+
+function getTests(obj, num) {
+let res = '';
+
+let suites = Object.keys(obj).sort();
+
+for (let suite of suites) {
+let suiteName = suite.split('_').filter((value, index) => index !=
0).join('_');
+
+res += '' + suiteName + '' + ' (' + obj[suite].length +
')' +
+'\n' +
+'';
+
+for (let v of obj[suite].sort()) {
+let list = v.toString().split(".");
+
+if (list.length < 2)
+list = v.toString().split(":");
+
+let testName = list.pop();
+
+let testClass = list.pop();
+
+res += ''
++ testClass + '.' + testName + ' ' +
+'' +
+'' +
+''
+}
+
+res += '';
+}
+
+res += '';
+
+return res;
+}
+
+function getTestRef(testName) {
+let res = '';
+
+$.ajax(
+{
Review comment:
Move to previous 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
> [TC Bot] Add comparison of failed tests lists in two date intervals
> ---
>
> Key: IGNITE-9645
>
[jira] [Commented] (IGNITE-9645) [TC Bot] Add comparison of failed tests lists in two date intervals
[ https://issues.apache.org/jira/browse/IGNITE-9645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16636974#comment-16636974 ] ASF GitHub Bot commented on IGNITE-9645: SomeFire commented on a change in pull request #25: IGNITE-9645 [TC Bot] Add comparison of failed tests lists in two date intervals URL: https://github.com/apache/ignite-teamcity-bot/pull/25#discussion_r63950 ## File path: ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/web/model/hist/BuildsHistory.java ## @@ -0,0 +1,209 @@ +package org.apache.ignite.ci.web.model.hist; Review comment: Missed license and javadocs. 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] Add comparison of failed tests lists in two date intervals > --- > > Key: IGNITE-9645 > URL: https://issues.apache.org/jira/browse/IGNITE-9645 > Project: Ignite > Issue Type: Task >Reporter: PetrovMikhail >Assignee: PetrovMikhail >Priority: Major > > Based on [IGNITE-9541|https://issues.apache.org/jira/browse/IGNITE-9541] It's > needed to add comparison of failed tests lists in two date intervals -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9645) [TC Bot] Add comparison of failed tests lists in two date intervals
[
https://issues.apache.org/jira/browse/IGNITE-9645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16636977#comment-16636977
]
ASF GitHub Bot commented on IGNITE-9645:
SomeFire commented on a change in pull request #25: IGNITE-9645 [TC Bot] Add
comparison of failed tests lists in two date intervals
URL: https://github.com/apache/ignite-teamcity-bot/pull/25#discussion_r85591
##
File path: ignite-tc-helper-web/src/main/webapp/comparison.html
##
@@ -173,6 +178,176 @@
return parseFloat(string.substring(string.indexOf("-") + 2,
string.lastIndexOf("-") - 1));
}
+var ch_disp = function(id) {
+let el = document.getElementById(id);
+
+el.style.display = el.style.display == 'block' ? 'none' : 'block';
+}
+
+function printTests(num, result) {
+let obj = {};
+
+try {
+obj = JSON.parse(result);
+} catch (e) {
+showErrInLoadStatus
Review comment:
String do nothing. This is not a method call.
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] Add comparison of failed tests lists in two date intervals
> ---
>
> Key: IGNITE-9645
> URL: https://issues.apache.org/jira/browse/IGNITE-9645
> Project: Ignite
> Issue Type: Task
>Reporter: PetrovMikhail
>Assignee: PetrovMikhail
>Priority: Major
>
> Based on [IGNITE-9541|https://issues.apache.org/jira/browse/IGNITE-9541] It's
> needed to add comparison of failed tests lists in two date intervals
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9645) [TC Bot] Add comparison of failed tests lists in two date intervals
[
https://issues.apache.org/jira/browse/IGNITE-9645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16636970#comment-16636970
]
ASF GitHub Bot commented on IGNITE-9645:
SomeFire commented on a change in pull request #25: IGNITE-9645 [TC Bot] Add
comparison of failed tests lists in two date intervals
URL: https://github.com/apache/ignite-teamcity-bot/pull/25#discussion_r222307517
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/web/rest/build/GetBuildTestFailures.java
##
@@ -159,75 +156,59 @@ public TestFailuresSummary getBuildTestFails(
}
@GET
-@Path("history")
-public List getBuildsHistory(
-@Nullable @QueryParam("server") String srv,
-@Nullable @QueryParam("buildType") String buildType,
-@Nullable @QueryParam("branch") String branch,
-@Nullable @QueryParam("sinceDate") String sinceDate,
-@Nullable @QueryParam("untilDate") String untilDate)
-throws ServiceUnauthorizedException {
-String srvId = isNullOrEmpty(srv) ? "apache" : srv;
-String buildTypeId = isNullOrEmpty(buildType) ?
"IgniteTests24Java8_RunAll" : buildType;
-String branchName = isNullOrEmpty(branch) ? "refs/heads/master" :
branch;
-Date sinceDateFilter = isNullOrEmpty(sinceDate) ? null :
dateParse(sinceDate);
-Date untilDateFilter = isNullOrEmpty(untilDate) ? null :
dateParse(untilDate);
-
-final BackgroundUpdater updater =
CtxListener.getBackgroundUpdater(ctx);
-
-final ITcHelper tcHelper = CtxListener.getTcHelper(ctx);
+@Produces(MediaType.TEXT_PLAIN)
+@Path("testRef")
+public String getTestRef(
+@NotNull @QueryParam("testName") String name,
+@Nullable @QueryParam("server") String server,
+@Nullable @QueryParam("projectId") String projectId)
+throws InterruptedException, ExecutionException {
+final ITcHelper helper = CtxListener.getTcHelper(ctx);
final ICredentialsProv prov = ICredentialsProv.get(req);
-IAnalyticsEnabledTeamcity teamcity = tcHelper.server(srvId, prov);
-
-int[] finishedBuilds =
teamcity.getBuildNumbersFromHistory(buildTypeId, branchName, sinceDateFilter,
untilDateFilter);
+String project = projectId == null ? "IgniteTests24Java8" : projectId;
Review comment:
Missed authorization check.
```
if (!prov.hasAccess(serverId))
throw ServiceUnauthorizedException.noCreds(serverId);
```
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] Add comparison of failed tests lists in two date intervals
> ---
>
> Key: IGNITE-9645
> URL: https://issues.apache.org/jira/browse/IGNITE-9645
> Project: Ignite
> Issue Type: Task
>Reporter: PetrovMikhail
>Assignee: PetrovMikhail
>Priority: Major
>
> Based on [IGNITE-9541|https://issues.apache.org/jira/browse/IGNITE-9541] It's
> needed to add comparison of failed tests lists in two date intervals
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9645) [TC Bot] Add comparison of failed tests lists in two date intervals
[
https://issues.apache.org/jira/browse/IGNITE-9645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16636979#comment-16636979
]
ASF GitHub Bot commented on IGNITE-9645:
SomeFire commented on a change in pull request #25: IGNITE-9645 [TC Bot] Add
comparison of failed tests lists in two date intervals
URL: https://github.com/apache/ignite-teamcity-bot/pull/25#discussion_r222307974
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/web/rest/build/GetBuildTestFailures.java
##
@@ -159,75 +156,59 @@ public TestFailuresSummary getBuildTestFails(
}
@GET
-@Path("history")
-public List getBuildsHistory(
-@Nullable @QueryParam("server") String srv,
-@Nullable @QueryParam("buildType") String buildType,
-@Nullable @QueryParam("branch") String branch,
-@Nullable @QueryParam("sinceDate") String sinceDate,
-@Nullable @QueryParam("untilDate") String untilDate)
-throws ServiceUnauthorizedException {
-String srvId = isNullOrEmpty(srv) ? "apache" : srv;
-String buildTypeId = isNullOrEmpty(buildType) ?
"IgniteTests24Java8_RunAll" : buildType;
-String branchName = isNullOrEmpty(branch) ? "refs/heads/master" :
branch;
-Date sinceDateFilter = isNullOrEmpty(sinceDate) ? null :
dateParse(sinceDate);
-Date untilDateFilter = isNullOrEmpty(untilDate) ? null :
dateParse(untilDate);
-
-final BackgroundUpdater updater =
CtxListener.getBackgroundUpdater(ctx);
-
-final ITcHelper tcHelper = CtxListener.getTcHelper(ctx);
+@Produces(MediaType.TEXT_PLAIN)
+@Path("testRef")
+public String getTestRef(
+@NotNull @QueryParam("testName") String name,
+@Nullable @QueryParam("server") String server,
Review comment:
Rename variable to `srv`. See [abbreviation
rules](https://cwiki.apache.org/confluence/display/IGNITE/Abbreviation+Rules).
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] Add comparison of failed tests lists in two date intervals
> ---
>
> Key: IGNITE-9645
> URL: https://issues.apache.org/jira/browse/IGNITE-9645
> Project: Ignite
> Issue Type: Task
>Reporter: PetrovMikhail
>Assignee: PetrovMikhail
>Priority: Major
>
> Based on [IGNITE-9541|https://issues.apache.org/jira/browse/IGNITE-9541] It's
> needed to add comparison of failed tests lists in two date intervals
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9645) [TC Bot] Add comparison of failed tests lists in two date intervals
[ https://issues.apache.org/jira/browse/IGNITE-9645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16636967#comment-16636967 ] ASF GitHub Bot commented on IGNITE-9645: SomeFire commented on a change in pull request #25: IGNITE-9645 [TC Bot] Add comparison of failed tests lists in two date intervals URL: https://github.com/apache/ignite-teamcity-bot/pull/25#discussion_r68058 ## File path: ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/IgniteTeamcityConnection.java ## @@ -42,12 +42,15 @@ import org.apache.ignite.ci.tcmodel.result.issues.IssuesUsagesList; import org.apache.ignite.ci.tcmodel.result.problems.ProblemOccurrences; import org.apache.ignite.ci.tcmodel.result.stat.Statistics; +import org.apache.ignite.ci.tcmodel.result.tests.TestOccurrence; Review comment: Unused import. 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] Add comparison of failed tests lists in two date intervals > --- > > Key: IGNITE-9645 > URL: https://issues.apache.org/jira/browse/IGNITE-9645 > Project: Ignite > Issue Type: Task >Reporter: PetrovMikhail >Assignee: PetrovMikhail >Priority: Major > > Based on [IGNITE-9541|https://issues.apache.org/jira/browse/IGNITE-9541] It's > needed to add comparison of failed tests lists in two date intervals -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9645) [TC Bot] Add comparison of failed tests lists in two date intervals
[ https://issues.apache.org/jira/browse/IGNITE-9645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16636968#comment-16636968 ] ASF GitHub Bot commented on IGNITE-9645: SomeFire commented on a change in pull request #25: IGNITE-9645 [TC Bot] Add comparison of failed tests lists in two date intervals URL: https://github.com/apache/ignite-teamcity-bot/pull/25#discussion_r222308185 ## File path: ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/web/rest/build/GetBuildTestFailures.java ## @@ -46,16 +50,9 @@ import javax.ws.rs.QueryParam; import javax.ws.rs.core.Context; import javax.ws.rs.core.MediaType; -import java.util.ArrayList; import java.util.Collections; -import java.util.List; -import java.util.Date; +import java.util.Optional; Review comment: Unused import. 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] Add comparison of failed tests lists in two date intervals > --- > > Key: IGNITE-9645 > URL: https://issues.apache.org/jira/browse/IGNITE-9645 > Project: Ignite > Issue Type: Task >Reporter: PetrovMikhail >Assignee: PetrovMikhail >Priority: Major > > Based on [IGNITE-9541|https://issues.apache.org/jira/browse/IGNITE-9541] It's > needed to add comparison of failed tests lists in two date intervals -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9645) [TC Bot] Add comparison of failed tests lists in two date intervals
[
https://issues.apache.org/jira/browse/IGNITE-9645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16636971#comment-16636971
]
ASF GitHub Bot commented on IGNITE-9645:
SomeFire commented on a change in pull request #25: IGNITE-9645 [TC Bot] Add
comparison of failed tests lists in two date intervals
URL: https://github.com/apache/ignite-teamcity-bot/pull/25#discussion_r90983
##
File path: ignite-tc-helper-web/src/main/webapp/comparison.html
##
@@ -247,6 +422,7 @@
$(document).ready(function() {
loadData(1, moment(oneWeekAgo), moment());
+
Review comment:
Don't separate same semantic units.
See [Coding
Guidelines](https://cwiki.apache.org/confluence/display/IGNITE/Coding+Guidelines#CodingGuidelines-SemanticUnits).
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] Add comparison of failed tests lists in two date intervals
> ---
>
> Key: IGNITE-9645
> URL: https://issues.apache.org/jira/browse/IGNITE-9645
> Project: Ignite
> Issue Type: Task
>Reporter: PetrovMikhail
>Assignee: PetrovMikhail
>Priority: Major
>
> Based on [IGNITE-9541|https://issues.apache.org/jira/browse/IGNITE-9541] It's
> needed to add comparison of failed tests lists in two date intervals
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9645) [TC Bot] Add comparison of failed tests lists in two date intervals
[
https://issues.apache.org/jira/browse/IGNITE-9645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16636975#comment-16636975
]
ASF GitHub Bot commented on IGNITE-9645:
SomeFire commented on a change in pull request #25: IGNITE-9645 [TC Bot] Add
comparison of failed tests lists in two date intervals
URL: https://github.com/apache/ignite-teamcity-bot/pull/25#discussion_r89732
##
File path: ignite-tc-helper-web/src/main/webapp/comparison.html
##
@@ -173,6 +178,176 @@
return parseFloat(string.substring(string.indexOf("-") + 2,
string.lastIndexOf("-") - 1));
}
+var ch_disp = function(id) {
+let el = document.getElementById(id);
+
+el.style.display = el.style.display == 'block' ? 'none' : 'block';
+}
+
+function printTests(num, result) {
+let obj = {};
+
+try {
+obj = JSON.parse(result);
+} catch (e) {
+showErrInLoadStatus
+
+return;
+}
+
+if (obj == null)
+return;
+
+let tests = getTests(obj, num);
+
+window.sessionStorage.setItem('tests' + num, tests);
+
+$('#MT' + num).html(tests);
+}
+
+function compareHandler() {
+var compareMode = window.sessionStorage.compareMode;
+
+var needTestsUpdate = window.sessionStorage.needTestsUpdate;
+
+if (needTestsUpdate == 'true') {
+let result1 = window.sessionStorage.result1;
+
+let result2 = window.sessionStorage.result2;
+
+if (result1 == null || result2 == null) {
+alert("Two columns should be loaded for compareMode!");
+
+return;
+}
+
+let obj1 = {};
+
+let obj2 = {};
+
+try {
+obj1 = JSON.parse(result1);
+
+obj2 = JSON.parse(result2);
+} catch (e) {
+showErrInLoadStatus
+}
+
+window.sessionStorage.uniqTests1 = getUniqueTests(obj1, obj2, 1);
+
+window.sessionStorage.uniqTests2 = getUniqueTests(obj2, obj1, 2);
+
+window.sessionStorage.needTestsUpdate = 'false';
+}
+
+if (compareMode == 'true') {
+$('#btt').html("CompareMode");
+
+$('#MT1').html(window.sessionStorage.tests1);
+
+$('#MT2').html(window.sessionStorage.tests2);
+
+window.sessionStorage.compareMode = 'false';
+} else {
+$('#btt').html("FullMode");
+
+$('#MT1').html(window.sessionStorage.uniqTests1);
+
+$('#MT2').html(window.sessionStorage.uniqTests2);
+
+window.sessionStorage.compareMode = 'true';
+}
+
+}
+
+function getUniqueTests(obj1, obj2, num) {
+let uniqObj = {};
+
+let suites = Object.keys(obj1);
+
+for (let suite of suites) {
+if (!obj2.hasOwnProperty(suite)) {
+uniqObj[suite] = obj1[suite];
+
+continue;
+}
+
+let tests = obj2[suite];
+
+let uniqTests = [];
+
+for (let v of obj1[suite])
Review comment:
Need bracers for multiline `for`.
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] Add comparison of failed tests lists in two date intervals
> ---
>
> Key: IGNITE-9645
> URL: https://issues.apache.org/jira/browse/IGNITE-9645
> Project: Ignite
> Issue Type: Task
>Reporter: PetrovMikhail
>Assignee: PetrovMikhail
>Priority: Major
>
> Based on [IGNITE-9541|https://issues.apache.org/jira/browse/IGNITE-9541] It's
> needed to add comparison of failed tests lists in two date intervals
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9645) [TC Bot] Add comparison of failed tests lists in two date intervals
[
https://issues.apache.org/jira/browse/IGNITE-9645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16636969#comment-16636969
]
ASF GitHub Bot commented on IGNITE-9645:
SomeFire commented on a change in pull request #25: IGNITE-9645 [TC Bot] Add
comparison of failed tests lists in two date intervals
URL: https://github.com/apache/ignite-teamcity-bot/pull/25#discussion_r63852
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/tcmodel/result/tests/TestOccurrence.java
##
@@ -98,4 +98,15 @@ public TestOccurrence setStatus(String status) {
return this;
}
+
+public Integer getBuildId() {
Review comment:
Missed javadoc.
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] Add comparison of failed tests lists in two date intervals
> ---
>
> Key: IGNITE-9645
> URL: https://issues.apache.org/jira/browse/IGNITE-9645
> Project: Ignite
> Issue Type: Task
>Reporter: PetrovMikhail
>Assignee: PetrovMikhail
>Priority: Major
>
> Based on [IGNITE-9541|https://issues.apache.org/jira/browse/IGNITE-9541] It's
> needed to add comparison of failed tests lists in two date intervals
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9645) [TC Bot] Add comparison of failed tests lists in two date intervals
[
https://issues.apache.org/jira/browse/IGNITE-9645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16636973#comment-16636973
]
ASF GitHub Bot commented on IGNITE-9645:
SomeFire commented on a change in pull request #25: IGNITE-9645 [TC Bot] Add
comparison of failed tests lists in two date intervals
URL: https://github.com/apache/ignite-teamcity-bot/pull/25#discussion_r71593
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/IgniteTeamcityConnection.java
##
@@ -542,6 +545,19 @@ public ProblemOccurrences getProblems(Build build) {
return supplyAsync(() -> getJaxbUsingHref(href,
TestOccurrenceFull.class), executor);
}
+@AutoProfiling
+@Override public TestOccurrences getFailedUnmutedTests(String href, int
count, String normalizedBranch) {
+return getTests(href + ",muted:false,status:FAILURE,count:" + count,
normalizedBranch);
+}
+
+@Override
Review comment:
`Override` annotation should be on the same line with method signature.
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] Add comparison of failed tests lists in two date intervals
> ---
>
> Key: IGNITE-9645
> URL: https://issues.apache.org/jira/browse/IGNITE-9645
> Project: Ignite
> Issue Type: Task
>Reporter: PetrovMikhail
>Assignee: PetrovMikhail
>Priority: Major
>
> Based on [IGNITE-9541|https://issues.apache.org/jira/browse/IGNITE-9541] It's
> needed to add comparison of failed tests lists in two date intervals
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9645) [TC Bot] Add comparison of failed tests lists in two date intervals
[ https://issues.apache.org/jira/browse/IGNITE-9645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16636972#comment-16636972 ] ASF GitHub Bot commented on IGNITE-9645: SomeFire commented on a change in pull request #25: IGNITE-9645 [TC Bot] Add comparison of failed tests lists in two date intervals URL: https://github.com/apache/ignite-teamcity-bot/pull/25#discussion_r78498 ## File path: ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/IgnitePersistentTeamcity.java ## @@ -125,6 +128,11 @@ */ private ConcurrentMap> testOccFullFutures = new ConcurrentHashMap<>(); +/** + * cached loads of test refs. Review comment: Start sentence with a capital letter. 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] Add comparison of failed tests lists in two date intervals > --- > > Key: IGNITE-9645 > URL: https://issues.apache.org/jira/browse/IGNITE-9645 > Project: Ignite > Issue Type: Task >Reporter: PetrovMikhail >Assignee: PetrovMikhail >Priority: Major > > Based on [IGNITE-9541|https://issues.apache.org/jira/browse/IGNITE-9541] It's > needed to add comparison of failed tests lists in two date intervals -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9619) Document REST "getall" array format
[ https://issues.apache.org/jira/browse/IGNITE-9619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Kasnacheev reassigned IGNITE-9619: --- Assignee: Ilya Kasnacheev > Document REST "getall" array format > --- > > Key: IGNITE-9619 > URL: https://issues.apache.org/jira/browse/IGNITE-9619 > Project: Ignite > Issue Type: Improvement > Components: documentation >Reporter: Ilya Kasnacheev >Assignee: Ilya Kasnacheev >Priority: Minor > Labels: documentation > Fix For: 2.7 > > > https://apacheignite.readme.io/docs/rest-api#get-all <-- this page should > have a section about new IGNITE_REST_GETALL_AS_ARRAY System Property, as well > as an example of response after it is set. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9619) Document REST "getall" array format
[ https://issues.apache.org/jira/browse/IGNITE-9619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Kasnacheev reassigned IGNITE-9619: --- Assignee: Prachi Garg (was: Ilya Kasnacheev) > Document REST "getall" array format > --- > > Key: IGNITE-9619 > URL: https://issues.apache.org/jira/browse/IGNITE-9619 > Project: Ignite > Issue Type: Improvement > Components: documentation >Reporter: Ilya Kasnacheev >Assignee: Prachi Garg >Priority: Minor > Labels: documentation > Fix For: 2.7 > > > https://apacheignite.readme.io/docs/rest-api#get-all <-- this page should > have a section about new IGNITE_REST_GETALL_AS_ARRAY System Property, as well > as an example of response after it is set. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-9606) JDBC getPrimaryKeys() returns wrong value for COLUMN_NAME
[
https://issues.apache.org/jira/browse/IGNITE-9606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16636941#comment-16636941
]
Pavel Kuznetsov edited comment on IGNITE-9606 at 10/3/18 1:24 PM:
--
I've written test that reproduced the bug, have fixed existing one and have
done prelementary fix.
https://github.com/apache/ignite/pull/4906/
[~tledkov-gridgain] Could you please take a look at the patch?
was (Author: pkouznet):
I've written test that reproduced the bug, have fixed existing one and have
done prelementary fix.
https://github.com/apache/ignite/pull/4906/
[~tledkov-gridgain]
> JDBC getPrimaryKeys() returns wrong value for COLUMN_NAME
> -
>
> Key: IGNITE-9606
> URL: https://issues.apache.org/jira/browse/IGNITE-9606
> Project: Ignite
> Issue Type: Bug
> Components: jdbc
>Affects Versions: 2.6
>Reporter: Pat Patterson
>Assignee: Pavel Kuznetsov
>Priority: Major
> Fix For: 2.8
>
>
> JDBC {{getPrimaryKeys()}} method returns {{_KEY}} as column name rather than
> actual column name. This breaks apps that expect a valid column name as the
> primary key.
> Trivially reproducible:
> {noformat}
> public static void main(String[] args) throws Exception {
> // Register JDBC driver.
> Class.forName("org.apache.ignite.IgniteJdbcThinDriver");
> // Open JDBC connection.
> try (Connection conn =
> DriverManager.getConnection("jdbc:ignite:thin://127.0.0.1/")) {
> // Create database tables.
> try (Statement stmt = conn.createStatement()) {
> stmt.executeUpdate("CREATE TABLE TESTER (" + " ID LONG PRIMARY KEY,
> NAME VARCHAR) " + " WITH \"template=replicated\"");
> }
> // Get database metadata
> DatabaseMetaData md = conn.getMetaData();
> // Get primary keys
> ResultSet rs = md.getPrimaryKeys(conn.getCatalog(), "", "TESTER");
> //
> while (rs.next()) {
> // Column 4 is COLUMN_NAME
> System.out.println("Primary key column is " + rs.getString(4));
> }
> }
> }
> {noformat}
> Expected output is:
> {noformat}
> Primary key column is ID
> {noformat}
> Actual output is:
> {noformat}
> Primary key column is _KEY
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9606) JDBC getPrimaryKeys() returns wrong value for COLUMN_NAME
[
https://issues.apache.org/jira/browse/IGNITE-9606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16636935#comment-16636935
]
ASF GitHub Bot commented on IGNITE-9606:
GitHub user pavel-kuznetsov opened a pull request:
https://github.com/apache/ignite/pull/4906
IGNITE-9606: JDBC getPrimaryKeys() returns wrong value for COLUMN_NAME
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9606
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4906.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 #4906
commit 5d144b2f57933b96dc4ccb68be119f7c205bb6f7
Author: Pavel Kuznetsov
Date: 2018-10-02T14:43:31Z
ignite-9606: Added test that reproduces the bug.
commit 0bf7d1c8265e681cdc5ea8b7d27c013844724be6
Author: Pavel Kuznetsov
Date: 2018-10-03T13:02:42Z
ignite-9606: fixed COLUMN_NAME metadata result.
Earlier, if key was of SQL type (so not wrapped), corresponding property
thought that it is not a key. This behaviour affected what COLUMN_NAME JDBC
metadata would contain.
> JDBC getPrimaryKeys() returns wrong value for COLUMN_NAME
> -
>
> Key: IGNITE-9606
> URL: https://issues.apache.org/jira/browse/IGNITE-9606
> Project: Ignite
> Issue Type: Bug
> Components: jdbc
>Affects Versions: 2.6
>Reporter: Pat Patterson
>Assignee: Pavel Kuznetsov
>Priority: Major
> Fix For: 2.8
>
>
> JDBC {{getPrimaryKeys()}} method returns {{_KEY}} as column name rather than
> actual column name. This breaks apps that expect a valid column name as the
> primary key.
> Trivially reproducible:
> {noformat}
> public static void main(String[] args) throws Exception {
> // Register JDBC driver.
> Class.forName("org.apache.ignite.IgniteJdbcThinDriver");
> // Open JDBC connection.
> try (Connection conn =
> DriverManager.getConnection("jdbc:ignite:thin://127.0.0.1/")) {
> // Create database tables.
> try (Statement stmt = conn.createStatement()) {
> stmt.executeUpdate("CREATE TABLE TESTER (" + " ID LONG PRIMARY KEY,
> NAME VARCHAR) " + " WITH \"template=replicated\"");
> }
> // Get database metadata
> DatabaseMetaData md = conn.getMetaData();
> // Get primary keys
> ResultSet rs = md.getPrimaryKeys(conn.getCatalog(), "", "TESTER");
> //
> while (rs.next()) {
> // Column 4 is COLUMN_NAME
> System.out.println("Primary key column is " + rs.getString(4));
> }
> }
> }
> {noformat}
> Expected output is:
> {noformat}
> Primary key column is ID
> {noformat}
> Actual output is:
> {noformat}
> Primary key column is _KEY
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9750) Prohibit near cache configuration for MVCC caches
[ https://issues.apache.org/jira/browse/IGNITE-9750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-9750: Ignite Flags: (was: Docs Required) > Prohibit near cache configuration for MVCC caches > - > > Key: IGNITE-9750 > URL: https://issues.apache.org/jira/browse/IGNITE-9750 > Project: Ignite > Issue Type: Task > Components: mvcc >Reporter: Ivan Pavlukhin >Assignee: Vladimir Ozerov >Priority: Major > Fix For: 2.7 > > > We should throw an exception when near cache is configured for MVCC cache. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9750) Prohibit near cache configuration for MVCC caches
[ https://issues.apache.org/jira/browse/IGNITE-9750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16636923#comment-16636923 ] ASF GitHub Bot commented on IGNITE-9750: Github user devozerov closed the pull request at: https://github.com/apache/ignite/pull/4891 > Prohibit near cache configuration for MVCC caches > - > > Key: IGNITE-9750 > URL: https://issues.apache.org/jira/browse/IGNITE-9750 > Project: Ignite > Issue Type: Task > Components: mvcc >Reporter: Ivan Pavlukhin >Assignee: Vladimir Ozerov >Priority: Major > Fix For: 2.7 > > > We should throw an exception when near cache is configured for MVCC cache. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9719) Extra rebalanceThreadPoolSize check on client node.
[ https://issues.apache.org/jira/browse/IGNITE-9719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16636917#comment-16636917 ] ASF GitHub Bot commented on IGNITE-9719: GitHub user luchnikovbsk opened a pull request: https://github.com/apache/ignite/pull/4905 IGNITE-9719 Extra rebalanceThreadPoolSize check on client node You can merge this pull request into a Git repository by running: $ git pull https://github.com/luchnikovbsk/ignite ignite-9719 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4905.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 #4905 commit 6f5a78d5d0c7ed3489f6acdcaf9db5304cad78f2 Author: luchnikovnsk Date: 2018-10-03T12:45:22Z IGNITE-9719 Extra rebalanceThreadPoolSize check on client node > Extra rebalanceThreadPoolSize check on client node. > --- > > Key: IGNITE-9719 > URL: https://issues.apache.org/jira/browse/IGNITE-9719 > Project: Ignite > Issue Type: Bug > Components: clients >Affects Versions: 2.6 >Reporter: Stanilovsky Evgeny >Assignee: Luchnikov Alexander >Priority: Minor > Fix For: 2.8 > > > No need to check rebalance thread pool size on client side in > IgniteKernal#ackRebalanceConfiguration method. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9783) MVCC: Track all nodes participating in transaction
[ https://issues.apache.org/jira/browse/IGNITE-9783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16636911#comment-16636911 ] ASF GitHub Bot commented on IGNITE-9783: GitHub user pavlukhin opened a pull request: https://github.com/apache/ignite/pull/4904 IGNITE-9783: MVCC: Track all nodes participating in transaction You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9783 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4904.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 #4904 commit 77dc283027793bee8831fe75c8947a825f81a539 Author: ipavlukhin Date: 2018-09-28T14:50:59Z accumulate backups participating in transaction in GridDistributedTxMapping, retrieve them from received enlist response commit 781dab6e0a2068acaaf859f4848f35c52327cc4f Author: ipavlukhin Date: 2018-09-28T15:14:11Z GridDistributedTxMapping normalize null backups to empty list commit 090d17e40e56f45258a5a3f27c4da6e065343ed9 Author: ipavlukhin Date: 2018-09-28T15:32:01Z pass backups to transaction mappings upon receiving response in GridNearTxEnlistFuture commit 0d2446b27da80944d203cfd3c8a218a6904daa1c Author: ipavlukhin Date: 2018-09-28T15:36:28Z putIfAbsent -> put commit 8d3eb13b40ba1bcd3fa70fa6af4c7af5ed521454 Author: ipavlukhin Date: 2018-09-28T15:48:16Z remove outdated todo commit 36a22a8b0ffc487dd47ab430057d185afdb81da9 Author: ipavlukhin Date: 2018-09-28T16:05:52Z make backups in GridDistributedTxMapping thread-safe commit 3ff50a1d2553d249f30858b478fc89986f344f8e Author: ipavlukhin Date: 2018-09-28T16:07:41Z add draft of a test commit 9087ab222ad5b5ef41cb3ed5183d88ba5a141a77 Author: ipavlukhin Date: 2018-10-01T13:26:10Z fix NPE occurring when enlist operation is finished by exception and response is null commit caafe2fbad8c09fd07e5e8d1a5ed39c55aac0d7d Author: ipavlukhin Date: 2018-10-02T05:30:54Z Merge branch 'master' into ignite-5935 commit 8329bf39dcf83e65f44c69766b75a8d018da4191 Author: ipavlukhin Date: 2018-10-02T08:10:45Z factor CacheMvccTxNodeMappingTest and add it to suite commit 5866adc686ff6521bbed443e48d54a8e18fddd19 Author: ipavlukhin Date: 2018-10-02T08:21:13Z test scenarios when near tx node is server commit 3d080c08d17c34369d4cccb7b01e5767a32d03c0 Author: ipavlukhin Date: 2018-10-02T12:34:50Z fail troublesome test commit 37c4bfb62af9685e9179e1de1fa27913bb4e326c Author: ipavlukhin Date: 2018-10-03T07:50:36Z fail hanging issue with a ticket > MVCC: Track all nodes participating in transaction > -- > > Key: IGNITE-9783 > URL: https://issues.apache.org/jira/browse/IGNITE-9783 > Project: Ignite > Issue Type: Bug > Components: mvcc >Reporter: Ivan Pavlukhin >Assignee: Ivan Pavlukhin >Priority: Major > Fix For: 2.7 > > > All nodes should be tracked by near tx in order to make recovery possible. > Backup nodes should be tracked as well. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9540) MVCC TX: make cache invoke\invokeAll operations support Mvcc tx mode.
[
https://issues.apache.org/jira/browse/IGNITE-9540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16636910#comment-16636910
]
ASF GitHub Bot commented on IGNITE-9540:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4832
> MVCC TX: make cache invoke\invokeAll operations support Mvcc tx mode.
> -
>
> Key: IGNITE-9540
> URL: https://issues.apache.org/jira/browse/IGNITE-9540
> Project: Ignite
> Issue Type: Task
> Components: cache, mvcc
>Reporter: Andrew Mashenkov
>Assignee: Vladimir Ozerov
>Priority: Major
> Fix For: 2.7
>
>
> {color:#FF}{color}Make invoke/invokeAll operations consistent with SQL
> queries in MVCC mode.
> This requires changes in protocol.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-9783) MVCC: Track all nodes participating in transaction
[ https://issues.apache.org/jira/browse/IGNITE-9783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Pavlukhin reassigned IGNITE-9783: -- Assignee: Ivan Pavlukhin > MVCC: Track all nodes participating in transaction > -- > > Key: IGNITE-9783 > URL: https://issues.apache.org/jira/browse/IGNITE-9783 > Project: Ignite > Issue Type: Bug > Components: mvcc >Reporter: Ivan Pavlukhin >Assignee: Ivan Pavlukhin >Priority: Major > Fix For: 2.7 > > > All nodes should be tracked by near tx in order to make recovery possible. > Backup nodes should be tracked as well. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9540) MVCC TX: make cache invoke\invokeAll operations support Mvcc tx mode.
[
https://issues.apache.org/jira/browse/IGNITE-9540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16636909#comment-16636909
]
ASF GitHub Bot commented on IGNITE-9540:
Github user devozerov closed the pull request at:
https://github.com/apache/ignite/pull/4881
> MVCC TX: make cache invoke\invokeAll operations support Mvcc tx mode.
> -
>
> Key: IGNITE-9540
> URL: https://issues.apache.org/jira/browse/IGNITE-9540
> Project: Ignite
> Issue Type: Task
> Components: cache, mvcc
>Reporter: Andrew Mashenkov
>Assignee: Vladimir Ozerov
>Priority: Major
> Fix For: 2.7
>
>
> {color:#FF}{color}Make invoke/invokeAll operations consistent with SQL
> queries in MVCC mode.
> This requires changes in protocol.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-5935) MVCC TX: Tx recovery protocol
[ https://issues.apache.org/jira/browse/IGNITE-5935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16636906#comment-16636906 ] ASF GitHub Bot commented on IGNITE-5935: Github user pavlukhin closed the pull request at: https://github.com/apache/ignite/pull/4873 > MVCC TX: Tx recovery protocol > - > > Key: IGNITE-5935 > URL: https://issues.apache.org/jira/browse/IGNITE-5935 > Project: Ignite > Issue Type: Task > Components: cache, mvcc >Reporter: Semen Boikov >Assignee: Ivan Pavlukhin >Priority: Major > Fix For: 2.7 > > > Transaction recovery procedure is initiated when near node failed before > transaction was finished. > In MVCC transactions _partition update counter_ modification is started on > prepare phase. If a transaction was prepared at least on one node we need to > finish _partition update counter_ modification consistently on all > participating nodes. > Also recovered transaction should be removed from active transactions list on > mvcc coordinator. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9783) MVCC: Track all nodes participating in transaction
Ivan Pavlukhin created IGNITE-9783: -- Summary: MVCC: Track all nodes participating in transaction Key: IGNITE-9783 URL: https://issues.apache.org/jira/browse/IGNITE-9783 Project: Ignite Issue Type: Bug Components: mvcc Reporter: Ivan Pavlukhin Fix For: 2.7 All nodes should be tracked by near tx in order to make recovery possible. Backup nodes should be tracked as well. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9750) Prohibit near cache configuration for MVCC caches
[ https://issues.apache.org/jira/browse/IGNITE-9750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16636905#comment-16636905 ] Vladimir Ozerov commented on IGNITE-9750: - Suspicious run: https://ci.ignite.apache.org/viewQueued.html?itemId=1996397 > Prohibit near cache configuration for MVCC caches > - > > Key: IGNITE-9750 > URL: https://issues.apache.org/jira/browse/IGNITE-9750 > Project: Ignite > Issue Type: Task > Components: mvcc >Reporter: Ivan Pavlukhin >Assignee: Vladimir Ozerov >Priority: Major > Fix For: 2.7 > > > We should throw an exception when near cache is configured for MVCC cache. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
