[jira] [Commented] (IGNITE-7226) Web console: Norification placeholder on empty user table
[ https://issues.apache.org/jira/browse/IGNITE-7226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16760540#comment-16760540 ] Alexander Kalinin commented on IGNITE-7226: --- [~kuaw26] This issue is fixed in current master. Can be closed. > Web console: Norification placeholder on empty user table > - > > Key: IGNITE-7226 > URL: https://issues.apache.org/jira/browse/IGNITE-7226 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Vasiliy Sisko >Assignee: Alexander Kalinin >Priority: Major > > # Open Admin panel > # Filter all data in table. > Table showed without data and any information message. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11200) SQL: query contexts should not be static
[
https://issues.apache.org/jira/browse/IGNITE-11200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16760533#comment-16760533
]
Ignite TC Bot commented on IGNITE-11200:
{panel:title=-- Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache (Restarts) 1{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=2997668]]
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithPutFourNodesNoBackups -
0,0% fails in last 395 master runs.
{color:#d04437}Cache (Restarts) 2{color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=2997669]]
* IgniteCacheRestartTestSuite2:
IgniteCacheAtomicNodeRestartTest.testRestartWithPutEightNodesTwoBackups - 0,5%
fails in last 414 master runs.
* IgniteCacheRestartTestSuite2:
IgniteCacheAtomicNodeRestartTest.testRestartWithTxTwoNodesOneBackup - 0,5%
fails in last 414 master runs.
* IgniteCacheRestartTestSuite2:
IgniteCacheAtomicNodeRestartTest.testRestartWithTxSixNodesTwoBackups - 0,5%
fails in last 414 master runs.
* IgniteCacheRestartTestSuite2:
IgniteCacheAtomicNodeRestartTest.testRestartWithTxFourNodesOneBackups - 0,5%
fails in last 414 master runs.
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2997723buildTypeId=IgniteTests24Java8_RunAll]
> SQL: query contexts should not be static
>
>
> Key: IGNITE-11200
> URL: https://issues.apache.org/jira/browse/IGNITE-11200
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Evgenii Zhuravlev
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently query contexts are static and as a result over complicated. Need to
> make them instance-bound and remove static.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-10965) Web console: in progress state for buttons
[ https://issues.apache.org/jira/browse/IGNITE-10965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kalinin reassigned IGNITE-10965: -- Assignee: Pavel Konstantinov (was: Alexander Kalinin) [~pkonstantinov] Please test the following screens: 1) Sign in 2) Sign up 3) Profile page When form is submitted the "submit" button should be blocked and progress-line appear in header. > Web console: in progress state for buttons > -- > > Key: IGNITE-10965 > URL: https://issues.apache.org/jira/browse/IGNITE-10965 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Ilya Borisov >Assignee: Pavel Konstantinov >Priority: Minor > Attachments: !icons.png, DisableBtn.png, ProgressBtn.png > > Original Estimate: 8h > Time Spent: 4h > Remaining Estimate: 4h > > *The problem:* > Some actions triggered by user might take awhile, during which user can > click on action button multiple times and, depending on internal details, > cause unwanted side effects (like registering multiple users instead of one). > *Solution:* > Disable action button when action is running. Tell user to wait that > something is happening. This can be integrated into special button state. > Places new button state can be used in: > - User registration. > I'd rather prefer that new button state would: > - Not affect button dimensions because sudden button size change might look > uncanny. Overlays are OK, though. This probably rules out spinning indicator > inline with button label. > - Not hide original button label so.user always knows what's in progress. > - Work for all button styles. Unique background for each button type is not > OK, same background or overlay is OK. This will simplify the implementation. > The requirements above are not set in stone, every point is open for > discussion. > [~vabramova] to provide design, [~Klaster_1] or [~alexdel] to implement. > > Useful article: [https://habr.com/ru/post/271881/] > Sample implemenation: https://johannesjo.github.io/angular-promise-buttons/ > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-11201) ConnectorConfiguration and TransactionConfiguration toString is not properly implemented.
[ https://issues.apache.org/jira/browse/IGNITE-11201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Voronkin resolved IGNITE-11201. - Resolution: Duplicate > ConnectorConfiguration and TransactionConfiguration toString is not properly > implemented. > - > > Key: IGNITE-11201 > URL: https://issues.apache.org/jira/browse/IGNITE-11201 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Voronkin >Priority: Major > > Ignite configuration prints on startup, but ConnectorConfiguration and > TransactionConfiguration are not properly printed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11201) ConnectorConfiguration and TransactionConfiguration toString is not properly implemented.
[ https://issues.apache.org/jira/browse/IGNITE-11201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Voronkin updated IGNITE-11201: Description: Ignite configuration prints on startup, but ConnectorConfiguration and TransactionConfiguration are not properly printed. > ConnectorConfiguration and TransactionConfiguration toString is not properly > implemented. > - > > Key: IGNITE-11201 > URL: https://issues.apache.org/jira/browse/IGNITE-11201 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Voronkin >Priority: Major > > Ignite configuration prints on startup, but ConnectorConfiguration and > TransactionConfiguration are not properly printed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-10031) REST: Introduce "caches" param for "top" command.
[ https://issues.apache.org/jira/browse/IGNITE-10031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov closed IGNITE-10031. --- Ignite Flags: (was: Docs Required) > REST: Introduce "caches" param for "top" command. > - > > Key: IGNITE-10031 > URL: https://issues.apache.org/jira/browse/IGNITE-10031 > Project: Ignite > Issue Type: Improvement > Components: rest >Reporter: Alexey Kuznetsov >Assignee: Pavel Konstantinov >Priority: Major > Fix For: 2.8 > > > We have top command on REST API: > [https://apacheignite.readme.io/docs/rest-api#topology] > And result of this command also contains short caches info (name, mode & SQL > Schema). > But in situation when node contains thousand caches and hundred nodes and > caches have long names - that will result in a HUGE JSON. > For example, I get 88Mb JSON for cluster of 128 nodes and 6000 caches. > And my application do not need that info about caches, I just need a list of > node IDs. > Lets add one more flag "caches" (with default value "true", for > compatibility) as we already have "attr" & "mtr". -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10031) REST: Introduce "caches" param for "top" command.
[ https://issues.apache.org/jira/browse/IGNITE-10031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16760511#comment-16760511 ] Pavel Konstantinov commented on IGNITE-10031: - Tested > REST: Introduce "caches" param for "top" command. > - > > Key: IGNITE-10031 > URL: https://issues.apache.org/jira/browse/IGNITE-10031 > Project: Ignite > Issue Type: Improvement > Components: rest >Reporter: Alexey Kuznetsov >Assignee: Pavel Konstantinov >Priority: Major > Fix For: 2.8 > > > We have top command on REST API: > [https://apacheignite.readme.io/docs/rest-api#topology] > And result of this command also contains short caches info (name, mode & SQL > Schema). > But in situation when node contains thousand caches and hundred nodes and > caches have long names - that will result in a HUGE JSON. > For example, I get 88Mb JSON for cluster of 128 nodes and 6000 caches. > And my application do not need that info about caches, I just need a list of > node IDs. > Lets add one more flag "caches" (with default value "true", for > compatibility) as we already have "attr" & "mtr". -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11201) ConnectorConfiguration and TransactionConfiguration toString is not properly implemented
[ https://issues.apache.org/jira/browse/IGNITE-11201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Voronkin updated IGNITE-11201: Summary: ConnectorConfiguration and TransactionConfiguration toString is not properly implemented (was: ConnectorConfdiguration and TransactionConfiguration toString is not properly implemented.) > ConnectorConfiguration and TransactionConfiguration toString is not properly > implemented > > > Key: IGNITE-11201 > URL: https://issues.apache.org/jira/browse/IGNITE-11201 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Voronkin >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11201) ConnectorConfiguration and TransactionConfiguration toString is not properly implemented.
[ https://issues.apache.org/jira/browse/IGNITE-11201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Voronkin updated IGNITE-11201: Summary: ConnectorConfiguration and TransactionConfiguration toString is not properly implemented. (was: ConnectorConfiguration and TransactionConfiguration toString is not properly implemented) > ConnectorConfiguration and TransactionConfiguration toString is not properly > implemented. > - > > Key: IGNITE-11201 > URL: https://issues.apache.org/jira/browse/IGNITE-11201 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Voronkin >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11201) ConnectorConfdiguration and TransactionConfiguration toString is not properly implemented.
Pavel Voronkin created IGNITE-11201: --- Summary: ConnectorConfdiguration and TransactionConfiguration toString is not properly implemented. Key: IGNITE-11201 URL: https://issues.apache.org/jira/browse/IGNITE-11201 Project: Ignite Issue Type: Bug Reporter: Pavel Voronkin -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10965) Web console: in progress state for buttons
[ https://issues.apache.org/jira/browse/IGNITE-10965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16760507#comment-16760507 ] Ilya Borisov commented on IGNITE-10965: --- [~alexdel] I have no complaints. The end result feels snappy, I like it. > Web console: in progress state for buttons > -- > > Key: IGNITE-10965 > URL: https://issues.apache.org/jira/browse/IGNITE-10965 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Ilya Borisov >Assignee: Alexander Kalinin >Priority: Minor > Attachments: !icons.png, DisableBtn.png, ProgressBtn.png > > Original Estimate: 8h > Time Spent: 4h > Remaining Estimate: 4h > > *The problem:* > Some actions triggered by user might take awhile, during which user can > click on action button multiple times and, depending on internal details, > cause unwanted side effects (like registering multiple users instead of one). > *Solution:* > Disable action button when action is running. Tell user to wait that > something is happening. This can be integrated into special button state. > Places new button state can be used in: > - User registration. > I'd rather prefer that new button state would: > - Not affect button dimensions because sudden button size change might look > uncanny. Overlays are OK, though. This probably rules out spinning indicator > inline with button label. > - Not hide original button label so.user always knows what's in progress. > - Work for all button styles. Unique background for each button type is not > OK, same background or overlay is OK. This will simplify the implementation. > The requirements above are not set in stone, every point is open for > discussion. > [~vabramova] to provide design, [~Klaster_1] or [~alexdel] to implement. > > Useful article: [https://habr.com/ru/post/271881/] > Sample implemenation: https://johannesjo.github.io/angular-promise-buttons/ > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-10965) Web console: in progress state for buttons
[ https://issues.apache.org/jira/browse/IGNITE-10965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov reassigned IGNITE-10965: - Assignee: Alexander Kalinin (was: Ilya Borisov) > Web console: in progress state for buttons > -- > > Key: IGNITE-10965 > URL: https://issues.apache.org/jira/browse/IGNITE-10965 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Ilya Borisov >Assignee: Alexander Kalinin >Priority: Minor > Attachments: !icons.png, DisableBtn.png, ProgressBtn.png > > Original Estimate: 8h > Time Spent: 4h > Remaining Estimate: 4h > > *The problem:* > Some actions triggered by user might take awhile, during which user can > click on action button multiple times and, depending on internal details, > cause unwanted side effects (like registering multiple users instead of one). > *Solution:* > Disable action button when action is running. Tell user to wait that > something is happening. This can be integrated into special button state. > Places new button state can be used in: > - User registration. > I'd rather prefer that new button state would: > - Not affect button dimensions because sudden button size change might look > uncanny. Overlays are OK, though. This probably rules out spinning indicator > inline with button label. > - Not hide original button label so.user always knows what's in progress. > - Work for all button styles. Unique background for each button type is not > OK, same background or overlay is OK. This will simplify the implementation. > The requirements above are not set in stone, every point is open for > discussion. > [~vabramova] to provide design, [~Klaster_1] or [~alexdel] to implement. > > Useful article: [https://habr.com/ru/post/271881/] > Sample implemenation: https://johannesjo.github.io/angular-promise-buttons/ > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-5745) Web console: Admin panel - add registration date and ability to filter by it
[ https://issues.apache.org/jira/browse/IGNITE-5745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16760496#comment-16760496 ] Alexander Kalinin commented on IGNITE-5745: --- This task requires some comlplicate data aggregation in MongoDB. As we are moving towards java backend I suppose this task can be postponed till backend migration. > Web console: Admin panel - add registration date and ability to filter by it > > > Key: IGNITE-5745 > URL: https://issues.apache.org/jira/browse/IGNITE-5745 > Project: Ignite > Issue Type: Task > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Alexander Kalinin >Priority: Major > > Will be nice to track user registration date in order to see how many users > registered each month. > Also period filtration should be configurable: use last activity date or > registration date to see numbers. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10965) Web console: in progress state for buttons
[ https://issues.apache.org/jira/browse/IGNITE-10965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16760485#comment-16760485 ] Alexander Kalinin commented on IGNITE-10965: [~Klaster_1] I've created a pr. Please review.https://github.com/apache/ignite/pull/6022 > Web console: in progress state for buttons > -- > > Key: IGNITE-10965 > URL: https://issues.apache.org/jira/browse/IGNITE-10965 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Ilya Borisov >Assignee: Alexander Kalinin >Priority: Minor > Attachments: !icons.png, DisableBtn.png, ProgressBtn.png > > Original Estimate: 8h > Time Spent: 4h > Remaining Estimate: 4h > > *The problem:* > Some actions triggered by user might take awhile, during which user can > click on action button multiple times and, depending on internal details, > cause unwanted side effects (like registering multiple users instead of one). > *Solution:* > Disable action button when action is running. Tell user to wait that > something is happening. This can be integrated into special button state. > Places new button state can be used in: > - User registration. > I'd rather prefer that new button state would: > - Not affect button dimensions because sudden button size change might look > uncanny. Overlays are OK, though. This probably rules out spinning indicator > inline with button label. > - Not hide original button label so.user always knows what's in progress. > - Work for all button styles. Unique background for each button type is not > OK, same background or overlay is OK. This will simplify the implementation. > The requirements above are not set in stone, every point is open for > discussion. > [~vabramova] to provide design, [~Klaster_1] or [~alexdel] to implement. > > Useful article: [https://habr.com/ru/post/271881/] > Sample implemenation: https://johannesjo.github.io/angular-promise-buttons/ > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-10965) Web console: in progress state for buttons
[ https://issues.apache.org/jira/browse/IGNITE-10965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kalinin reassigned IGNITE-10965: -- Assignee: Ilya Borisov (was: Alexander Kalinin) > Web console: in progress state for buttons > -- > > Key: IGNITE-10965 > URL: https://issues.apache.org/jira/browse/IGNITE-10965 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Ilya Borisov >Assignee: Ilya Borisov >Priority: Minor > Attachments: !icons.png, DisableBtn.png, ProgressBtn.png > > Original Estimate: 8h > Time Spent: 4h > Remaining Estimate: 4h > > *The problem:* > Some actions triggered by user might take awhile, during which user can > click on action button multiple times and, depending on internal details, > cause unwanted side effects (like registering multiple users instead of one). > *Solution:* > Disable action button when action is running. Tell user to wait that > something is happening. This can be integrated into special button state. > Places new button state can be used in: > - User registration. > I'd rather prefer that new button state would: > - Not affect button dimensions because sudden button size change might look > uncanny. Overlays are OK, though. This probably rules out spinning indicator > inline with button label. > - Not hide original button label so.user always knows what's in progress. > - Work for all button styles. Unique background for each button type is not > OK, same background or overlay is OK. This will simplify the implementation. > The requirements above are not set in stone, every point is open for > discussion. > [~vabramova] to provide design, [~Klaster_1] or [~alexdel] to implement. > > Useful article: [https://habr.com/ru/post/271881/] > Sample implemenation: https://johannesjo.github.io/angular-promise-buttons/ > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-11006) Enable problematic whitespace inspection check
[
https://issues.apache.org/jira/browse/IGNITE-11006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolay Izhikov resolved IGNITE-11006.
--
Resolution: Fixed
> Enable problematic whitespace inspection check
> --
>
> Key: IGNITE-11006
> URL: https://issues.apache.org/jira/browse/IGNITE-11006
> Project: Ignite
> Issue Type: Task
>Reporter: Maxim Muzafarov
>Assignee: Nikolay Izhikov
>Priority: Minor
> Labels: inspections
> Fix For: 2.8
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> We need to enable inspection {{General | Problematic whitespace}} to report
> tabs used for indentation when the code style is configured to use only
> spaces.
> Todo:
> # Update the appropriate {{ignite_inspections_teamcity.xml}} configuration
> file
> # Fix all founded code style issues according to the new inspecton rule
> # Update the default inspection profile:
> {{.idea\inspectionProfiles\Project_Default.xml}}
> Probable, this line should be added to the configuration file:
> {code}
>enabled_by_default="true" />
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-11035) Web console: Implemement improvements for query page controller.
[
https://issues.apache.org/jira/browse/IGNITE-11035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16755948#comment-16755948
]
Vasiliy Sisko edited comment on IGNITE-11035 at 2/5/19 3:20 AM:
Implemented confirmation and query cancellation on cluster change and remove of
paragraph.
[~Klaster_1] Please review my changes.
was (Author: vsisko):
Implemented confirmation and query cancellation on cluster change and remove of
paragraph.
> Web console: Implemement improvements for query page controller.
>
>
> Key: IGNITE-11035
> URL: https://issues.apache.org/jira/browse/IGNITE-11035
> Project: Ignite
> Issue Type: Improvement
>Reporter: Vasiliy Sisko
>Assignee: Pavel Konstantinov
>Priority: Major
> Time Spent: 25m
> Remaining Estimate: 0h
>
> # Implement processing of query result task without one level recursion.
> # Explicit serialization to JSON of Paragraph object. Possible
> {{Paragraph.prototype.toJSON should be implemented.}}
> # {{Try to use RXJS operator chain instead of direct usage of subscription
> object.}}
> # {{On query cancel task unlock UI in Promise.prototype.finally.}}
> # {{Check initialization of queryId and resultNodeId on execute of refresh
> in auto refresh mode.}}
> # {{Some paragraph manipulation methods should be moved into Paragraph
> class: _initQueryResult}}{{{color:#00}_, _showLoading._
> {color}}}{{{color:#00}Check other methods with paragraph as
> argument.{color}}}
> # {{{color:#00}Check clearing of data in _initQueryResult method.
> {color}}}{{{color:#00}Try to not use direct calling of grid
> API{color}}}{{{color:#00}. Possible we should show
> “{color}}}{{{color:#00}Query execution{color}}}{{{color:#00}” stub
> {color}}}{{{color:#00}instead.{color}}}
> # {{{color:#00}Remove “beforeunload” listener on leave of Queries
> page.{color}}}
> # {{{color:#00}Possible we should cancel queries when client session is
> over.{color}}}
> # {{{color:#00}Add docs for return values of queries task in agent
> manager. F.e:{color}}}
> {code:java}
> /*
> @returns {Promise}
> */{code}
> # Confirm on leaving of Queries page when running queries exist:
> {code:java}
> You have running queries. Are you sure you want to cancel them?
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-11200) SQL: query contexts should not be static
[ https://issues.apache.org/jira/browse/IGNITE-11200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgenii Zhuravlev reassigned IGNITE-11200: -- Assignee: Evgenii Zhuravlev (was: Vladimir Ozerov) > SQL: query contexts should not be static > > > Key: IGNITE-11200 > URL: https://issues.apache.org/jira/browse/IGNITE-11200 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Vladimir Ozerov >Assignee: Evgenii Zhuravlev >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > Currently query contexts are static and as a result over complicated. Need to > make them instance-bound and remove static. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10602) Failure parsing INLINE_SIZE if CREATE INDEX is one of multiple statements
[
https://issues.apache.org/jira/browse/IGNITE-10602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16760271#comment-16760271
]
Ignite TC Bot commented on IGNITE-10602:
{panel:title=- Run :: SQL: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Queries 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2999293]]
* IgniteBinaryCacheQueryTestSuite:
IgniteCheckClusterStateBeforeExecuteQueryTest.testDynamicSchemaChangesPersistence
- 0,0% fails in last 410 master runs.
{color:#d04437}Platform C++ (Linux){color} [[tests 0 TIMEOUT , Failure on
metric |https://ci.ignite.apache.org/viewLog.html?buildId=2999295]]
{panel}
[TeamCity *- Run :: SQL*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2999298buildTypeId=IgniteTests24Java8_RunAllSql]
> Failure parsing INLINE_SIZE if CREATE INDEX is one of multiple statements
> -
>
> Key: IGNITE-10602
> URL: https://issues.apache.org/jira/browse/IGNITE-10602
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.7
>Reporter: Ilya Kasnacheev
>Assignee: Pavel Kuznetsov
>Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> On an empty cluster issue the following statements (shown using sqlline):
> {code}
> 0: jdbc:ignite:thin://localhost> CREATE TABLE public.transactions (pk INT, id
> INT, k
> . . . . . . . . . . . . . . . .> VARCHAR, v VARCHAR, PRIMARY KEY (pk, id));
> CREATE INDEX transactions_id_k_v ON public.transactions (id, k, v)
> INLINE_SIZE 150; CREATE INDEX transactions_k_v_id ON
> . . . . . . . . . . . . . . . .> public.transactions (k, v, id) INLINE_SIZE
> 150; CREATE INDEX transactions_pk_id ON public.transactions
> . . . . . . . . . . . . . . . .> (pk, id) INLINE_SIZE 20;
> {code}
> Expected: Table is created, three indexes are created.
> Actual: table is created, indexes are NOT created, error is printed:
> {{Error: Failed to parse query. Синтаксическая ошибка в выражении SQL "CREATE
> INDEX TRANSACTIONS_ID_K_V ON PUBLIC.TRANSACTIONS (ID, K, V) INLINE_SIZE[*]
> 150; CREATE INDEX TRANSACTIONS_K_V_ID ON}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10347) Expose system SQL view for running queries
[
https://issues.apache.org/jira/browse/IGNITE-10347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16760220#comment-16760220
]
Ignite TC Bot commented on IGNITE-10347:
{panel:title=-- Run :: All: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2995138buildTypeId=IgniteTests24Java8_RunAll]
> Expose system SQL view for running queries
> --
>
> Key: IGNITE-10347
> URL: https://issues.apache.org/jira/browse/IGNITE-10347
> Project: Ignite
> Issue Type: Task
>Reporter: Yury Gerzhedovich
>Assignee: Yury Gerzhedovich
>Priority: Major
> Labels: iep-29, sql
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Need to expose system SQL view to provide list of running queries. Proposed
> name is *running_queries* with following columns: query_id, node_id, sql,
> schema_name, duration.
> Where,
> query_id - cluster unique id of query
> sql - sql command
> cancelable - is is possible to cancel the query.
> schema_name - SQL schema name
> duration - time in ms from start of execution of query
>
> The view should contains all kind of running queries from RunningQueryManager
> on local node
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11191) Fix Hibernate integration by providing JAXB dependency during compile
[
https://issues.apache.org/jira/browse/IGNITE-11191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16760201#comment-16760201
]
Dmitriy Pavlov commented on IGNITE-11191:
-
https://ci.ignite.apache.org/viewQueued.html?itemId=2999419=queuedBuildOverviewTab_IgniteTests24Java8=ignite-11191
> Fix Hibernate integration by providing JAXB dependency during compile
> -
>
> Key: IGNITE-11191
> URL: https://issues.apache.org/jira/browse/IGNITE-11191
> Project: Ignite
> Issue Type: Bug
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
>
> https://ci.ignite.apache.org/viewLog.html?buildId=2973733=buildResultsDiv=IgniteTests24Java8_Hibernate53#testNameId-1306520535171712877
> {noformat}
> java.lang.NoClassDefFoundError: javax/xml/bind/JAXBException
> at
> org.apache.ignite.cache.hibernate.HibernateL2CacheSelfTest.startHibernate(HibernateL2CacheSelfTest.java:1923)
> at
> org.apache.ignite.cache.hibernate.HibernateL2CacheSelfTest.createSessionFactories(HibernateL2CacheSelfTest.java:1900)
> at
> org.apache.ignite.cache.hibernate.HibernateL2CacheSelfTest.testVersionedEntity(HibernateL2CacheSelfTest.java:1026)
> at
> org.apache.ignite.cache.hibernate.HibernateL2CacheSelfTest.testVersionedEntity(HibernateL2CacheSelfTest.java:1018)
> Caused by: java.lang.ClassNotFoundException: javax.xml.bind.JAXBException
> at
> org.apache.ignite.cache.hibernate.HibernateL2CacheSelfTest.startHibernate(HibernateL2CacheSelfTest.java:1923)
> at
> org.apache.ignite.cache.hibernate.HibernateL2CacheSelfTest.createSessionFactories(HibernateL2CacheSelfTest.java:1900)
> at
> org.apache.ignite.cache.hibernate.HibernateL2CacheSelfTest.testVersionedEntity(HibernateL2CacheSelfTest.java:1026)
> at org.apache.ignite.cache
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-9978) [ML] Implement Compound Naive Bayes classifier
[ https://issues.apache.org/jira/browse/IGNITE-9978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravil Galeyev reassigned IGNITE-9978: - Assignee: Ravil Galeyev > [ML] Implement Compound Naive Bayes classifier > -- > > Key: IGNITE-9978 > URL: https://issues.apache.org/jira/browse/IGNITE-9978 > Project: Ignite > Issue Type: Task > Components: ml >Reporter: Alexey Platonov >Assignee: Ravil Galeyev >Priority: Major > Labels: new-feature > Fix For: 2.8 > > > We need to create compound Naive Bayes classifier as model composition of > several Naive Bayes classifiers where each classifier represents subset of > features of one type. For example such model may contain Naive Bayes model > over Gauss Distribution for all continuous features and Naive Bayes model > over Discrete Distribution for enum-like features. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8841) MVCC TX: Read transactions remap when coordinator fails.
[
https://issues.apache.org/jira/browse/IGNITE-8841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16760147#comment-16760147
]
Roman Kondakov commented on IGNITE-8841:
[~gvvinblade], patch looks good for me. There are a couple of minor remarks:
# {{MvccProcessor#requestWriteSnapshotAsync()}} is not used anymore.
# {{MvccProcessorImpl.java:235}} blank lines in constructor.
> MVCC TX: Read transactions remap when coordinator fails.
>
>
> Key: IGNITE-8841
> URL: https://issues.apache.org/jira/browse/IGNITE-8841
> Project: Ignite
> Issue Type: Bug
> Components: mvcc, sql
>Reporter: Roman Kondakov
>Assignee: Igor Seliverstov
>Priority: Major
> Labels: failover
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> At the moment read transactions that don't acquire topology lock will be
> forcibly rolled back on topology change as read tx can be in fly while
> topology being change.
> This is done to prevent having active transaction with stale snapshots on
> new topology in cases of TX coordinator or Near node were lost.
>
> It would be nice to remap it somehow until they locked a topology or at least
> throw some meaningful exception to user.
> For example, it is possible to obtain a new "write" mvcc version from the
> new coordinator and use this version for all further writes while using "old"
> version for reads. In this case we need to change visibility rules a little:
> "old" version should see "own" updates made by "new" "write" version.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10602) Failure parsing INLINE_SIZE if CREATE INDEX is one of multiple statements
[
https://issues.apache.org/jira/browse/IGNITE-10602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16760138#comment-16760138
]
Ignite TC Bot commented on IGNITE-10602:
{panel:title=-- Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Queries 1{color} [[tests
6|https://ci.ignite.apache.org/viewLog.html?buildId=2997465]]
* IgniteBinaryCacheQueryTestSuite:
IgniteCheckClusterStateBeforeExecuteQueryTest.testDynamicSchemaChangesPersistence
- 0,0% fails in last 413 master runs.
{color:#d04437}Data Structures{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2997449]]
* IgniteCacheDataStructuresSelfTestSuite:
IgniteCacheAtomicReplicatedNodeRestartSelfTest.testRestartWithPutSixNodesTwoBackups
- 0,0% fails in last 414 master runs.
{color:#d04437}Platform C++ (Linux){color} [[tests 500 JVM CRASH , Exit Code ,
Failure on metric |https://ci.ignite.apache.org/viewLog.html?buildId=2997413]]
* IgniteCoreTest: CacheQueryTestSuite: TestFieldsQuerySeveral - 3,9% fails in
last 947 master runs.
* IgniteCoreTest: CacheQueryTestSuite: TestFieldsQueryPagesSeveral - 3,9% fails
in last 947 master runs.
* IgniteOdbcTest: SqlOperatorTestSuite: TestOperatorNotEquealInt - 1,4% fails
in last 948 master runs.
* IgniteOdbcTest: SqlValueExpressionTestSuite: TestCase - 1,4% fails in last
948 master runs.
* IgniteOdbcTest: SqlValueExpressionTestSuite: TestCast - 1,4% fails in last
948 master runs.
* IgniteOdbcTest: SqlValueExpressionTestSuite: TestCoalesce - 1,4% fails in
last 948 master runs.
* IgniteOdbcTest: SqlTypesTestSuite: TestByteArraySelect - 1,4% fails in last
948 master runs.
* IgniteOdbcTest: SqlTypesTestSuite: TestByteArrayParam - 1,4% fails in last
948 master runs.
* IgniteOdbcTest: SqlTypesTestSuite: TestByteArrayParamInsert - 1,4% fails in
last 948 master runs.
* IgniteOdbcTest: SqlTypesTestSuite: TestTimestampSelect - 1,4% fails in last
948 master runs.
* IgniteOdbcTest: SqlTypesTestSuite: TestTimestampInsert - 1,4% fails in last
948 master runs.
* IgniteOdbcTest: SqlTypesTestSuite: TestTimeInsert - 1,4% fails in last 948
master runs.
* IgniteOdbcTest: SslQueriesTestSuite: TestConnectionSslSuccess - 1,4% fails in
last 948 master runs.
* IgniteOdbcTest: StreamingTestSuite: TestStreamingManyObjects - 1,3% fails in
last 947 master runs.
* IgniteOdbcTest: TypesTestSuite: TestZeroDecimal - 1,3% fails in last 947
master runs.
* IgniteOdbcTest: StreamingTestSuite: TestStreamingSimple - 1,3% fails in last
947 master runs.
* IgniteOdbcTest: TransactionTestSuite: TransactionConnectionRollbackUpdate1 -
1,3% fails in last 947 master runs.
* IgniteOdbcTest: StreamingTestSuite: TestStreamingAllOptions - 1,3% fails in
last 947 master runs.
* IgniteOdbcTest: TransactionTestSuite: TransactionConnectionTxModeCommit -
1,3% fails in last 947 master runs.
* IgniteOdbcTest: StreamingTestSuite: TestStreamingReset - 1,3% fails in last
947 master runs.
* IgniteOdbcTest: StreamingTestSuite: TestStreamingClosingStatement - 1,3%
fails in last 947 master runs.
* IgniteOdbcTest: StreamingTestSuite: TestStreamingSeveralStatements - 1,3%
fails in last 947 master runs.
* IgniteOdbcTest: StreamingTestSuite: TestStreamingDifferentStatements - 1,3%
fails in last 947 master runs.
* IgniteOdbcTest: TransactionTestSuite: TransactionEnvironmentCommit - 1,3%
fails in last 947 master runs.
* IgniteOdbcTest: TransactionTestSuite: TransactionEnvironmentRollbackInsert -
1,3% fails in last 947 master runs.
* IgniteOdbcTest: TransactionTestSuite: TransactionEnvironmentTxModeCommit -
1,3% fails in last 947 master runs.
* IgniteOdbcTest: SqlSystemFunctionTestSuite: TestSystemFunctionUser - 1,3%
fails in last 948 master runs.
* IgniteOdbcTest: SqlEscConvertFunctionTestSuite: TestEscConvertFunctionGetInfo
- 1,3% fails in last 948 master runs.
* IgniteOdbcTest: SqlEscConvertFunctionTestSuite: TestEscConvertFunctionBool -
1,3% fails in last 948 master runs.
* IgniteOdbcTest: SqlEscConvertFunctionTestSuite: TestEscConvertFunctionDecimal
- 1,3% fails in last 948 master runs.
* IgniteOdbcTest: SqlEscConvertFunctionTestSuite: TestEscConvertFunctionDouble
- 1,3% fails in last 948 master runs.
* IgniteOdbcTest: SqlEscConvertFunctionTestSuite: TestEscConvertFunctionFloat -
1,3% fails in last 948 master runs.
* IgniteOdbcTest: SqlOperatorTestSuite: TestOperatorGreaterEquealInt - 1,3%
fails in last 948 master runs.
* IgniteOdbcTest: SqlOperatorTestSuite: TestOperatorLessEquealInt - 1,3% fails
in last 948 master runs.
* IgniteOdbcTest: SqlOperatorTestSuite: TestOperatorEquealInt - 1,3% fails in
last 948 master runs.
* IgniteOdbcTest: SqlOperatorTestSuite: TestOperatorEquealDouble - 1,3% fails
in last 948 master runs.
* IgniteOdbcTest: SqlOperatorTestSuite: TestOperatorEquealString - 1,3% fails
in last 948 master runs.
* IgniteOdbcTest: SqlTypesTestSuite: TestGuidTrivial - 1,3% fails in last 948
[jira] [Updated] (IGNITE-10927) Relieve JUnit3TestLegacySupport from inheriting deprecated junit.framework.Assert (follow-up to IGNITE-10177)
[
https://issues.apache.org/jira/browse/IGNITE-10927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Kasnacheev updated IGNITE-10927:
-
Ignite Flags: (was: Docs Required)
> Relieve JUnit3TestLegacySupport from inheriting deprecated
> junit.framework.Assert (follow-up to IGNITE-10177)
> -
>
> Key: IGNITE-10927
> URL: https://issues.apache.org/jira/browse/IGNITE-10927
> Project: Ignite
> Issue Type: Sub-task
>Affects Versions: 2.7
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> {{JUnit3TestLegacySupport}} currently inherits deprecated
> {{junit.framework.Assert}}. This was done only in order to minimize risky
> code changes when tests were migrating from Junit 3, after
> {{GridAbstractTest}} has dropped inheriting {{junit.framework.TestCase}}.
> Now that migration is over it is less risky to cleanup project from
> deprecated assert methods and drop the harmful inheritance. In order to make
> this smoother and minimize amount of test changes, after inheritance is
> dropped, {{JUnit3TestLegacySupport}} should be extended with a set of
> "temporary patch" methods that would delegate most popular assertions used by
> subclasses to respective methods of {{org.junit.Assert}}.
> Mentioned temporary patch methods, in turn, should respective
> {{2deprecation}} notices in javadocs that would encourage developers to
> (safely and gradually) change them to direct invocations and static imports
> of respective Assert methods instead of using those inherited from
> superclass. These patch methods should be declared {{protected final}} or
> {{protected static}}, in order to minimize their applicability and prevent
> them spreading more than intended. (as a side note, experimenting has shown
> that use of {{@Deprecated}} annotation is not feasible as it deprives
> developers an option to use static imports)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10927) Relieve JUnit3TestLegacySupport from inheriting deprecated junit.framework.Assert (follow-up to IGNITE-10177)
[
https://issues.apache.org/jira/browse/IGNITE-10927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16760137#comment-16760137
]
Ilya Kasnacheev commented on IGNITE-10927:
--
Thank you for this contribution! I have merged it to master with minor tweak.
> Relieve JUnit3TestLegacySupport from inheriting deprecated
> junit.framework.Assert (follow-up to IGNITE-10177)
> -
>
> Key: IGNITE-10927
> URL: https://issues.apache.org/jira/browse/IGNITE-10927
> Project: Ignite
> Issue Type: Sub-task
>Affects Versions: 2.7
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> {{JUnit3TestLegacySupport}} currently inherits deprecated
> {{junit.framework.Assert}}. This was done only in order to minimize risky
> code changes when tests were migrating from Junit 3, after
> {{GridAbstractTest}} has dropped inheriting {{junit.framework.TestCase}}.
> Now that migration is over it is less risky to cleanup project from
> deprecated assert methods and drop the harmful inheritance. In order to make
> this smoother and minimize amount of test changes, after inheritance is
> dropped, {{JUnit3TestLegacySupport}} should be extended with a set of
> "temporary patch" methods that would delegate most popular assertions used by
> subclasses to respective methods of {{org.junit.Assert}}.
> Mentioned temporary patch methods, in turn, should respective
> {{2deprecation}} notices in javadocs that would encourage developers to
> (safely and gradually) change them to direct invocations and static imports
> of respective Assert methods instead of using those inherited from
> superclass. These patch methods should be declared {{protected final}} or
> {{protected static}}, in order to minimize their applicability and prevent
> them spreading more than intended. (as a side note, experimenting has shown
> that use of {{@Deprecated}} annotation is not feasible as it deprives
> developers an option to use static imports)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11195) Platform C++ tests failed to find JVM for Java 11 build
[
https://issues.apache.org/jira/browse/IGNITE-11195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16760102#comment-16760102
]
Alexey Goncharuk commented on IGNITE-11195:
---
In the run I can see that {{JAVA_HOME}} is set correctly. [~isapego], can you
please take a look?
> Platform C++ tests failed to find JVM for Java 11 build
> ---
>
> Key: IGNITE-11195
> URL: https://issues.apache.org/jira/browse/IGNITE-11195
> Project: Ignite
> Issue Type: Bug
>Reporter: Dmitriy Pavlov
>Priority: Major
>
> 482 C++ tests failed with error
> {noformat}
> std::exception: JVM library is not found (did you set JAVA_HOME environment
> variable?)
> {noformat}
> https://ci.ignite.apache.org/viewLog.html?buildId=2973675=IgniteTests24Java8_PlatformCWinX64Release=buildResultsDiv_IgniteTests24Java8=ignite-11155
> Looks like we need somehow handle new parameters in C++ tests
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11199) Add extra logging for client-server connections in TCP discovery
[
https://issues.apache.org/jira/browse/IGNITE-11199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Rakov updated IGNITE-11199:
Summary: Add extra logging for client-server connections in TCP discovery
(was: Extend logging for client-server connections in TCP discovery)
> Add extra logging for client-server connections in TCP discovery
>
>
> Key: IGNITE-11199
> URL: https://issues.apache.org/jira/browse/IGNITE-11199
> Project: Ignite
> Issue Type: Improvement
>Reporter: Ivan Rakov
>Priority: Major
>
> When client node connects to a server node, it should print detailed
> information about server (at least, server node ID and consistent ID).
> When server node starts serving client node connection, it also should print
> detailed information about client.
> Currently, all we have is abstract logs about connections.
> On client side:
> {code:java}
> [2019-02-02 17:50:43,270][INFO
> ][grid-nio-worker-tcp-comm-0-#24][TcpCommunicationSpi] Established outgoing
> communication connection [locAddr=/127.0.0.1:53183, rmtAddr=/127.0.0.1:47100]
> [2019-02-02 17:50:43,446][INFO
> ][grid-nio-worker-tcp-comm-1-#25][TcpCommunicationSpi] Established outgoing
> communication connection [locAddr=/127.0.0.1:53184, rmtAddr=/127.0.0.1:47103]
> {code}
> On server side:
> {code:java}
> ./mahina98-2019-02-01.log:<190>Feb 1 18:24:19 mahina98.ca.sbrf.ru 2019-02-01
> 18:24:19.236[INFO
> ][tcp-disco-sock-reader-#5%DPL_GRID%DplGridNodeName%][o.a.i.s.d.tcp.TcpDiscoverySpi][tcp-disco-sock-reader-#5%DPL_GRID%DplGridNodeName%]
> Started serving remote node connection [rmtAddr=/10.124.133.5:56297,
> rmtPort=56297]
> {code}
> This is definetely not enough to find out which clients connected to local
> server node and to which server local client node has been connected.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10755) MVCC: Flaky continuous query tests
[
https://issues.apache.org/jira/browse/IGNITE-10755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16760049#comment-16760049
]
Roman Kondakov commented on IGNITE-10755:
-
[~gvvinblade],
# Listeners initialization (obtaining the current update counters map) was
moved under the listeners write lock. This allows to avoid collecting pending
events in the dedicated map.
# Listener registration lock has been moved from the cache context to the
group context to avoid races between adding cache to the
{{CacheGroupContext#contQryCaches}} and listeners registration. When each cache
has it's own listener lock, adding and notifying listeners are not synchronized
between different caches within same group. And there were possible situations
when uninitialized listener was supplied with a skip update event fired in the
neighbor cache.
> MVCC: Flaky continuous query tests
> --
>
> Key: IGNITE-10755
> URL: https://issues.apache.org/jira/browse/IGNITE-10755
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Assignee: Roman Kondakov
>Priority: Major
> Labels: CQ, MakeTeamcityGreenAgain, mvcc_stabilization_stage_1
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Some continuous query tests are flaky when MVCC is enabled:
> * {{CacheContinuousQueryConcurrentPartitionUpdateTest}}
> ** {{testConcurrentUpdatesAndQueryStartMvccTxCacheGroup}}
> ** {{testConcurrentUpdatesAndQueryStartMvccTx}}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10261) MVCC: cache operation may hang during late affinity assignment.
[
https://issues.apache.org/jira/browse/IGNITE-10261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16760005#comment-16760005
]
Ignite TC Bot commented on IGNITE-10261:
{panel:title=-- Run :: All: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2964160buildTypeId=IgniteTests24Java8_RunAll]
> MVCC: cache operation may hang during late affinity assignment.
> ---
>
> Key: IGNITE-10261
> URL: https://issues.apache.org/jira/browse/IGNITE-10261
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Affects Versions: 2.7
>Reporter: Andrew Mashenkov
>Assignee: Roman Kondakov
>Priority: Critical
> Labels: failover, mvcc_stabilization_stage_1
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> ForceKey response processing fails with ClassCastException with Mvcc mode
> that causes test hanging.
> Issue can be easily reproduced with backups > 0 and disabled rebalance. See
> GridCacheDhtPreloadPutGetSelfTest.testPutGetNone1().
> Also CacheLateAffinityAssignmentTest.testRandomOperations() hangs sometimes
> due to same reason.
>
> {noformat}
> java.lang.ClassCastException:
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheEntry
> cannot be cast to
> org.apache.ignite.internal.processors.cache.mvcc.MvccVersionAware
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtForceKeysFuture$MiniFuture.onResult(GridDhtForceKeysFuture.java:545)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtForceKeysFuture.onResult(GridDhtForceKeysFuture.java:202)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter.processForceKeyResponse(GridDhtCacheAdapter.java:180)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$11.onMessage(GridDhtTransactionalCacheAdapter.java:208)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$11.onMessage(GridDhtTransactionalCacheAdapter.java:206)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter$MessageHandler.apply(GridDhtCacheAdapter.java:1434)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter$MessageHandler.apply(GridDhtCacheAdapter.java:1416)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1054)
> {noformat}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9998) .NET: Implement partition preload API
[ https://issues.apache.org/jira/browse/IGNITE-9998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16759997#comment-16759997 ] Pavel Tupitsyn commented on IGNITE-9998: [~ivandasch] Looks good to me in general; please see a couple comments on GitHub. > .NET: Implement partition preload API > - > > Key: IGNITE-9998 > URL: https://issues.apache.org/jira/browse/IGNITE-9998 > Project: Ignite > Issue Type: Improvement >Reporter: Alexei Scherbakov >Assignee: Ivan Daschinskiy >Priority: Major > Fix For: 2.8 > > Time Spent: 20m > Remaining Estimate: 0h > > ICache.PreloadPartition > ICache.PreloadPartitionAsync -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10261) MVCC: cache operation may hang during late affinity assignment.
[
https://issues.apache.org/jira/browse/IGNITE-10261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16760007#comment-16760007
]
Roman Kondakov commented on IGNITE-10261:
-
[~amashenkov], [~gvvinblade], patch is ready for review. TC looks good.
> MVCC: cache operation may hang during late affinity assignment.
> ---
>
> Key: IGNITE-10261
> URL: https://issues.apache.org/jira/browse/IGNITE-10261
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Affects Versions: 2.7
>Reporter: Andrew Mashenkov
>Assignee: Roman Kondakov
>Priority: Critical
> Labels: failover, mvcc_stabilization_stage_1
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> ForceKey response processing fails with ClassCastException with Mvcc mode
> that causes test hanging.
> Issue can be easily reproduced with backups > 0 and disabled rebalance. See
> GridCacheDhtPreloadPutGetSelfTest.testPutGetNone1().
> Also CacheLateAffinityAssignmentTest.testRandomOperations() hangs sometimes
> due to same reason.
>
> {noformat}
> java.lang.ClassCastException:
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheEntry
> cannot be cast to
> org.apache.ignite.internal.processors.cache.mvcc.MvccVersionAware
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtForceKeysFuture$MiniFuture.onResult(GridDhtForceKeysFuture.java:545)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtForceKeysFuture.onResult(GridDhtForceKeysFuture.java:202)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter.processForceKeyResponse(GridDhtCacheAdapter.java:180)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$11.onMessage(GridDhtTransactionalCacheAdapter.java:208)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$11.onMessage(GridDhtTransactionalCacheAdapter.java:206)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter$MessageHandler.apply(GridDhtCacheAdapter.java:1434)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter$MessageHandler.apply(GridDhtCacheAdapter.java:1416)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1054)
> {noformat}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9927) Fix flaky failures in CacheContinuousQueryOperationFromCallbackTest
[
https://issues.apache.org/jira/browse/IGNITE-9927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16760002#comment-16760002
]
Roman Kondakov commented on IGNITE-9927:
[~amashenkov], [~gvvinblade], I've merged patch with updated master and fixed
MVCC write conflict handling. TC looks good. Patch is ready for review.
> Fix flaky failures in CacheContinuousQueryOperationFromCallbackTest
> ---
>
> Key: IGNITE-9927
> URL: https://issues.apache.org/jira/browse/IGNITE-9927
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Vladimir Ozerov
>Assignee: Roman Kondakov
>Priority: Major
> Labels: CQ, mvcc_stabilization_stage_1
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> This test was reworked significantly as a part of IGNITE-7953. Unfortunately
> it led to a number of failures appearing from time to time. The goal of this
> ticket is to get rid of these failures.
> Changes from {{51a202a4c48220fa919f47147bd4889033cd35a8}} commit should be
> applied to the test before starting investigation.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9927) Fix flaky failures in CacheContinuousQueryOperationFromCallbackTest
[
https://issues.apache.org/jira/browse/IGNITE-9927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1675#comment-1675
]
Ignite TC Bot commented on IGNITE-9927:
---
{panel:title=-- Run :: All: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2994874buildTypeId=IgniteTests24Java8_RunAll]
> Fix flaky failures in CacheContinuousQueryOperationFromCallbackTest
> ---
>
> Key: IGNITE-9927
> URL: https://issues.apache.org/jira/browse/IGNITE-9927
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Vladimir Ozerov
>Assignee: Roman Kondakov
>Priority: Major
> Labels: CQ, mvcc_stabilization_stage_1
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> This test was reworked significantly as a part of IGNITE-7953. Unfortunately
> it led to a number of failures appearing from time to time. The goal of this
> ticket is to get rid of these failures.
> Changes from {{51a202a4c48220fa919f47147bd4889033cd35a8}} commit should be
> applied to the test before starting investigation.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11200) SQL: query contexts should not be static
[ https://issues.apache.org/jira/browse/IGNITE-11200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16759989#comment-16759989 ] Vladimir Ozerov commented on IGNITE-11200: -- Implemented. Test run: https://ci.ignite.apache.org/viewQueued.html?itemId=2997723 > SQL: query contexts should not be static > > > Key: IGNITE-11200 > URL: https://issues.apache.org/jira/browse/IGNITE-11200 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > Currently query contexts are static and as a result over complicated. Need to > make them instance-bound and remove static. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11200) SQL: query contexts should not be static
Vladimir Ozerov created IGNITE-11200: Summary: SQL: query contexts should not be static Key: IGNITE-11200 URL: https://issues.apache.org/jira/browse/IGNITE-11200 Project: Ignite Issue Type: Task Components: sql Reporter: Vladimir Ozerov Assignee: Vladimir Ozerov Fix For: 2.8 Currently query contexts are static and as a result over complicated. Need to make them instance-bound and remove static. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11191) Fix Hibernate integration by providing JAXB dependency during compile
[
https://issues.apache.org/jira/browse/IGNITE-11191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-11191:
Ignite Flags: (was: Docs Required)
> Fix Hibernate integration by providing JAXB dependency during compile
> -
>
> Key: IGNITE-11191
> URL: https://issues.apache.org/jira/browse/IGNITE-11191
> Project: Ignite
> Issue Type: Bug
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
>
> https://ci.ignite.apache.org/viewLog.html?buildId=2973733=buildResultsDiv=IgniteTests24Java8_Hibernate53#testNameId-1306520535171712877
> {noformat}
> java.lang.NoClassDefFoundError: javax/xml/bind/JAXBException
> at
> org.apache.ignite.cache.hibernate.HibernateL2CacheSelfTest.startHibernate(HibernateL2CacheSelfTest.java:1923)
> at
> org.apache.ignite.cache.hibernate.HibernateL2CacheSelfTest.createSessionFactories(HibernateL2CacheSelfTest.java:1900)
> at
> org.apache.ignite.cache.hibernate.HibernateL2CacheSelfTest.testVersionedEntity(HibernateL2CacheSelfTest.java:1026)
> at
> org.apache.ignite.cache.hibernate.HibernateL2CacheSelfTest.testVersionedEntity(HibernateL2CacheSelfTest.java:1018)
> Caused by: java.lang.ClassNotFoundException: javax.xml.bind.JAXBException
> at
> org.apache.ignite.cache.hibernate.HibernateL2CacheSelfTest.startHibernate(HibernateL2CacheSelfTest.java:1923)
> at
> org.apache.ignite.cache.hibernate.HibernateL2CacheSelfTest.createSessionFactories(HibernateL2CacheSelfTest.java:1900)
> at
> org.apache.ignite.cache.hibernate.HibernateL2CacheSelfTest.testVersionedEntity(HibernateL2CacheSelfTest.java:1026)
> at org.apache.ignite.cache
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11199) Extend logging for client-server connections in TCP discovery
Ivan Rakov created IGNITE-11199:
---
Summary: Extend logging for client-server connections in TCP
discovery
Key: IGNITE-11199
URL: https://issues.apache.org/jira/browse/IGNITE-11199
Project: Ignite
Issue Type: Improvement
Reporter: Ivan Rakov
When client node connects to a server node, it should print detailed
information about server (at least, server node ID and consistent ID).
When server node starts serving client node connection, it also should print
detailed information about client.
Currently, all we have is abstract logs about connections.
On client side:
{code:java}
[2019-02-02 17:50:43,270][INFO
][grid-nio-worker-tcp-comm-0-#24][TcpCommunicationSpi] Established outgoing
communication connection [locAddr=/127.0.0.1:53183, rmtAddr=/127.0.0.1:47100]
[2019-02-02 17:50:43,446][INFO
][grid-nio-worker-tcp-comm-1-#25][TcpCommunicationSpi] Established outgoing
communication connection [locAddr=/127.0.0.1:53184, rmtAddr=/127.0.0.1:47103]
{code}
On server side:
{code:java}
./mahina98-2019-02-01.log:<190>Feb 1 18:24:19 mahina98.ca.sbrf.ru 2019-02-01
18:24:19.236[INFO
][tcp-disco-sock-reader-#5%DPL_GRID%DplGridNodeName%][o.a.i.s.d.tcp.TcpDiscoverySpi][tcp-disco-sock-reader-#5%DPL_GRID%DplGridNodeName%]
Started serving remote node connection [rmtAddr=/10.124.133.5:56297,
rmtPort=56297]
{code}
This is definetely not enough to find out which clients connected to local
server node and to which server local client node has been connected.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11198) [TC Bot] Apache Ignite TeamCity Bot unable to issue visa for special symbol '|'
Dmitriy Pavlov created IGNITE-11198: --- Summary: [TC Bot] Apache Ignite TeamCity Bot unable to issue visa for special symbol '|' Key: IGNITE-11198 URL: https://issues.apache.org/jira/browse/IGNITE-11198 Project: Ignite Issue Type: Bug Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov Presence of special symbol '|' in suite name, which failure during TC run, makes the Bot to be unable to left JIRA comment, JIRA REST failed with escape. Replace '|' to, for example, '_' symbol in suites name for JIRA comment generation -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11104) Remove Java 7 and AI 1.x leftovers from IgniteSystemProperties & IgniteProductVersion
[ https://issues.apache.org/jira/browse/IGNITE-11104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16759950#comment-16759950 ] Dmitriy Pavlov commented on IGNITE-11104: - LGTM, [~ilyak], could you please merge the change? Thank you for making the code more clear. > Remove Java 7 and AI 1.x leftovers from IgniteSystemProperties & > IgniteProductVersion > - > > Key: IGNITE-11104 > URL: https://issues.apache.org/jira/browse/IGNITE-11104 > Project: Ignite > Issue Type: Improvement > Components: general >Affects Versions: 2.7 >Reporter: Ilya Kasnacheev >Assignee: Ilya Kasnacheev >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > IGNITE_FORCE_START_JAVA7 can no longer do anything useful, for example. > Should remove it right away since it's noop. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11153) Support Java 11 for control.sh & ignitevisorcmd.sh: remove odd --add-modules for java.xml.bind
[
https://issues.apache.org/jira/browse/IGNITE-11153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Ivanov updated IGNITE-11153:
--
Fix Version/s: 2.8
> Support Java 11 for control.sh & ignitevisorcmd.sh: remove odd --add-modules
> for java.xml.bind
> --
>
> Key: IGNITE-11153
> URL: https://issues.apache.org/jira/browse/IGNITE-11153
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Assignee: Peter Ivanov
>Priority: Major
> Fix For: 2.8
>
>
> JAXB module was removed from Java 11.
> Please adopt ignite control.sh in the same way as it is done for ignite.sh/bat
> {noformat}
> elif [ $version -gt 8 ] && [ $version -lt 11 ]; then
> JVM_OPTS="\
> -XX:+AggressiveOpts \
> --add-exports=java.base/jdk.internal.misc=ALL-UNNAMED \
> --add-exports=java.base/sun.nio.ch=ALL-UNNAMED \
> --add-exports=java.management/com.sun.jmx.mbeanserver=ALL-UNNAMED \
> --add-exports=jdk.internal.jvmstat/sun.jvmstat.monitor=ALL-UNNAMED \
>
> --add-exports=java.base/sun.reflect.generics.reflectiveObjects=ALL-UNNAMED \
> --illegal-access=permit \
> --add-modules=java.transaction \
> --add-modules=java.xml.bind \
> ${JVM_OPTS}"
> elif [ $version -eq 11 ] ; then
> JVM_OPTS="\
> --add-exports=java.base/jdk.internal.misc=ALL-UNNAMED \
> --add-exports=java.base/sun.nio.ch=ALL-UNNAMED \
> --add-exports=java.management/com.sun.jmx.mbeanserver=ALL-UNNAMED \
> --add-exports=jdk.internal.jvmstat/sun.jvmstat.monitor=ALL-UNNAMED \
>
> --add-exports=java.base/sun.reflect.generics.reflectiveObjects=ALL-UNNAMED \
> --illegal-access=permit \
> ${JVM_OPTS}"
> {noformat}
> But control.sh for master still declares --add-modules java.xml.bind \
> {noformat}
> JVM_OPTS="--add-exports java.base/jdk.internal.misc=ALL-UNNAMED \
> --add-exports java.base/sun.nio.ch=ALL-UNNAMED \
> --add-exports java.management/com.sun.jmx.mbeanserver=ALL-UNNAMED \
> --add-exports jdk.internal.jvmstat/sun.jvmstat.monitor=ALL-UNNAMED \
> --add-modules java.xml.bind \
> ${JVM_OPTS}"
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-11153) Support Java 11 for control.sh & ignitevisorcmd.sh: remove odd --add-modules for java.xml.bind
[
https://issues.apache.org/jira/browse/IGNITE-11153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Ivanov reassigned IGNITE-11153:
-
Assignee: Peter Ivanov
> Support Java 11 for control.sh & ignitevisorcmd.sh: remove odd --add-modules
> for java.xml.bind
> --
>
> Key: IGNITE-11153
> URL: https://issues.apache.org/jira/browse/IGNITE-11153
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Assignee: Peter Ivanov
>Priority: Major
>
> JAXB module was removed from Java 11.
> Please adopt ignite control.sh in the same way as it is done for ignite.sh/bat
> {noformat}
> elif [ $version -gt 8 ] && [ $version -lt 11 ]; then
> JVM_OPTS="\
> -XX:+AggressiveOpts \
> --add-exports=java.base/jdk.internal.misc=ALL-UNNAMED \
> --add-exports=java.base/sun.nio.ch=ALL-UNNAMED \
> --add-exports=java.management/com.sun.jmx.mbeanserver=ALL-UNNAMED \
> --add-exports=jdk.internal.jvmstat/sun.jvmstat.monitor=ALL-UNNAMED \
>
> --add-exports=java.base/sun.reflect.generics.reflectiveObjects=ALL-UNNAMED \
> --illegal-access=permit \
> --add-modules=java.transaction \
> --add-modules=java.xml.bind \
> ${JVM_OPTS}"
> elif [ $version -eq 11 ] ; then
> JVM_OPTS="\
> --add-exports=java.base/jdk.internal.misc=ALL-UNNAMED \
> --add-exports=java.base/sun.nio.ch=ALL-UNNAMED \
> --add-exports=java.management/com.sun.jmx.mbeanserver=ALL-UNNAMED \
> --add-exports=jdk.internal.jvmstat/sun.jvmstat.monitor=ALL-UNNAMED \
>
> --add-exports=java.base/sun.reflect.generics.reflectiveObjects=ALL-UNNAMED \
> --illegal-access=permit \
> ${JVM_OPTS}"
> {noformat}
> But control.sh for master still declares --add-modules java.xml.bind \
> {noformat}
> JVM_OPTS="--add-exports java.base/jdk.internal.misc=ALL-UNNAMED \
> --add-exports java.base/sun.nio.ch=ALL-UNNAMED \
> --add-exports java.management/com.sun.jmx.mbeanserver=ALL-UNNAMED \
> --add-exports jdk.internal.jvmstat/sun.jvmstat.monitor=ALL-UNNAMED \
> --add-modules java.xml.bind \
> ${JVM_OPTS}"
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11153) Support Java 11 for control.sh & ignitevisorcmd.sh: remove odd --add-modules for java.xml.bind
[
https://issues.apache.org/jira/browse/IGNITE-11153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Ivanov updated IGNITE-11153:
--
Affects Version/s: 2.7
> Support Java 11 for control.sh & ignitevisorcmd.sh: remove odd --add-modules
> for java.xml.bind
> --
>
> Key: IGNITE-11153
> URL: https://issues.apache.org/jira/browse/IGNITE-11153
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.7
>Reporter: Dmitriy Pavlov
>Assignee: Peter Ivanov
>Priority: Major
> Fix For: 2.8
>
>
> JAXB module was removed from Java 11.
> Please adopt ignite control.sh in the same way as it is done for ignite.sh/bat
> {noformat}
> elif [ $version -gt 8 ] && [ $version -lt 11 ]; then
> JVM_OPTS="\
> -XX:+AggressiveOpts \
> --add-exports=java.base/jdk.internal.misc=ALL-UNNAMED \
> --add-exports=java.base/sun.nio.ch=ALL-UNNAMED \
> --add-exports=java.management/com.sun.jmx.mbeanserver=ALL-UNNAMED \
> --add-exports=jdk.internal.jvmstat/sun.jvmstat.monitor=ALL-UNNAMED \
>
> --add-exports=java.base/sun.reflect.generics.reflectiveObjects=ALL-UNNAMED \
> --illegal-access=permit \
> --add-modules=java.transaction \
> --add-modules=java.xml.bind \
> ${JVM_OPTS}"
> elif [ $version -eq 11 ] ; then
> JVM_OPTS="\
> --add-exports=java.base/jdk.internal.misc=ALL-UNNAMED \
> --add-exports=java.base/sun.nio.ch=ALL-UNNAMED \
> --add-exports=java.management/com.sun.jmx.mbeanserver=ALL-UNNAMED \
> --add-exports=jdk.internal.jvmstat/sun.jvmstat.monitor=ALL-UNNAMED \
>
> --add-exports=java.base/sun.reflect.generics.reflectiveObjects=ALL-UNNAMED \
> --illegal-access=permit \
> ${JVM_OPTS}"
> {noformat}
> But control.sh for master still declares --add-modules java.xml.bind \
> {noformat}
> JVM_OPTS="--add-exports java.base/jdk.internal.misc=ALL-UNNAMED \
> --add-exports java.base/sun.nio.ch=ALL-UNNAMED \
> --add-exports java.management/com.sun.jmx.mbeanserver=ALL-UNNAMED \
> --add-exports jdk.internal.jvmstat/sun.jvmstat.monitor=ALL-UNNAMED \
> --add-modules java.xml.bind \
> ${JVM_OPTS}"
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11118) SQL: Ability to resolve argument without H2
[ https://issues.apache.org/jira/browse/IGNITE-8?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Lapin updated IGNITE-8: - Summary: SQL: Ability to resolve argument without H2 (was: SQL: Ability to resolve partition from argument without H2) > SQL: Ability to resolve argument without H2 > --- > > Key: IGNITE-8 > URL: https://issues.apache.org/jira/browse/IGNITE-8 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Vladimir Ozerov >Assignee: Alexander Lapin >Priority: Major > Labels: iep-24 > Fix For: 2.8 > > > Currently we rely on H2 to get final partition: we need to convert originally > passed argument to expected argument type. > We need to write our own code to handle this as H2 code will not be available > by thin clients. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9998) .NET: Implement partition preload API
[
https://issues.apache.org/jira/browse/IGNITE-9998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16759920#comment-16759920
]
Ignite TC Bot commented on IGNITE-9998:
---
{panel:title=- Run :: .NET: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *- Run :: .NET*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2995395buildTypeId=IgniteTests24Java8_RunAllNet]
> .NET: Implement partition preload API
> -
>
> Key: IGNITE-9998
> URL: https://issues.apache.org/jira/browse/IGNITE-9998
> Project: Ignite
> Issue Type: Improvement
>Reporter: Alexei Scherbakov
>Assignee: Ivan Daschinskiy
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> ICache.PreloadPartition
> ICache.PreloadPartitionAsync
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11197) SQL:Ability to resolve partiton for temporal data types.
Alexander Lapin created IGNITE-11197: Summary: SQL:Ability to resolve partiton for temporal data types. Key: IGNITE-11197 URL: https://issues.apache.org/jira/browse/IGNITE-11197 Project: Ignite Issue Type: Bug Components: sql Reporter: Alexander Lapin Within org.apache.ignite.internal.sql.optimizer.affinity.PartitionUtils#convert it's now possible to convert following data types: * BOOLEAN, * BYTE, * SHORT, * INT, * LONG, * FLOAT, * DOUBLE, * STRING, * DECIMAL, * UUID; Following temporal data types should also be supported: * DATE, * TIME, * TIMESTAMP The most critical part here is that convertation result should be exactly the same as H2 convertation result (see org.apache.ignite.internal.processors.query.h2.H2Utils#convert), in other case partitions might be resolved incorrectly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11197) SQL:Ability to resolve arguments for temporal data types.
[ https://issues.apache.org/jira/browse/IGNITE-11197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Lapin updated IGNITE-11197: - Issue Type: Task (was: Bug) > SQL:Ability to resolve arguments for temporal data types. > - > > Key: IGNITE-11197 > URL: https://issues.apache.org/jira/browse/IGNITE-11197 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Alexander Lapin >Priority: Minor > > Within > org.apache.ignite.internal.sql.optimizer.affinity.PartitionUtils#convert it's > now possible to convert following data types: > * BOOLEAN, > * BYTE, > * SHORT, > * INT, > * LONG, > * FLOAT, > * DOUBLE, > * STRING, > * DECIMAL, > * UUID; > Following temporal data types should also be supported: > * DATE, > * TIME, > * TIMESTAMP > The most critical part here is that convertation result should be exactly the > same as within H2 convertation result (see > org.apache.ignite.internal.processors.query.h2.H2Utils#convert), in other > case partitions might be resolved incorrectly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11196) A number of suited failed because of maven-enforcer-plugin failure for Java 11 build
[
https://issues.apache.org/jira/browse/IGNITE-11196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16759914#comment-16759914
]
Dmitriy Pavlov commented on IGNITE-11196:
-
TC with fix was started:
https://ci.ignite.apache.org/viewQueued.html?itemId=2996903=queuedBuildOverviewTab_IgniteTests24Java8=ignite-11155
> A number of suited failed because of maven-enforcer-plugin failure for Java
> 11 build
>
>
> Key: IGNITE-11196
> URL: https://issues.apache.org/jira/browse/IGNITE-11196
> Project: Ignite
> Issue Type: Bug
>Reporter: Dmitriy Pavlov
>Assignee: Peter Ivanov
>Priority: Major
>
> A number of exit codes occurred in Java 11 tests build:
> - SPI (URI Deploy) [ tests 0 Exit Code ] 1 queued
> - RDD* [ tests 0 Exit Code ]
> - OSGi [ tests 0 Exit Code ]
> - Logging [ tests 0 Exit Code ]
> - AOP [ tests 0 Exit Code ]
> - JCache TCK 1.1 [ tests 0 Exit Code ]
> - _Licenses Headers_ [ tests 0 Exit Code ]
> - Cassandra Store [ tests 0 Exit Code ]
> For example, SPI (URI Deploy) failed with maven enforcer plugin:
>
> https://ci.ignite.apache.org/viewLog.html?tab=buildLog=tree=debug=all=2995900&_focus=1525
> {noformat}
> org.apache.maven.plugins:maven-enforcer-plugin:1.4:enforce (default) on
> project ignite-tools: Execution default of goal
> org.apache.maven.plugins:maven-enforcer-plugin:1.4:enforce failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-enforcer-plugin:1.4:enforce:
> java.lang.ExceptionInInitializerError: null
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11197) SQL:Ability to resolve arguments for temporal data types.
[ https://issues.apache.org/jira/browse/IGNITE-11197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Lapin updated IGNITE-11197: - Summary: SQL:Ability to resolve arguments for temporal data types. (was: SQL:Ability to resolve partiton for temporal data types.) > SQL:Ability to resolve arguments for temporal data types. > - > > Key: IGNITE-11197 > URL: https://issues.apache.org/jira/browse/IGNITE-11197 > Project: Ignite > Issue Type: Bug > Components: sql >Reporter: Alexander Lapin >Priority: Minor > > Within > org.apache.ignite.internal.sql.optimizer.affinity.PartitionUtils#convert it's > now possible to convert following data types: > * BOOLEAN, > * BYTE, > * SHORT, > * INT, > * LONG, > * FLOAT, > * DOUBLE, > * STRING, > * DECIMAL, > * UUID; > Following temporal data types should also be supported: > * DATE, > * TIME, > * TIMESTAMP > The most critical part here is that convertation result should be exactly the > same as within H2 convertation result (see > org.apache.ignite.internal.processors.query.h2.H2Utils#convert), in other > case partitions might be resolved incorrectly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11197) SQL:Ability to resolve partiton for temporal data types.
[ https://issues.apache.org/jira/browse/IGNITE-11197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Lapin updated IGNITE-11197: - Description: Within org.apache.ignite.internal.sql.optimizer.affinity.PartitionUtils#convert it's now possible to convert following data types: * BOOLEAN, * BYTE, * SHORT, * INT, * LONG, * FLOAT, * DOUBLE, * STRING, * DECIMAL, * UUID; Following temporal data types should also be supported: * DATE, * TIME, * TIMESTAMP The most critical part here is that convertation result should be exactly the same as within H2 convertation result (see org.apache.ignite.internal.processors.query.h2.H2Utils#convert), in other case partitions might be resolved incorrectly. was: Within org.apache.ignite.internal.sql.optimizer.affinity.PartitionUtils#convert it's now possible to convert following data types: * BOOLEAN, * BYTE, * SHORT, * INT, * LONG, * FLOAT, * DOUBLE, * STRING, * DECIMAL, * UUID; Following temporal data types should also be supported: * DATE, * TIME, * TIMESTAMP The most critical part here is that convertation result should be exactly the same as H2 convertation result (see org.apache.ignite.internal.processors.query.h2.H2Utils#convert), in other case partitions might be resolved incorrectly. > SQL:Ability to resolve partiton for temporal data types. > > > Key: IGNITE-11197 > URL: https://issues.apache.org/jira/browse/IGNITE-11197 > Project: Ignite > Issue Type: Bug > Components: sql >Reporter: Alexander Lapin >Priority: Minor > > Within > org.apache.ignite.internal.sql.optimizer.affinity.PartitionUtils#convert it's > now possible to convert following data types: > * BOOLEAN, > * BYTE, > * SHORT, > * INT, > * LONG, > * FLOAT, > * DOUBLE, > * STRING, > * DECIMAL, > * UUID; > Following temporal data types should also be supported: > * DATE, > * TIME, > * TIMESTAMP > The most critical part here is that convertation result should be exactly the > same as within H2 convertation result (see > org.apache.ignite.internal.processors.query.h2.H2Utils#convert), in other > case partitions might be resolved incorrectly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11196) A number of suited failed because of maven-enforcer-plugin failure for Java 11 build
Dmitriy Pavlov created IGNITE-11196:
---
Summary: A number of suited failed because of
maven-enforcer-plugin failure for Java 11 build
Key: IGNITE-11196
URL: https://issues.apache.org/jira/browse/IGNITE-11196
Project: Ignite
Issue Type: Bug
Reporter: Dmitriy Pavlov
Assignee: Peter Ivanov
A number of exit codes occurred in Java 11 tests build:
- SPI (URI Deploy) [ tests 0 Exit Code ] 1 queued
- RDD* [ tests 0 Exit Code ]
- OSGi [ tests 0 Exit Code ]
- Logging [ tests 0 Exit Code ]
- AOP [ tests 0 Exit Code ]
- JCache TCK 1.1 [ tests 0 Exit Code ]
- _Licenses Headers_ [ tests 0 Exit Code ]
- Cassandra Store [ tests 0 Exit Code ]
For example, SPI (URI Deploy) failed with maven enforcer plugin:
https://ci.ignite.apache.org/viewLog.html?tab=buildLog=tree=debug=all=2995900&_focus=1525
{noformat}
org.apache.maven.plugins:maven-enforcer-plugin:1.4:enforce (default) on project
ignite-tools: Execution default of goal
org.apache.maven.plugins:maven-enforcer-plugin:1.4:enforce failed: An API
incompatibility was encountered while executing
org.apache.maven.plugins:maven-enforcer-plugin:1.4:enforce:
java.lang.ExceptionInInitializerError: null
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11159) Collections of 'start-on-join' caches and 'init-caches' should be filtered
[
https://issues.apache.org/jira/browse/IGNITE-11159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16759895#comment-16759895
]
Ignite TC Bot commented on IGNITE-11159:
{panel:title=-- Run :: All: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2960479buildTypeId=IgniteTests24Java8_RunAll]
> Collections of 'start-on-join' caches and 'init-caches' should be filtered
> --
>
> Key: IGNITE-11159
> URL: https://issues.apache.org/jira/browse/IGNITE-11159
> Project: Ignite
> Issue Type: Bug
>Reporter: Sergey Chugunov
>Assignee: Sergey Chugunov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> IGNITE-10878 added filtering of cache descriptors when new node receives some
> additional descriptors from cluster that dies before finishing new node join.
> It turned out there are additional collections in LocalJoinCachesContext that
> need to be filtered.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11195) Platform C++ tests failed to find JVM for Java 11 build
Dmitriy Pavlov created IGNITE-11195:
---
Summary: Platform C++ tests failed to find JVM for Java 11 build
Key: IGNITE-11195
URL: https://issues.apache.org/jira/browse/IGNITE-11195
Project: Ignite
Issue Type: Bug
Reporter: Dmitriy Pavlov
482 C++ tests failed with error
{noformat}
std::exception: JVM library is not found (did you set JAVA_HOME environment
variable?)
{noformat}
https://ci.ignite.apache.org/viewLog.html?buildId=2973675=IgniteTests24Java8_PlatformCWinX64Release=buildResultsDiv_IgniteTests24Java8=ignite-11155
Looks like we need somehow handle new parameters in C++ tests
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11195) Platform C++ tests failed to find JVM for Java 11 build
[
https://issues.apache.org/jira/browse/IGNITE-11195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-11195:
Ignite Flags: (was: Docs Required)
> Platform C++ tests failed to find JVM for Java 11 build
> ---
>
> Key: IGNITE-11195
> URL: https://issues.apache.org/jira/browse/IGNITE-11195
> Project: Ignite
> Issue Type: Bug
>Reporter: Dmitriy Pavlov
>Priority: Major
>
> 482 C++ tests failed with error
> {noformat}
> std::exception: JVM library is not found (did you set JAVA_HOME environment
> variable?)
> {noformat}
> https://ci.ignite.apache.org/viewLog.html?buildId=2973675=IgniteTests24Java8_PlatformCWinX64Release=buildResultsDiv_IgniteTests24Java8=ignite-11155
> Looks like we need somehow handle new parameters in C++ tests
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10582) MVCC: Error on txLog initialization.
[
https://issues.apache.org/jira/browse/IGNITE-10582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16759880#comment-16759880
]
Ignite TC Bot commented on IGNITE-10582:
{panel:title=-- Run :: All: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2994161buildTypeId=IgniteTests24Java8_RunAll]
> MVCC: Error on txLog initialization.
>
>
> Key: IGNITE-10582
> URL: https://issues.apache.org/jira/browse/IGNITE-10582
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Assignee: Andrew Mashenkov
>Priority: Major
> Labels: Muted_test, mvcc_stabilization_stage_1, pagememory
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> A sporadic error occurs during {{txLog}} initialization. Reproducer:
> {{IgnitePdsCacheAssignmentNodeRestartsTest#testAssignmentAfterRestarts}}.
> This error may be the result of the test settings. We need to check it more
> carefully.
> Stacktrace:
> {noformat}
> javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException:
> Failed to complete exchange process.
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1337)
> at
> org.apache.ignite.internal.IgniteKernal.getOrCreateCaches(IgniteKernal.java:3068)
> at
> org.apache.ignite.internal.processors.cache.persistence.IgnitePdsCacheAssignmentNodeRestartsTest.testAssignmentAfterRestarts(IgnitePdsCacheAssignmentNodeRestartsTest.java:148)
> 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.access$001(GridAbstractTest.java:149)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$6.evaluate(GridAbstractTest.java:2106)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2123)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to complete
> exchange process.
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.createExchangeException(GridDhtPartitionsExchangeFuture.java:3041)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.sendExchangeFailureMessage(GridDhtPartitionsExchangeFuture.java:3069)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.finishExchangeOnCoordinator(GridDhtPartitionsExchangeFuture.java:3151)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onAllReceived(GridDhtPartitionsExchangeFuture.java:3135)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.processSingleMessage(GridDhtPartitionsExchangeFuture.java:2748)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.access$100(GridDhtPartitionsExchangeFuture.java:138)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2.apply(GridDhtPartitionsExchangeFuture.java:2556)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2.apply(GridDhtPartitionsExchangeFuture.java:2544)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:395)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:355)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onReceiveSingleMessage(GridDhtPartitionsExchangeFuture.java:2544)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.processSinglePartitionUpdate(GridCachePartitionExchangeManager.java:1807)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.access$1200(GridCachePartitionExchangeManager.java:145)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$2.onMessage(GridCachePartitionExchangeManager.java:382)
> at
>
[jira] [Commented] (IGNITE-8841) MVCC TX: Read transactions remap when coordinator fails.
[ https://issues.apache.org/jira/browse/IGNITE-8841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16759873#comment-16759873 ] Ivan Pavlukhin commented on IGNITE-8841: [~gvvinblade] then everything looks ok to me. > MVCC TX: Read transactions remap when coordinator fails. > > > Key: IGNITE-8841 > URL: https://issues.apache.org/jira/browse/IGNITE-8841 > Project: Ignite > Issue Type: Bug > Components: mvcc, sql >Reporter: Roman Kondakov >Assignee: Igor Seliverstov >Priority: Major > Labels: failover > Time Spent: 50m > Remaining Estimate: 0h > > At the moment read transactions that don't acquire topology lock will be > forcibly rolled back on topology change as read tx can be in fly while > topology being change. > This is done to prevent having active transaction with stale snapshots on > new topology in cases of TX coordinator or Near node were lost. > > It would be nice to remap it somehow until they locked a topology or at least > throw some meaningful exception to user. > For example, it is possible to obtain a new "write" mvcc version from the > new coordinator and use this version for all further writes while using "old" > version for reads. In this case we need to change visibility rules a little: > "old" version should see "own" updates made by "new" "write" version. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8841) MVCC TX: Read transactions remap when coordinator fails.
[ https://issues.apache.org/jira/browse/IGNITE-8841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16759866#comment-16759866 ] Igor Seliverstov commented on IGNITE-8841: -- [~Pavlukhin] 1) Probably it makes sense, I left it like this not to change callers. Anyway we need to do some cleanup of involved classes, I've planned it as a separate task. 2) This is a special case, there can be active queries which survived several exchanges and there was no coordinator (no applicable for a coordinator node filter nodes) before new node have joined. We need to track such queries too. > MVCC TX: Read transactions remap when coordinator fails. > > > Key: IGNITE-8841 > URL: https://issues.apache.org/jira/browse/IGNITE-8841 > Project: Ignite > Issue Type: Bug > Components: mvcc, sql >Reporter: Roman Kondakov >Assignee: Igor Seliverstov >Priority: Major > Labels: failover > Time Spent: 50m > Remaining Estimate: 0h > > At the moment read transactions that don't acquire topology lock will be > forcibly rolled back on topology change as read tx can be in fly while > topology being change. > This is done to prevent having active transaction with stale snapshots on > new topology in cases of TX coordinator or Near node were lost. > > It would be nice to remap it somehow until they locked a topology or at least > throw some meaningful exception to user. > For example, it is possible to obtain a new "write" mvcc version from the > new coordinator and use this version for all further writes while using "old" > version for reads. In this case we need to change visibility rules a little: > "old" version should see "own" updates made by "new" "write" version. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-8841) MVCC TX: Read transactions remap when coordinator fails.
[
https://issues.apache.org/jira/browse/IGNITE-8841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16759857#comment-16759857
]
Ivan Pavlukhin edited comment on IGNITE-8841 at 2/4/19 1:48 PM:
[~gvvinblade] please find my comments below.
# Can we get rid of {{MvccUtils.requestSnapshot}} as it mostly delegates to
{{GridNearTxLocal}}?
# I did not get why do we need to call {{PreviousQueries.init}} from
{{onLocalJoin}} callback? It worth adding a comment explaining the idea.
was (Author: pavlukhin):
[~gvvinblade] please find my comments below.
# Can we get rid of {{MvccUtils.requestSnapshot as it mostly delegates to
{{GridNearTxLocal}}?
# I did not get why do we need to call {{PreviousQueries.init}} from
{{onLocalJoin}} callback? It worth adding a comment explaining the idea.
> MVCC TX: Read transactions remap when coordinator fails.
>
>
> Key: IGNITE-8841
> URL: https://issues.apache.org/jira/browse/IGNITE-8841
> Project: Ignite
> Issue Type: Bug
> Components: mvcc, sql
>Reporter: Roman Kondakov
>Assignee: Igor Seliverstov
>Priority: Major
> Labels: failover
> Time Spent: 50m
> Remaining Estimate: 0h
>
> At the moment read transactions that don't acquire topology lock will be
> forcibly rolled back on topology change as read tx can be in fly while
> topology being change.
> This is done to prevent having active transaction with stale snapshots on
> new topology in cases of TX coordinator or Near node were lost.
>
> It would be nice to remap it somehow until they locked a topology or at least
> throw some meaningful exception to user.
> For example, it is possible to obtain a new "write" mvcc version from the
> new coordinator and use this version for all further writes while using "old"
> version for reads. In this case we need to change visibility rules a little:
> "old" version should see "own" updates made by "new" "write" version.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11194) [ML] Stacking example
Artem Malykh created IGNITE-11194: - Summary: [ML] Stacking example Key: IGNITE-11194 URL: https://issues.apache.org/jira/browse/IGNITE-11194 Project: Ignite Issue Type: Improvement Components: ml Affects Versions: 2.8 Reporter: Artem Malykh Assignee: Artem Malykh -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-8841) MVCC TX: Read transactions remap when coordinator fails.
[
https://issues.apache.org/jira/browse/IGNITE-8841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16759857#comment-16759857
]
Ivan Pavlukhin edited comment on IGNITE-8841 at 2/4/19 1:48 PM:
[~gvvinblade] please find my comments below.
# Can we get rid of {{MvccUtils.requestSnapshot as it mostly delegates to
{{GridNearTxLocal}}?
# I did not get why do we need to call {{PreviousQueries.init}} from
{{onLocalJoin}} callback? It worth adding a comment explaining the idea.
was (Author: pavlukhin):
[~gvvinblade] please find my comments below.
# Can we get rid of {{MvccUtils.requestSnapshot as it mostly delegates to
}}{{GridNearTxLocal}}?
# I did not get why do we need to call {{PreviousQueries.init}} from
{{onLocalJoin}} callback? It worth adding a comment explaining the idea.
> MVCC TX: Read transactions remap when coordinator fails.
>
>
> Key: IGNITE-8841
> URL: https://issues.apache.org/jira/browse/IGNITE-8841
> Project: Ignite
> Issue Type: Bug
> Components: mvcc, sql
>Reporter: Roman Kondakov
>Assignee: Igor Seliverstov
>Priority: Major
> Labels: failover
> Time Spent: 50m
> Remaining Estimate: 0h
>
> At the moment read transactions that don't acquire topology lock will be
> forcibly rolled back on topology change as read tx can be in fly while
> topology being change.
> This is done to prevent having active transaction with stale snapshots on
> new topology in cases of TX coordinator or Near node were lost.
>
> It would be nice to remap it somehow until they locked a topology or at least
> throw some meaningful exception to user.
> For example, it is possible to obtain a new "write" mvcc version from the
> new coordinator and use this version for all further writes while using "old"
> version for reads. In this case we need to change visibility rules a little:
> "old" version should see "own" updates made by "new" "write" version.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IGNITE-10468) MVCC TX: Failover
[ https://issues.apache.org/jira/browse/IGNITE-10468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Seliverstov resolved IGNITE-10468. --- Resolution: Done Is no longer needed. > MVCC TX: Failover > - > > Key: IGNITE-10468 > URL: https://issues.apache.org/jira/browse/IGNITE-10468 > Project: Ignite > Issue Type: Task >Reporter: Igor Seliverstov >Assignee: Igor Seliverstov >Priority: Major > > There is several problems in mvcc failover scenarios. > The task is an umbrella ticket for currently known issues. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8841) MVCC TX: Read transactions remap when coordinator fails.
[
https://issues.apache.org/jira/browse/IGNITE-8841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16759857#comment-16759857
]
Ivan Pavlukhin commented on IGNITE-8841:
[~gvvinblade] please find my comments below.
# Can we get rid of {{MvccUtils.requestSnapshot as it mostly delegates to
}}{{GridNearTxLocal}}?
# I did not get why do we need to call {{PreviousQueries.init}} from
{{onLocalJoin}} callback? It worth adding a comment explaining the idea.
> MVCC TX: Read transactions remap when coordinator fails.
>
>
> Key: IGNITE-8841
> URL: https://issues.apache.org/jira/browse/IGNITE-8841
> Project: Ignite
> Issue Type: Bug
> Components: mvcc, sql
>Reporter: Roman Kondakov
>Assignee: Igor Seliverstov
>Priority: Major
> Labels: failover
> Time Spent: 50m
> Remaining Estimate: 0h
>
> At the moment read transactions that don't acquire topology lock will be
> forcibly rolled back on topology change as read tx can be in fly while
> topology being change.
> This is done to prevent having active transaction with stale snapshots on
> new topology in cases of TX coordinator or Near node were lost.
>
> It would be nice to remap it somehow until they locked a topology or at least
> throw some meaningful exception to user.
> For example, it is possible to obtain a new "write" mvcc version from the
> new coordinator and use this version for all further writes while using "old"
> version for reads. In this case we need to change visibility rules a little:
> "old" version should see "own" updates made by "new" "write" version.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11193) MVCC TX: the query with specified explicit patririons fails
Taras Ledkov created IGNITE-11193:
-
Summary: MVCC TX: the query with specified explicit patririons
fails
Key: IGNITE-11193
URL: https://issues.apache.org/jira/browse/IGNITE-11193
Project: Ignite
Issue Type: Bug
Components: mvcc, sql
Affects Versions: 2.7
Reporter: Taras Ledkov
Assignee: Taras Ledkov
Fix For: 2.8
If the explicit partitions specified by {{SqlFieldsQuery#setPartitions}} are
placed on the several nodes the query fails at the partition reservation
({{GridDhtTxQueryEnlistFuture.checkPartitions}}) with error: "{{Cannot run
update query. Node must own all the necessary partitions.}}"
*Root cause*: MVCC DML doesn't map the requests
{{GridNearTxQueryEnlistRequest}}. Each node received the messages with all
explicit partitions.
*Proposal fix*: use the partitions/node mapping similar to SELECT queries. See
more:
- {{GridH2QueryRequest#partitions}}
- {{ReducePartitionsSpecializer#ReducePartitionsSpecializer}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11185) SQL: Move distributed joins code from base index to H2TreeIndex
[
https://issues.apache.org/jira/browse/IGNITE-11185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-11185:
-
Component/s: sql
> SQL: Move distributed joins code from base index to H2TreeIndex
> ---
>
> Key: IGNITE-11185
> URL: https://issues.apache.org/jira/browse/IGNITE-11185
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {{H2TreeIndex}} is the only implementation concerned with distributed joins.
> Let's move associated from {{GridH2IndexBase}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11185) SQL: Move distributed joins code from base index to H2TreeIndex
[
https://issues.apache.org/jira/browse/IGNITE-11185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-11185:
-
Ignite Flags: (was: Docs Required)
> SQL: Move distributed joins code from base index to H2TreeIndex
> ---
>
> Key: IGNITE-11185
> URL: https://issues.apache.org/jira/browse/IGNITE-11185
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {{H2TreeIndex}} is the only implementation concerned with distributed joins.
> Let's move associated from {{GridH2IndexBase}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11185) SQL: Move distributed joins code from base index to H2TreeIndex
[
https://issues.apache.org/jira/browse/IGNITE-11185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16759844#comment-16759844
]
Vladimir Ozerov commented on IGNITE-11185:
--
Headers - fixed.
Spring, Cache 7 - unrelated.
> SQL: Move distributed joins code from base index to H2TreeIndex
> ---
>
> Key: IGNITE-11185
> URL: https://issues.apache.org/jira/browse/IGNITE-11185
> Project: Ignite
> Issue Type: Task
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {{H2TreeIndex}} is the only implementation concerned with distributed joins.
> Let's move associated from {{GridH2IndexBase}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11185) SQL: Move distributed joins code from base index to H2TreeIndex
[
https://issues.apache.org/jira/browse/IGNITE-11185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16759841#comment-16759841
]
Ignite TC Bot commented on IGNITE-11185:
{panel:title=-- Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Spring{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2993561]]
{color:#d04437}_Licenses Headers_{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2993586]]
{color:#d04437}Cache 7{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2993604]]
* IgniteCacheTestSuite7:
TxRollbackAsyncWithPersistenceTest.testSynchronousRollback - 0,0% fails in last
414 master runs.
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2993650buildTypeId=IgniteTests24Java8_RunAll]
> SQL: Move distributed joins code from base index to H2TreeIndex
> ---
>
> Key: IGNITE-11185
> URL: https://issues.apache.org/jira/browse/IGNITE-11185
> Project: Ignite
> Issue Type: Task
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {{H2TreeIndex}} is the only implementation concerned with distributed joins.
> Let's move associated from {{GridH2IndexBase}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11192) [ML] Use nd4j for matrix inversions and determinants
Alexey Platonov created IGNITE-11192: Summary: [ML] Use nd4j for matrix inversions and determinants Key: IGNITE-11192 URL: https://issues.apache.org/jira/browse/IGNITE-11192 Project: Ignite Issue Type: Improvement Components: ml Reporter: Alexey Platonov Assignee: Alexey Platonov >From optimization point of view we should use matrix inversions and >determinant computations of dl4j instead of own realization. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11191) Fix Hibernate integration by providing JAXB dependency during compile
Dmitriy Pavlov created IGNITE-11191:
---
Summary: Fix Hibernate integration by providing JAXB dependency
during compile
Key: IGNITE-11191
URL: https://issues.apache.org/jira/browse/IGNITE-11191
Project: Ignite
Issue Type: Bug
Reporter: Dmitriy Pavlov
Assignee: Dmitriy Pavlov
https://ci.ignite.apache.org/viewLog.html?buildId=2973733=buildResultsDiv=IgniteTests24Java8_Hibernate53#testNameId-1306520535171712877
{noformat}
java.lang.NoClassDefFoundError: javax/xml/bind/JAXBException
at
org.apache.ignite.cache.hibernate.HibernateL2CacheSelfTest.startHibernate(HibernateL2CacheSelfTest.java:1923)
at
org.apache.ignite.cache.hibernate.HibernateL2CacheSelfTest.createSessionFactories(HibernateL2CacheSelfTest.java:1900)
at
org.apache.ignite.cache.hibernate.HibernateL2CacheSelfTest.testVersionedEntity(HibernateL2CacheSelfTest.java:1026)
at
org.apache.ignite.cache.hibernate.HibernateL2CacheSelfTest.testVersionedEntity(HibernateL2CacheSelfTest.java:1018)
Caused by: java.lang.ClassNotFoundException: javax.xml.bind.JAXBException
at
org.apache.ignite.cache.hibernate.HibernateL2CacheSelfTest.startHibernate(HibernateL2CacheSelfTest.java:1923)
at
org.apache.ignite.cache.hibernate.HibernateL2CacheSelfTest.createSessionFactories(HibernateL2CacheSelfTest.java:1900)
at
org.apache.ignite.cache.hibernate.HibernateL2CacheSelfTest.testVersionedEntity(HibernateL2CacheSelfTest.java:1026)
at org.apache.ignite.cache
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11190) Fix Apache Ignite tests of Camel Streamer under Java 11
Dmitriy Pavlov created IGNITE-11190: --- Summary: Fix Apache Ignite tests of Camel Streamer under Java 11 Key: IGNITE-11190 URL: https://issues.apache.org/jira/browse/IGNITE-11190 Project: Ignite Issue Type: Bug Reporter: Dmitriy Pavlov Under Java 11 tests failed with an Error 500 - internal server error https://ci.ignite.apache.org/viewLog.html?buildId=2973663=buildResultsDiv=IgniteTests24Java8_Streamers Probably we need to pass startup parameters to 3rd party product/JVM. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10748) Remove dead code in TcpCommunicationSpi for the tcp client creation flow
[
https://issues.apache.org/jira/browse/IGNITE-10748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16759835#comment-16759835
]
Sergey Chugunov commented on IGNITE-10748:
--
[~Mmuzaf],
Proposed change looks good to me in general, I left some comments in the PR
suggesting minor changes and fixes.
> Remove dead code in TcpCommunicationSpi for the tcp client creation flow
>
>
> Key: IGNITE-10748
> URL: https://issues.apache.org/jira/browse/IGNITE-10748
> Project: Ignite
> Issue Type: Task
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Minor
> Fix For: 2.8
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Currently, a batch of changes can be applied over {{TcpCommunicationSpi}}
> class implementation due to:
> # {{safeTcpHandshake(..)}}
> #* {{handshakeConnIdx}} - parameter is always not null
> #* {{recovery}} - parameter is always not null
> #* {{HandhakeMessage}} - is not used in current flow at all
> # {{HandshakeMessage2}}
> #* Message size must be defined in the message class as constant
> # {{createTcpClient(..)}}
> #* Instantiation of {{GridTcpNioCommunicationClient}} must be performed
> outside the while-loop
> # Code-style issues. Fix one-liner if statements.
> # Extract internal {{HandshakeException}}, {{HandshakeTimeoutException}} from
> class.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11153) Support Java 11 for control.sh & ignitevisorcmd.sh: remove odd --add-modules for java.xml.bind
[
https://issues.apache.org/jira/browse/IGNITE-11153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16759836#comment-16759836
]
Dmitriy Pavlov commented on IGNITE-11153:
-
[~vveider], [~agoncharuk], I still need assistance here. I'm not an expert in
sh scripts.
Of course, I can prepare a PR. - It will be more likely to have bugs in it than
PR prepared by an expert.
> Support Java 11 for control.sh & ignitevisorcmd.sh: remove odd --add-modules
> for java.xml.bind
> --
>
> Key: IGNITE-11153
> URL: https://issues.apache.org/jira/browse/IGNITE-11153
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Priority: Major
>
> JAXB module was removed from Java 11.
> Please adopt ignite control.sh in the same way as it is done for ignite.sh/bat
> {noformat}
> elif [ $version -gt 8 ] && [ $version -lt 11 ]; then
> JVM_OPTS="\
> -XX:+AggressiveOpts \
> --add-exports=java.base/jdk.internal.misc=ALL-UNNAMED \
> --add-exports=java.base/sun.nio.ch=ALL-UNNAMED \
> --add-exports=java.management/com.sun.jmx.mbeanserver=ALL-UNNAMED \
> --add-exports=jdk.internal.jvmstat/sun.jvmstat.monitor=ALL-UNNAMED \
>
> --add-exports=java.base/sun.reflect.generics.reflectiveObjects=ALL-UNNAMED \
> --illegal-access=permit \
> --add-modules=java.transaction \
> --add-modules=java.xml.bind \
> ${JVM_OPTS}"
> elif [ $version -eq 11 ] ; then
> JVM_OPTS="\
> --add-exports=java.base/jdk.internal.misc=ALL-UNNAMED \
> --add-exports=java.base/sun.nio.ch=ALL-UNNAMED \
> --add-exports=java.management/com.sun.jmx.mbeanserver=ALL-UNNAMED \
> --add-exports=jdk.internal.jvmstat/sun.jvmstat.monitor=ALL-UNNAMED \
>
> --add-exports=java.base/sun.reflect.generics.reflectiveObjects=ALL-UNNAMED \
> --illegal-access=permit \
> ${JVM_OPTS}"
> {noformat}
> But control.sh for master still declares --add-modules java.xml.bind \
> {noformat}
> JVM_OPTS="--add-exports java.base/jdk.internal.misc=ALL-UNNAMED \
> --add-exports java.base/sun.nio.ch=ALL-UNNAMED \
> --add-exports java.management/com.sun.jmx.mbeanserver=ALL-UNNAMED \
> --add-exports jdk.internal.jvmstat/sun.jvmstat.monitor=ALL-UNNAMED \
> --add-modules java.xml.bind \
> ${JVM_OPTS}"
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11189) Support Java 11 for Apache Ignite
Dmitriy Pavlov created IGNITE-11189: --- Summary: Support Java 11 for Apache Ignite Key: IGNITE-11189 URL: https://issues.apache.org/jira/browse/IGNITE-11189 Project: Ignite Issue Type: Improvement Reporter: Dmitriy Pavlov This is an umbrella ticket to link all Java 11 related efforts in one ticket. 'Blocked by' link type is used in case change is mandatory to be done. Other link types, e.g. 'related to' used for nice-to-have fixes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10508) Need to support the new checkpoint feature, checkpint should not wait for the previous operation to complete
[ https://issues.apache.org/jira/browse/IGNITE-10508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16759816#comment-16759816 ] Vyacheslav Koptilin commented on IGNITE-10508: -- Hello [~DmitriyGovorukhin] , In general, this change looks good and reasonable to me. I have added a few comments to the PR, please take a look. > Need to support the new checkpoint feature, checkpint should not wait for the > previous operation to complete > > > Key: IGNITE-10508 > URL: https://issues.apache.org/jira/browse/IGNITE-10508 > Project: Ignite > Issue Type: New Feature >Reporter: Dmitriy Govorukhin >Assignee: Dmitriy Govorukhin >Priority: Critical > Fix For: 2.8 > > Time Spent: 2.5h > Remaining Estimate: 0h > > There are cases we should trigger the checkpoint, some operations will be > sure that all operation finished before the checkpoint. It is necessary to > support the possibility of run checkpoint without waiting for the completion > of the previous checkpoint. > Solution: > Merge checkpoint pages and append write new dirty pages to a current > checkpoint. > Restrictions: > Trigger new checkpoint should not wait for the previous checkpoint operation > completed. > - It should not break crash recovery mechanisms > - Only one merged is allow in the first implementation (potentially OOM, if > we will try to merge many checkpoint operations) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10347) Expose system SQL view for running queries
[ https://issues.apache.org/jira/browse/IGNITE-10347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16759804#comment-16759804 ] Yury Gerzhedovich commented on IGNITE-10347: [~vozerov], thanks for the comments. All of that have been implemented. Getting Bot vise in progress. > Expose system SQL view for running queries > -- > > Key: IGNITE-10347 > URL: https://issues.apache.org/jira/browse/IGNITE-10347 > Project: Ignite > Issue Type: Task >Reporter: Yury Gerzhedovich >Assignee: Yury Gerzhedovich >Priority: Major > Labels: iep-29, sql > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > Need to expose system SQL view to provide list of running queries. Proposed > name is *running_queries* with following columns: query_id, node_id, sql, > schema_name, duration. > Where, > query_id - cluster unique id of query > sql - sql command > cancelable - is is possible to cancel the query. > schema_name - SQL schema name > duration - time in ms from start of execution of query > > The view should contains all kind of running queries from RunningQueryManager > on local node -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11153) Support Java 11 for control.sh & ignitevisorcmd.sh: remove odd --add-modules for java.xml.bind
[
https://issues.apache.org/jira/browse/IGNITE-11153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-11153:
Summary: Support Java 11 for control.sh & ignitevisorcmd.sh: remove odd
--add-modules for java.xml.bind (was: Support Java 11 for control.sh)
> Support Java 11 for control.sh & ignitevisorcmd.sh: remove odd --add-modules
> for java.xml.bind
> --
>
> Key: IGNITE-11153
> URL: https://issues.apache.org/jira/browse/IGNITE-11153
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Priority: Major
>
> JAXB module was removed from Java 11.
> Please adopt ignite control.sh in the same way as it is done for ignite.sh/bat
> {noformat}
> elif [ $version -gt 8 ] && [ $version -lt 11 ]; then
> JVM_OPTS="\
> -XX:+AggressiveOpts \
> --add-exports=java.base/jdk.internal.misc=ALL-UNNAMED \
> --add-exports=java.base/sun.nio.ch=ALL-UNNAMED \
> --add-exports=java.management/com.sun.jmx.mbeanserver=ALL-UNNAMED \
> --add-exports=jdk.internal.jvmstat/sun.jvmstat.monitor=ALL-UNNAMED \
>
> --add-exports=java.base/sun.reflect.generics.reflectiveObjects=ALL-UNNAMED \
> --illegal-access=permit \
> --add-modules=java.transaction \
> --add-modules=java.xml.bind \
> ${JVM_OPTS}"
> elif [ $version -eq 11 ] ; then
> JVM_OPTS="\
> --add-exports=java.base/jdk.internal.misc=ALL-UNNAMED \
> --add-exports=java.base/sun.nio.ch=ALL-UNNAMED \
> --add-exports=java.management/com.sun.jmx.mbeanserver=ALL-UNNAMED \
> --add-exports=jdk.internal.jvmstat/sun.jvmstat.monitor=ALL-UNNAMED \
>
> --add-exports=java.base/sun.reflect.generics.reflectiveObjects=ALL-UNNAMED \
> --illegal-access=permit \
> ${JVM_OPTS}"
> {noformat}
> But control.sh for master still declares --add-modules java.xml.bind \
> {noformat}
> JVM_OPTS="--add-exports java.base/jdk.internal.misc=ALL-UNNAMED \
> --add-exports java.base/sun.nio.ch=ALL-UNNAMED \
> --add-exports java.management/com.sun.jmx.mbeanserver=ALL-UNNAMED \
> --add-exports jdk.internal.jvmstat/sun.jvmstat.monitor=ALL-UNNAMED \
> --add-modules java.xml.bind \
> ${JVM_OPTS}"
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IGNITE-11140) Check and fix Ignite examples for Java 11
[ https://issues.apache.org/jira/browse/IGNITE-11140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov resolved IGNITE-11140. - Resolution: Fixed Fixed in master, all changes were related not to Java 11, but to compilation itself. See short description how to run examples using Java 9+ here: https://github.com/apache/ignite/tree/master/examples#running-examples-on-jdk-91011 > Check and fix Ignite examples for Java 11 > - > > Key: IGNITE-11140 > URL: https://issues.apache.org/jira/browse/IGNITE-11140 > Project: Ignite > Issue Type: Task >Reporter: Dmitriy Pavlov >Assignee: Dmitriy Pavlov >Priority: Major > Fix For: 2.8 > > Time Spent: 20m > Remaining Estimate: 0h > > Apache Ignite has a nightly release builds > https://ci.ignite.apache.org/viewType.html?buildTypeId=Releases_NightlyRelease_RunApacheIgniteNightlyRelease_Releases_NightlyRelease=%3Cdefault%3E=buildTypeStatusDiv > These builds contain examples, as well as releases. > It is required to check these release builds for examples compatibility with > Java 11 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11188) Optimize baseline autoadjustment for in-memory clusters with zero timeout
[ https://issues.apache.org/jira/browse/IGNITE-11188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Bessonov updated IGNITE-11188: --- Labels: IEP-4 Phase-2 (was: ) > Optimize baseline autoadjustment for in-memory clusters with zero timeout > - > > Key: IGNITE-11188 > URL: https://issues.apache.org/jira/browse/IGNITE-11188 > Project: Ignite > Issue Type: Improvement >Reporter: Ivan Bessonov >Assignee: Ivan Bessonov >Priority: Major > Labels: IEP-4, Phase-2 > Fix For: 2.8 > > > In current implementation (IGNITE-8571) zero-timeout case initiates two > partition map exchanges on join/leave node events. This could be improved so > that baseline is updated at the same time as join/leave event processing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-10104) MVCC TX: client SFU doesn't work on replicated caches
[
https://issues.apache.org/jira/browse/IGNITE-10104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Seliverstov reassigned IGNITE-10104:
-
Assignee: (was: Igor Seliverstov)
> MVCC TX: client SFU doesn't work on replicated caches
> -
>
> Key: IGNITE-10104
> URL: https://issues.apache.org/jira/browse/IGNITE-10104
> Project: Ignite
> Issue Type: Bug
> Components: mvcc, sql
>Reporter: Igor Seliverstov
>Priority: Major
> Labels: mvcc_stabilization_stage_1, transactions
> Fix For: 2.8
>
>
> When select for update executes from client node the execution is sent to
> random owning node. On that node dht enlist operation is started what causes
> an assertion error because dht enlist operation implies that the node is
> primary for all processed keys.
> see
> {{CacheMvccReplicatedBackupsTest.testBackupsCoherenceWithLargeOperations}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IGNITE-10241) MVCC TX: orphaned remote transactions
[
https://issues.apache.org/jira/browse/IGNITE-10241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Seliverstov resolved IGNITE-10241.
---
Resolution: Duplicate
Fixed in scope of IGNITE-10752
> MVCC TX: orphaned remote transactions
> -
>
> Key: IGNITE-10241
> URL: https://issues.apache.org/jira/browse/IGNITE-10241
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Igor Seliverstov
>Assignee: Igor Seliverstov
>Priority: Major
> Labels: failover, mvcc_stabilization_stage_1
> Fix For: 2.8
>
>
> {{*CacheMvccPartitionedSqlCoordinatorFailoverTest#testUpdate_N_Objects_ClientServer_Backups2_Sql*
> occasionally fails with following error:}}
> {code:java}
> [2018-11-13
> 15:03:44,240][ERROR][sys-#19392%mvcc.CacheMvccPartitionedSqlCoordinatorFailoverTest0%][GridDhtPartitionsExchangeFuture]
> Failed to notify listener:
> o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2@22ae2fbd
> java.lang.ClassCastException:
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxRemote
> cannot be cast to
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager.rollbackMvccTxOnCoordinatorChange(IgniteTxManager.java:327)
> at
> org.apache.ignite.internal.processors.cache.mvcc.MvccProcessorImpl.onExchangeDone(MvccProcessorImpl.java:394)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onDone(GridDhtPartitionsExchangeFuture.java:2095)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.finishExchangeOnCoordinator(GridDhtPartitionsExchangeFuture.java:3391)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onAllReceived(GridDhtPartitionsExchangeFuture.java:3157)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.processSingleMessage(GridDhtPartitionsExchangeFuture.java:2773)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.access$100(GridDhtPartitionsExchangeFuture.java:139)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2.apply(GridDhtPartitionsExchangeFuture.java:2578)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2.apply(GridDhtPartitionsExchangeFuture.java:2566)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:395)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:355)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onReceiveSingleMessage(GridDhtPartitionsExchangeFuture.java:2566)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.processSinglePartitionUpdate(GridCachePartitionExchangeManager.java:1747)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.access$1200(GridCachePartitionExchangeManager.java:144)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$2.onMessage(GridCachePartitionExchangeManager.java:377)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$2.onMessage(GridCachePartitionExchangeManager.java:335)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$MessageHandler.apply(GridCachePartitionExchangeManager.java:3194)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$MessageHandler.apply(GridCachePartitionExchangeManager.java:3173)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1054)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:579)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:378)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:304)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:100)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:294)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1568)
> at
>
[jira] [Updated] (IGNITE-11023) Processing data bag on GridMarshallerMappingProcessor consume many time
[
https://issues.apache.org/jira/browse/IGNITE-11023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-11023:
--
Ignite Flags: (was: Docs Required)
> Processing data bag on GridMarshallerMappingProcessor consume many time
> ---
>
> Key: IGNITE-11023
> URL: https://issues.apache.org/jira/browse/IGNITE-11023
> Project: Ignite
> Issue Type: Improvement
>Reporter: Vladislav Pyatkov
>Assignee: Vladislav Pyatkov
>Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> I have measure a processing data bag time on each join node and discovered
> what GridMarshallerMappingProcessor consume more time then others.
> It slow down on collecting topology, in particular case if joining some
> nodes.
> {noformat}
> 2019-01-11 20:35:01.207 [INFO
> ][tcp-disco-msg-worker-#2%NodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> Starting processing discovery data bag
> 2019-01-11 20:35:01.207 [INFO
> ][tcp-disco-msg-worker-#2%NodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> Component ClusterProcessor processed joining node data bag in 0ms
> 2019-01-11 20:35:01.207 [INFO
> ][tcp-disco-msg-worker-#2%NodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> Component IgnitePluginProcessor processed joining node data bag in 0ms
> 2019-01-11 20:35:01.208 [INFO
> ][tcp-disco-msg-worker-#2%NodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> Component CacheObjectBinaryProcessorImpl processed joining node data bag in
> 0ms
> 2019-01-11 20:35:01.208 [INFO
> ][tcp-disco-msg-worker-#2%NodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> Component IgniteAuthenticationProcessor processed joining node data bag in 0ms
> 2019-01-11 20:35:01.219 [INFO
> ][tcp-disco-msg-worker-#2%NodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> Component GridCacheProcessor processed joining node data bag in 10ms
> 2019-01-11 20:35:01.219 [INFO
> ][tcp-disco-msg-worker-#2%NodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> Component GridQueryProcessor processed joining node data bag in 0ms
> 2019-01-11 20:35:01.219 [INFO
> ][tcp-disco-msg-worker-#2%NodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> Component GridContinuousProcessor processed joining node data bag in 0ms
> 2019-01-11 20:35:01.463 [INFO
> ][tcp-disco-msg-worker-#2%NodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> Component GridMarshallerMappingProcessor processed joining node data bag in
> 242ms
> 2019-01-11 20:35:01.463 [INFO
> ][tcp-disco-msg-worker-#2%NodeName%][o.a.i.i.m.d.GridDiscoveryManager] Total
> time of processing discovery data bag: 252ms
> 2019-01-11 20:35:01.780 [INFO
> ][tcp-disco-msg-worker-#2%NodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> Starting processing discovery data bag
> 2019-01-11 20:35:01.781 [INFO
> ][tcp-disco-msg-worker-#2%NodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> Component ClusterProcessor processed joining node data bag in 0ms
> 2019-01-11 20:35:01.781 [INFO
> ][tcp-disco-msg-worker-#2%NodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> Component IgnitePluginProcessor processed joining node data bag in 0ms
> 2019-01-11 20:35:01.781 [INFO
> ][tcp-disco-msg-worker-#2%NodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> Component CacheObjectBinaryProcessorImpl processed joining node data bag in
> 0ms
> 2019-01-11 20:35:01.781 [INFO
> ][tcp-disco-msg-worker-#2%NodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> Component IgniteAuthenticationProcessor processed joining node data bag in 0ms
> 2019-01-11 20:35:01.791 [INFO
> ][tcp-disco-msg-worker-#2%NodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> Component GridCacheProcessor processed joining node data bag in 10ms
> 2019-01-11 20:35:01.792 [INFO
> ][tcp-disco-msg-worker-#2%NodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> Component GridQueryProcessor processed joining node data bag in 0ms
> 2019-01-11 20:35:01.792 [INFO
> ][tcp-disco-msg-worker-#2%NodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> Component GridContinuousProcessor processed joining node data bag in 0ms
> 2019-01-11 20:35:02.134 [INFO
> ][tcp-disco-msg-worker-#2%NodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> Component GridMarshallerMappingProcessor processed joining node data bag in
> 338ms
> 2019-01-11 20:35:02.134 [INFO
> ][tcp-disco-msg-worker-#2%NodeName%][o.a.i.i.m.d.GridDiscoveryManager] Total
> time of processing discovery data bag: 348ms
> 2019-01-11 20:35:02.326 [INFO
> ][tcp-disco-msg-worker-#2%NodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> Starting processing discovery data bag
> 2019-01-11 20:35:02.326 [INFO
> ][tcp-disco-msg-worker-#2%NodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> Component ClusterProcessor processed joining node data bag in 0ms
> 2019-01-11 20:35:02.326 [INFO
> ][tcp-disco-msg-worker-#2%NodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> Component
[jira] [Updated] (IGNITE-11023) Processing data bag on GridMarshallerMappingProcessor consume many time
[
https://issues.apache.org/jira/browse/IGNITE-11023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-11023:
--
Fix Version/s: 2.8
> Processing data bag on GridMarshallerMappingProcessor consume many time
> ---
>
> Key: IGNITE-11023
> URL: https://issues.apache.org/jira/browse/IGNITE-11023
> Project: Ignite
> Issue Type: Improvement
>Reporter: Vladislav Pyatkov
>Assignee: Vladislav Pyatkov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> I have measure a processing data bag time on each join node and discovered
> what GridMarshallerMappingProcessor consume more time then others.
> It slow down on collecting topology, in particular case if joining some
> nodes.
> {noformat}
> 2019-01-11 20:35:01.207 [INFO
> ][tcp-disco-msg-worker-#2%NodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> Starting processing discovery data bag
> 2019-01-11 20:35:01.207 [INFO
> ][tcp-disco-msg-worker-#2%NodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> Component ClusterProcessor processed joining node data bag in 0ms
> 2019-01-11 20:35:01.207 [INFO
> ][tcp-disco-msg-worker-#2%NodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> Component IgnitePluginProcessor processed joining node data bag in 0ms
> 2019-01-11 20:35:01.208 [INFO
> ][tcp-disco-msg-worker-#2%NodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> Component CacheObjectBinaryProcessorImpl processed joining node data bag in
> 0ms
> 2019-01-11 20:35:01.208 [INFO
> ][tcp-disco-msg-worker-#2%NodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> Component IgniteAuthenticationProcessor processed joining node data bag in 0ms
> 2019-01-11 20:35:01.219 [INFO
> ][tcp-disco-msg-worker-#2%NodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> Component GridCacheProcessor processed joining node data bag in 10ms
> 2019-01-11 20:35:01.219 [INFO
> ][tcp-disco-msg-worker-#2%NodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> Component GridQueryProcessor processed joining node data bag in 0ms
> 2019-01-11 20:35:01.219 [INFO
> ][tcp-disco-msg-worker-#2%NodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> Component GridContinuousProcessor processed joining node data bag in 0ms
> 2019-01-11 20:35:01.463 [INFO
> ][tcp-disco-msg-worker-#2%NodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> Component GridMarshallerMappingProcessor processed joining node data bag in
> 242ms
> 2019-01-11 20:35:01.463 [INFO
> ][tcp-disco-msg-worker-#2%NodeName%][o.a.i.i.m.d.GridDiscoveryManager] Total
> time of processing discovery data bag: 252ms
> 2019-01-11 20:35:01.780 [INFO
> ][tcp-disco-msg-worker-#2%NodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> Starting processing discovery data bag
> 2019-01-11 20:35:01.781 [INFO
> ][tcp-disco-msg-worker-#2%NodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> Component ClusterProcessor processed joining node data bag in 0ms
> 2019-01-11 20:35:01.781 [INFO
> ][tcp-disco-msg-worker-#2%NodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> Component IgnitePluginProcessor processed joining node data bag in 0ms
> 2019-01-11 20:35:01.781 [INFO
> ][tcp-disco-msg-worker-#2%NodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> Component CacheObjectBinaryProcessorImpl processed joining node data bag in
> 0ms
> 2019-01-11 20:35:01.781 [INFO
> ][tcp-disco-msg-worker-#2%NodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> Component IgniteAuthenticationProcessor processed joining node data bag in 0ms
> 2019-01-11 20:35:01.791 [INFO
> ][tcp-disco-msg-worker-#2%NodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> Component GridCacheProcessor processed joining node data bag in 10ms
> 2019-01-11 20:35:01.792 [INFO
> ][tcp-disco-msg-worker-#2%NodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> Component GridQueryProcessor processed joining node data bag in 0ms
> 2019-01-11 20:35:01.792 [INFO
> ][tcp-disco-msg-worker-#2%NodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> Component GridContinuousProcessor processed joining node data bag in 0ms
> 2019-01-11 20:35:02.134 [INFO
> ][tcp-disco-msg-worker-#2%NodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> Component GridMarshallerMappingProcessor processed joining node data bag in
> 338ms
> 2019-01-11 20:35:02.134 [INFO
> ][tcp-disco-msg-worker-#2%NodeName%][o.a.i.i.m.d.GridDiscoveryManager] Total
> time of processing discovery data bag: 348ms
> 2019-01-11 20:35:02.326 [INFO
> ][tcp-disco-msg-worker-#2%NodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> Starting processing discovery data bag
> 2019-01-11 20:35:02.326 [INFO
> ][tcp-disco-msg-worker-#2%NodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> Component ClusterProcessor processed joining node data bag in 0ms
> 2019-01-11 20:35:02.326 [INFO
> ][tcp-disco-msg-worker-#2%NodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> Component
[jira] [Created] (IGNITE-11188) Optimize baseline autoadjustment for in-memory clusters with zero timeout
Ivan Bessonov created IGNITE-11188: -- Summary: Optimize baseline autoadjustment for in-memory clusters with zero timeout Key: IGNITE-11188 URL: https://issues.apache.org/jira/browse/IGNITE-11188 Project: Ignite Issue Type: Improvement Reporter: Ivan Bessonov Assignee: Ivan Bessonov Fix For: 2.8 In current implementation (IGNITE-8571) zero-timeout case initiates two partition map exchanges on join/leave node events. This could be improved so that baseline is updated at the same time as join/leave event processing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11187) Additional documentation for re-balancing is canceled if client node joins.
Stanilovsky Evgeny created IGNITE-11187: --- Summary: Additional documentation for re-balancing is canceled if client node joins. Key: IGNITE-11187 URL: https://issues.apache.org/jira/browse/IGNITE-11187 Project: Ignite Issue Type: Improvement Affects Versions: 2.7 Reporter: Stanilovsky Evgeny Assignee: Maxim Muzafarov Fix For: 2.8 Need additional documentation for [IGNITE-7165] Re-balancing is canceled if client node joins. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11187) Additional documentation for re-balancing is canceled if client node joins.
[ https://issues.apache.org/jira/browse/IGNITE-11187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-11187: - Component/s: documentation > Additional documentation for re-balancing is canceled if client node joins. > --- > > Key: IGNITE-11187 > URL: https://issues.apache.org/jira/browse/IGNITE-11187 > Project: Ignite > Issue Type: Improvement > Components: documentation >Affects Versions: 2.7 >Reporter: Stanilovsky Evgeny >Assignee: Maxim Muzafarov >Priority: Major > Fix For: 2.8 > > > Need additional documentation for [IGNITE-7165] Re-balancing is canceled if > client node joins. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8571) Baseline auto-adjust feature
[ https://issues.apache.org/jira/browse/IGNITE-8571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16759782#comment-16759782 ] Ivan Bessonov commented on IGNITE-8571: --- [~akalashnikov] code looks good, thank you! > Baseline auto-adjust feature > > > Key: IGNITE-8571 > URL: https://issues.apache.org/jira/browse/IGNITE-8571 > Project: Ignite > Issue Type: New Feature >Reporter: Eduard Shangareev >Assignee: Anton Kalashnikov >Priority: Major > Labels: IEP-4, Phase-2 > Fix For: 2.8 > > Time Spent: 20m > Remaining Estimate: 0h > > Now we have only one way to change BLAT - manually update it via console.sh > or API. > We need to add the possibility to change it automatically. Adjust to current > topology. > So, I propose 3 new parameters which would be responsible to tune this > feature. > 1. Flag autoAdjustEnabled - true/false. Easy. Manual baseline control or auto > adjusting baseline. > 2. autoAdjustTimeout - time which we would wait after the actual topology > change. But it would be reset if new discovery event happened. (node > join/exit). > 3. autoAdjustMaxTimeout - time which we would wait from the first dicovery > event in the chain. If we achieved it than we would change BLAT right away > (no matter were another node join/exit happened or not). > We need to change API next way: > 1. org.apache.ignite.IgniteCluster > *Add* > isBaselineAutoAdjustEnabled() > setBaselineAutoAdjustEnabled(boolean enabled); > setBaselineAutoAdjustTimeout(long timeoutInMs); > setBaselineAutoAdjustMaxTimeout(long timeoutInMs); > 2. org.apache.ignite.configuration.IgniteConfiguration > *Add* > IgniteConfiguration setBaselineAutoAdjustEnabled(boolean enabled); > IgniteConfiguration setBaselineAutoAdjustTimeout(long timeoutInMs); > IgniteConfiguration setBaselineAutoAdjustMaxTimeout(long timeoutInMs); > Also, we need to ensure that all nodes would have the same parameters. > And we should be able to survive coordinator left during parameters changes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10876) "Affinity changes (coordinator) applied" can be executed in parallel
[
https://issues.apache.org/jira/browse/IGNITE-10876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-10876:
--
Fix Version/s: 2.8
> "Affinity changes (coordinator) applied" can be executed in parallel
>
>
> Key: IGNITE-10876
> URL: https://issues.apache.org/jira/browse/IGNITE-10876
> Project: Ignite
> Issue Type: Improvement
>Reporter: Pavel Voronkin
>Assignee: Pavel Voronkin
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> There is for loop over all cache groups which execution N*P operations in
> exchange worker where N is number of cache groups, P is number of partitions.
> We spend 80% of time in a loop
> for (CacheGroupContext grp : cctx.cache().cacheGroups()){
> GridDhtPartitionTopology top = grp != null ? grp.topology() :
> cctx.exchange().clientTopology(grp.groupId(), events().discoveryCache());
> top.beforeExchange(this, true, true);
> }
> I believe we can execute it in parallel
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11186) Web console: Border is visible on disabled dropdown component
[ https://issues.apache.org/jira/browse/IGNITE-11186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko updated IGNITE-11186: --- Attachment: (was: Selection_301.png) > Web console: Border is visible on disabled dropdown component > - > > Key: IGNITE-11186 > URL: https://issues.apache.org/jira/browse/IGNITE-11186 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Vasiliy Sisko >Priority: Minor > Attachments: ignite-11186.png > > > See attached screenshot. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11186) Web console: Border is visible on disabled dropdown component
[ https://issues.apache.org/jira/browse/IGNITE-11186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko updated IGNITE-11186: --- Attachment: ignite-11186.png > Web console: Border is visible on disabled dropdown component > - > > Key: IGNITE-11186 > URL: https://issues.apache.org/jira/browse/IGNITE-11186 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Vasiliy Sisko >Priority: Minor > Attachments: ignite-11186.png > > > See attached screenshot. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10876) "Affinity changes (coordinator) applied" can be executed in parallel
[
https://issues.apache.org/jira/browse/IGNITE-10876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-10876:
--
Ignite Flags: (was: Docs Required)
> "Affinity changes (coordinator) applied" can be executed in parallel
>
>
> Key: IGNITE-10876
> URL: https://issues.apache.org/jira/browse/IGNITE-10876
> Project: Ignite
> Issue Type: Improvement
>Reporter: Pavel Voronkin
>Assignee: Pavel Voronkin
>Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> There is for loop over all cache groups which execution N*P operations in
> exchange worker where N is number of cache groups, P is number of partitions.
> We spend 80% of time in a loop
> for (CacheGroupContext grp : cctx.cache().cacheGroups()){
> GridDhtPartitionTopology top = grp != null ? grp.topology() :
> cctx.exchange().clientTopology(grp.groupId(), events().discoveryCache());
> top.beforeExchange(this, true, true);
> }
> I believe we can execute it in parallel
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11186) Web console: Border is visible on disabled dropdown component
[ https://issues.apache.org/jira/browse/IGNITE-11186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko updated IGNITE-11186: --- Attachment: Selection_301.png > Web console: Border is visible on disabled dropdown component > - > > Key: IGNITE-11186 > URL: https://issues.apache.org/jira/browse/IGNITE-11186 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Vasiliy Sisko >Priority: Minor > Attachments: ignite-11186.png > > > See attached screenshot. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11186) Web console: Border is visible on disabled dropdown component
Vasiliy Sisko created IGNITE-11186: -- Summary: Web console: Border is visible on disabled dropdown component Key: IGNITE-11186 URL: https://issues.apache.org/jira/browse/IGNITE-11186 Project: Ignite Issue Type: Improvement Components: wizards Reporter: Vasiliy Sisko Attachments: ignite-11186.png See attached screenshot. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9290) Make remove explicit locks async when node left.
[ https://issues.apache.org/jira/browse/IGNITE-9290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov updated IGNITE-9290: - Labels: deadlock (was: deadlock iep-25) > Make remove explicit locks async when node left. > > > Key: IGNITE-9290 > URL: https://issues.apache.org/jira/browse/IGNITE-9290 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Andrew Mashenkov >Assignee: Andrew Mashenkov >Priority: Critical > Labels: deadlock > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > GridCacheMvccManager.removeExplicitNodeLocks() run synchronously in discovery > and exchange threads. This introduce unnecessary delays in discovery and > exchange process. > Also, this may cause a deadlock on node stop if user transaction holds an > entry lock and awaits some Ignite manager response (e.g. cache store or DR or > CQ), as manager stops right after last exchange has finished so managers > can't detect node is stopping. > > [1] > [http://apache-ignite-developers.2346864.n4.nabble.com/Synchronous-tx-entries-unlocking-in-discovery-exchange-threads-td33827.html] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10905) org.apache.ignite.internal.processors.cache.distributed.dht.topology.GridDhtInvalidPartitionException happens during rolling restart of a cluster
[
https://issues.apache.org/jira/browse/IGNITE-10905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-10905:
--
Ignite Flags: (was: Docs Required)
> org.apache.ignite.internal.processors.cache.distributed.dht.topology.GridDhtInvalidPartitionException
> happens during rolling restart of a cluster
> -
>
> Key: IGNITE-10905
> URL: https://issues.apache.org/jira/browse/IGNITE-10905
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.7
>Reporter: Maxim Pudov
>Assignee: Stepachev Maksim
>Priority: Critical
> Fix For: 2.8
>
>
> JVM is halted after this error during rolling restart of a cluster:
> {code}
> org.apache.ignite.internal.processors.cache.distributed.dht.topology.GridDhtInvalidPartitionException:
> Adding entry to partition that is concurrently evicted [grp=cacheGroup_7,
> part=518, shouldBeMoving=, belongs=true, topVer=AffinityTopologyVersion
> [topVer=42, minorTopVer=0], curTopVer=AffinityTopologyVersion [topVer=43,
> minorTopVer=0]]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.topology.GridDhtPartitionTopologyImpl.localPartition0(GridDhtPartitionTopologyImpl.java:950)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.topology.GridDhtPartitionTopologyImpl.localPartition(GridDhtPartitionTopologyImpl.java:825)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander.handleSupplyMessage(GridDhtPartitionDemander.java:744)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader.handleSupplyMessage(GridDhtPreloader.java:387)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$5.apply(GridCachePartitionExchangeManager.java:418)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$5.apply(GridCachePartitionExchangeManager.java:408)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1056)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:581)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$700(GridCacheIoManager.java:101)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$OrderedMessageListener.onMessage(GridCacheIoManager.java:1613)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1569)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4100(GridIoManager.java:127)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$GridCommunicationMessageSet.unwind(GridIoManager.java:2768)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.unwindMessageSet(GridIoManager.java:1529)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4400(GridIoManager.java:127)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$10.run(GridIoManager.java:1498)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10767) MVCC: Unknown page type error during scan query
[
https://issues.apache.org/jira/browse/IGNITE-10767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Pavlukhin updated IGNITE-10767:
Description:
Sometimes "Unknown page type: 1" error occurs during scan query execution.
Reproducer:
{{CacheMvccReplicatedSqlCoordinatorFailoverTest.testPutAllGetAll_SingleNode_RestartCoordinator_ScanDml_Persistence}}
Stack trace:
{noformat}
junit.framework.AssertionFailedError: Unexpected error:
junit.framework.AssertionFailedError: Unexpected tx exception.
java.lang.IllegalStateException: Unknown page type: 1 pageId: 00010079
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.io(BPlusTree.java:5094)
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.access$200(BPlusTree.java:90)
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$AbstractForwardCursor.nextPage(BPlusTree.java:5366)
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$ForwardCursor.next(BPlusTree.java:5602)
at
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$6.onHasNext(IgniteCacheOffheapManagerImpl.java:989)
at
org.apache.ignite.internal.util.GridCloseableIteratorAdapter.hasNextX(GridCloseableIteratorAdapter.java:53)
at
org.apache.ignite.internal.util.lang.GridIteratorAdapter.hasNext(GridIteratorAdapter.java:45)
at
org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager$ScanQueryIterator.advance(GridCacheQueryManager.java:2993)
at
org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager$ScanQueryIterator.onHasNext(GridCacheQueryManager.java:2962)
at
org.apache.ignite.internal.util.GridCloseableIteratorAdapter.hasNextX(GridCloseableIteratorAdapter.java:53)
at
org.apache.ignite.internal.util.lang.GridIteratorAdapter.hasNext(GridIteratorAdapter.java:45)
at
org.apache.ignite.internal.processors.cache.query.GridCacheQueryAdapter$MvccTrackingIterator.hasNext(GridCacheQueryAdapter.java:963)
at
org.apache.ignite.internal.processors.cache.QueryCursorImpl.getAll(QueryCursorImpl.java:114)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest.readAllByMode(CacheMvccAbstractTest.java:1918)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest$5.apply(CacheMvccAbstractTest.java:1007)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest$5.apply(CacheMvccAbstractTest.java:983)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest$10.call(CacheMvccAbstractTest.java:1362)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest$10.call(CacheMvccAbstractTest.java:1357)
at
org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:84)
{noformat}
was:
Sometimes "Unknown page type: 1" error occurs during scan query execution.
Reproducer:
{{CacheMvccReplicatedSqlCoordinatorFailoverTest.testPutAllGetAll_SingleNode_RestartCoordinator_ScanDml_Persistence}}
Stack trace:
{noformat}
junit.framework.AssertionFailedError: Unexpected error:
junit.framework.AssertionFailedError: Unexpected tx exception.
java.lang.IllegalStateException: Unknown page type: 1 pageId: 00010079
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.io(BPlusTree.java:5094)
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.access$200(BPlusTree.java:90)
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$AbstractForwardCursor.nextPage(BPlusTree.java:5366)
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$ForwardCursor.next(BPlusTree.java:5602)
at
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$6.onHasNext(IgniteCacheOffheapManagerImpl.java:989)
at
org.apache.ignite.internal.util.GridCloseableIteratorAdapter.hasNextX(GridCloseableIteratorAdapter.java:53)
at
org.apache.ignite.internal.util.lang.GridIteratorAdapter.hasNext(GridIteratorAdapter.java:45)
at
org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager$ScanQueryIterator.advance(GridCacheQueryManager.java:2993)
at
org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager$ScanQueryIterator.onHasNext(GridCacheQueryManager.java:2962)
at
org.apache.ignite.internal.util.GridCloseableIteratorAdapter.hasNextX(GridCloseableIteratorAdapter.java:53)
at
org.apache.ignite.internal.util.lang.GridIteratorAdapter.hasNext(GridIteratorAdapter.java:45)
at
org.apache.ignite.internal.processors.cache.query.GridCacheQueryAdapter$MvccTrackingIterator.hasNext(GridCacheQueryAdapter.java:963)
at
[jira] [Assigned] (IGNITE-10965) Web console: in progress state for buttons
[ https://issues.apache.org/jira/browse/IGNITE-10965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov reassigned IGNITE-10965: - Assignee: Alexander Kalinin (was: Ilya Borisov) > Web console: in progress state for buttons > -- > > Key: IGNITE-10965 > URL: https://issues.apache.org/jira/browse/IGNITE-10965 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Ilya Borisov >Assignee: Alexander Kalinin >Priority: Minor > Attachments: !icons.png, ProgressBtn.png > > Original Estimate: 8h > Remaining Estimate: 8h > > *The problem:* > Some actions triggered by user might take awhile, during which user can > click on action button multiple times and, depending on internal details, > cause unwanted side effects (like registering multiple users instead of one). > *Solution:* > Disable action button when action is running. Tell user to wait that > something is happening. This can be integrated into special button state. > Places new button state can be used in: > - User registration. > I'd rather prefer that new button state would: > - Not affect button dimensions because sudden button size change might look > uncanny. Overlays are OK, though. This probably rules out spinning indicator > inline with button label. > - Not hide original button label so.user always knows what's in progress. > - Work for all button styles. Unique background for each button type is not > OK, same background or overlay is OK. This will simplify the implementation. > The requirements above are not set in stone, every point is open for > discussion. > [~vabramova] to provide design, [~Klaster_1] or [~alexdel] to implement. > > Useful article: [https://habr.com/ru/post/271881/] > Sample implemenation: https://johannesjo.github.io/angular-promise-buttons/ > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10767) MVCC: Unknown page type error during scan query
[
https://issues.apache.org/jira/browse/IGNITE-10767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Pavlukhin updated IGNITE-10767:
Description:
Sometimes "Unknown page type: 1" error occurs during scan query execution.
Reproducer:
{{CacheMvccReplicatedSqlCoordinatorFailoverTest.testPutAllGetAll_SingleNode_RestartCoordinator_ScanDml_Persistence}}
Stack trace:
{noformat}
junit.framework.AssertionFailedError: Unexpected error:
junit.framework.AssertionFailedError: Unexpected tx exception.
java.lang.IllegalStateException: Unknown page type: 1 pageId: 00010079
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.io(BPlusTree.java:5094)
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.access$200(BPlusTree.java:90)
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$AbstractForwardCursor.nextPage(BPlusTree.java:5366)
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$ForwardCursor.next(BPlusTree.java:5602)
at
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$6.onHasNext(IgniteCacheOffheapManagerImpl.java:989)
at
org.apache.ignite.internal.util.GridCloseableIteratorAdapter.hasNextX(GridCloseableIteratorAdapter.java:53)
at
org.apache.ignite.internal.util.lang.GridIteratorAdapter.hasNext(GridIteratorAdapter.java:45)
at
org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager$ScanQueryIterator.advance(GridCacheQueryManager.java:2993)
at
org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager$ScanQueryIterator.onHasNext(GridCacheQueryManager.java:2962)
at
org.apache.ignite.internal.util.GridCloseableIteratorAdapter.hasNextX(GridCloseableIteratorAdapter.java:53)
at
org.apache.ignite.internal.util.lang.GridIteratorAdapter.hasNext(GridIteratorAdapter.java:45)
at
org.apache.ignite.internal.processors.cache.query.GridCacheQueryAdapter$MvccTrackingIterator.hasNext(GridCacheQueryAdapter.java:963)
at
org.apache.ignite.internal.processors.cache.QueryCursorImpl.getAll(QueryCursorImpl.java:114)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest.readAllByMode(CacheMvccAbstractTest.java:1918)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest$5.apply(CacheMvccAbstractTest.java:1007)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest$5.apply(CacheMvccAbstractTest.java:983)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest$10.call(CacheMvccAbstractTest.java:1362)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest$10.call(CacheMvccAbstractTest.java:1357)
at
org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:84)
{noformat}
was:
Sometimes "Unknown page type: 1" error occurs during scan query execution.
Reproducer:
{{CacheMvccReplicatedSqlCoordinatorFailoverTest.testPutAllGetAll_SingleNode_RestartCoordinator_ScanDml_Persistence}}
Stack trace:
{noformat}
junit.framework.AssertionFailedError: Unexpected error:
junit.framework.AssertionFailedError: Unexpected tx exception.
java.lang.IllegalStateException: Unknown page type: 1 pageId: 00010079
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.io(BPlusTree.java:5094)
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.access$200(BPlusTree.java:90)
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$AbstractForwardCursor.nextPage(BPlusTree.java:5366)
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$ForwardCursor.next(BPlusTree.java:5602)
at
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$6.onHasNext(IgniteCacheOffheapManagerImpl.java:989)
at
org.apache.ignite.internal.util.GridCloseableIteratorAdapter.hasNextX(GridCloseableIteratorAdapter.java:53)
at
org.apache.ignite.internal.util.lang.GridIteratorAdapter.hasNext(GridIteratorAdapter.java:45)
at
org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager$ScanQueryIterator.advance(GridCacheQueryManager.java:2993)
at
org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager$ScanQueryIterator.onHasNext(GridCacheQueryManager.java:2962)
at
org.apache.ignite.internal.util.GridCloseableIteratorAdapter.hasNextX(GridCloseableIteratorAdapter.java:53)
at
org.apache.ignite.internal.util.lang.GridIteratorAdapter.hasNext(GridIteratorAdapter.java:45)
at
org.apache.ignite.internal.processors.cache.query.GridCacheQueryAdapter$MvccTrackingIterator.hasNext(GridCacheQueryAdapter.java:963)
at
[jira] [Commented] (IGNITE-10582) MVCC: Error on txLog initialization.
[
https://issues.apache.org/jira/browse/IGNITE-10582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16759734#comment-16759734
]
Ignite TC Bot commented on IGNITE-10582:
{panel:title=-- Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}MVCC Queries{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2834121]]
* IgniteCacheMvccSqlTestSuite:
CacheMvccPartitionedSqlCoordinatorFailoverTest.testSqlReadInProgressCoordinatorFails_ReadDelay
- 0,0% fails in last 423 master runs.
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2834187buildTypeId=IgniteTests24Java8_RunAll]
> MVCC: Error on txLog initialization.
>
>
> Key: IGNITE-10582
> URL: https://issues.apache.org/jira/browse/IGNITE-10582
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Assignee: Andrew Mashenkov
>Priority: Major
> Labels: Muted_test, mvcc_stabilization_stage_1, pagememory
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> A sporadic error occurs during {{txLog}} initialization. Reproducer:
> {{IgnitePdsCacheAssignmentNodeRestartsTest#testAssignmentAfterRestarts}}.
> This error may be the result of the test settings. We need to check it more
> carefully.
> Stacktrace:
> {noformat}
> javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException:
> Failed to complete exchange process.
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1337)
> at
> org.apache.ignite.internal.IgniteKernal.getOrCreateCaches(IgniteKernal.java:3068)
> at
> org.apache.ignite.internal.processors.cache.persistence.IgnitePdsCacheAssignmentNodeRestartsTest.testAssignmentAfterRestarts(IgnitePdsCacheAssignmentNodeRestartsTest.java:148)
> 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.access$001(GridAbstractTest.java:149)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$6.evaluate(GridAbstractTest.java:2106)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2123)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to complete
> exchange process.
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.createExchangeException(GridDhtPartitionsExchangeFuture.java:3041)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.sendExchangeFailureMessage(GridDhtPartitionsExchangeFuture.java:3069)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.finishExchangeOnCoordinator(GridDhtPartitionsExchangeFuture.java:3151)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onAllReceived(GridDhtPartitionsExchangeFuture.java:3135)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.processSingleMessage(GridDhtPartitionsExchangeFuture.java:2748)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.access$100(GridDhtPartitionsExchangeFuture.java:138)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2.apply(GridDhtPartitionsExchangeFuture.java:2556)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2.apply(GridDhtPartitionsExchangeFuture.java:2544)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:395)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:355)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onReceiveSingleMessage(GridDhtPartitionsExchangeFuture.java:2544)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.processSinglePartitionUpdate(GridCachePartitionExchangeManager.java:1807)
> at
>
[jira] [Closed] (IGNITE-10786) MVCC: Flaky test IgniteClusterActivateDeactivateTestWithPersistence#testDeactivateDuringEvictionAndRebalance
[
https://issues.apache.org/jira/browse/IGNITE-10786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Mashenkov closed IGNITE-10786.
-
> MVCC: Flaky test
> IgniteClusterActivateDeactivateTestWithPersistence#testDeactivateDuringEvictionAndRebalance
>
>
> Key: IGNITE-10786
> URL: https://issues.apache.org/jira/browse/IGNITE-10786
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Assignee: Andrew Mashenkov
>Priority: Major
> Labels: failover, mvcc_stabilization_stage_1
> Fix For: 2.8
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Test
> {{IgniteClusterActivateDeactivateTestWithPersistence#testDeactivateDuringEvictionAndRebalance}}
> is flaky when MVCC is enabled. We should investigate it.
> {noformat}
> [2018-12-21 02:26:51,592][ERROR][main][root] Test failed.
> java.lang.AssertionError:
> node=cache.IgniteClusterActivateDeactivateTestWithPersistence0, key=12
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertNotNull(Assert.java:621)
> at
> org.apache.ignite.internal.processors.cache.IgniteClusterActivateDeactivateTestWithPersistence.testDeactivateDuringEvictionAndRebalance(IgniteClusterActivateDeactivateTestWithPersistence.java:425)
> 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
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2115)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (IGNITE-10788) MVCC: Get operation may hang in some cases
[
https://issues.apache.org/jira/browse/IGNITE-10788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Mashenkov closed IGNITE-10788.
-
> MVCC: Get operation may hang in some cases
> --
>
> Key: IGNITE-10788
> URL: https://issues.apache.org/jira/browse/IGNITE-10788
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Assignee: Andrew Mashenkov
>Priority: Major
> Labels: Hanging, mvcc_stabilization_stage_1
> Fix For: 2.8
>
>
> Get operation may hang on snapshot acquisition in some cases. Reproducer:
> {{IgniteClusterActivateDeactivateTestWithPersistenceAndMemoryReuse.testDeactivateDuringEvictionAndRebalance}}
> StackTrace:
> {noformat}
> Thread
> [name="test-runner-#4675%cache.IgniteClusterActivateDeactivateTestWithPersistenceAndMemoryReuse%",
> id=5136, state=WAITING, blockCnt=42, waitCnt=382996]
> at sun.misc.Unsafe.park(Native Method)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:304)
> at
> o.a.i.i.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:178)
> at
> o.a.i.i.util.future.GridFutureAdapter.get(GridFutureAdapter.java:141)
> at
> o.a.i.i.processors.cache.mvcc.MvccUtils.mvccTracker(MvccUtils.java:817)
> at
> o.a.i.i.processors.cache.distributed.dht.colocated.GridDhtColocatedCache.getAsync(GridDhtColocatedCache.java:244)
> at
> o.a.i.i.processors.cache.GridCacheAdapter.get0(GridCacheAdapter.java:4725)
> at
> o.a.i.i.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4706)
> at
> o.a.i.i.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1450)
> at
> o.a.i.i.processors.cache.IgniteCacheProxyImpl.get(IgniteCacheProxyImpl.java:927)
> at
> o.a.i.i.processors.cache.GatewayProtectedCacheProxy.get(GatewayProtectedCacheProxy.java:640)
> at
> o.a.i.i.processors.cache.IgniteClusterActivateDeactivateTestWithPersistence.testDeactivateDuringEvictionAndRebalance(IgniteClusterActivateDeactivateTestWithPersistence.java:415)
> 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
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at
> o.a.i.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2115)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
