[jira] [Commented] (IGNITE-9596) Web console: invisible checkbox is visible
[ https://issues.apache.org/jira/browse/IGNITE-9596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16641301#comment-16641301 ] Pavel Konstantinov commented on IGNITE-9596: Tested on the branch with Firefox, Chrome, Edge, Safari. > Web console: invisible checkbox is visible > -- > > Key: IGNITE-9596 > URL: https://issues.apache.org/jira/browse/IGNITE-9596 > Project: Ignite > Issue Type: Bug > Components: wizards > Environment: Firefox, Chrome (macOS), Safari >Reporter: Ilya Borisov >Assignee: Pavel Konstantinov >Priority: Minor > Attachments: image-2018-09-14-10-58-23-054.png > > Original Estimate: 3h > Time Spent: 0.5h > Remaining Estimate: 2.5h > > How it looks: > !image-2018-09-14-10-58-23-054.png! > How to reproduce: > 1. Connect to a cluster > 2. Open queries > 3. Click "+Add scan" > 4. Scroll down to filter input with "Cs" appendix. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9596) Web console: invisible checkbox is visible
[ https://issues.apache.org/jira/browse/IGNITE-9596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov reassigned IGNITE-9596: -- Resolution: Fixed Assignee: Alexey Kuznetsov (was: Pavel Konstantinov) > Web console: invisible checkbox is visible > -- > > Key: IGNITE-9596 > URL: https://issues.apache.org/jira/browse/IGNITE-9596 > Project: Ignite > Issue Type: Bug > Components: wizards > Environment: Firefox, Chrome (macOS), Safari >Reporter: Ilya Borisov >Assignee: Alexey Kuznetsov >Priority: Minor > Attachments: image-2018-09-14-10-58-23-054.png > > Original Estimate: 3h > Time Spent: 0.5h > Remaining Estimate: 2.5h > > How it looks: > !image-2018-09-14-10-58-23-054.png! > How to reproduce: > 1. Connect to a cluster > 2. Open queries > 3. Click "+Add scan" > 4. Scroll down to filter input with "Cs" appendix. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9809) Web Console: Minor Fixes
Alexey Kuznetsov created IGNITE-9809: Summary: Web Console: Minor Fixes Key: IGNITE-9809 URL: https://issues.apache.org/jira/browse/IGNITE-9809 Project: Ignite Issue Type: Task Components: wizards Reporter: Alexey Kuznetsov Assignee: Alexey Kuznetsov Fix For: 2.8 We have a bunch of minor fixes: # Duration filter # i18n constants # Minor CSS tweaks # Minor code fixes -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8613) Web console: investigate E2E tests on Node.js 10
[ https://issues.apache.org/jira/browse/IGNITE-8613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16641322#comment-16641322 ] Andrey Novikov commented on IGNITE-8613: [~alexdel], please check e2e test under node 10 and latest version of testcafe docker image. > Web console: investigate E2E tests on Node.js 10 > > > Key: IGNITE-8613 > URL: https://issues.apache.org/jira/browse/IGNITE-8613 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Ilya Borisov >Assignee: Alexander Kalinin >Priority: Minor > > Web console E2E tests fail spontaneously when run under Node.js 10. We should > investigate what causes it: Testcafe incompatibility or something in the web > console code. If new, compatible version of Testcafe becomes available, let's > update to it as a part of this issue. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-8613) Web console: investigate E2E tests on Node.js 10
[ https://issues.apache.org/jira/browse/IGNITE-8613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Novikov reassigned IGNITE-8613: -- Assignee: Alexander Kalinin (was: Andrey Novikov) > Web console: investigate E2E tests on Node.js 10 > > > Key: IGNITE-8613 > URL: https://issues.apache.org/jira/browse/IGNITE-8613 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Ilya Borisov >Assignee: Alexander Kalinin >Priority: Minor > > Web console E2E tests fail spontaneously when run under Node.js 10. We should > investigate what causes it: Testcafe incompatibility or something in the web > console code. If new, compatible version of Testcafe becomes available, let's > update to it as a part of this issue. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9460) Update styles on WC top menu
[ https://issues.apache.org/jira/browse/IGNITE-9460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-9460: - Component/s: wizards > Update styles on WC top menu > > > Key: IGNITE-9460 > URL: https://issues.apache.org/jira/browse/IGNITE-9460 > Project: Ignite > Issue Type: Bug > Components: UI, wizards >Reporter: Alexander Kalinin >Assignee: Alexey Kuznetsov >Priority: Minor > Fix For: 2.8 > > Original Estimate: 2h > Time Spent: 1h > Remaining Estimate: 1h > > Accroding to design there should be no underlines on top menu. Let's remove > underline on focus. > !https://snag.gy/RBMZyn.jpg! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9460) Web console: Update styles of top menu items
[ https://issues.apache.org/jira/browse/IGNITE-9460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-9460: - Fix Version/s: 2.8 > Web console: Update styles of top menu items > > > Key: IGNITE-9460 > URL: https://issues.apache.org/jira/browse/IGNITE-9460 > Project: Ignite > Issue Type: Bug > Components: UI, wizards >Reporter: Alexander Kalinin >Assignee: Alexey Kuznetsov >Priority: Minor > Fix For: 2.8 > > Original Estimate: 2h > Time Spent: 1h > Remaining Estimate: 1h > > Accroding to design there should be no underlines on top menu. Let's remove > underline on focus. > !https://snag.gy/RBMZyn.jpg! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9460) Web console: Update styles of top menu items
[ https://issues.apache.org/jira/browse/IGNITE-9460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-9460: - Summary: Web console: Update styles of top menu items (was: Update styles on WC top menu) > Web console: Update styles of top menu items > > > Key: IGNITE-9460 > URL: https://issues.apache.org/jira/browse/IGNITE-9460 > Project: Ignite > Issue Type: Bug > Components: UI, wizards >Reporter: Alexander Kalinin >Assignee: Alexey Kuznetsov >Priority: Minor > Fix For: 2.8 > > Original Estimate: 2h > Time Spent: 1h > Remaining Estimate: 1h > > Accroding to design there should be no underlines on top menu. Let's remove > underline on focus. > !https://snag.gy/RBMZyn.jpg! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9808) Web Console: Refactor sockets caching
Alexey Kuznetsov created IGNITE-9808: Summary: Web Console: Refactor sockets caching Key: IGNITE-9808 URL: https://issues.apache.org/jira/browse/IGNITE-9808 Project: Ignite Issue Type: Task Components: wizards Reporter: Alexey Kuznetsov Assignee: Alexey Kuznetsov Fix For: 2.8 In current implementation we cache sockets by tokens, but token can be changed at any moment. It is better to use account ID as it can not be changed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-9808) Web Console: Refactor sockets caching
[ https://issues.apache.org/jira/browse/IGNITE-9808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-9808. > Web Console: Refactor sockets caching > - > > Key: IGNITE-9808 > URL: https://issues.apache.org/jira/browse/IGNITE-9808 > Project: Ignite > Issue Type: Task > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov >Priority: Major > Fix For: 2.8 > > > In current implementation we cache sockets by tokens, but token can be > changed at any moment. It is better to use account ID as it can not be > changed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-7623) Thin client Java API - async API
[ https://issues.apache.org/jira/browse/IGNITE-7623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16641380#comment-16641380 ] Ivan Artukhov edited comment on IGNITE-7623 at 10/8/18 5:52 AM: Current benchmarking results for Ignite native client vs thin client are as follows. Clients used 64 threads to generate load. 1) 1 server, 4 clients !Screenshot from 2018-10-08 08-49-22.png! 2) 4 servers, 8 clients !Screenshot from 2018-10-08 08-46-38.png! was (Author: artukhov): Current benchmarking results for Ignite native client vs thin client are as follows. Clients used 64 threads to generate load. 1) 1 server, 4 clients !Screenshot from 2018-10-08 08-49-22.png! 2) 4 servers, 8 clients !Screenshot from 2018-10-08 08-49-22.png! > Thin client Java API - async API > > > Key: IGNITE-7623 > URL: https://issues.apache.org/jira/browse/IGNITE-7623 > Project: Ignite > Issue Type: Task > Components: clients >Reporter: Alexey Kukushkin >Priority: Major > Labels: data, java, thin > Attachments: Screenshot from 2018-10-08 08-46-38.png, Screenshot from > 2018-10-08 08-49-22.png > > Original Estimate: 0.4h > Remaining Estimate: 0.4h > > Implement Async version of all the Java thin client APIs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7623) Thin client Java API - async API
[ https://issues.apache.org/jira/browse/IGNITE-7623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16641380#comment-16641380 ] Ivan Artukhov commented on IGNITE-7623: --- Current benchmarking results for Ignite native client vs thin client are as follows. Clients used 64 threads to generate load. 1) 1 server, 4 clients !Screenshot from 2018-10-08 08-49-22.png! 2) 4 servers, 8 clients !Screenshot from 2018-10-08 08-49-22.png! > Thin client Java API - async API > > > Key: IGNITE-7623 > URL: https://issues.apache.org/jira/browse/IGNITE-7623 > Project: Ignite > Issue Type: Task > Components: clients >Reporter: Alexey Kukushkin >Priority: Major > Labels: data, java, thin > Attachments: Screenshot from 2018-10-08 08-46-38.png, Screenshot from > 2018-10-08 08-49-22.png > > Original Estimate: 0.4h > Remaining Estimate: 0.4h > > Implement Async version of all the Java thin client APIs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9807) Web Agent: Add support for cluster ID
Alexey Kuznetsov created IGNITE-9807: Summary: Web Agent: Add support for cluster ID Key: IGNITE-9807 URL: https://issues.apache.org/jira/browse/IGNITE-9807 Project: Ignite Issue Type: Task Components: wizards Reporter: Alexey Kuznetsov Assignee: Alexey Kuznetsov Fix For: 2.8 We have cluster name, but user can name two different cluster with same name. Lets add optional cluster ID (may be passed via node.attributes for example). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9596) Web console: invisible checkbox is visible
[ https://issues.apache.org/jira/browse/IGNITE-9596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-9596: - Fix Version/s: 2.8 > Web console: invisible checkbox is visible > -- > > Key: IGNITE-9596 > URL: https://issues.apache.org/jira/browse/IGNITE-9596 > Project: Ignite > Issue Type: Bug > Components: wizards > Environment: Firefox, Chrome (macOS), Safari >Reporter: Ilya Borisov >Assignee: Alexey Kuznetsov >Priority: Minor > Fix For: 2.8 > > Attachments: image-2018-09-14-10-58-23-054.png > > Original Estimate: 3h > Time Spent: 0.5h > Remaining Estimate: 2.5h > > How it looks: > !image-2018-09-14-10-58-23-054.png! > How to reproduce: > 1. Connect to a cluster > 2. Open queries > 3. Click "+Add scan" > 4. Scroll down to filter input with "Cs" appendix. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7623) Thin client Java API - async API
[ https://issues.apache.org/jira/browse/IGNITE-7623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Artukhov updated IGNITE-7623: -- Attachment: Screenshot from 2018-10-08 08-46-38.png > Thin client Java API - async API > > > Key: IGNITE-7623 > URL: https://issues.apache.org/jira/browse/IGNITE-7623 > Project: Ignite > Issue Type: Task > Components: clients >Reporter: Alexey Kukushkin >Priority: Major > Labels: data, java, thin > Attachments: Screenshot from 2018-10-08 08-46-38.png, Screenshot from > 2018-10-08 08-49-22.png > > Original Estimate: 0.4h > Remaining Estimate: 0.4h > > Implement Async version of all the Java thin client APIs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-5935) MVCC TX: Tx recovery protocol
[ https://issues.apache.org/jira/browse/IGNITE-5935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16641358#comment-16641358 ] Ivan Pavlukhin edited comment on IGNITE-5935 at 10/8/18 5:50 AM: - If a node fails before finishing all initiated by it transactions they must be removed from active list on mvcc coordinator strictly after local transaction completion on each participating node. There are 2 cases handled differently depending on node type (client or server). # Transactions left by a server node are removed from the active list on PME. # Transactions left by a client node are removed from the active list after cluster-wide voting when each node gives a vote after making decision on all transactions recovery on that node. Possible problem: not all transactions can be recovered. Such transactions can prevent other recovered transactions removal from the active list. Also _partition counters_ should be kept consistent among partition replicas after recovery. Current protocol delivers _partition counters_ to backups on _prepare_ phase. During recovery there could occur a situation when transaction is recovering case when primary has failed and one backup received counters and another do not. Such case is a rollback and counters should be aligned. As primary has failed PME will occur. We rely on counters alignment during PME. was (Author: pavlukhin): If a node fails before finishing all initiated by it transactions the must be removed from active list on mvcc coordinator strictly after local transaction completion on each participating node. There are 2 cases handled differently depending on node type (client or server). # Transactions left by a server node are removed from the active list on PME. # Transactions left by a client node are removed from the active list after cluster-wide voting when each node gives a vote after making decision on all transactions recovery on that node. Possible problem: not all transactions can be recovered. Such transactions can prevent other recovered transactions removal from the active list. > 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] [Updated] (IGNITE-7623) Thin client Java API - async API
[ https://issues.apache.org/jira/browse/IGNITE-7623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Artukhov updated IGNITE-7623: -- Attachment: Screenshot from 2018-10-08 08-49-22.png > Thin client Java API - async API > > > Key: IGNITE-7623 > URL: https://issues.apache.org/jira/browse/IGNITE-7623 > Project: Ignite > Issue Type: Task > Components: clients >Reporter: Alexey Kukushkin >Priority: Major > Labels: data, java, thin > Attachments: Screenshot from 2018-10-08 08-46-38.png, Screenshot from > 2018-10-08 08-49-22.png > > Original Estimate: 0.4h > Remaining Estimate: 0.4h > > Implement Async version of all the Java thin client APIs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9789) "Starting Demo" message on top of Web console is rendered with delay,
[ https://issues.apache.org/jira/browse/IGNITE-9789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov reassigned IGNITE-9789: Assignee: Alexander Kalinin (was: Ilya Borisov) > "Starting Demo" message on top of Web console is rendered with delay, > - > > Key: IGNITE-9789 > URL: https://issues.apache.org/jira/browse/IGNITE-9789 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Alexander Kalinin >Assignee: Alexander Kalinin >Priority: Minor > Original Estimate: 1h > Time Spent: 2h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-9809) Web Console: Minor Fixes
[ https://issues.apache.org/jira/browse/IGNITE-9809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov resolved IGNITE-9809. -- Resolution: Fixed Looks good to me. Merged to master. > Web Console: Minor Fixes > > > Key: IGNITE-9809 > URL: https://issues.apache.org/jira/browse/IGNITE-9809 > Project: Ignite > Issue Type: Task > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov >Priority: Major > Fix For: 2.8 > > > We have a bunch of minor fixes: > # Duration filter > # i18n constants > # Minor CSS tweaks > # Minor code fixes -- 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=16641358#comment-16641358 ] Ivan Pavlukhin commented on IGNITE-5935: If a node fails before finishing all initiated by it transactions the must be removed from active list on mvcc coordinator strictly after local transaction completion on each participating node. There are 2 cases handled differently depending on node type (client or server). # Transactions left by a server node are removed from the active list on PME. # Transactions left by a client node are removed from the active list after cluster-wide voting when each node gives a vote after making decision on all transactions recovery on that node. Possible problem: not all transactions can be recovered. Such transactions can prevent other recovered transactions removal from the active list. > 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] [Assigned] (IGNITE-9059) Extra "'await" in loader service in WC front-end
[
https://issues.apache.org/jira/browse/IGNITE-9059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Kalinin reassigned IGNITE-9059:
-
Assignee: Pavel Konstantinov (was: Alexander Kalinin)
Please check that disabling screen on "Loading" works correlty on queries page
and others.
> Extra "'await" in loader service in WC front-end
>
>
> Key: IGNITE-9059
> URL: https://issues.apache.org/jira/browse/IGNITE-9059
> Project: Ignite
> Issue Type: Bug
> Components: wizards
>Reporter: Alexander Kalinin
>Assignee: Pavel Konstantinov
>Priority: Minor
> Original Estimate: 1h
> Time Spent: 1h
> Remaining Estimate: 0h
>
> code like "await this.IgniteLoading.finish('notebooksLoading')" doesn't need
> to have await, as it's doesn't return return promise, This part should be
> cleaned.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9809) Web Console: Minor Fixes
[ https://issues.apache.org/jira/browse/IGNITE-9809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-9809: - Ignite Flags: (was: Docs Required) > Web Console: Minor Fixes > > > Key: IGNITE-9809 > URL: https://issues.apache.org/jira/browse/IGNITE-9809 > Project: Ignite > Issue Type: Task > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov >Priority: Major > Fix For: 2.8 > > > We have a bunch of minor fixes: > # Duration filter > # i18n constants > # Minor CSS tweaks > # Minor code fixes -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-9809) Web Console: Minor Fixes
[ https://issues.apache.org/jira/browse/IGNITE-9809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-9809. > Web Console: Minor Fixes > > > Key: IGNITE-9809 > URL: https://issues.apache.org/jira/browse/IGNITE-9809 > Project: Ignite > Issue Type: Task > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov >Priority: Major > Fix For: 2.8 > > > We have a bunch of minor fixes: > # Duration filter > # i18n constants > # Minor CSS tweaks > # Minor code fixes -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-7838) Fix redirection on logo click
[ https://issues.apache.org/jira/browse/IGNITE-7838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov reassigned IGNITE-7838: -- Assignee: Alexey Kuznetsov (was: Pavel Konstantinov) > Fix redirection on logo click > - > > Key: IGNITE-7838 > URL: https://issues.apache.org/jira/browse/IGNITE-7838 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Alexander Kalinin >Assignee: Alexey Kuznetsov >Priority: Major > > Redirection to last state was broken after login\landing pages split > (IGNITE-7650 ) > > Steps: > 1) Login the app > 2) Go to configuration page > 3) Go to profile page > 4) Click logo > Actual: Redirection didn't occur > Expected: User is redirectd to default state (confiuration) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9807) Web Agent: Add support for cluster ID
[ https://issues.apache.org/jira/browse/IGNITE-9807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-9807: - Ignite Flags: (was: Docs Required) > Web Agent: Add support for cluster ID > - > > Key: IGNITE-9807 > URL: https://issues.apache.org/jira/browse/IGNITE-9807 > Project: Ignite > Issue Type: Task > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov >Priority: Major > Fix For: 2.8 > > > We have cluster name, but user can name two different cluster with same name. > Lets add optional cluster ID (may be passed via node.attributes for example). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7838) Fix redirection on logo click
[ https://issues.apache.org/jira/browse/IGNITE-7838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16641290#comment-16641290 ] Pavel Konstantinov commented on IGNITE-7838: It doesn't work on SQL(paragraph) screen, user profile screen, admin screen. So please fix if needed. > Fix redirection on logo click > - > > Key: IGNITE-7838 > URL: https://issues.apache.org/jira/browse/IGNITE-7838 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Alexander Kalinin >Assignee: Pavel Konstantinov >Priority: Major > > Redirection to last state was broken after login\landing pages split > (IGNITE-7650 ) > > Steps: > 1) Login the app > 2) Go to configuration page > 3) Go to profile page > 4) Click logo > Actual: Redirection didn't occur > Expected: User is redirectd to default state (confiuration) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (IGNITE-7838) Fix redirection on logo click
[ https://issues.apache.org/jira/browse/IGNITE-7838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov reopened IGNITE-7838: > Fix redirection on logo click > - > > Key: IGNITE-7838 > URL: https://issues.apache.org/jira/browse/IGNITE-7838 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Alexander Kalinin >Assignee: Alexey Kuznetsov >Priority: Major > > Redirection to last state was broken after login\landing pages split > (IGNITE-7650 ) > > Steps: > 1) Login the app > 2) Go to configuration page > 3) Go to profile page > 4) Click logo > Actual: Redirection didn't occur > Expected: User is redirectd to default state (confiuration) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9460) Web console: Update styles of top menu items
[ https://issues.apache.org/jira/browse/IGNITE-9460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov reassigned IGNITE-9460: Assignee: Pavel Konstantinov (was: Alexey Kuznetsov) > Web console: Update styles of top menu items > > > Key: IGNITE-9460 > URL: https://issues.apache.org/jira/browse/IGNITE-9460 > Project: Ignite > Issue Type: Bug > Components: UI, wizards >Reporter: Alexander Kalinin >Assignee: Pavel Konstantinov >Priority: Minor > Fix For: 2.8 > > Original Estimate: 2h > Time Spent: 1h > Remaining Estimate: 1h > > Accroding to design there should be no underlines on top menu. Let's remove > underline on focus. > !https://snag.gy/RBMZyn.jpg! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9455) Total allocated size memory metric is always zero for metastore data region.
[ https://issues.apache.org/jira/browse/IGNITE-9455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov reassigned IGNITE-9455: --- Assignee: Maxim Muzafarov > Total allocated size memory metric is always zero for metastore data region. > > > Key: IGNITE-9455 > URL: https://issues.apache.org/jira/browse/IGNITE-9455 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.6 >Reporter: Pavel Pereslegin >Assignee: Maxim Muzafarov >Priority: Major > Attachments: Reproducer.java > > > Persistence enabled and metrics for all regions enabled, but total allocated > size is always zero for metastore data region > Even if we change NO_OP allocated page tracker to a real page tracker in > CacheStoreHolder this metric counts incorrectly, because this region is > recreated, > Reproducer attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-9803) GridDhtInvalidPartitionException in GridDhtPartitionDemander
[ https://issues.apache.org/jira/browse/IGNITE-9803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semen Boikov resolved IGNITE-9803. -- Resolution: Fixed Assignee: (was: Semen Boikov) Merged fix in master (4e6727fe4c2952bb3d5be1c7767b3dd0dfe392da). > GridDhtInvalidPartitionException in GridDhtPartitionDemander > > > Key: IGNITE-9803 > URL: https://issues.apache.org/jira/browse/IGNITE-9803 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Semen Boikov >Priority: Major > Fix For: 2.8 > > > Debugged failure of > DynamicIndexPartitionedTransactionalConcurrentSelfTest.testConcurrentRebalance > with GridDhtInvalidPartitionException, here is scenario where this error > occurs: > * test starts node1, node2, loads data > * node3 is started, one partition is assigned to [node2, node3] and node3 > starts rebalancing > * node4 is started, partition is re-assigned to [node2, node4] > * at this time rebalancing on node3 is in progress, it is going to handle > supply message and at this moment exchange thread moves partition to RENTING > state, and at this moment partition can not be moved to EVICTED since async > partition cleanup is needed > * thread doing rebalancing at node3 sees RENTING partition and gets > GridDhtInvalidPartitionException > Probability of such failure is very high if insert sleep(5000) in the code > doing async partition cleanup (PartitionEvictionTask.run). > > I think fix for this issue is just handle GridDhtInvalidPartitionException in > GridDhtPartitionDemander. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7196) Exchange can stuck and wait while new node restoring state from disk and starting caches
[ https://issues.apache.org/jira/browse/IGNITE-7196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16641128#comment-16641128 ] Maxim Muzafarov commented on IGNITE-7196: - Folks, I've had flaky `JVM crashed` on my PR branch on TC. Can't reproduce it locally. I will fix it and back to you soon, hopefully before code freeze. ||Result||Changes||Started|| |Tests failed: 1 (1 new), passed: 1765, ignored: 35, muted: 2|No changes|07 Oct 18 18:33| |JVM crashed; tests passed: 679, ignored: 9, muted: 2|No changes|07 Oct 18 18:18| |JVM crashed (new); tests passed: 679, ignored: 9, muted: 2|No changes|07 Oct 18 18:09| |Tests passed: 1766, ignored: 35, muted: 2|No changes|07 Oct 18 18:09| |Tests failed: 1 (1 new), passed: 1765, ignored: 35, muted: 2|Maxim Muzafarov (2)|07 Oct 18 17:46| > Exchange can stuck and wait while new node restoring state from disk and > starting caches > > > Key: IGNITE-7196 > URL: https://issues.apache.org/jira/browse/IGNITE-7196 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.3 >Reporter: Mikhail Cherkasov >Assignee: Maxim Muzafarov >Priority: Critical > Fix For: 2.7 > > > Exchange can stuck and wait while new node restoring state from disk and > starting caches, there's a log snippet from a just joined new node that shows > the issue: > [21:36:13,023][INFO][exchange-worker-#62%statement_grid%][time] Started > exchange init [topVer=AffinityTopologyVersion [topVer=57, minorTopVer=0], > crd=false, evt=NODE_JOINED, evtNode=3ac1160e-0de4-41bc-a366-59292c9f03c1, > customEvt=null, allowMerge=true] > [21:36:13,023][INFO][exchange-worker-#62%statement_grid%][FilePageStoreManager] > Resolved page store work directory: > /mnt/store/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463 > [21:36:13,024][INFO][exchange-worker-#62%statement_grid%][FileWriteAheadLogManager] > Resolved write ahead log work directory: > /mnt/wal/WAL/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463 > [21:36:13,024][INFO][exchange-worker-#62%statement_grid%][FileWriteAheadLogManager] > Resolved write ahead log archive directory: > /mnt/wal/WAL_archive/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463 > [21:36:13,046][INFO][exchange-worker-#62%statement_grid%][FileWriteAheadLogManager] > Started write-ahead log manager [mode=DEFAULT] > [21:36:13,065][INFO][exchange-worker-#62%statement_grid%][PageMemoryImpl] > Started page memory [memoryAllocated=100.0 MiB, pages=6352, tableSize=373.4 > KiB, checkpointBuffer=100.0 MiB] > [21:36:13,105][INFO][exchange-worker-#62%statement_grid%][PageMemoryImpl] > Started page memory [memoryAllocated=32.0 GiB, pages=2083376, tableSize=119.6 > MiB, checkpointBuffer=896.0 MiB] > [21:36:13,428][INFO][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager] > Read checkpoint status > [startMarker=/mnt/store/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463/cp/1512930965253-306c0895-1f5f-4237-bebf-8bf2b49682af-START.bin, > > endMarker=/mnt/store/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463/cp/1512930869357-1c24b6dc-d64c-4b83-8166-11edf1bfdad3-END.bin] > [21:36:13,429][INFO][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager] > Checking memory state [lastValidPos=FileWALPointer [idx=3582, > fileOffset=59186076, len=9229, forceFlush=false], lastMarked=FileWALPointer > [idx=3629, fileOffset=50829700, len=9229, forceFlush=false], > lastCheckpointId=306c0895-1f5f-4237-bebf-8bf2b49682af] > [21:36:13,429][WARNING][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager] > Ignite node stopped in the middle of checkpoint. Will restore memory state > and finish checkpoint on node start. > [21:36:18,312][INFO][grid-nio-worker-tcp-comm-0-#41%statement_grid%][TcpCommunicationSpi] > Accepted incoming communication connection [locAddr=/172.31.20.209:48100, > rmtAddr=/172.31.17.115:57148] > [21:36:21,619][INFO][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager] > Found last checkpoint marker [cpId=306c0895-1f5f-4237-bebf-8bf2b49682af, > pos=FileWALPointer [idx=3629, fileOffset=50829700, len=9229, > forceFlush=false]] > [21:36:21,620][INFO][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager] > Finished applying memory changes [changesApplied=165103, time=8189ms] > [21:36:22,403][INFO][grid-nio-worker-tcp-comm-1-#42%statement_grid%][TcpCommunicationSpi] > Accepted incoming communication connection [locAddr=/172.31.20.209:48100, > rmtAddr=/172.31.28.10:47964] > [21:36:23,414][INFO][grid-nio-worker-tcp-comm-2-#43%statement_grid%][TcpCommunicationSpi] > Accepted incoming communication connection [locAddr=/172.31.20.209:48100, > rmtAddr=/172.31.27.101:46000] > [21:36:33,019][WARNING][main][GridCachePartitionExchangeManager] Failed to
[jira] [Commented] (IGNITE-7196) Exchange can stuck and wait while new node restoring state from disk and starting caches
[ https://issues.apache.org/jira/browse/IGNITE-7196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16641132#comment-16641132 ] Dmitriy Pavlov commented on IGNITE-7196: Please check if it is not the same problem as in [IGNITE-]. If it is same tests affected, probably there is nothing to worry about. > Exchange can stuck and wait while new node restoring state from disk and > starting caches > > > Key: IGNITE-7196 > URL: https://issues.apache.org/jira/browse/IGNITE-7196 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.3 >Reporter: Mikhail Cherkasov >Assignee: Maxim Muzafarov >Priority: Critical > Fix For: 2.7 > > > Exchange can stuck and wait while new node restoring state from disk and > starting caches, there's a log snippet from a just joined new node that shows > the issue: > [21:36:13,023][INFO][exchange-worker-#62%statement_grid%][time] Started > exchange init [topVer=AffinityTopologyVersion [topVer=57, minorTopVer=0], > crd=false, evt=NODE_JOINED, evtNode=3ac1160e-0de4-41bc-a366-59292c9f03c1, > customEvt=null, allowMerge=true] > [21:36:13,023][INFO][exchange-worker-#62%statement_grid%][FilePageStoreManager] > Resolved page store work directory: > /mnt/store/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463 > [21:36:13,024][INFO][exchange-worker-#62%statement_grid%][FileWriteAheadLogManager] > Resolved write ahead log work directory: > /mnt/wal/WAL/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463 > [21:36:13,024][INFO][exchange-worker-#62%statement_grid%][FileWriteAheadLogManager] > Resolved write ahead log archive directory: > /mnt/wal/WAL_archive/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463 > [21:36:13,046][INFO][exchange-worker-#62%statement_grid%][FileWriteAheadLogManager] > Started write-ahead log manager [mode=DEFAULT] > [21:36:13,065][INFO][exchange-worker-#62%statement_grid%][PageMemoryImpl] > Started page memory [memoryAllocated=100.0 MiB, pages=6352, tableSize=373.4 > KiB, checkpointBuffer=100.0 MiB] > [21:36:13,105][INFO][exchange-worker-#62%statement_grid%][PageMemoryImpl] > Started page memory [memoryAllocated=32.0 GiB, pages=2083376, tableSize=119.6 > MiB, checkpointBuffer=896.0 MiB] > [21:36:13,428][INFO][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager] > Read checkpoint status > [startMarker=/mnt/store/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463/cp/1512930965253-306c0895-1f5f-4237-bebf-8bf2b49682af-START.bin, > > endMarker=/mnt/store/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463/cp/1512930869357-1c24b6dc-d64c-4b83-8166-11edf1bfdad3-END.bin] > [21:36:13,429][INFO][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager] > Checking memory state [lastValidPos=FileWALPointer [idx=3582, > fileOffset=59186076, len=9229, forceFlush=false], lastMarked=FileWALPointer > [idx=3629, fileOffset=50829700, len=9229, forceFlush=false], > lastCheckpointId=306c0895-1f5f-4237-bebf-8bf2b49682af] > [21:36:13,429][WARNING][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager] > Ignite node stopped in the middle of checkpoint. Will restore memory state > and finish checkpoint on node start. > [21:36:18,312][INFO][grid-nio-worker-tcp-comm-0-#41%statement_grid%][TcpCommunicationSpi] > Accepted incoming communication connection [locAddr=/172.31.20.209:48100, > rmtAddr=/172.31.17.115:57148] > [21:36:21,619][INFO][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager] > Found last checkpoint marker [cpId=306c0895-1f5f-4237-bebf-8bf2b49682af, > pos=FileWALPointer [idx=3629, fileOffset=50829700, len=9229, > forceFlush=false]] > [21:36:21,620][INFO][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager] > Finished applying memory changes [changesApplied=165103, time=8189ms] > [21:36:22,403][INFO][grid-nio-worker-tcp-comm-1-#42%statement_grid%][TcpCommunicationSpi] > Accepted incoming communication connection [locAddr=/172.31.20.209:48100, > rmtAddr=/172.31.28.10:47964] > [21:36:23,414][INFO][grid-nio-worker-tcp-comm-2-#43%statement_grid%][TcpCommunicationSpi] > Accepted incoming communication connection [locAddr=/172.31.20.209:48100, > rmtAddr=/172.31.27.101:46000] > [21:36:33,019][WARNING][main][GridCachePartitionExchangeManager] Failed to > wait for initial partition map exchange. Possible reasons are: > ^-- Transactions in deadlock. > ^-- Long running transactions (ignore if this is the case). > ^-- Unreleased explicit locks. > [21:36:53,021][WARNING][main][GridCachePartitionExchangeManager] Still > waiting for initial partition map exchange > [fut=GridDhtPartitionsExchangeFuture [firstDiscoEvt=DiscoveryEvent > [evtNode=TcpDiscoveryNode [id=3ac1160e-0de4-41bc-a366-59292c9f03c1, > addrs=[0:0:0:0:0:0:0:1%lo,
[jira] [Updated] (IGNITE-7196) Exchange can stuck and wait while new node restoring state from disk and starting caches
[
https://issues.apache.org/jira/browse/IGNITE-7196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-7196:
---
Description:
Exchange can stuck and wait while new node restoring state from disk and
starting caches, there's a log snippet from a just joined new node that shows
the issue:
{noformat}
[21:36:13,023][INFO][exchange-worker-#62%statement_grid%][time] Started
exchange init [topVer=AffinityTopologyVersion [topVer=57, minorTopVer=0],
crd=false, evt=NODE_JOINED, evtNode=3ac1160e-0de4-41bc-a366-59292c9f03c1,
customEvt=null, allowMerge=true]
[21:36:13,023][INFO][exchange-worker-#62%statement_grid%][FilePageStoreManager]
Resolved page store work directory:
/mnt/store/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463
[21:36:13,024][INFO][exchange-worker-#62%statement_grid%][FileWriteAheadLogManager]
Resolved write ahead log work directory:
/mnt/wal/WAL/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463
[21:36:13,024][INFO][exchange-worker-#62%statement_grid%][FileWriteAheadLogManager]
Resolved write ahead log archive directory:
/mnt/wal/WAL_archive/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463
[21:36:13,046][INFO][exchange-worker-#62%statement_grid%][FileWriteAheadLogManager]
Started write-ahead log manager [mode=DEFAULT]
[21:36:13,065][INFO][exchange-worker-#62%statement_grid%][PageMemoryImpl]
Started page memory [memoryAllocated=100.0 MiB, pages=6352, tableSize=373.4
KiB, checkpointBuffer=100.0 MiB]
[21:36:13,105][INFO][exchange-worker-#62%statement_grid%][PageMemoryImpl]
Started page memory [memoryAllocated=32.0 GiB, pages=2083376, tableSize=119.6
MiB, checkpointBuffer=896.0 MiB]
[21:36:13,428][INFO][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager]
Read checkpoint status
[startMarker=/mnt/store/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463/cp/1512930965253-306c0895-1f5f-4237-bebf-8bf2b49682af-START.bin,
endMarker=/mnt/store/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463/cp/1512930869357-1c24b6dc-d64c-4b83-8166-11edf1bfdad3-END.bin]
[21:36:13,429][INFO][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager]
Checking memory state [lastValidPos=FileWALPointer [idx=3582,
fileOffset=59186076, len=9229, forceFlush=false], lastMarked=FileWALPointer
[idx=3629, fileOffset=50829700, len=9229, forceFlush=false],
lastCheckpointId=306c0895-1f5f-4237-bebf-8bf2b49682af]
[21:36:13,429][WARNING][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager]
Ignite node stopped in the middle of checkpoint. Will restore memory state and
finish checkpoint on node start.
[21:36:18,312][INFO][grid-nio-worker-tcp-comm-0-#41%statement_grid%][TcpCommunicationSpi]
Accepted incoming communication connection [locAddr=/172.31.20.209:48100,
rmtAddr=/172.31.17.115:57148]
[21:36:21,619][INFO][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager]
Found last checkpoint marker [cpId=306c0895-1f5f-4237-bebf-8bf2b49682af,
pos=FileWALPointer [idx=3629, fileOffset=50829700, len=9229, forceFlush=false]]
[21:36:21,620][INFO][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager]
Finished applying memory changes [changesApplied=165103, time=8189ms]
[21:36:22,403][INFO][grid-nio-worker-tcp-comm-1-#42%statement_grid%][TcpCommunicationSpi]
Accepted incoming communication connection [locAddr=/172.31.20.209:48100,
rmtAddr=/172.31.28.10:47964]
[21:36:23,414][INFO][grid-nio-worker-tcp-comm-2-#43%statement_grid%][TcpCommunicationSpi]
Accepted incoming communication connection [locAddr=/172.31.20.209:48100,
rmtAddr=/172.31.27.101:46000]
[21:36:33,019][WARNING][main][GridCachePartitionExchangeManager] Failed to wait
for initial partition map exchange. Possible reasons are:
^-- Transactions in deadlock.
^-- Long running transactions (ignore if this is the case).
^-- Unreleased explicit locks.
[21:36:53,021][WARNING][main][GridCachePartitionExchangeManager] Still waiting
for initial partition map exchange [fut=GridDhtPartitionsExchangeFuture
[firstDiscoEvt=DiscoveryEvent [evtNode=TcpDiscoveryNode
[id=3ac1160e-0de4-41bc-a366-59292c9f03c1, addrs=[0:0:0:0:0:0:0:1%lo, 127.0.0.1,
172.31.20.209], sockAddrs=[/0:0:0:0:0:0:0:1%lo:48500, /127.0.0.1:48500,
ip-172-31-20-209.eu-central-1.compute.internal/172.31.20.209:48500],
discPort=48500, order=57, intOrder=36, lastExchangeTime=1512931012268,
loc=true, ver=2.3.1#20171129-sha1:4b1ec0fe, isClient=false], topVer=57,
nodeId8=3ac1160e, msg=null, type=NODE_JOINED, tstamp=1512930972992],
crd=TcpDiscoveryNode [id=56c97317-26cf-43d2-bf76-0cab59c6fa5f,
addrs=[0:0:0:0:0:0:0:1%lo, 127.0.0.1, 172.31.27.101],
sockAddrs=[/0:0:0:0:0:0:0:1%lo:48500, /127.0.0.1:48500,
ip-172-31-27-101.eu-central-1.compute.internal/172.31.27.101:48500],
discPort=48500, order=1, intOrder=1, lastExchangeTime=1512930972830, loc=false,
ver=2.3.1#20171129-sha1:4b1ec0fe, isClient=false],
exchId=GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion
[jira] [Updated] (IGNITE-9806) Legacy tx invalidation code breaks data consistency between owners.
[
https://issues.apache.org/jira/browse/IGNITE-9806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexei Scherbakov updated IGNITE-9806:
--
Ignite Flags: (was: Docs Required)
> Legacy tx invalidation code breaks data consistency between owners.
> ---
>
> Key: IGNITE-9806
> URL: https://issues.apache.org/jira/browse/IGNITE-9806
> Project: Ignite
> Issue Type: Improvement
>Reporter: Alexei Scherbakov
>Priority: Major
> Fix For: 2.8
>
>
> Reproducer:
> {noformat}
> /*
> * Licensed to the Apache Software Foundation (ASF) under one or more
> * contributor license agreements. See the NOTICE file distributed with
> * this work for additional information regarding copyright ownership.
> * The ASF licenses this file to You under the Apache License, Version 2.0
> * (the "License"); you may not use this file except in compliance with
> * the License. You may obtain a copy of the License at
> *
> * http://www.apache.org/licenses/LICENSE-2.0
> *
> * Unless required by applicable law or agreed to in writing, software
> * distributed under the License is distributed on an "AS IS" BASIS,
> * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> * See the License for the specific language governing permissions and
> * limitations under the License.
> */
> package org.apache.ignite.internal.processors.cache.transactions;
> import java.util.UUID;
> import java.util.function.Supplier;
> import org.apache.ignite.Ignite;
> import org.apache.ignite.IgniteCheckedException;
> import org.apache.ignite.IgniteTransactions;
> import org.apache.ignite.cache.CacheAtomicityMode;
> import org.apache.ignite.cache.CacheMode;
> import org.apache.ignite.cache.CacheWriteSynchronizationMode;
> import org.apache.ignite.configuration.CacheConfiguration;
> import org.apache.ignite.configuration.IgniteConfiguration;
> import org.apache.ignite.internal.IgniteEx;
> import org.apache.ignite.internal.managers.communication.GridIoPolicy;
> import org.apache.ignite.internal.processors.cache.GridCacheSharedContext;
> import
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal;
> import org.apache.ignite.internal.util.typedef.G;
> import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;
> import org.apache.ignite.testsuites.IgniteIgnore;
> import org.apache.ignite.transactions.Transaction;
> import org.apache.ignite.transactions.TransactionConcurrency;
> import org.apache.ignite.transactions.TransactionIsolation;
> import org.jetbrains.annotations.Nullable;
> import org.mockito.Mockito;
> import org.mockito.invocation.InvocationOnMock;
> import org.mockito.stubbing.Answer;
> /**
> * Tests data consistency if transaction is failed due to heuristic exception
> on originating node.
> */
> public class TxDataConsistencyOnCommitFailureTest extends
> GridCommonAbstractTest {
> /** */
> public static final int KEY = 0;
> /** */
> public static final String CLIENT = "client";
> /** */
> private int nodesCnt;
> /** */
> private int backups;
> /** {@inheritDoc} */
> @Override protected IgniteConfiguration getConfiguration(String
> igniteInstanceName) throws Exception {
> IgniteConfiguration cfg = super.getConfiguration(igniteInstanceName);
> cfg.setClientMode(igniteInstanceName.startsWith(CLIENT));
> cfg.setCacheConfiguration(new CacheConfiguration(DEFAULT_CACHE_NAME).
> setCacheMode(CacheMode.PARTITIONED).
> setAtomicityMode(CacheAtomicityMode.TRANSACTIONAL).
> setBackups(backups).
>
> setWriteSynchronizationMode(CacheWriteSynchronizationMode.FULL_SYNC));
> return cfg;
> }
> /** {@inheritDoc} */
> @Override protected void afterTest() throws Exception {
> super.afterTest();
> stopAllGrids();
> }
> /** */
> @IgniteIgnore(value = "https://issues.apache.org/jira/browse/IGNITE-590;,
> forceFailure = false)
> public void testCommitErrorOnColocatedNode2PC() throws Exception {
> nodesCnt = 3;
> backups = 2;
> doTestCommitError(() -> primaryNode(KEY, DEFAULT_CACHE_NAME));
> }
> /**
> * @param factory Factory.
> */
> private void doTestCommitError(Supplier factory) throws Exception
> {
> Ignite crd = startGridsMultiThreaded(nodesCnt);
> crd.cache(DEFAULT_CACHE_NAME).put(KEY, KEY);
> Ignite ignite = factory.get();
> if (ignite == null)
> ignite = startGrid("client");
> assertNotNull(ignite.cache(DEFAULT_CACHE_NAME));
> injectMockedTxManager(ignite);
> checkKey();
> IgniteTransactions transactions = ignite.transactions();
> try(Transaction tx =
>
[jira] [Created] (IGNITE-9806) Legacy tx invalidation code breaks data consistency between owners.
Alexei Scherbakov created IGNITE-9806:
-
Summary: Legacy tx invalidation code breaks data consistency
between owners.
Key: IGNITE-9806
URL: https://issues.apache.org/jira/browse/IGNITE-9806
Project: Ignite
Issue Type: Improvement
Reporter: Alexei Scherbakov
Fix For: 2.8
Reproducer:
{noformat}
/*
* Licensed to the Apache Software Foundation (ASF) under one or more
* contributor license agreements. See the NOTICE file distributed with
* this work for additional information regarding copyright ownership.
* The ASF licenses this file to You under the Apache License, Version 2.0
* (the "License"); you may not use this file except in compliance with
* the License. You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/
package org.apache.ignite.internal.processors.cache.transactions;
import java.util.UUID;
import java.util.function.Supplier;
import org.apache.ignite.Ignite;
import org.apache.ignite.IgniteCheckedException;
import org.apache.ignite.IgniteTransactions;
import org.apache.ignite.cache.CacheAtomicityMode;
import org.apache.ignite.cache.CacheMode;
import org.apache.ignite.cache.CacheWriteSynchronizationMode;
import org.apache.ignite.configuration.CacheConfiguration;
import org.apache.ignite.configuration.IgniteConfiguration;
import org.apache.ignite.internal.IgniteEx;
import org.apache.ignite.internal.managers.communication.GridIoPolicy;
import org.apache.ignite.internal.processors.cache.GridCacheSharedContext;
import
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal;
import org.apache.ignite.internal.util.typedef.G;
import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;
import org.apache.ignite.testsuites.IgniteIgnore;
import org.apache.ignite.transactions.Transaction;
import org.apache.ignite.transactions.TransactionConcurrency;
import org.apache.ignite.transactions.TransactionIsolation;
import org.jetbrains.annotations.Nullable;
import org.mockito.Mockito;
import org.mockito.invocation.InvocationOnMock;
import org.mockito.stubbing.Answer;
/**
* Tests data consistency if transaction is failed due to heuristic exception
on originating node.
*/
public class TxDataConsistencyOnCommitFailureTest extends
GridCommonAbstractTest {
/** */
public static final int KEY = 0;
/** */
public static final String CLIENT = "client";
/** */
private int nodesCnt;
/** */
private int backups;
/** {@inheritDoc} */
@Override protected IgniteConfiguration getConfiguration(String
igniteInstanceName) throws Exception {
IgniteConfiguration cfg = super.getConfiguration(igniteInstanceName);
cfg.setClientMode(igniteInstanceName.startsWith(CLIENT));
cfg.setCacheConfiguration(new CacheConfiguration(DEFAULT_CACHE_NAME).
setCacheMode(CacheMode.PARTITIONED).
setAtomicityMode(CacheAtomicityMode.TRANSACTIONAL).
setBackups(backups).
setWriteSynchronizationMode(CacheWriteSynchronizationMode.FULL_SYNC));
return cfg;
}
/** {@inheritDoc} */
@Override protected void afterTest() throws Exception {
super.afterTest();
stopAllGrids();
}
/** */
@IgniteIgnore(value = "https://issues.apache.org/jira/browse/IGNITE-590;,
forceFailure = false)
public void testCommitErrorOnColocatedNode2PC() throws Exception {
nodesCnt = 3;
backups = 2;
doTestCommitError(() -> primaryNode(KEY, DEFAULT_CACHE_NAME));
}
/**
* @param factory Factory.
*/
private void doTestCommitError(Supplier factory) throws Exception {
Ignite crd = startGridsMultiThreaded(nodesCnt);
crd.cache(DEFAULT_CACHE_NAME).put(KEY, KEY);
Ignite ignite = factory.get();
if (ignite == null)
ignite = startGrid("client");
assertNotNull(ignite.cache(DEFAULT_CACHE_NAME));
injectMockedTxManager(ignite);
checkKey();
IgniteTransactions transactions = ignite.transactions();
try(Transaction tx =
transactions.txStart(TransactionConcurrency.PESSIMISTIC,
TransactionIsolation.REPEATABLE_READ, 0, 1)) {
assertNotNull(transactions.tx());
ignite.cache(DEFAULT_CACHE_NAME).put(KEY, KEY + 1);
tx.commit();
fail();
}
catch (Exception t) {
// No-op.
}
checkKey();
checkFutures();
}
/**
* @param ignite Ignite.
*/
private void
