[jira] [Created] (IGNITE-9797) Refer to PHP, Python and Node.JS getting started guides from the website
Denis Magda created IGNITE-9797: --- Summary: Refer to PHP, Python and Node.JS getting started guides from the website Key: IGNITE-9797 URL: https://issues.apache.org/jira/browse/IGNITE-9797 Project: Ignite Issue Type: Task Components: site Affects Versions: 2.7 Reporter: Denis Magda Assignee: Prachi Garg This page includes a section with the list of references to getting started guides: https://ignite.apache.org/features/multilanguage.html Add references to Python, PHP and Node.JS docs on readme.io (Instantiation and Configuration pages on readme). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9799) Web console: remove unused code
Ilya Borisov created IGNITE-9799: Summary: Web console: remove unused code Key: IGNITE-9799 URL: https://issues.apache.org/jira/browse/IGNITE-9799 Project: Ignite Issue Type: Improvement Components: wizards Reporter: Ilya Borisov Assignee: Alexander Kalinin There's a bunch of legacy/unused code and dependencies, let's remove those. Here's an incomplete list, feel free to add more items: 1. angular-cookies dependency -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9798) Add TensorFlow Integration Page to Ignite website
Denis Magda created IGNITE-9798: --- Summary: Add TensorFlow Integration Page to Ignite website Key: IGNITE-9798 URL: https://issues.apache.org/jira/browse/IGNITE-9798 Project: Ignite Issue Type: Task Components: site Reporter: Denis Magda Assignee: Prachi Garg Fix For: 2.7 We need to create a dedicated page for Ignite and TensorFlow integration. Please put it under Machine Learning item of the Features menu. [~abchaudhri], will provide a reference to the readme.io page with in-depth integration description. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9797) Refer to PHP, Python and Node.JS getting started guides from the website
[ https://issues.apache.org/jira/browse/IGNITE-9797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-9797: Fix Version/s: 2.7 > Refer to PHP, Python and Node.JS getting started guides from the website > > > Key: IGNITE-9797 > URL: https://issues.apache.org/jira/browse/IGNITE-9797 > Project: Ignite > Issue Type: Task > Components: site >Affects Versions: 2.7 >Reporter: Denis Magda >Assignee: Prachi Garg >Priority: Major > Fix For: 2.7 > > > This page includes a section with the list of references to getting started > guides: > https://ignite.apache.org/features/multilanguage.html > Add references to Python, PHP and Node.JS docs on readme.io (Instantiation > and Configuration pages on readme). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-9523) Document PHP thin client
[ https://issues.apache.org/jira/browse/IGNITE-9523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda closed IGNITE-9523. --- > Document PHP thin client > > > Key: IGNITE-9523 > URL: https://issues.apache.org/jira/browse/IGNITE-9523 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Prachi Garg >Assignee: Denis Magda >Priority: Critical > Fix For: 2.7 > > > Jira with the scope of work - [1]. > Implementation, examples, tests: > PR - [2], > repository - [3]. > API spec - [4]. > Readme (how to for the client, instructions for the examples and tests, etc.) > - [5]. > [1] https://issues.apache.org/jira/browse/IGNITE-7783 > [2] [https://github.com/apache/ignite/pull/4649] > [3] > [https://github.com/nobitlost/ignite/tree/ignite-7783/modules/platforms/php] > [4] > [https://rawgit.com/nobitlost/ignite/ignite-7783-docs/modules/platforms/php/api_docs/html/index.html] > [5] > [https://github.com/nobitlost/ignite/blob/ignite-7783-docs/modules/platforms/php/README.md] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9714) Document ODBC streaming mode
[
https://issues.apache.org/jira/browse/IGNITE-9714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16639216#comment-16639216
]
Denis Magda commented on IGNITE-9714:
-
[~Artem Budnikov], this page needs to be updated as well:
https://apacheignite-sql.readme.io/v2.6/docs/set
Presently it says that the streaming through SET is supported for JDBC only.
> Document ODBC streaming mode
>
>
> Key: IGNITE-9714
> URL: https://issues.apache.org/jira/browse/IGNITE-9714
> Project: Ignite
> Issue Type: Task
> Components: documentation
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Major
> Fix For: 2.7
>
>
> Need to document ODBC streaming mode introduced in IGNITE-7855.
> Need to mention that ODBC supports streaming mode now and give a link to a
> {{SET}} command description, pretty much the same way it's done for JDBC:
> https://apacheignite-sql.readme.io/docs/jdbc-driver#section-streaming
> Maybe it makes sense to mention that "array of parameters" feature and
> "data-on-execution" are not supported in the streaming mode.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (IGNITE-9522) Document Python thin client
[ https://issues.apache.org/jira/browse/IGNITE-9522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda closed IGNITE-9522. --- > Document Python thin client > --- > > Key: IGNITE-9522 > URL: https://issues.apache.org/jira/browse/IGNITE-9522 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Prachi Garg >Assignee: Denis Magda >Priority: Critical > Fix For: 2.7 > > > Bring documentation from here - > [https://apache-ignite-binary-protocol-client.readthedocs.io/en/latest/readme.html] > into readme.io -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9522) Document Python thin client
[ https://issues.apache.org/jira/browse/IGNITE-9522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16639215#comment-16639215 ] Denis Magda commented on IGNITE-9522: - [~pgarg], excellent! Let's roll the docs out once the release is ready and get the first user feedback. > Document Python thin client > --- > > Key: IGNITE-9522 > URL: https://issues.apache.org/jira/browse/IGNITE-9522 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Prachi Garg >Assignee: Denis Magda >Priority: Critical > Fix For: 2.7 > > > Bring documentation from here - > [https://apache-ignite-binary-protocol-client.readthedocs.io/en/latest/readme.html] > into readme.io -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9523) Document PHP thin client
[ https://issues.apache.org/jira/browse/IGNITE-9523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16639214#comment-16639214 ] Denis Magda commented on IGNITE-9523: - [~pgarg], looks perfect! Thanks a lot for a tremendous job. > Document PHP thin client > > > Key: IGNITE-9523 > URL: https://issues.apache.org/jira/browse/IGNITE-9523 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Prachi Garg >Assignee: Denis Magda >Priority: Critical > Fix For: 2.7 > > > Jira with the scope of work - [1]. > Implementation, examples, tests: > PR - [2], > repository - [3]. > API spec - [4]. > Readme (how to for the client, instructions for the examples and tests, etc.) > - [5]. > [1] https://issues.apache.org/jira/browse/IGNITE-7783 > [2] [https://github.com/apache/ignite/pull/4649] > [3] > [https://github.com/nobitlost/ignite/tree/ignite-7783/modules/platforms/php] > [4] > [https://rawgit.com/nobitlost/ignite/ignite-7783-docs/modules/platforms/php/api_docs/html/index.html] > [5] > [https://github.com/nobitlost/ignite/blob/ignite-7783-docs/modules/platforms/php/README.md] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7728) Put together a doc that shows how to blend SQL with k/v APIs
[ https://issues.apache.org/jira/browse/IGNITE-7728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16639212#comment-16639212 ] Denis Magda commented on IGNITE-7728: - [~Artem Budnikov], thanks for the documentation. I reviewed it and made minor changes: * renamed to SQL and Key-Value Usage * removed the requirement of having the PRIVATE deployment mode. It was never required. We always use the default mode and the peer-class-loading works fine. Send a message to the dev list if the issue persists, it sounds like a bug on your side. [~pgarg], please do a final review. > Put together a doc that shows how to blend SQL with k/v APIs > > > Key: IGNITE-7728 > URL: https://issues.apache.org/jira/browse/IGNITE-7728 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis Magda >Assignee: Denis Magda >Priority: Blocker > Fix For: 2.7 > > > More and more people start blending SQL with key-value APIs in Ignite. > Usually, they create tables/caches with DDL and wish to use key-value later > as well: > [https://stackoverflow.com/questions/48795533/how-do-i-read-data-from-cache-using-javaapi-after-i-put-it-through-jdbc] > https://stackoverflow.com/questions/49834964/mixing-apache-ignite-binaryobject-with-sql-tables/49864396#49864396 > > We already have a project that demonstrates this approach: > [https://github.com/dmagda/ignite_world_demo] > > Put together a doc that points out to it and elaborates on this topic. The > doc needs to explain how tables are mapped to the caches, columns to types as > discussed here: > http://apache-ignite-developers.2346864.n4.nabble.com/write-through-when-using-SQL-updates-td29767.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-7728) Put together a doc that shows how to blend SQL with k/v APIs
[ https://issues.apache.org/jira/browse/IGNITE-7728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda reassigned IGNITE-7728: --- Assignee: Prachi Garg (was: Denis Magda) > Put together a doc that shows how to blend SQL with k/v APIs > > > Key: IGNITE-7728 > URL: https://issues.apache.org/jira/browse/IGNITE-7728 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis Magda >Assignee: Prachi Garg >Priority: Blocker > Fix For: 2.7 > > > More and more people start blending SQL with key-value APIs in Ignite. > Usually, they create tables/caches with DDL and wish to use key-value later > as well: > [https://stackoverflow.com/questions/48795533/how-do-i-read-data-from-cache-using-javaapi-after-i-put-it-through-jdbc] > https://stackoverflow.com/questions/49834964/mixing-apache-ignite-binaryobject-with-sql-tables/49864396#49864396 > > We already have a project that demonstrates this approach: > [https://github.com/dmagda/ignite_world_demo] > > Put together a doc that points out to it and elaborates on this topic. The > doc needs to explain how tables are mapped to the caches, columns to types as > discussed here: > http://apache-ignite-developers.2346864.n4.nabble.com/write-through-when-using-SQL-updates-td29767.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9576) Document Multi-Class Logistic Regression
[ https://issues.apache.org/jira/browse/IGNITE-9576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda reassigned IGNITE-9576: --- Assignee: Akmal Chaudhri (was: Denis Magda) > Document Multi-Class Logistic Regression > > > Key: IGNITE-9576 > URL: https://issues.apache.org/jira/browse/IGNITE-9576 > Project: Ignite > Issue Type: Task > Components: documentation, ml >Reporter: Aleksey Zinoviev >Assignee: Akmal Chaudhri >Priority: Major > Fix For: 2.7 > > > Added documentation for "Multi-class Logisitic Regression" > [https://docs.google.com/document/d/1L2NIZ0K3fn74VswT8k7Qk0Tezqyc_hAJETQGN–TZb4/edit?usp=sharing|https://docs.google.com/document/d/1L2NIZ0K3fn74VswT8k7Qk0Tezqyc_hAJETQGN--TZb4/edit?usp=sharing] > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9579) Document Random Forest
[ https://issues.apache.org/jira/browse/IGNITE-9579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda reassigned IGNITE-9579: --- Assignee: Akmal Chaudhri (was: Denis Magda) > Document Random Forest > -- > > Key: IGNITE-9579 > URL: https://issues.apache.org/jira/browse/IGNITE-9579 > Project: Ignite > Issue Type: Task > Components: documentation, ml >Reporter: Aleksey Zinoviev >Assignee: Akmal Chaudhri >Priority: Major > Fix For: 2.7 > > > The link for new page with name "Random Forest" is here > https://docs.google.com/document/d/14t67HlWBaoV91887NjqbrsT0dAuExIxUOxYiaIbwEt4/edit?usp=sharing -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7131) Document Web Console deployment in Kubernetes
[ https://issues.apache.org/jira/browse/IGNITE-7131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16639201#comment-16639201 ] Denis Magda commented on IGNITE-7131: - [~pgarg], please do a final review. > Document Web Console deployment in Kubernetes > - > > Key: IGNITE-7131 > URL: https://issues.apache.org/jira/browse/IGNITE-7131 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 2.5 >Reporter: Denis Magda >Assignee: Denis Magda >Priority: Major > Fix For: 2.7 > > > The ticket is inspired by the following topic: > http://apache-ignite-users.70518.x6.nabble.com/Web-Console-on-Kubernetes-Cluster-td18591.html > It will be great to put together a documentation about Web Console deployment > on Kubernetes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-7131) Document Web Console deployment in Kubernetes
[ https://issues.apache.org/jira/browse/IGNITE-7131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda reassigned IGNITE-7131: --- Assignee: Prachi Garg (was: Denis Magda) > Document Web Console deployment in Kubernetes > - > > Key: IGNITE-7131 > URL: https://issues.apache.org/jira/browse/IGNITE-7131 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 2.5 >Reporter: Denis Magda >Assignee: Prachi Garg >Priority: Major > Fix For: 2.7 > > > The ticket is inspired by the following topic: > http://apache-ignite-users.70518.x6.nabble.com/Web-Console-on-Kubernetes-Cluster-td18591.html > It will be great to put together a documentation about Web Console deployment > on Kubernetes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-8994) Configuring dedicated volumes for WAL and data with Kubernetes
[ https://issues.apache.org/jira/browse/IGNITE-8994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda resolved IGNITE-8994. - Resolution: Fixed Looks good, thanks! > Configuring dedicated volumes for WAL and data with Kubernetes > -- > > Key: IGNITE-8994 > URL: https://issues.apache.org/jira/browse/IGNITE-8994 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis Magda >Assignee: Denis Magda >Priority: Major > Fix For: 2.7 > > Attachments: yaml.zip > > > The current StatefulSet documentation request only one persistent volume for > both WAL and data/index files: > https://apacheignite.readme.io/docs/stateful-deployment#section-statefulset-deployment > However, according to Ignite performance guide the WAL has to be located on a > dedicated volume: > https://apacheignite.readme.io/docs/durable-memory-tuning#section-separate-disk-device-for-wal > Provide StatefulSet configuration that shows how to request separate volumes > for the WAL and data/index files. If needed, provide YAML configs for > StorageClass and volume claims. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-8994) Configuring dedicated volumes for WAL and data with Kubernetes
[ https://issues.apache.org/jira/browse/IGNITE-8994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda closed IGNITE-8994. --- > Configuring dedicated volumes for WAL and data with Kubernetes > -- > > Key: IGNITE-8994 > URL: https://issues.apache.org/jira/browse/IGNITE-8994 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis Magda >Assignee: Denis Magda >Priority: Major > Fix For: 2.7 > > Attachments: yaml.zip > > > The current StatefulSet documentation request only one persistent volume for > both WAL and data/index files: > https://apacheignite.readme.io/docs/stateful-deployment#section-statefulset-deployment > However, according to Ignite performance guide the WAL has to be located on a > dedicated volume: > https://apacheignite.readme.io/docs/durable-memory-tuning#section-separate-disk-device-for-wal > Provide StatefulSet configuration that shows how to request separate volumes > for the WAL and data/index files. If needed, provide YAML configs for > StorageClass and volume claims. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9574) Document Gradient boosting
[ https://issues.apache.org/jira/browse/IGNITE-9574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda reassigned IGNITE-9574: --- Assignee: Akmal Chaudhri (was: Denis Magda) > Document Gradient boosting > -- > > Key: IGNITE-9574 > URL: https://issues.apache.org/jira/browse/IGNITE-9574 > Project: Ignite > Issue Type: Task > Components: documentation, ml >Reporter: Aleksey Zinoviev >Assignee: Akmal Chaudhri >Priority: Major > Fix For: 2.7 > > > The documentation for the new page with name "Gradient Boosting" > https://docs.google.com/document/d/1Twztetmpu9hH9ueomhAOUZSLUCukk8AvY9ibuicDCXI/edit -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9575) Document Binary Logistic Regression
[ https://issues.apache.org/jira/browse/IGNITE-9575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda reassigned IGNITE-9575: --- Assignee: Akmal Chaudhri (was: Denis Magda) > Document Binary Logistic Regression > --- > > Key: IGNITE-9575 > URL: https://issues.apache.org/jira/browse/IGNITE-9575 > Project: Ignite > Issue Type: Task > Components: documentation, ml >Reporter: Aleksey Zinoviev >Assignee: Akmal Chaudhri >Priority: Major > Fix For: 2.7 > > > The docs for the page "Binary Logistic Regression" > [https://docs.google.com/document/d/1UjcyxHdcRDffbhcFEGkaPvxcG9Xn1SuTy-gmeHWaWFg/edit?usp=sharing] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9577) Document Preprocessing
[ https://issues.apache.org/jira/browse/IGNITE-9577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda reassigned IGNITE-9577: --- Assignee: Akmal Chaudhri (was: Denis Magda) > Document Preprocessing > -- > > Key: IGNITE-9577 > URL: https://issues.apache.org/jira/browse/IGNITE-9577 > Project: Ignite > Issue Type: Task > Components: documentation, ml >Reporter: Aleksey Zinoviev >Assignee: Akmal Chaudhri >Priority: Major > Fix For: 2.7 > > > The link for the updating > [https://apacheignite.readme.io/docs/ml-preprocessing] > > is here > [https://docs.google.com/document/d/1_KAZd5rVTlgWI3ZI9Q5gPVo06SuNZN4Sc6XD7KOX-Xw/edit?usp=sharing] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9581) Document ANN algorithm based on ACD concept
[ https://issues.apache.org/jira/browse/IGNITE-9581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda reassigned IGNITE-9581: --- Assignee: Akmal Chaudhri (was: Denis Magda) > Document ANN algorithm based on ACD concept > --- > > Key: IGNITE-9581 > URL: https://issues.apache.org/jira/browse/IGNITE-9581 > Project: Ignite > Issue Type: Task > Components: documentation, ml >Reporter: Aleksey Zinoviev >Assignee: Akmal Chaudhri >Priority: Major > Fix For: 2.7 > > > The documentation for ANN classification algorithm > https://docs.google.com/document/d/1-ie6qrLy6ufkHVabG7ZggKLS2JbsLN2Ciyd_rr6nRgA/edit?usp=sharing -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-9752) Fix ODBC documentation
[ https://issues.apache.org/jira/browse/IGNITE-9752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda closed IGNITE-9752. --- > Fix ODBC documentation > -- > > Key: IGNITE-9752 > URL: https://issues.apache.org/jira/browse/IGNITE-9752 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Dmitry Sherstobitov >Assignee: Prachi Garg >Priority: Blocker > Fix For: 2.7 > > Attachments: image-2018-10-01-17-12-21-555.png > > > See screen shot. > There is no matching between default values and values in example > host in default - 0.0.0.0 > port in default - 10800 > host in example 127.0.0.1 (does it visible inside machine?) > port - 12345 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9752) Fix ODBC documentation
[ https://issues.apache.org/jira/browse/IGNITE-9752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16639022#comment-16639022 ] Denis Magda commented on IGNITE-9752: - I set the port number to 10800 in the example configuration. That's enough. > Fix ODBC documentation > -- > > Key: IGNITE-9752 > URL: https://issues.apache.org/jira/browse/IGNITE-9752 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Dmitry Sherstobitov >Assignee: Prachi Garg >Priority: Blocker > Fix For: 2.7 > > Attachments: image-2018-10-01-17-12-21-555.png > > > See screen shot. > There is no matching between default values and values in example > host in default - 0.0.0.0 > port in default - 10800 > host in example 127.0.0.1 (does it visible inside machine?) > port - 12345 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-9752) Fix ODBC documentation
[ https://issues.apache.org/jira/browse/IGNITE-9752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda resolved IGNITE-9752. - Resolution: Fixed > Fix ODBC documentation > -- > > Key: IGNITE-9752 > URL: https://issues.apache.org/jira/browse/IGNITE-9752 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Dmitry Sherstobitov >Assignee: Prachi Garg >Priority: Blocker > Fix For: 2.7 > > Attachments: image-2018-10-01-17-12-21-555.png > > > See screen shot. > There is no matching between default values and values in example > host in default - 0.0.0.0 > port in default - 10800 > host in example 127.0.0.1 (does it visible inside machine?) > port - 12345 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9796) NPE if you call array() method on empty GridLongList
[
https://issues.apache.org/jira/browse/IGNITE-9796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16638948#comment-16638948
]
Eduard Shangareev commented on IGNITE-9796:
---
[~DmitriyGovorukhin], please, take a look.
> NPE if you call array() method on empty GridLongList
>
>
> Key: IGNITE-9796
> URL: https://issues.apache.org/jira/browse/IGNITE-9796
> Project: Ignite
> Issue Type: Bug
>Reporter: Eduard Shangareev
>Assignee: Eduard Shangareev
>Priority: Major
>
> {code}
> /**
> *
> */
> public void testArray() {
> GridLongList list = new GridLongList();
> long[] array = list.array();
> assertNotNull(array);
> assertEquals(0, array.length);
> }
> {code}
> That is it, current version of GridLongList would cause NPE.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9796) NPE if you call array() method on empty GridLongList
[
https://issues.apache.org/jira/browse/IGNITE-9796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16638914#comment-16638914
]
ASF GitHub Bot commented on IGNITE-9796:
GitHub user EdShangGG opened a pull request:
https://github.com/apache/ignite/pull/4917
IGNITE-9796 NPE if you call array() method on empty GridLongList
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9796
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4917.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #4917
commit 534a0b0f4b7cd570fd10fcf69d8dcaf8fd2b944b
Author: Eduard Shangareev
Date: 2018-10-04T21:45:42Z
IGNITE-9796 NPE if you call array() method on empty GridLongList
> NPE if you call array() method on empty GridLongList
>
>
> Key: IGNITE-9796
> URL: https://issues.apache.org/jira/browse/IGNITE-9796
> Project: Ignite
> Issue Type: Bug
>Reporter: Eduard Shangareev
>Assignee: Eduard Shangareev
>Priority: Major
>
> {code}
> /**
> *
> */
> public void testArray() {
> GridLongList list = new GridLongList();
> long[] array = list.array();
> assertNotNull(array);
> assertEquals(0, array.length);
> }
> {code}
> That is it, current version of GridLongList would cause NPE.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9796) NPE if you call array() method on empty GridLongList
[
https://issues.apache.org/jira/browse/IGNITE-9796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Shangareev updated IGNITE-9796:
--
Summary: NPE if you call array() method on empty GridLongList (was: NPE if
you call array on empty GridLongList)
> NPE if you call array() method on empty GridLongList
>
>
> Key: IGNITE-9796
> URL: https://issues.apache.org/jira/browse/IGNITE-9796
> Project: Ignite
> Issue Type: Bug
>Reporter: Eduard Shangareev
>Assignee: Eduard Shangareev
>Priority: Major
>
> {code}
> /**
> *
> */
> public void testArray() {
> GridLongList list = new GridLongList();
> long[] array = list.array();
> assertNotNull(array);
> assertEquals(0, array.length);
> }
> {code}
> That is it, current version of GridLongList would cause NPE.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9796) NPE if you call array on empty GridLongList
Eduard Shangareev created IGNITE-9796:
-
Summary: NPE if you call array on empty GridLongList
Key: IGNITE-9796
URL: https://issues.apache.org/jira/browse/IGNITE-9796
Project: Ignite
Issue Type: Bug
Reporter: Eduard Shangareev
Assignee: Eduard Shangareev
{code}
/**
*
*/
public void testArray() {
GridLongList list = new GridLongList();
long[] array = list.array();
assertNotNull(array);
assertEquals(0, array.length);
}
{code}
That is it, current version of GridLongList would cause NPE.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9794) Registration of a binary type with POJO field under topology lock leads to UnregisteredBinaryTypeException
[ https://issues.apache.org/jira/browse/IGNITE-9794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16638684#comment-16638684 ] Stanilovsky Evgeny commented on IGNITE-9794: [~dgladkikh] plz take a look too. > Registration of a binary type with POJO field under topology lock leads to > UnregisteredBinaryTypeException > -- > > Key: IGNITE-9794 > URL: https://issues.apache.org/jira/browse/IGNITE-9794 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.6 >Reporter: Denis Mekhanikov >Assignee: Denis Mekhanikov >Priority: Major > Fix For: 2.8 > > Attachments: BinaryMetadataRegistrationInsideEntryProcessorTest.java > > > Please find attached test class with a reproducer. > The exception was introduced in IGNITE-8926. Metadata registration should be > retried when this exception is thrown, but it doesn't happen. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9431) Documentation for zk paths used by ZookeeperDiscovery.
[ https://issues.apache.org/jira/browse/IGNITE-9431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stanilovsky Evgeny reassigned IGNITE-9431: -- Assignee: (was: Stanilovsky Evgeny) > Documentation for zk paths used by ZookeeperDiscovery. > -- > > Key: IGNITE-9431 > URL: https://issues.apache.org/jira/browse/IGNITE-9431 > Project: Ignite > Issue Type: Improvement > Components: documentation >Affects Versions: 2.6 >Reporter: Stanilovsky Evgeny >Priority: Major > > I found that under /apacheIgnite zk directory, there are also: > /jd, /ce, /cp, /ca and some other dirs, from source i found that they take > place from : org.apache.ignite.spi.discovery.zk.internal.ZkIgnitePaths. Plz > document this paths purpose. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9431) Documentation for zk paths used by ZookeeperDiscovery.
[ https://issues.apache.org/jira/browse/IGNITE-9431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16638601#comment-16638601 ] Stanilovsky Evgeny commented on IGNITE-9431: [~Artem Budnikov] this ticket has been filled due to users request. [~dpavlov] are you ok with Artem ? > Documentation for zk paths used by ZookeeperDiscovery. > -- > > Key: IGNITE-9431 > URL: https://issues.apache.org/jira/browse/IGNITE-9431 > Project: Ignite > Issue Type: Improvement > Components: documentation >Affects Versions: 2.6 >Reporter: Stanilovsky Evgeny >Assignee: Stanilovsky Evgeny >Priority: Major > > I found that under /apacheIgnite zk directory, there are also: > /jd, /ce, /cp, /ca and some other dirs, from source i found that they take > place from : org.apache.ignite.spi.discovery.zk.internal.ZkIgnitePaths. Plz > document this paths purpose. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9744) Fix SYSTEM_WORKER_TERMINATION detection in general case
[
https://issues.apache.org/jira/browse/IGNITE-9744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16638546#comment-16638546
]
Ignite TC Bot commented on IGNITE-9744:
---
{panel:title=Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Hadoop{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=1991789]]
* HadoopExecutorServiceTest.testShutdown (last started)
{color:#d04437}MVCC Cache{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=1991869]]
* CacheMvccTransactionsTest.testPutAllGetAll_ClientServer_Backups1_Restart_Scan
(last started)
{color:#d04437}JDBC Driver{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=1991798]]
*
JdbcThinTransactionsServerNoAutoCommitComplexSelfTest.testRepeatableReadWithConcurrentCacheReplace
(last started)
{color:#d04437}Queries 1{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=1991855]]
* GridOrderedMessageCancelSelfTest.testTaskException (last started)
{color:#d04437}Cache 7 (With Persistence){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=1991857]]
* IgniteCacheTestSuite7: WalModeChangeAdvancedSelfTest.testClientReconnect -
0,0% fails in last 100 master runs.
{color:#d04437}Cache 2{color} [[tests
3|https://ci.ignite.apache.org/viewLog.html?buildId=1991850]]
* IgniteCacheTestSuite2:
CacheTxLoadingConcurrentGridStartSelfTestAllowOverwrite.testLoadCacheWithDataStreamerSequentialClientWithConfig
- 2,0% fails in last 100 master runs.
{color:#d04437}Cache 8{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=1991862]]
* IgniteCacheTestSuite8: GridCacheRebalancingAsyncSelfTest.testLoadRebalancing
- 1,0% fails in last 100 master runs.
* IgniteCacheTestSuite8:
GridCacheRebalancingAsyncSelfTest.testSimpleRebalancing - 1,0% fails in last
100 master runs.
{panel}
[TeamCity Run
All|http://ci.ignite.apache.org/viewLog.html?buildId=1991872buildTypeId=IgniteTests24Java8_RunAll]
> Fix SYSTEM_WORKER_TERMINATION detection in general case
> ---
>
> Key: IGNITE-9744
> URL: https://issues.apache.org/jira/browse/IGNITE-9744
> Project: Ignite
> Issue Type: Bug
>Reporter: Andrey Kuznetsov
>Assignee: Andrey Kuznetsov
>Priority: Major
> Fix For: 2.7
>
>
> All existing critical workers handle unintended termination individually.
> This should be done for arbitrtary critical worker as well. There is a test
> to check this situation, {{SystemWorkersTerminationTest.testTermination}},
> but now it passes in fact due to {{SYSTEM_WORKER_BLOCKED}} instead of
> {{SYSTEM_WORKER_TERMINATION}}, and this should be fixed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9744) Fix SYSTEM_WORKER_TERMINATION detection in general case
[
https://issues.apache.org/jira/browse/IGNITE-9744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16638548#comment-16638548
]
Ivan Rakov commented on IGNITE-9744:
Changes look good to me.
TC Bot reports about possible blockers, but all failures seem unrelated to the
fix.
> Fix SYSTEM_WORKER_TERMINATION detection in general case
> ---
>
> Key: IGNITE-9744
> URL: https://issues.apache.org/jira/browse/IGNITE-9744
> Project: Ignite
> Issue Type: Bug
>Reporter: Andrey Kuznetsov
>Assignee: Andrey Kuznetsov
>Priority: Major
> Fix For: 2.7
>
>
> All existing critical workers handle unintended termination individually.
> This should be done for arbitrtary critical worker as well. There is a test
> to check this situation, {{SystemWorkersTerminationTest.testTermination}},
> but now it passes in fact due to {{SYSTEM_WORKER_BLOCKED}} instead of
> {{SYSTEM_WORKER_TERMINATION}}, and this should be fixed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9719) Extra rebalanceThreadPoolSize check on client node.
[ https://issues.apache.org/jira/browse/IGNITE-9719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16638481#comment-16638481 ] Dmitriy Pavlov commented on IGNITE-9719: [~zstan] could you please take a look? > Extra rebalanceThreadPoolSize check on client node. > --- > > Key: IGNITE-9719 > URL: https://issues.apache.org/jira/browse/IGNITE-9719 > Project: Ignite > Issue Type: Improvement > Components: clients >Affects Versions: 2.6 >Reporter: Stanilovsky Evgeny >Assignee: Luchnikov Alexander >Priority: Minor > Fix For: 2.8 > > > No need to check rebalance thread pool size on client side in > IgniteKernal#ackRebalanceConfiguration method. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9282) [ML] Add Naive Bayes classifier
[ https://issues.apache.org/jira/browse/IGNITE-9282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16638474#comment-16638474 ] Dmitriy Pavlov commented on IGNITE-9282: [~chief] could you please take a look? > [ML] Add Naive Bayes classifier > --- > > Key: IGNITE-9282 > URL: https://issues.apache.org/jira/browse/IGNITE-9282 > Project: Ignite > Issue Type: Sub-task > Components: ml >Reporter: Aleksey Zinoviev >Assignee: Ravil Galeyev >Priority: Major > Labels: new-feature > Fix For: 2.8 > > > Naive Bayes classifiers are a family of simple probabilistic classifiers > based on applying Bayes' theorem with strong (naive) independence assumptions > between the features. > So we want to add this algorithm to Apache Ignite ML module. > Ideally, implementation should support both multinomial naive Bayes and > Bernoulli naive Bayes. > Requirements for successful PR: > # PartitionedDataset usage > # Trainer-Model paradigm support > # Tests for Model and for Trainer (and other stuff) > # Example of usage with small, but famous dataset like IRIS, Titanic or > House Prices > # Javadocs/codestyle according guidelines > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9769) IgniteCacheAtomicProtocolTest.testPutReaderUpdate1 is flaky
[
https://issues.apache.org/jira/browse/IGNITE-9769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-9769:
---
Labels: MakeTeamcityGreenAgain (was: )
> IgniteCacheAtomicProtocolTest.testPutReaderUpdate1 is flaky
> ---
>
> Key: IGNITE-9769
> URL: https://issues.apache.org/jira/browse/IGNITE-9769
> Project: Ignite
> Issue Type: Task
>Reporter: Ryabov Dmitrii
>Assignee: Ryabov Dmitrii
>Priority: Trivial
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
>
> {{IgniteCacheAtomicProtocolTest.testPutReaderUpdate1}} and
> {{IgniteCacheAtomicProtocolTest.testPutReaderUpdate2}} are flaky.
> In the {{#readerUpdateDhtFails}} method we blocks
> {{GridDhtAtomicNearResponse}} messages and do put operation. Put should hangs
> always, but sometimes it doesn't.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IGNITE-9795) Web Agent: Improve information message in case REST command failed on cluster
[
https://issues.apache.org/jira/browse/IGNITE-9795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Kuznetsov resolved IGNITE-9795.
--
Resolution: Fixed
> Web Agent: Improve information message in case REST command failed on cluster
> -
>
> Key: IGNITE-9795
> URL: https://issues.apache.org/jira/browse/IGNITE-9795
> Project: Ignite
> Issue Type: Bug
> Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
>Priority: Major
> Fix For: 2.8
>
>
> In current implementation we print `res.message()`, but I found that
> Responce.toString() method contains much more information:
> {code}
> "Response\{protocol=" + this.protocol + ", code=" + this.code + ", message="
> + this.message + ", url=" + this.request.url() + '}';
> {code}
>
> lets print it instead of just message, it will help in case of finding the
> reasons of failures.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (IGNITE-9795) Web Agent: Improve information message in case REST command failed on cluster
[
https://issues.apache.org/jira/browse/IGNITE-9795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Kuznetsov closed IGNITE-9795.
> Web Agent: Improve information message in case REST command failed on cluster
> -
>
> Key: IGNITE-9795
> URL: https://issues.apache.org/jira/browse/IGNITE-9795
> Project: Ignite
> Issue Type: Bug
> Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
>Priority: Major
> Fix For: 2.8
>
>
> In current implementation we print `res.message()`, but I found that
> Responce.toString() method contains much more information:
> {code}
> "Response\{protocol=" + this.protocol + ", code=" + this.code + ", message="
> + this.message + ", url=" + this.request.url() + '}';
> {code}
>
> lets print it instead of just message, it will help in case of finding the
> reasons of failures.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9795) Web Agent: Improve information message in case REST command failed on cluster
[
https://issues.apache.org/jira/browse/IGNITE-9795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Kuznetsov updated IGNITE-9795:
-
Description:
In current implementation we print `res.message()`, but I found that
Responce.toString() method contains much more information:
{code}
"Response\{protocol=" + this.protocol + ", code=" + this.code + ", message=" +
this.message + ", url=" + this.request.url() + '}';
{code}
lets print it instead of just message, it will help in case of finding the
reasons of failures.
was:
In current implementation we print `res.message()`, but I found that
Responce.toString() method contains much more information:
{code}
"Response\{protocol=" + this.protocol + ", code=" + this.code + ", message=" +
this.message + ", url=" + this.request.url() + '}';
}
{code}
lets print it instead of just message, it will help in case of finding the
reasons of failures.
> Web Agent: Improve information message in case REST command failed on cluster
> -
>
> Key: IGNITE-9795
> URL: https://issues.apache.org/jira/browse/IGNITE-9795
> Project: Ignite
> Issue Type: Bug
> Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
>Priority: Major
> Fix For: 2.8
>
>
> In current implementation we print `res.message()`, but I found that
> Responce.toString() method contains much more information:
> {code}
> "Response\{protocol=" + this.protocol + ", code=" + this.code + ", message="
> + this.message + ", url=" + this.request.url() + '}';
> {code}
>
> lets print it instead of just message, it will help in case of finding the
> reasons of failures.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8766) TcpDiscoverySpi: discovery threads naming
[ https://issues.apache.org/jira/browse/IGNITE-8766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16638380#comment-16638380 ] Dmitry Karachentsev commented on IGNITE-8766: - [~NIzhikov] it's just waiting to be merged to master as I can see. > TcpDiscoverySpi: discovery threads naming > - > > Key: IGNITE-8766 > URL: https://issues.apache.org/jira/browse/IGNITE-8766 > Project: Ignite > Issue Type: Improvement > Components: general >Reporter: Sergey Chugunov >Assignee: Dmitry Karachentsev >Priority: Major > Labels: discovery > Fix For: 2.8 > > > Including information about next/prev nodes into names of discovery-related > threads could be very helpful when investigating situations of network > glitches. > tcp-disco-sock-reader and tcp-disco-msg-worker threads must include such > information in their names. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9795) Web Agent: Improve information message in case REST command failed on cluster
[
https://issues.apache.org/jira/browse/IGNITE-9795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Kuznetsov updated IGNITE-9795:
-
Ignite Flags: (was: Docs Required)
> Web Agent: Improve information message in case REST command failed on cluster
> -
>
> Key: IGNITE-9795
> URL: https://issues.apache.org/jira/browse/IGNITE-9795
> Project: Ignite
> Issue Type: Bug
> Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
>Priority: Major
> Fix For: 2.8
>
>
> In current implementation we print `res.message()`, but I found that
> Responce.toString() method contains much more information:
> {code}
> "Response\{protocol=" + this.protocol + ", code=" + this.code + ", message="
> + this.message + ", url=" + this.request.url() + '}';
> }
> {code}
>
> lets print it instead of just message, it will help in case of finding the
> reasons of failures.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9312) Remove unnecessary @SuppressWarnings annotation
[
https://issues.apache.org/jira/browse/IGNITE-9312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16638353#comment-16638353
]
Ignite TC Bot commented on IGNITE-9312:
---
{panel:title=Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}SPI{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=1987858]]
* IgniteSpiTestSuite:
TcpClientDiscoverySpiFailureTimeoutSelfTest.testJoinErrorMissedAddFinishedMessage2
- 0,0% fails in last 100 master runs.
{color:#d04437}Continuous Query 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=1987832]]
* IgniteCacheQuerySelfTestSuite3:
CacheContinuousQueryOrderingEventTest.testAtomicOnheapTwoBackupAsyncFullSync -
0,0% fails in last 100 master runs.
{color:#d04437}PDS 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=1987880]]
* IgnitePdsTestSuite: PagesWriteThrottleSmokeTest.testThrottle - 0,0% fails in
last 100 master runs.
{color:#d04437}PDS 4{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=1987885]]
* IgnitePdsTransactionsHangTest.testTransactionsDontHang (last started)
{color:#d04437}PDS 3{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=1987884]]
* IgnitePdsContinuousRestartTest.testRebalancingDuringLoad_8000_8000_8_1 (last
started)
{color:#d04437}PDS 2{color} [[tests 0 TIMEOUT , Exit Code , JAVA_LEVEL_DEADLOCK
|https://ci.ignite.apache.org/viewLog.html?buildId=1987881]]
* IgniteWalFlushLogOnlySelfTest.testFailWhileStart (last started)
{panel}
[TeamCity Run
All|http://ci.ignite.apache.org/viewLog.html?buildId=1987924buildTypeId=IgniteTests24Java8_RunAll]
> Remove unnecessary @SuppressWarnings annotation
> ---
>
> Key: IGNITE-9312
> URL: https://issues.apache.org/jira/browse/IGNITE-9312
> Project: Ignite
> Issue Type: Bug
>Reporter: Maxim Muzafarov
>Assignee: PetrovMikhail
>Priority: Minor
> Labels: inspections
>
> New `Code Inspections` profile can be found
> \idea\ignite_inspections.xml.
> We will need to fix all methods with unnecessary {{@SuppressWarnings}}
> annotation regarding this inscpetion profile.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9792) Setting system property IGNITE_MBEANS_DISABLED to true lead to NPE.
[
https://issues.apache.org/jira/browse/IGNITE-9792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Kuznetsov updated IGNITE-9792:
-
Ignite Flags: (was: Docs Required)
> Setting system property IGNITE_MBEANS_DISABLED to true lead to NPE.
> ---
>
> Key: IGNITE-9792
> URL: https://issues.apache.org/jira/browse/IGNITE-9792
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
>Priority: Critical
> Fix For: 2.7
>
>
> Javadocs for IGNITE_MBEANS_DISABLED: "This may be helpful if MBeans are not
> allowed e.g. for security reasons."
> So I set in code:
> {code}
> System.setProperty(IgniteSystemProperties.IGNITE_MBEANS_DISABLED, "true")
> {code}
>
> And on node start node failed with NPE:
> {code}
> Caused by: class org.apache.ignite.IgniteCheckedException: Unexpected
> exception when starting grid.
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2079)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1728)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1156)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:676)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:601)
> at org.apache.ignite.Ignition.start(Ignition.java:323)
> ... 3 more
> Caused by: java.lang.NullPointerException: Ouch! Argument cannot be null:
> cfg.getMBeanServer()
> at
> org.apache.ignite.internal.util.GridArgumentCheck.notNull(GridArgumentCheck.java:48)
> at
> org.apache.ignite.internal.IgniteKernal.validateCommon(IgniteKernal.java:1355)
> at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:833)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2033)
> ... 8 more
> {code}
>
> The fix is trivial: in org.apache.ignite.internal.IgniteKernal#validateCommon
> {code}
> if (!U.IGNITE_MBEANS_DISABLED) // <<< The fix
> A.notNull(cfg.getMBeanServer(), "cfg.getMBeanServer()");
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9312) Remove unnecessary @SuppressWarnings annotation
[
https://issues.apache.org/jira/browse/IGNITE-9312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16638359#comment-16638359
]
PetrovMikhail commented on IGNITE-9312:
---
{color:#d04437}Platform .NET (Core Linux){color} was reruned. All failed tests
passed locally.
> Remove unnecessary @SuppressWarnings annotation
> ---
>
> Key: IGNITE-9312
> URL: https://issues.apache.org/jira/browse/IGNITE-9312
> Project: Ignite
> Issue Type: Bug
>Reporter: Maxim Muzafarov
>Assignee: PetrovMikhail
>Priority: Minor
> Labels: inspections
>
> New `Code Inspections` profile can be found
> \idea\ignite_inspections.xml.
> We will need to fix all methods with unnecessary {{@SuppressWarnings}}
> annotation regarding this inscpetion profile.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9794) Registration of a binary type with POJO field under topology lock leads to UnregisteredBinaryTypeException
Denis Mekhanikov created IGNITE-9794: Summary: Registration of a binary type with POJO field under topology lock leads to UnregisteredBinaryTypeException Key: IGNITE-9794 URL: https://issues.apache.org/jira/browse/IGNITE-9794 Project: Ignite Issue Type: Bug Affects Versions: 2.6 Reporter: Denis Mekhanikov Assignee: Denis Mekhanikov Fix For: 2.8 Attachments: BinaryMetadataRegistrationInsideEntryProcessorTest.java Please find attached test class with a reproducer. The exception was introduced in IGNITE-8926. Metadata registration should be retried when this exception is thrown, but it doesn't happen. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9795) Web Agent: Improve information message in case REST command failed on cluster
Alexey Kuznetsov created IGNITE-9795:
Summary: Web Agent: Improve information message in case REST
command failed on cluster
Key: IGNITE-9795
URL: https://issues.apache.org/jira/browse/IGNITE-9795
Project: Ignite
Issue Type: Bug
Components: wizards
Reporter: Alexey Kuznetsov
Assignee: Alexey Kuznetsov
Fix For: 2.8
In current implementation we print `res.message()`, but I found that
Responce.toString() method contains much more information:
{code}
"Response\{protocol=" + this.protocol + ", code=" + this.code + ", message=" +
this.message + ", url=" + this.request.url() + '}';
}
{code}
lets print it instead of just message, it will help in case of finding the
reasons of failures.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9794) Registration of a binary type with POJO field under topology lock leads to UnregisteredBinaryTypeException
[ https://issues.apache.org/jira/browse/IGNITE-9794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16638348#comment-16638348 ] ASF GitHub Bot commented on IGNITE-9794: GitHub user dmekhanikov opened a pull request: https://github.com/apache/ignite/pull/4916 IGNITE-9794 Handle UnregisteredBinaryTypeException on metadata registration under topology lock. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite IGNITE-9794 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4916.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4916 commit b49ddc9600c6483e4d00d75018eb5839e076e0bf Author: Denis Mekhanikov Date: 2018-10-04T14:59:02Z IGNITE-9794 Handle UnregisteredBinaryTypeException on metadata registration under topology lock. > Registration of a binary type with POJO field under topology lock leads to > UnregisteredBinaryTypeException > -- > > Key: IGNITE-9794 > URL: https://issues.apache.org/jira/browse/IGNITE-9794 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.6 >Reporter: Denis Mekhanikov >Assignee: Denis Mekhanikov >Priority: Major > Fix For: 2.8 > > Attachments: BinaryMetadataRegistrationInsideEntryProcessorTest.java > > > Please find attached test class with a reproducer. > The exception was introduced in IGNITE-8926. Metadata registration should be > retried when this exception is thrown, but it doesn't happen. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-9726) GridCacheAbstractFailoverSelfTest may lock all suite on put/remove cache operations
[ https://issues.apache.org/jira/browse/IGNITE-9726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16638327#comment-16638327 ] Ryabov Dmitrii edited comment on IGNITE-9726 at 10/4/18 2:54 PM: - Hi, Alexey, If this test can hangs rarely then we need to do mass run for this test. Please, create separate PR with suite filled with at least 100 instances of this test and run it on TeamCity. was (Author: somefire): Hi, Alexey, If this method can hangs then we need to do mass run for this test. Please, create separate PR with suite filled with at least 100 instances of this test and run it on TeamCity. > GridCacheAbstractFailoverSelfTest may lock all suite on put/remove cache > operations > --- > > Key: IGNITE-9726 > URL: https://issues.apache.org/jira/browse/IGNITE-9726 > Project: Ignite > Issue Type: Bug >Reporter: Alexey Platonov >Assignee: Alexey Platonov >Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.7 > > > Example of timeouts: > [https://ci.ignite.apache.org/viewLog.html?buildId=1944646=IgniteTests24Java8_CacheFailover2=buildLog] > method testConstantTopologyChange can misses interrupt from test runner and > lock suite > see that after thread dump put/remove cache operations will continue in test > testOptimisticSerializableTxConstantTopologyChange -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9793) Deactivation, segmentation of one node, activation may lead to hang activation forever
[
https://issues.apache.org/jira/browse/IGNITE-9793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Voronkin updated IGNITE-9793:
---
Description:
There is topology with ring of nodes:
*665(coordinator) > 601 > 724 > 910 > 655 > ...* deactivated
*665(coordinator)* *> 601 > {color:#ff}724{color} > 910 > 655 > ...*
node failed
*665(coordinator) > 601 > 910 > 655 > ...* **activated
During activation node 910 haven't received StateChangedMessage, hovever 655
and all subsequent nodes received and responded to coordinator.
So coordinator expects to have 154 messages but received only 153 that is why
activation hangs.
Details bellow:
*Coordinator deactivated:*
2018-09-24 15:09:01.609 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=e002e011-8d1c-4353-a0f3-b71264c5b0f4, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
2018-09-24 15:09:01.620
[DEBUG][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.l.ExchangeLatchManager]
Server latch is created [latch=CompletableLatchUid
{id='exchange', topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]}
, participantsSize=160]
2018-09-24 15:09:01.621 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%]
*nodes 601, 724, 910, 655 were deactivated:*
2018-09-24 15:09:01.609 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=e002e011-8d1c-4353-a0f3-b71264c5b0f4, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
2018-09-24 15:09:03.328 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=22a58223-47b5-43c2-897b-e70e8e50edf7, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
2018-09-24 15:09:03.334 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=973eb8ce-3b8c-463d-a6ab-00ac66d93f13, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
2018-09-24 15:09:03.332 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=a904bac4-aaed-4f69-90f3-c13bc4d331d1, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
*Spi on coordinator received node 724 failed message:*
2018-09-24 15:17:00.220 [WARN
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
Node FAILED: TcpDiscoveryNode [id=a904bac4-aaed-4f69-90f3-c13bc4d331d1,
addrs=ArrayList [10.116.206.98], sockAddrs=HashSet
[grid724.domain/10.116.206.98:47500], discPort=47500, order=110, intOrder=110,
lastExchangeTime=1537528210290, loc=false, ver=2.5.1#20180906-sha1:ebde6c79,
isClient=false]
2018-09-24 15:17:00.221 [INFO
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
Topology snapshot [ver=187, servers=156, clients=0, CPUs=8736,
offheap=19.0GB, heap=4800.0GB]
2018-09-24 15:17:00.221 [INFO
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
^-- Node [id=E002E011-8D1C-4353-A0F3-B71264C5B0F4, clusterState=INACTIVE]
2018-09-24 15:17:00.221 [INFO
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
^-- Baseline [id=6, size=160, online=156, offline=4]
*topology rolled to version 187, then another node 931 failed:*
2018-09-24 15:17:00.466 [WARN
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
Node FAILED: TcpDiscoveryNode [id=83536b6d-8aa3-4c85-b3da-5e577ae37ac6,
addrs=ArrayList [10.116.215.3], sockAddrs=HashSet
[grid931.domain/10.116.215.3:47500], discPort=47500, order=73, intOrder=73,
lastExchangeTime=1537528186599, loc=false, ver=2.5.1#20180906-sha1:ebde6c79,
isClient=false]
2018-09-24 15:17:00.467 [INFO
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
Topology snapshot [ver=188, servers=155, clients=0, CPUs=8680,
offheap=19.0GB, heap=4800.0GB]
2018-09-24 15:17:00.467 [INFO
[jira] [Commented] (IGNITE-9726) GridCacheAbstractFailoverSelfTest may lock all suite on put/remove cache operations
[ https://issues.apache.org/jira/browse/IGNITE-9726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16638327#comment-16638327 ] Ryabov Dmitrii commented on IGNITE-9726: Hi, Alexey, If this method can hangs then we need to do mass run for this test. Please, create separate PR with suite filled with at least 100 instances of this test and run it on TeamCity. > GridCacheAbstractFailoverSelfTest may lock all suite on put/remove cache > operations > --- > > Key: IGNITE-9726 > URL: https://issues.apache.org/jira/browse/IGNITE-9726 > Project: Ignite > Issue Type: Bug >Reporter: Alexey Platonov >Assignee: Alexey Platonov >Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.7 > > > Example of timeouts: > [https://ci.ignite.apache.org/viewLog.html?buildId=1944646=IgniteTests24Java8_CacheFailover2=buildLog] > method testConstantTopologyChange can misses interrupt from test runner and > lock suite > see that after thread dump put/remove cache operations will continue in test > testOptimisticSerializableTxConstantTopologyChange -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-5967) Flaky fail in Ignite Java Client: RedisProtocolStringSelfTest.testGetSet
[ https://issues.apache.org/jira/browse/IGNITE-5967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita reassigned IGNITE-5967: --- Assignee: Amelchev Nikita > Flaky fail in Ignite Java Client: RedisProtocolStringSelfTest.testGetSet > - > > Key: IGNITE-5967 > URL: https://issues.apache.org/jira/browse/IGNITE-5967 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.1 >Reporter: Dmitriy Govorukhin >Assignee: Amelchev Nikita >Priority: Major > Labels: MakeTeamcityGreenAgain > > RedisProtocolStringSelfTest.testGetSet > redis.clients.jedis.exceptions.JedisConnectionException: Unexpected end of > stream. > at > redis.clients.util.RedisInputStream.ensureFill(RedisInputStream.java:199) > at redis.clients.util.RedisInputStream.readByte(RedisInputStream.java:40) > at redis.clients.jedis.Protocol.process(Protocol.java:151) > at redis.clients.jedis.Protocol.read(Protocol.java:215) > at > redis.clients.jedis.Connection.readProtocolWithCheckingBroken(Connection.java:340) > at redis.clients.jedis.Connection.getBinaryBulkReply(Connection.java:259) > at redis.clients.jedis.Connection.getBulkReply(Connection.java:248) > at redis.clients.jedis.Jedis.get(Jedis.java:153) > at > org.apache.ignite.internal.processors.rest.protocols.tcp.redis.RedisProtocolStringSelfTest.testGetSet(RedisProtocolStringSelfTest.java:62) > --- Stdout: --- > [2017-08-07 06:28:44,379][INFO ][main][root] >>> Starting test: > RedisProtocolStringSelfTest#testGetSet <<< > [2017-08-07 06:28:52,390][INFO ][main][root] >>> Stopping test: > RedisProtocolStringSelfTest#testGetSet in 8010 ms <<< > --- Stderr: --- > [2017-08-07 06:28:52,389][ERROR][main][root] Test failed. > redis.clients.jedis.exceptions.JedisConnectionException: Unexpected end of > stream. > at > redis.clients.util.RedisInputStream.ensureFill(RedisInputStream.java:199) > at redis.clients.util.RedisInputStream.readByte(RedisInputStream.java:40) > at redis.clients.jedis.Protocol.process(Protocol.java:151) > at redis.clients.jedis.Protocol.read(Protocol.java:215) > at > redis.clients.jedis.Connection.readProtocolWithCheckingBroken(Connection.java:340) > at redis.clients.jedis.Connection.getBinaryBulkReply(Connection.java:259) > at redis.clients.jedis.Connection.getBulkReply(Connection.java:248) > at redis.clients.jedis.Jedis.get(Jedis.java:153) > at > org.apache.ignite.internal.processors.rest.protocols.tcp.redis.RedisProtocolStringSelfTest.testGetSet(RedisProtocolStringSelfTest.java:62) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at junit.framework.TestCase.runTest(TestCase.java:176) > at > org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000) > at > org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132) > at > org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915) > at java.lang.Thread.run(Thread.java:745) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9792) Setting system property IGNITE_MBEANS_DISABLED to true lead to NPE.
[
https://issues.apache.org/jira/browse/IGNITE-9792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16638319#comment-16638319
]
Dmitriy Pavlov commented on IGNITE-9792:
Change looks good to me, I've triggered tests, once it completes JIRA ticket
IGNITE-9792 will be notified.
> Setting system property IGNITE_MBEANS_DISABLED to true lead to NPE.
> ---
>
> Key: IGNITE-9792
> URL: https://issues.apache.org/jira/browse/IGNITE-9792
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
>Priority: Critical
> Fix For: 2.7
>
>
> Javadocs for IGNITE_MBEANS_DISABLED: "This may be helpful if MBeans are not
> allowed e.g. for security reasons."
> So I set in code:
> {code}
> System.setProperty(IgniteSystemProperties.IGNITE_MBEANS_DISABLED, "true")
> {code}
>
> And on node start node failed with NPE:
> {code}
> Caused by: class org.apache.ignite.IgniteCheckedException: Unexpected
> exception when starting grid.
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2079)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1728)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1156)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:676)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:601)
> at org.apache.ignite.Ignition.start(Ignition.java:323)
> ... 3 more
> Caused by: java.lang.NullPointerException: Ouch! Argument cannot be null:
> cfg.getMBeanServer()
> at
> org.apache.ignite.internal.util.GridArgumentCheck.notNull(GridArgumentCheck.java:48)
> at
> org.apache.ignite.internal.IgniteKernal.validateCommon(IgniteKernal.java:1355)
> at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:833)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2033)
> ... 8 more
> {code}
>
> The fix is trivial: in org.apache.ignite.internal.IgniteKernal#validateCommon
> {code}
> if (!U.IGNITE_MBEANS_DISABLED) // <<< The fix
> A.notNull(cfg.getMBeanServer(), "cfg.getMBeanServer()");
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9728) JDK11: IGNITE_HOME setup for tests, hibernate modules maven dependencies
[
https://issues.apache.org/jira/browse/IGNITE-9728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-9728:
-
Summary: JDK11: IGNITE_HOME setup for tests, hibernate modules maven
dependencies (was: JDK11: IGNITE_HOME setup for tests )
> JDK11: IGNITE_HOME setup for tests, hibernate modules maven dependencies
>
>
> Key: IGNITE-9728
> URL: https://issues.apache.org/jira/browse/IGNITE-9728
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.6
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
>Priority: Major
> Labels: jdk11, test
> Fix For: 2.7
>
>
> A lot of tests fail with {{ClassNotFoundException}} because external class
> loader set up incorrect.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9719) Extra rebalanceThreadPoolSize check on client node.
[ https://issues.apache.org/jira/browse/IGNITE-9719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stanilovsky Evgeny updated IGNITE-9719: --- Ignite Flags: (was: Docs Required) Issue Type: Improvement (was: Bug) > Extra rebalanceThreadPoolSize check on client node. > --- > > Key: IGNITE-9719 > URL: https://issues.apache.org/jira/browse/IGNITE-9719 > Project: Ignite > Issue Type: Improvement > Components: clients >Affects Versions: 2.6 >Reporter: Stanilovsky Evgeny >Assignee: Luchnikov Alexander >Priority: Minor > Fix For: 2.8 > > > No need to check rebalance thread pool size on client side in > IgniteKernal#ackRebalanceConfiguration method. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9792) Setting system property IGNITE_MBEANS_DISABLED to true lead to NPE.
[
https://issues.apache.org/jira/browse/IGNITE-9792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16638291#comment-16638291
]
ASF GitHub Bot commented on IGNITE-9792:
GitHub user akuznetsov-gridgain opened a pull request:
https://github.com/apache/ignite/pull/4915
IGNITE-9792 Fixed assert in case if IGNITE_MBEANS_DISABLED is true. F…
…ixed tests.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apache/ignite ignite-9792
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4915.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #4915
commit e66c9850ce1ba5e8c2c028f837aff646577beebe
Author: Alexey Kuznetsov
Date: 2018-10-04T11:19:02Z
IGNITE-9792 Fixed assert in case if IGNITE_MBEANS_DISABLED is true. Fixed
tests.
> Setting system property IGNITE_MBEANS_DISABLED to true lead to NPE.
> ---
>
> Key: IGNITE-9792
> URL: https://issues.apache.org/jira/browse/IGNITE-9792
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
>Priority: Critical
> Fix For: 2.7
>
>
> Javadocs for IGNITE_MBEANS_DISABLED: "This may be helpful if MBeans are not
> allowed e.g. for security reasons."
> So I set in code:
> {code}
> System.setProperty(IgniteSystemProperties.IGNITE_MBEANS_DISABLED, "true")
> {code}
>
> And on node start node failed with NPE:
> {code}
> Caused by: class org.apache.ignite.IgniteCheckedException: Unexpected
> exception when starting grid.
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2079)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1728)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1156)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:676)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:601)
> at org.apache.ignite.Ignition.start(Ignition.java:323)
> ... 3 more
> Caused by: java.lang.NullPointerException: Ouch! Argument cannot be null:
> cfg.getMBeanServer()
> at
> org.apache.ignite.internal.util.GridArgumentCheck.notNull(GridArgumentCheck.java:48)
> at
> org.apache.ignite.internal.IgniteKernal.validateCommon(IgniteKernal.java:1355)
> at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:833)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2033)
> ... 8 more
> {code}
>
> The fix is trivial: in org.apache.ignite.internal.IgniteKernal#validateCommon
> {code}
> if (!U.IGNITE_MBEANS_DISABLED) // <<< The fix
> A.notNull(cfg.getMBeanServer(), "cfg.getMBeanServer()");
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (IGNITE-9298) control.sh does not support SSL (org.apache.ignite.internal.commandline.CommandHandler)
[
https://issues.apache.org/jira/browse/IGNITE-9298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Sherstobitov updated IGNITE-9298:
Comment: was deleted
(was: We've increased chaos in args naming:
{code:java}
/** */
protected static final String CMD_PING_TIMEOUT = "--ping-timeout";
/** */
private static final String CMD_DUMP = "--dump";
/** */
private static final String CMD_SKIP_ZEROS = "--skipZeros";
// SSL configuration section
/** */
protected static final String CMD_SSL_ENABLED = "--ssl_enabled";
/** */
protected static final String CMD_SSL_PROTOCOL = "--ssl_protocol";{code}
Here is 3 different types of split word: with dash, with capital letter and
with '_')
> control.sh does not support SSL
> (org.apache.ignite.internal.commandline.CommandHandler)
> ---
>
> Key: IGNITE-9298
> URL: https://issues.apache.org/jira/browse/IGNITE-9298
> Project: Ignite
> Issue Type: Bug
> Components: clients
>Affects Versions: 2.6
>Reporter: Paul Anderson
>Assignee: Paul Anderson
>Priority: Major
> Fix For: 2.7
>
> Attachments: Arguments.patch, CommandHandler.patch
>
>
> We required SSL on the connector port and to use control.sh to work with the
> baseline configuration.
> This morning I added support, see attached patches against 2.6.0 for
> org/apache/ignite/internal/commandline/CommandHandler.java
> org/apache/ignite/internal/commandline/Arguments.java
> No tests, no docs.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9298) control.sh does not support SSL (org.apache.ignite.internal.commandline.CommandHandler)
[
https://issues.apache.org/jira/browse/IGNITE-9298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16638287#comment-16638287
]
Dmitry Sherstobitov commented on IGNITE-9298:
-
We've increased chaos in args naming:
{code:java}
/** */
protected static final String CMD_PING_TIMEOUT = "--ping-timeout";
/** */
private static final String CMD_DUMP = "--dump";
/** */
private static final String CMD_SKIP_ZEROS = "--skipZeros";
// SSL configuration section
/** */
protected static final String CMD_SSL_ENABLED = "--ssl_enabled";
/** */
protected static final String CMD_SSL_PROTOCOL = "--ssl_protocol";{code}
Here is 3 different types of split word: with dash, with capital letter and
with '_'
> control.sh does not support SSL
> (org.apache.ignite.internal.commandline.CommandHandler)
> ---
>
> Key: IGNITE-9298
> URL: https://issues.apache.org/jira/browse/IGNITE-9298
> Project: Ignite
> Issue Type: Bug
> Components: clients
>Affects Versions: 2.6
>Reporter: Paul Anderson
>Assignee: Paul Anderson
>Priority: Major
> Fix For: 2.7
>
> Attachments: Arguments.patch, CommandHandler.patch
>
>
> We required SSL on the connector port and to use control.sh to work with the
> baseline configuration.
> This morning I added support, see attached patches against 2.6.0 for
> org/apache/ignite/internal/commandline/CommandHandler.java
> org/apache/ignite/internal/commandline/Arguments.java
> No tests, no docs.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9793) Deactivation, segmentation of one node, activation may lead to hang activation forever
[
https://issues.apache.org/jira/browse/IGNITE-9793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Voronkin updated IGNITE-9793:
---
Description:
There is topology with ring of nodes:
*665(coordinator) > 601 > 724 > 910 > 655 > ...* deactivated
*665(coordinator)* *> 601 > {color:#ff}724{color} > 910 > 655 > ...*
node failed
*665(coordinator) > 601 > 910 > 655 > ...* **activated
During activation node 910 haven't received StateChangedMessage, hovever 655
and all subsequent nodes received and responded to coordinator.
So coordinator expects to have 154 messages but received only 153 that is why
activation hangs.
Details bellow:
*Coordinator deactivated:*
2018-09-24 15:09:01.609 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=e002e011-8d1c-4353-a0f3-b71264c5b0f4, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
2018-09-24 15:09:01.620
[DEBUG][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.l.ExchangeLatchManager]
Server latch is created [latch=CompletableLatchUid
{id='exchange', topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]}
, participantsSize=160]
2018-09-24 15:09:01.621 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%]
*nodes 601, 724, 910, 655 were deactivated:*
2018-09-24 15:09:01.609 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=e002e011-8d1c-4353-a0f3-b71264c5b0f4, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
2018-09-24 15:09:03.328 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=22a58223-47b5-43c2-897b-e70e8e50edf7, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
2018-09-24 15:09:03.334 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=973eb8ce-3b8c-463d-a6ab-00ac66d93f13, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
2018-09-24 15:09:03.332 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=a904bac4-aaed-4f69-90f3-c13bc4d331d1, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
*Spi on coordinator received node 724 failed message:*
2018-09-24 15:17:00.220 [WARN
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
Node FAILED: TcpDiscoveryNode [id=a904bac4-aaed-4f69-90f3-c13bc4d331d1,
addrs=ArrayList [10.116.206.98], sockAddrs=HashSet
[grid724.domain/10.116.206.98:47500], discPort=47500, order=110, intOrder=110,
lastExchangeTime=1537528210290, loc=false, ver=2.5.1#20180906-sha1:ebde6c79,
isClient=false]
2018-09-24 15:17:00.221 [INFO
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
Topology snapshot [ver=187, servers=156, clients=0, CPUs=8736,
offheap=19.0GB, heap=4800.0GB]
2018-09-24 15:17:00.221 [INFO
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
^-- Node [id=E002E011-8D1C-4353-A0F3-B71264C5B0F4, clusterState=INACTIVE]
2018-09-24 15:17:00.221 [INFO
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
^-- Baseline [id=6, size=160, online=156, offline=4]
*topology rolled to version 187, then another node 931 failed:*
2018-09-24 15:17:00.466 [WARN
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
Node FAILED: TcpDiscoveryNode [id=83536b6d-8aa3-4c85-b3da-5e577ae37ac6,
addrs=ArrayList [10.116.215.3], sockAddrs=HashSet
[grid931.domain/10.116.215.3:47500], discPort=47500, order=73, intOrder=73,
lastExchangeTime=1537528186599, loc=false, ver=2.5.1#20180906-sha1:ebde6c79,
isClient=false]
2018-09-24 15:17:00.467 [INFO
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
Topology snapshot [ver=188, servers=155, clients=0, CPUs=8680,
offheap=19.0GB, heap=4800.0GB]
2018-09-24 15:17:00.467 [INFO
[jira] [Updated] (IGNITE-9793) Deactivation, segmentation of one node, activation may lead to hang activation forever
[
https://issues.apache.org/jira/browse/IGNITE-9793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Voronkin updated IGNITE-9793:
---
Description:
There is topology with ring of nodes:
*665(coordinator) > 601 > 724 > 910 > 655 > ...* deactivated
*665(coordinator)* *> 601 > {color:#ff}724{color} > 910 > 655 > ...*
node failed
*665(coordinator) > 601 > 910 > 655 > ...* **activated
During activation node 910 haven't received StateChangedMessage, hovever 655
and all subsequent nodes received and responded to coordinator.
So coordinator expects to have 154 messages but received only 153 that is why
activation hangs.
Details bellow:
*Coordinator deactivated:*
2018-09-24 15:09:01.609 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=e002e011-8d1c-4353-a0f3-b71264c5b0f4, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
2018-09-24 15:09:01.620
[DEBUG][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.l.ExchangeLatchManager]
Server latch is created [latch=CompletableLatchUid
{id='exchange', topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]}
, participantsSize=160]
2018-09-24 15:09:01.621 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%]
*nodes 601, 724, 910, 655 were deactivated:*
2018-09-24 15:09:01.609 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=e002e011-8d1c-4353-a0f3-b71264c5b0f4, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
2018-09-24 15:09:03.328 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=22a58223-47b5-43c2-897b-e70e8e50edf7, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
2018-09-24 15:09:03.334 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=973eb8ce-3b8c-463d-a6ab-00ac66d93f13, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
2018-09-24 15:09:03.332 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=a904bac4-aaed-4f69-90f3-c13bc4d331d1, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
*Spi on coordinator received node 724 failed message:*
2018-09-24 15:17:00.220 [WARN
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
Node FAILED: TcpDiscoveryNode [id=a904bac4-aaed-4f69-90f3-c13bc4d331d1,
addrs=ArrayList [10.116.206.98], sockAddrs=HashSet
[grid724.domain/10.116.206.98:47500], discPort=47500, order=110, intOrder=110,
lastExchangeTime=1537528210290, loc=false, ver=2.5.1#20180906-sha1:ebde6c79,
isClient=false]
2018-09-24 15:17:00.221 [INFO
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
Topology snapshot [ver=187, servers=156, clients=0, CPUs=8736,
offheap=19.0GB, heap=4800.0GB]
2018-09-24 15:17:00.221 [INFO
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
^-- Node [id=E002E011-8D1C-4353-A0F3-B71264C5B0F4, clusterState=INACTIVE]
2018-09-24 15:17:00.221 [INFO
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
^-- Baseline [id=6, size=160, online=156, offline=4]
*topology rolled to version 187, then another node 931 failed:*
2018-09-24 15:17:00.466 [WARN
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
Node FAILED: TcpDiscoveryNode [id=83536b6d-8aa3-4c85-b3da-5e577ae37ac6,
addrs=ArrayList [10.116.215.3], sockAddrs=HashSet
[grid931.ca.sbrf.ru/10.116.215.3:47500], discPort=47500, order=73, intOrder=73,
lastExchangeTime=1537528186599, loc=false, ver=2.5.1#20180906-sha1:ebde6c79,
isClient=false]
2018-09-24 15:17:00.467 [INFO
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
Topology snapshot [ver=188, servers=155, clients=0, CPUs=8680,
offheap=19.0GB, heap=4800.0GB]
2018-09-24 15:17:00.467 [INFO
[jira] [Commented] (IGNITE-9788) ML: IgniteDataset op is not loaded in TensorFlow worker
[ https://issues.apache.org/jira/browse/IGNITE-9788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16638272#comment-16638272 ] ASF GitHub Bot commented on IGNITE-9788: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4912 > ML: IgniteDataset op is not loaded in TensorFlow worker > --- > > Key: IGNITE-9788 > URL: https://issues.apache.org/jira/browse/IGNITE-9788 > Project: Ignite > Issue Type: Bug > Components: ml >Affects Versions: 2.7 >Reporter: Anton Dmitriev >Assignee: Anton Dmitriev >Priority: Blocker > Fix For: 2.7 > > > Due to late changes in TensorFlow master (third-party library used by > "TensorFlow on Apache Ignite") worker code now requires explicit import of > operations declared in contrib package. > > We have to explicitly import IgniteDataset op. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9793) Deactivation, segmentation of one node, activation may lead to hang activation forever
[
https://issues.apache.org/jira/browse/IGNITE-9793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Voronkin updated IGNITE-9793:
---
Description:
There is topology with ring of nodes:
*665(coordinator) > 601 > 724 > 910 > 655 > ...* deactivated
*665(coordinator)* *> 601 > {color:#ff}724{color} > 910 > 655 > ...*
node failed
*665(coordinator) > 601 > 910 > 655 > ...* **activated
During activation node 910 haven't received StateChangedMessage, hovever 655
and all subsequent nodes received and responded to coordinator.
So coordinator expects to have 154 messages but received only 153 that is why
activation hangs.
Details bellow:
*Coordinator deactivated:*
2018-09-24 15:09:01.609 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=e002e011-8d1c-4353-a0f3-b71264c5b0f4, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
2018-09-24 15:09:01.620
[DEBUG][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.l.ExchangeLatchManager]
Server latch is created [latch=CompletableLatchUid
{id='exchange', topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]}
, participantsSize=160]
2018-09-24 15:09:01.621 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%]
*nodes 601, 724, 910, 655 were deactivated:*
2018-09-24 15:09:01.609 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=e002e011-8d1c-4353-a0f3-b71264c5b0f4, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
2018-09-24 15:09:03.328 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=22a58223-47b5-43c2-897b-e70e8e50edf7, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
2018-09-24 15:09:03.334 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=973eb8ce-3b8c-463d-a6ab-00ac66d93f13, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
2018-09-24 15:09:03.332 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=a904bac4-aaed-4f69-90f3-c13bc4d331d1, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
*Spi on coordinator received node 724 failed message:*
2018-09-24 15:17:00.220 [WARN
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
Node FAILED: TcpDiscoveryNode [id=a904bac4-aaed-4f69-90f3-c13bc4d331d1,
addrs=ArrayList [10.116.206.98], sockAddrs=HashSet
[grid724.domain/10.116.206.98:47500], discPort=47500, order=110, intOrder=110,
lastExchangeTime=1537528210290, loc=false, ver=2.5.1#20180906-sha1:ebde6c79,
isClient=false]
2018-09-24 15:17:00.221 [INFO
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
Topology snapshot [ver=187, servers=156, clients=0, CPUs=8736,
offheap=19.0GB, heap=4800.0GB]
2018-09-24 15:17:00.221 [INFO
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
^-- Node [id=E002E011-8D1C-4353-A0F3-B71264C5B0F4, clusterState=INACTIVE]
2018-09-24 15:17:00.221 [INFO
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
^-- Baseline [id=6, size=160, online=156, offline=4]
*topology rolled to version 187, then another node 931 failed:*
2018-09-24 15:17:00.466 [WARN
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
Node FAILED: TcpDiscoveryNode [id=83536b6d-8aa3-4c85-b3da-5e577ae37ac6,
addrs=ArrayList [10.116.215.3], sockAddrs=HashSet
[grid931.ca.sbrf.ru/10.116.215.3:47500], discPort=47500, order=73, intOrder=73,
lastExchangeTime=1537528186599, loc=false, ver=2.5.1#20180906-sha1:ebde6c79,
isClient=false]
2018-09-24 15:17:00.467 [INFO
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
Topology snapshot [ver=188, servers=155, clients=0, CPUs=8680,
offheap=19.0GB, heap=4800.0GB]
2018-09-24 15:17:00.467 [INFO
[jira] [Commented] (IGNITE-9661) Improve partition states validation
[
https://issues.apache.org/jira/browse/IGNITE-9661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16638266#comment-16638266
]
Ignite TC Bot commented on IGNITE-9661:
---
{panel:title=No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity Run
All|http://ci.ignite.apache.org/viewLog.html?buildId=1996121buildTypeId=IgniteTests24Java8_RunAll]
> Improve partition states validation
> ---
>
> Key: IGNITE-9661
> URL: https://issues.apache.org/jira/browse/IGNITE-9661
> Project: Ignite
> Issue Type: Improvement
> Components: cache
>Affects Versions: 2.5
>Reporter: Pavel Kovalenko
>Assignee: Pavel Kovalenko
>Priority: Major
> Labels: cache, perfomance
> Fix For: 2.8
>
>
> Currently, we validate partition states one-by-one and the whole algorithm
> has complexity O (G * P * N * logP), where G - number of cache groups, P -
> number of partition in each of cache groups, N - the number of nodes. Overall
> complexity can be optimized (logP can be removed). We also should consider
> parallelization of algorithm.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9661) Improve partition states validation
[
https://issues.apache.org/jira/browse/IGNITE-9661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16638268#comment-16638268
]
Ignite TC Bot commented on IGNITE-9661:
---
{panel:title=No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity Run
All|http://ci.ignite.apache.org/viewLog.html?buildId=1996121buildTypeId=IgniteTests24Java8_RunAll]
> Improve partition states validation
> ---
>
> Key: IGNITE-9661
> URL: https://issues.apache.org/jira/browse/IGNITE-9661
> Project: Ignite
> Issue Type: Improvement
> Components: cache
>Affects Versions: 2.5
>Reporter: Pavel Kovalenko
>Assignee: Pavel Kovalenko
>Priority: Major
> Labels: cache, perfomance
> Fix For: 2.8
>
>
> Currently, we validate partition states one-by-one and the whole algorithm
> has complexity O (G * P * N * logP), where G - number of cache groups, P -
> number of partition in each of cache groups, N - the number of nodes. Overall
> complexity can be optimized (logP can be removed). We also should consider
> parallelization of algorithm.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9793) Deactivation, segmentation of one node, activation may lead to hang activation forever
[
https://issues.apache.org/jira/browse/IGNITE-9793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Voronkin updated IGNITE-9793:
---
Attachment: 910_gc_server_memory.log.0.current.7z
> Deactivation, segmentation of one node, activation may lead to hang
> activation forever
> --
>
> Key: IGNITE-9793
> URL: https://issues.apache.org/jira/browse/IGNITE-9793
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Pavel Voronkin
>Priority: Major
> Attachments: 601_gc_server_memory.log.0.current.7z,
> 724_gc_server_memory.log.0.current.7z, 910_gc_server_memory.log.0.current.7z
>
>
> There is topology with ring of nodes:
> *665(coordinator) > 601 > 724 > 910 > 655 > ...* deactivated
> *665(coordinator)* *> 601 > {color:#FF}724{color} > 910 > 655 > ...*
> node failed
> *665(coordinator) > 601 > 910 > 655 > ...* **activated
> During activation node 910 haven't received StateChangedMessage, hovever 655
> and all subsequent nodes received and responded to coordinator.
> So coordinator expects to have 154 messages but received only 153 that is why
> activation hangs.
> Details bellow:
>
> Coordinator deactivated:
> 2018-09-24 15:09:01.609 [INFO
> ][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
> Successfully deactivated data structures, services and caches
> [nodeId=e002e011-8d1c-4353-a0f3-b71264c5b0f4, client=false,
> topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
> 2018-09-24 15:09:01.620
> [DEBUG][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.l.ExchangeLatchManager]
> Server latch is created [latch=CompletableLatchUid
> {id='exchange', topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]}
> , participantsSize=160]
> 2018-09-24 15:09:01.621 [INFO
> ][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%]
> nodes 601, 724, 910, 655 were deactivated:
> 2018-09-24 15:09:01.609 [INFO
> ][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
> Successfully deactivated data structures, services and caches
> [nodeId=e002e011-8d1c-4353-a0f3-b71264c5b0f4, client=false,
> topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
> 2018-09-24 15:09:03.328 [INFO
> ][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
> Successfully deactivated data structures, services and caches
> [nodeId=22a58223-47b5-43c2-897b-e70e8e50edf7, client=false,
> topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
> 2018-09-24 15:09:03.334 [INFO
> ][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
> Successfully deactivated data structures, services and caches
> [nodeId=973eb8ce-3b8c-463d-a6ab-00ac66d93f13, client=false,
> topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
> 2018-09-24 15:09:03.332 [INFO
> ][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
> Successfully deactivated data structures, services and caches
> [nodeId=a904bac4-aaed-4f69-90f3-c13bc4d331d1, client=false,
> topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
> Spi on coordinator received node 724 failed message:
> 2018-09-24 15:17:00.220 [WARN
> ][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> Node FAILED: TcpDiscoveryNode [id=a904bac4-aaed-4f69-90f3-c13bc4d331d1,
> addrs=ArrayList [10.116.206.98], sockAddrs=HashSet
> [grid724.domain/10.116.206.98:47500], discPort=47500, order=110,
> intOrder=110, lastExchangeTime=1537528210290, loc=false,
> ver=2.5.1#20180906-sha1:ebde6c79, isClient=false]
> 2018-09-24 15:17:00.221 [INFO
> ][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> Topology snapshot [ver=187, servers=156, clients=0, CPUs=8736,
> offheap=19.0GB, heap=4800.0GB]
> 2018-09-24 15:17:00.221 [INFO
> ][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> ^-- Node [id=E002E011-8D1C-4353-A0F3-B71264C5B0F4, clusterState=INACTIVE]
> 2018-09-24 15:17:00.221 [INFO
> ][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> ^-- Baseline [id=6, size=160, online=156, offline=4]
> topology rolled to version 187, then another node 931 failed:
> 2018-09-24 15:17:00.466 [WARN
>
[jira] [Updated] (IGNITE-9793) Deactivation, segmentation of one node, activation may lead to hang activation forever
[
https://issues.apache.org/jira/browse/IGNITE-9793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Voronkin updated IGNITE-9793:
---
Attachment: 724_gc_server_memory.log.0.current.7z
> Deactivation, segmentation of one node, activation may lead to hang
> activation forever
> --
>
> Key: IGNITE-9793
> URL: https://issues.apache.org/jira/browse/IGNITE-9793
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Pavel Voronkin
>Priority: Major
> Attachments: 601_gc_server_memory.log.0.current.7z,
> 724_gc_server_memory.log.0.current.7z
>
>
> There is topology with ring of nodes:
> *665(coordinator) > 601 > 724 > 910 > 655 > ...* deactivated
> *665(coordinator)* *> 601 > {color:#FF}724{color} > 910 > 655 > ...*
> node failed
> *665(coordinator) > 601 > 910 > 655 > ...* **activated
> During activation node 910 haven't received StateChangedMessage, hovever 655
> and all subsequent nodes received and responded to coordinator.
> So coordinator expects to have 154 messages but received only 153 that is why
> activation hangs.
> Details bellow:
>
> Coordinator deactivated:
> 2018-09-24 15:09:01.609 [INFO
> ][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
> Successfully deactivated data structures, services and caches
> [nodeId=e002e011-8d1c-4353-a0f3-b71264c5b0f4, client=false,
> topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
> 2018-09-24 15:09:01.620
> [DEBUG][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.l.ExchangeLatchManager]
> Server latch is created [latch=CompletableLatchUid
> {id='exchange', topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]}
> , participantsSize=160]
> 2018-09-24 15:09:01.621 [INFO
> ][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%]
> nodes 601, 724, 910, 655 were deactivated:
> 2018-09-24 15:09:01.609 [INFO
> ][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
> Successfully deactivated data structures, services and caches
> [nodeId=e002e011-8d1c-4353-a0f3-b71264c5b0f4, client=false,
> topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
> 2018-09-24 15:09:03.328 [INFO
> ][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
> Successfully deactivated data structures, services and caches
> [nodeId=22a58223-47b5-43c2-897b-e70e8e50edf7, client=false,
> topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
> 2018-09-24 15:09:03.334 [INFO
> ][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
> Successfully deactivated data structures, services and caches
> [nodeId=973eb8ce-3b8c-463d-a6ab-00ac66d93f13, client=false,
> topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
> 2018-09-24 15:09:03.332 [INFO
> ][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
> Successfully deactivated data structures, services and caches
> [nodeId=a904bac4-aaed-4f69-90f3-c13bc4d331d1, client=false,
> topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
> Spi on coordinator received node 724 failed message:
> 2018-09-24 15:17:00.220 [WARN
> ][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> Node FAILED: TcpDiscoveryNode [id=a904bac4-aaed-4f69-90f3-c13bc4d331d1,
> addrs=ArrayList [10.116.206.98], sockAddrs=HashSet
> [grid724.domain/10.116.206.98:47500], discPort=47500, order=110,
> intOrder=110, lastExchangeTime=1537528210290, loc=false,
> ver=2.5.1#20180906-sha1:ebde6c79, isClient=false]
> 2018-09-24 15:17:00.221 [INFO
> ][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> Topology snapshot [ver=187, servers=156, clients=0, CPUs=8736,
> offheap=19.0GB, heap=4800.0GB]
> 2018-09-24 15:17:00.221 [INFO
> ][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> ^-- Node [id=E002E011-8D1C-4353-A0F3-B71264C5B0F4, clusterState=INACTIVE]
> 2018-09-24 15:17:00.221 [INFO
> ][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> ^-- Baseline [id=6, size=160, online=156, offline=4]
> topology rolled to version 187, then another node 931 failed:
> 2018-09-24 15:17:00.466 [WARN
>
[jira] [Updated] (IGNITE-9793) Deactivation, segmentation of one node, activation may lead to hang activation forever
[
https://issues.apache.org/jira/browse/IGNITE-9793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Voronkin updated IGNITE-9793:
---
Attachment: 601_gc_server_memory.log.0.current.7z
> Deactivation, segmentation of one node, activation may lead to hang
> activation forever
> --
>
> Key: IGNITE-9793
> URL: https://issues.apache.org/jira/browse/IGNITE-9793
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Pavel Voronkin
>Priority: Major
> Attachments: 601_gc_server_memory.log.0.current.7z
>
>
> There is topology with ring of nodes:
> *665(coordinator) > 601 > 724 > 910 > 655 > ...* deactivated
> *665(coordinator)* *> 601 > {color:#FF}724{color} > 910 > 655 > ...*
> node failed
> *665(coordinator) > 601 > 910 > 655 > ...* **activated
> During activation node 910 haven't received StateChangedMessage, hovever 655
> and all subsequent nodes received and responded to coordinator.
> So coordinator expects to have 154 messages but received only 153 that is why
> activation hangs.
> Details bellow:
>
> Coordinator deactivated:
> 2018-09-24 15:09:01.609 [INFO
> ][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
> Successfully deactivated data structures, services and caches
> [nodeId=e002e011-8d1c-4353-a0f3-b71264c5b0f4, client=false,
> topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
> 2018-09-24 15:09:01.620
> [DEBUG][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.l.ExchangeLatchManager]
> Server latch is created [latch=CompletableLatchUid
> {id='exchange', topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]}
> , participantsSize=160]
> 2018-09-24 15:09:01.621 [INFO
> ][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%]
> nodes 601, 724, 910, 655 were deactivated:
> 2018-09-24 15:09:01.609 [INFO
> ][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
> Successfully deactivated data structures, services and caches
> [nodeId=e002e011-8d1c-4353-a0f3-b71264c5b0f4, client=false,
> topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
> 2018-09-24 15:09:03.328 [INFO
> ][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
> Successfully deactivated data structures, services and caches
> [nodeId=22a58223-47b5-43c2-897b-e70e8e50edf7, client=false,
> topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
> 2018-09-24 15:09:03.334 [INFO
> ][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
> Successfully deactivated data structures, services and caches
> [nodeId=973eb8ce-3b8c-463d-a6ab-00ac66d93f13, client=false,
> topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
> 2018-09-24 15:09:03.332 [INFO
> ][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
> Successfully deactivated data structures, services and caches
> [nodeId=a904bac4-aaed-4f69-90f3-c13bc4d331d1, client=false,
> topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
> Spi on coordinator received node 724 failed message:
> 2018-09-24 15:17:00.220 [WARN
> ][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> Node FAILED: TcpDiscoveryNode [id=a904bac4-aaed-4f69-90f3-c13bc4d331d1,
> addrs=ArrayList [10.116.206.98], sockAddrs=HashSet
> [grid724.domain/10.116.206.98:47500], discPort=47500, order=110,
> intOrder=110, lastExchangeTime=1537528210290, loc=false,
> ver=2.5.1#20180906-sha1:ebde6c79, isClient=false]
> 2018-09-24 15:17:00.221 [INFO
> ][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> Topology snapshot [ver=187, servers=156, clients=0, CPUs=8736,
> offheap=19.0GB, heap=4800.0GB]
> 2018-09-24 15:17:00.221 [INFO
> ][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> ^-- Node [id=E002E011-8D1C-4353-A0F3-B71264C5B0F4, clusterState=INACTIVE]
> 2018-09-24 15:17:00.221 [INFO
> ][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> ^-- Baseline [id=6, size=160, online=156, offline=4]
> topology rolled to version 187, then another node 931 failed:
> 2018-09-24 15:17:00.466 [WARN
>
[jira] [Updated] (IGNITE-9793) Deactivation, segmentation of one node, activation may lead to hang activation forever
[
https://issues.apache.org/jira/browse/IGNITE-9793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Voronkin updated IGNITE-9793:
---
Description:
There is topology with ring of nodes:
*665(coordinator) > 601 > 724 > 910 > 655 > ...* deactivated
*665(coordinator)* *> 601 > {color:#FF}724{color} > 910 > 655 > ...*
node failed
*665(coordinator) > 601 > 910 > 655 > ...* **activated
During activation node 910 haven't received StateChangedMessage, hovever 655
and all subsequent nodes received and responded to coordinator.
So coordinator expects to have 154 messages but received only 153 that is why
activation hangs.
Details bellow:
Coordinator deactivated:
2018-09-24 15:09:01.609 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=e002e011-8d1c-4353-a0f3-b71264c5b0f4, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
2018-09-24 15:09:01.620
[DEBUG][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.l.ExchangeLatchManager]
Server latch is created [latch=CompletableLatchUid
{id='exchange', topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]}
, participantsSize=160]
2018-09-24 15:09:01.621 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%]
nodes 601, 724, 910, 655 were deactivated:
2018-09-24 15:09:01.609 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=e002e011-8d1c-4353-a0f3-b71264c5b0f4, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
2018-09-24 15:09:03.328 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=22a58223-47b5-43c2-897b-e70e8e50edf7, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
2018-09-24 15:09:03.334 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=973eb8ce-3b8c-463d-a6ab-00ac66d93f13, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
2018-09-24 15:09:03.332 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=a904bac4-aaed-4f69-90f3-c13bc4d331d1, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
Spi on coordinator received node 724 failed message:
2018-09-24 15:17:00.220 [WARN
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
Node FAILED: TcpDiscoveryNode [id=a904bac4-aaed-4f69-90f3-c13bc4d331d1,
addrs=ArrayList [10.116.206.98], sockAddrs=HashSet
[grid724.domain/10.116.206.98:47500], discPort=47500, order=110, intOrder=110,
lastExchangeTime=1537528210290, loc=false, ver=2.5.1#20180906-sha1:ebde6c79,
isClient=false]
2018-09-24 15:17:00.221 [INFO
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
Topology snapshot [ver=187, servers=156, clients=0, CPUs=8736,
offheap=19.0GB, heap=4800.0GB]
2018-09-24 15:17:00.221 [INFO
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
^-- Node [id=E002E011-8D1C-4353-A0F3-B71264C5B0F4, clusterState=INACTIVE]
2018-09-24 15:17:00.221 [INFO
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
^-- Baseline [id=6, size=160, online=156, offline=4]
topology rolled to version 187, then another node 931 failed:
2018-09-24 15:17:00.466 [WARN
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
Node FAILED: TcpDiscoveryNode [id=83536b6d-8aa3-4c85-b3da-5e577ae37ac6,
addrs=ArrayList [10.116.215.3], sockAddrs=HashSet
[grid931.ca.sbrf.ru/10.116.215.3:47500], discPort=47500, order=73, intOrder=73,
lastExchangeTime=1537528186599, loc=false, ver=2.5.1#20180906-sha1:ebde6c79,
isClient=false]
2018-09-24 15:17:00.467 [INFO
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
Topology snapshot [ver=188, servers=155, clients=0, CPUs=8680,
offheap=19.0GB, heap=4800.0GB]
2018-09-24 15:17:00.467 [INFO
[jira] [Updated] (IGNITE-9793) Deactivation, segmentation of one node, activation may lead to hang activation forever
[
https://issues.apache.org/jira/browse/IGNITE-9793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Voronkin updated IGNITE-9793:
---
Description:
There is topology with ring of nodes:
*665(coordinator) > 601 > 724 > 910 > 655 > ...* deactivated
*665(coordinator) --> 601 -> {color:#ff}724{color} - > 910 -> 655-* -*>
...* **node failed
*665(coordinator) -> 601 -> 910 -> 655-* *> ...* **activated
During activation node 910 haven't received StateChangedMessage, hovever 655
and all subsequent nodes received and responded to coordinator.
So coordinator expects to have 154 messages but received only 153 that is why
activation hangs.
Details bellow:
Coordinator deactivated:
2018-09-24 15:09:01.609 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=e002e011-8d1c-4353-a0f3-b71264c5b0f4, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
2018-09-24 15:09:01.620
[DEBUG][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.l.ExchangeLatchManager]
Server latch is created [latch=CompletableLatchUid
{id='exchange', topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]}
, participantsSize=160]
2018-09-24 15:09:01.621 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%]
nodes 601, 724, 910, 655 were deactivated:
2018-09-24 15:09:01.609 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=e002e011-8d1c-4353-a0f3-b71264c5b0f4, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
2018-09-24 15:09:03.328 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=22a58223-47b5-43c2-897b-e70e8e50edf7, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
2018-09-24 15:09:03.334 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=973eb8ce-3b8c-463d-a6ab-00ac66d93f13, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
2018-09-24 15:09:03.332 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=a904bac4-aaed-4f69-90f3-c13bc4d331d1, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
Spi on coordinator received node 724 failed message:
2018-09-24 15:17:00.220 [WARN
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
Node FAILED: TcpDiscoveryNode [id=a904bac4-aaed-4f69-90f3-c13bc4d331d1,
addrs=ArrayList [10.116.206.98], sockAddrs=HashSet
[grid724.domain/10.116.206.98:47500], discPort=47500, order=110, intOrder=110,
lastExchangeTime=1537528210290, loc=false, ver=2.5.1#20180906-sha1:ebde6c79,
isClient=false]
2018-09-24 15:17:00.221 [INFO
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
Topology snapshot [ver=187, servers=156, clients=0, CPUs=8736,
offheap=19.0GB, heap=4800.0GB]
2018-09-24 15:17:00.221 [INFO
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
^-- Node [id=E002E011-8D1C-4353-A0F3-B71264C5B0F4, clusterState=INACTIVE]
2018-09-24 15:17:00.221 [INFO
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
^-- Baseline [id=6, size=160, online=156, offline=4]
topology rolled to version 187, then another node 931 failed:
2018-09-24 15:17:00.466 [WARN
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
Node FAILED: TcpDiscoveryNode [id=83536b6d-8aa3-4c85-b3da-5e577ae37ac6,
addrs=ArrayList [10.116.215.3], sockAddrs=HashSet
[grid931.ca.sbrf.ru/10.116.215.3:47500], discPort=47500, order=73, intOrder=73,
lastExchangeTime=1537528186599, loc=false, ver=2.5.1#20180906-sha1:ebde6c79,
isClient=false]
2018-09-24 15:17:00.467 [INFO
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
Topology snapshot [ver=188, servers=155, clients=0, CPUs=8680,
offheap=19.0GB, heap=4800.0GB]
2018-09-24 15:17:00.467 [INFO
[jira] [Updated] (IGNITE-9793) Deactivation, segmentation of one node, activation may lead to hang activation forever
[
https://issues.apache.org/jira/browse/IGNITE-9793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Voronkin updated IGNITE-9793:
---
Description:
There is topology with ring of nodes:
*665(coordinator) > 601 > 724 > 910 > 655 > ...* deactivated
*665(coordinator) -> 601 > {color:#ff}724{color} > 910 > 655-* *> ...*
**node failed
*665(coordinator) -> 601 -> 910 -> 655-* *> ...* **activated
During activation node 910 haven't received StateChangedMessage, hovever 655
and all subsequent nodes received and responded to coordinator.
So coordinator expects to have 154 messages but received only 153 that is why
activation hangs.
Details bellow:
Coordinator deactivated:
2018-09-24 15:09:01.609 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=e002e011-8d1c-4353-a0f3-b71264c5b0f4, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
2018-09-24 15:09:01.620
[DEBUG][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.l.ExchangeLatchManager]
Server latch is created [latch=CompletableLatchUid
{id='exchange', topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]}
, participantsSize=160]
2018-09-24 15:09:01.621 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%]
nodes 601, 724, 910, 655 were deactivated:
2018-09-24 15:09:01.609 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=e002e011-8d1c-4353-a0f3-b71264c5b0f4, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
2018-09-24 15:09:03.328 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=22a58223-47b5-43c2-897b-e70e8e50edf7, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
2018-09-24 15:09:03.334 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=973eb8ce-3b8c-463d-a6ab-00ac66d93f13, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
2018-09-24 15:09:03.332 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=a904bac4-aaed-4f69-90f3-c13bc4d331d1, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
Spi on coordinator received node 724 failed message:
2018-09-24 15:17:00.220 [WARN
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
Node FAILED: TcpDiscoveryNode [id=a904bac4-aaed-4f69-90f3-c13bc4d331d1,
addrs=ArrayList [10.116.206.98], sockAddrs=HashSet
[grid724.domain/10.116.206.98:47500], discPort=47500, order=110, intOrder=110,
lastExchangeTime=1537528210290, loc=false, ver=2.5.1#20180906-sha1:ebde6c79,
isClient=false]
2018-09-24 15:17:00.221 [INFO
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
Topology snapshot [ver=187, servers=156, clients=0, CPUs=8736,
offheap=19.0GB, heap=4800.0GB]
2018-09-24 15:17:00.221 [INFO
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
^-- Node [id=E002E011-8D1C-4353-A0F3-B71264C5B0F4, clusterState=INACTIVE]
2018-09-24 15:17:00.221 [INFO
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
^-- Baseline [id=6, size=160, online=156, offline=4]
topology rolled to version 187, then another node 931 failed:
2018-09-24 15:17:00.466 [WARN
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
Node FAILED: TcpDiscoveryNode [id=83536b6d-8aa3-4c85-b3da-5e577ae37ac6,
addrs=ArrayList [10.116.215.3], sockAddrs=HashSet
[grid931.ca.sbrf.ru/10.116.215.3:47500], discPort=47500, order=73, intOrder=73,
lastExchangeTime=1537528186599, loc=false, ver=2.5.1#20180906-sha1:ebde6c79,
isClient=false]
2018-09-24 15:17:00.467 [INFO
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
Topology snapshot [ver=188, servers=155, clients=0, CPUs=8680,
offheap=19.0GB, heap=4800.0GB]
2018-09-24 15:17:00.467 [INFO
[jira] [Updated] (IGNITE-9793) Deactivation, segmentation of one node, activation may lead to hang activation forever
[
https://issues.apache.org/jira/browse/IGNITE-9793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Voronkin updated IGNITE-9793:
---
Description:
There is topology with ring of nodes:
*665(coordinator) -> 601 -> 724 - > 910 -> 655 -> ...* deactivated
*665(coordinator) --> 601 -> {color:#ff}724{color} - > 910 -> 655-* -*>
...* **node failed
*665(coordinator) -> 601 -> 910 -> 655-* *> ...* **activated
During activation node 910 haven't received StateChangedMessage, hovever 655
and all subsequent nodes received and responded to coordinator.
So coordinator expects to have 154 messages but received only 153 that is why
activation hangs.
Details bellow:
Coordinator deactivated:
2018-09-24 15:09:01.609 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=e002e011-8d1c-4353-a0f3-b71264c5b0f4, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
2018-09-24 15:09:01.620
[DEBUG][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.l.ExchangeLatchManager]
Server latch is created [latch=CompletableLatchUid
{id='exchange', topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]}
, participantsSize=160]
2018-09-24 15:09:01.621 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%]
nodes 601, 724, 910, 655 were deactivated:
2018-09-24 15:09:01.609 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=e002e011-8d1c-4353-a0f3-b71264c5b0f4, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
2018-09-24 15:09:03.328 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=22a58223-47b5-43c2-897b-e70e8e50edf7, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
2018-09-24 15:09:03.334 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=973eb8ce-3b8c-463d-a6ab-00ac66d93f13, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
2018-09-24 15:09:03.332 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=a904bac4-aaed-4f69-90f3-c13bc4d331d1, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
Spi on coordinator received node 724 failed message:
2018-09-24 15:17:00.220 [WARN
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
Node FAILED: TcpDiscoveryNode [id=a904bac4-aaed-4f69-90f3-c13bc4d331d1,
addrs=ArrayList [10.116.206.98], sockAddrs=HashSet
[grid724.domain/10.116.206.98:47500], discPort=47500, order=110, intOrder=110,
lastExchangeTime=1537528210290, loc=false, ver=2.5.1#20180906-sha1:ebde6c79,
isClient=false]
2018-09-24 15:17:00.221 [INFO
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
Topology snapshot [ver=187, servers=156, clients=0, CPUs=8736,
offheap=19.0GB, heap=4800.0GB]
2018-09-24 15:17:00.221 [INFO
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
^-- Node [id=E002E011-8D1C-4353-A0F3-B71264C5B0F4, clusterState=INACTIVE]
2018-09-24 15:17:00.221 [INFO
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
^-- Baseline [id=6, size=160, online=156, offline=4]
topology rolled to version 187, then another node 931 failed:
2018-09-24 15:17:00.466 [WARN
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
Node FAILED: TcpDiscoveryNode [id=83536b6d-8aa3-4c85-b3da-5e577ae37ac6,
addrs=ArrayList [10.116.215.3], sockAddrs=HashSet
[grid931.ca.sbrf.ru/10.116.215.3:47500], discPort=47500, order=73, intOrder=73,
lastExchangeTime=1537528186599, loc=false, ver=2.5.1#20180906-sha1:ebde6c79,
isClient=false]
2018-09-24 15:17:00.467 [INFO
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
Topology snapshot [ver=188, servers=155, clients=0, CPUs=8680,
offheap=19.0GB, heap=4800.0GB]
2018-09-24 15:17:00.467 [INFO
[jira] [Updated] (IGNITE-9793) Deactivation, segmentation of one node, activation may lead to hang activation forever
[
https://issues.apache.org/jira/browse/IGNITE-9793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Voronkin updated IGNITE-9793:
---
Description:
There is topology with ring of nodes:
*665(coordinator) -> 601 -> 724 - > 910 -> 655 -> ...* deactivated
*665(coordinator) -> 601 -> {color:#FF}724{color} - > 910 -> 655* *-> ...*
**node failed
*665(coordinator) -> 601 -> 910 -> 655* *-> ...* **activated
During activation node 910 haven't received StateChangedMessage, hovever 655
and all subsequent nodes received and responded to coordinator.
So coordinator expects to have 154 messages but received only 153 that is why
activation hangs.
Details bellow:
Coordinator deactivated:
2018-09-24 15:09:01.609 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=e002e011-8d1c-4353-a0f3-b71264c5b0f4, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
2018-09-24 15:09:01.620
[DEBUG][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.l.ExchangeLatchManager]
Server latch is created [latch=CompletableLatchUid
{id='exchange', topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]}
, participantsSize=160]
2018-09-24 15:09:01.621 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%]
nodes 601, 724, 910, 655 were deactivated:
2018-09-24 15:09:01.609 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=e002e011-8d1c-4353-a0f3-b71264c5b0f4, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
2018-09-24 15:09:03.328 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=22a58223-47b5-43c2-897b-e70e8e50edf7, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
2018-09-24 15:09:03.334 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=973eb8ce-3b8c-463d-a6ab-00ac66d93f13, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
2018-09-24 15:09:03.332 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=a904bac4-aaed-4f69-90f3-c13bc4d331d1, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
Spi on coordinator received node 724 failed message:
2018-09-24 15:17:00.220 [WARN
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
Node FAILED: TcpDiscoveryNode [id=a904bac4-aaed-4f69-90f3-c13bc4d331d1,
addrs=ArrayList [10.116.206.98], sockAddrs=HashSet
[grid724.domain/10.116.206.98:47500], discPort=47500, order=110, intOrder=110,
lastExchangeTime=1537528210290, loc=false, ver=2.5.1#20180906-sha1:ebde6c79,
isClient=false]
2018-09-24 15:17:00.221 [INFO
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
Topology snapshot [ver=187, servers=156, clients=0, CPUs=8736,
offheap=19.0GB, heap=4800.0GB]
2018-09-24 15:17:00.221 [INFO
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
^-- Node [id=E002E011-8D1C-4353-A0F3-B71264C5B0F4, clusterState=INACTIVE]
2018-09-24 15:17:00.221 [INFO
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
^-- Baseline [id=6, size=160, online=156, offline=4]
topology rolled to version 187, then another node 931 failed:
2018-09-24 15:17:00.466 [WARN
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
Node FAILED: TcpDiscoveryNode [id=83536b6d-8aa3-4c85-b3da-5e577ae37ac6,
addrs=ArrayList [10.116.215.3], sockAddrs=HashSet
[grid931.ca.sbrf.ru/10.116.215.3:47500], discPort=47500, order=73, intOrder=73,
lastExchangeTime=1537528186599, loc=false, ver=2.5.1#20180906-sha1:ebde6c79,
isClient=false]
2018-09-24 15:17:00.467 [INFO
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
Topology snapshot [ver=188, servers=155, clients=0, CPUs=8680,
offheap=19.0GB, heap=4800.0GB]
2018-09-24 15:17:00.467 [INFO
[jira] [Updated] (IGNITE-9793) Deactivation, segmentation of one node, activation may lead to hang activation forever
[
https://issues.apache.org/jira/browse/IGNITE-9793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Voronkin updated IGNITE-9793:
---
Description:
There is coordinator and ring of nodes
665(coordinator) -> 601 -> 724 - > 910 -> 655
coordinator deactivated:
2018-09-24 15:09:01.609 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=e002e011-8d1c-4353-a0f3-b71264c5b0f4, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
2018-09-24 15:09:01.620
[DEBUG][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.l.ExchangeLatchManager]
Server latch is created [latch=CompletableLatchUid
{id='exchange', topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]},
participantsSize=160]
2018-09-24 15:09:01.621 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%]
nodes 601, 724, 910, 655 were deactivated:
2018-09-24 15:09:01.609 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=e002e011-8d1c-4353-a0f3-b71264c5b0f4, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
2018-09-24 15:09:03.328 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=22a58223-47b5-43c2-897b-e70e8e50edf7, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
2018-09-24 15:09:03.334 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=973eb8ce-3b8c-463d-a6ab-00ac66d93f13, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
2018-09-24 15:09:03.332 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=a904bac4-aaed-4f69-90f3-c13bc4d331d1, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
Spi on coordinator received node 724 failed message:
2018-09-24 15:17:00.220 [WARN
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
Node FAILED: TcpDiscoveryNode [id=a904bac4-aaed-4f69-90f3-c13bc4d331d1,
addrs=ArrayList [10.116.206.98], sockAddrs=HashSet
[grid724.domain/10.116.206.98:47500], discPort=47500, order=110, intOrder=110,
lastExchangeTime=1537528210290, loc=false, ver=2.5.1#20180906-sha1:ebde6c79,
isClient=false]
2018-09-24 15:17:00.221 [INFO
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
Topology snapshot [ver=187, servers=156, clients=0, CPUs=8736,
offheap=19.0GB, heap=4800.0GB]
2018-09-24 15:17:00.221 [INFO
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
^-- Node [id=E002E011-8D1C-4353-A0F3-B71264C5B0F4, clusterState=INACTIVE]
2018-09-24 15:17:00.221 [INFO
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
^-- Baseline [id=6, size=160, online=156, offline=4]
topology rolled to version 187, then another node 931 failed:
2018-09-24 15:17:00.466 [WARN
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
Node FAILED: TcpDiscoveryNode [id=83536b6d-8aa3-4c85-b3da-5e577ae37ac6,
addrs=ArrayList [10.116.215.3], sockAddrs=HashSet
[grid931.ca.sbrf.ru/10.116.215.3:47500], discPort=47500, order=73, intOrder=73,
lastExchangeTime=1537528186599, loc=false, ver=2.5.1#20180906-sha1:ebde6c79,
isClient=false]
2018-09-24 15:17:00.467 [INFO
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
Topology snapshot [ver=188, servers=155, clients=0, CPUs=8680,
offheap=19.0GB, heap=4800.0GB]
2018-09-24 15:17:00.467 [INFO
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
^-- Node [id=E002E011-8D1C-4353-A0F3-B71264C5B0F4, clusterState=INACTIVE]
2018-09-24 15:17:00.467 [INFO
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
^-- Baseline [id=6, size=160, online=155, offline=5]
topology rolled to version 188.
Node 724 SEGMENTED before activation starts:
2018-09-24 15:17:50.068 [WARN
][tcp-disco-msg-worker-#2%DPL_GRID%DplGridNodeName%|#2%DPL_GRID%DplGridNodeName%][o.a.i.s.d.tcp.TcpDiscoverySpi]
Node is out of topology (probably, due to short-time network problems).
2018-09-24 15:17:50.069 [WARN
[jira] [Updated] (IGNITE-9793) Deactivation, segmentation of one node, activation may lead to hang activation forever
[
https://issues.apache.org/jira/browse/IGNITE-9793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Voronkin updated IGNITE-9793:
---
Description:
There is coordinator and ring of nodes
coordinator -> 1 -> 2 - > 3 -> 4
coordinator deactivated:
2018-09-24 15:09:01.609 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=e002e011-8d1c-4353-a0f3-b71264c5b0f4, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
2018-09-24 15:09:01.620
[DEBUG][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.l.ExchangeLatchManager]
Server latch is created [latch=CompletableLatchUid
{id='exchange', topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]}
, participantsSize=160]
2018-09-24 15:09:01.621 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%]
nodes 1, 2, 3, 4 were deactivated:
2018-09-24 15:09:01.609 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=e002e011-8d1c-4353-a0f3-b71264c5b0f4, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
2018-09-24 15:09:03.328 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=22a58223-47b5-43c2-897b-e70e8e50edf7, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
2018-09-24 15:09:03.334 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=973eb8ce-3b8c-463d-a6ab-00ac66d93f13, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
2018-09-24 15:09:03.332 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=a904bac4-aaed-4f69-90f3-c13bc4d331d1, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
Node 2 SEGMENTED
2018-09-24 15:17:50.068 [WARN
][tcp-disco-msg-worker-#2%DPL_GRID%DplGridNodeName%|#2%DPL_GRID%DplGridNodeName%][o.a.i.s.d.tcp.TcpDiscoverySpi]
Node is out of topology (probably, due to short-time network problems).
2018-09-24 15:17:50.069 [WARN
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
Local node SEGMENTED: TcpDiscoveryNode
[id=a904bac4-aaed-4f69-90f3-c13bc4d331d1, addrs=ArrayList [10.116.206.98],
sockAddrs=HashSet [grid724.domain/10.116.206.98:47500], discPort=47500,
order=110, intOrder=110, lastExchangeTime=1537791470063, loc=true,
ver=2.5.1#20180906-sha1:ebde6c79, isClient=false]
Coordinator started activation on topology without node2
2018-09-24 15:19:48.686 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Start activation process [nodeId=e002e011-8d1c-4353-a0f3-b71264c5b0f4,
client=false, topVer=AffinityTopologyVersion [topVer=188, minorTopVer=1]]
But node 3 which is next to node 2 haven't received activation message.
Coordinator sent activation to all except 3.
2018-09-24 15:24:25.911 [INFO
][sys-#28144%DPL_GRID%DplGridNodeName%|#28144%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Coordinator received single message [ver=AffinityTopologyVersion [topVer=188,
minorTopVer=1], node=073f1598-6b70-49df-8f45-126735611775, allReceived=false]
GridDhtPartitionsExchangeFuture hangs forever.
So one node in the ring missed the message, hovever all other nodes in
topology got it, how is that possible?
was:
There is coordinator and ring of nodes
coordinator -> 1 -> 2 - > 3 -> 4
coordinator deactivated:
2018-09-24 15:09:01.609 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=e002e011-8d1c-4353-a0f3-b71264c5b0f4, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
2018-09-24 15:09:01.620
[DEBUG][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.l.ExchangeLatchManager]
Server latch is created [latch=CompletableLatchUid
{id='exchange', topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]}
, participantsSize=160]
2018-09-24 15:09:01.621 [INFO
[jira] [Updated] (IGNITE-9793) Deactivation, segmentation of one node, activation may lead to hang activation forever
[
https://issues.apache.org/jira/browse/IGNITE-9793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Voronkin updated IGNITE-9793:
---
Description:
There is coordinator and ring of nodes
coordinator -> 1 -> 2 - > 3 -> 4
coordinator deactivated:
2018-09-24 15:09:01.609 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=e002e011-8d1c-4353-a0f3-b71264c5b0f4, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
2018-09-24 15:09:01.620
[DEBUG][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.l.ExchangeLatchManager]
Server latch is created [latch=CompletableLatchUid
{id='exchange', topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]}
, participantsSize=160]
2018-09-24 15:09:01.621 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%]
nodes 1, 2, 3, 4 were deactivated:
2018-09-24 15:09:01.609 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=e002e011-8d1c-4353-a0f3-b71264c5b0f4, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
2018-09-24 15:09:03.328 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=22a58223-47b5-43c2-897b-e70e8e50edf7, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
2018-09-24 15:09:03.334 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=973eb8ce-3b8c-463d-a6ab-00ac66d93f13, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
2018-09-24 15:09:03.332 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=a904bac4-aaed-4f69-90f3-c13bc4d331d1, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
Node 2 SEGMENTED
2018-09-24 15:17:50.068 [WARN
][tcp-disco-msg-worker-#2%DPL_GRID%DplGridNodeName%|#2%DPL_GRID%DplGridNodeName%][o.a.i.s.d.tcp.TcpDiscoverySpi]
Node is out of topology (probably, due to short-time network problems).
2018-09-24 15:17:50.069 [WARN
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
Local node SEGMENTED: TcpDiscoveryNode
[id=a904bac4-aaed-4f69-90f3-c13bc4d331d1, addrs=ArrayList [10.116.206.98],
sockAddrs=HashSet [grid724.domain/10.116.206.98:47500], discPort=47500,
order=110, intOrder=110, lastExchangeTime=1537791470063, loc=true,
ver=2.5.1#20180906-sha1:ebde6c79, isClient=false]
Coordinator started activation on topology without node2
2018-09-24 15:19:48.686 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Start activation process [nodeId=e002e011-8d1c-4353-a0f3-b71264c5b0f4,
client=false, topVer=AffinityTopologyVersion [topVer=188, minorTopVer=1]]
But node 3 which is next to node 2 haven't received activation message.
Coordinator sent activation to all except 3.
2018-09-24 15:24:25.911 [INFO
][sys-#28144%DPL_GRID%DplGridNodeName%|#28144%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Coordinator received single message [ver=AffinityTopologyVersion [topVer=188,
minorTopVer=1], node=073f1598-6b70-49df-8f45-126735611775, allReceived=false]
GridDhtPartitionsExchangeFuture hangs forever.
was:
There is coordinator and ring of nodes
coordinator -> 1 -> 2 - > 3 -> 4
coordinator deactivated:
2018-09-24 15:09:01.609 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=e002e011-8d1c-4353-a0f3-b71264c5b0f4, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
2018-09-24 15:09:01.620
[DEBUG][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.l.ExchangeLatchManager]
Server latch is created [latch=CompletableLatchUid{id='exchange',
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]},
participantsSize=160]
2018-09-24 15:09:01.621 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%]
nodes 1, 2, 3, 4 were deactivated:
2018-09-24
[jira] [Created] (IGNITE-9793) Deactivation, segmentation of one node, activation may lead to hang activation forever
Pavel Voronkin created IGNITE-9793:
--
Summary: Deactivation, segmentation of one node, activation may
lead to hang activation forever
Key: IGNITE-9793
URL: https://issues.apache.org/jira/browse/IGNITE-9793
Project: Ignite
Issue Type: Bug
Affects Versions: 2.5
Reporter: Pavel Voronkin
There is coordinator and ring of nodes
coordinator -> 1 -> 2 - > 3 -> 4
coordinator deactivated:
2018-09-24 15:09:01.609 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=e002e011-8d1c-4353-a0f3-b71264c5b0f4, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
2018-09-24 15:09:01.620
[DEBUG][exchange-worker-#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.l.ExchangeLatchManager]
Server latch is created [latch=CompletableLatchUid\{id='exchange',
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]},
participantsSize=160]
2018-09-24 15:09:01.621 [INFO ][exchange-worker-#153%DPL_GRID%DplGridNodeName%]
nodes 1, 2, 3, 4 were deactivated:
2018-09-24 15:09:01.609 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=e002e011-8d1c-4353-a0f3-b71264c5b0f4, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
2018-09-24 15:09:03.328 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=22a58223-47b5-43c2-897b-e70e8e50edf7, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
2018-09-24 15:09:03.334 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=973eb8ce-3b8c-463d-a6ab-00ac66d93f13, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
2018-09-24 15:09:03.332 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=a904bac4-aaed-4f69-90f3-c13bc4d331d1, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
Node 2 SEGMENTED
2018-09-24 15:17:50.068 [WARN
][tcp-disco-msg-worker-#2%DPL_GRID%DplGridNodeName%][o.a.i.s.d.tcp.TcpDiscoverySpi]
Node is out of topology (probably, due to short-time network problems).
2018-09-24 15:17:50.069 [WARN
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
Local node SEGMENTED: TcpDiscoveryNode
[id=a904bac4-aaed-4f69-90f3-c13bc4d331d1, addrs=ArrayList [10.116.206.98],
sockAddrs=HashSet [grid724.domain/10.116.206.98:47500], discPort=47500,
order=110, intOrder=110, lastExchangeTime=1537791470063, loc=true,
ver=2.5.1#20180906-sha1:ebde6c79, isClient=false]
Coordinator started activation on topology without node2
2018-09-24 15:19:48.686 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Start activation process [nodeId=e002e011-8d1c-4353-a0f3-b71264c5b0f4,
client=false, topVer=AffinityTopologyVersion [topVer=188, minorTopVer=1]]
But node 3 which is next to node 2 haven't received activation message.
Coordinator sent activation to all except
2018-09-24 15:24:25.911 [INFO
][sys-#28144%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Coordinator received single message [ver=AffinityTopologyVersion [topVer=188,
minorTopVer=1], node=073f1598-6b70-49df-8f45-126735611775, allReceived=false]
GridDhtPartitionsExchangeFuture hangs forever.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9652) Fix `Missorted modifiers' according inspections profile`
[ https://issues.apache.org/jira/browse/IGNITE-9652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16638220#comment-16638220 ] Maxim Muzafarov commented on IGNITE-9652: - I've resolved conflicts with the master branch. Re-run TC. > Fix `Missorted modifiers' according inspections profile` > > > Key: IGNITE-9652 > URL: https://issues.apache.org/jira/browse/IGNITE-9652 > Project: Ignite > Issue Type: Bug >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Minor > Labels: inspections > Fix For: 2.8 > > > New `Code Inspections` profile can be found > \idea\ignite_inspections.xml. > We need to fix rule `Missorted modifiers` in ignite-core module. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9449) Lazy unmarshalling of discovery events in TcpDiscovery
[ https://issues.apache.org/jira/browse/IGNITE-9449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov reassigned IGNITE-9449: --- Assignee: (was: Nikolay Izhikov) > Lazy unmarshalling of discovery events in TcpDiscovery > -- > > Key: IGNITE-9449 > URL: https://issues.apache.org/jira/browse/IGNITE-9449 > Project: Ignite > Issue Type: Improvement > Components: cache >Affects Versions: 2.4, 2.5, 2.6 >Reporter: Pavel Kovalenko >Priority: Major > Fix For: 2.8 > > > Currently disco-msg-worker thread spend major part of time on disocvery > message unmarshalling before send it to the next node. In most cases this is > unnecessary and message can be send immediately after receiving and notyfing > discovery-event-worker. > Responsibility of unmarshalling should moved to discovery-event-worker thread > and this improvement will significantly reduce latency of sending custom > messages across ring. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9449) Lazy unmarshalling of discovery events in TcpDiscovery
[ https://issues.apache.org/jira/browse/IGNITE-9449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov reassigned IGNITE-9449: --- Assignee: Nikolay Izhikov > Lazy unmarshalling of discovery events in TcpDiscovery > -- > > Key: IGNITE-9449 > URL: https://issues.apache.org/jira/browse/IGNITE-9449 > Project: Ignite > Issue Type: Improvement > Components: cache >Affects Versions: 2.4, 2.5, 2.6 >Reporter: Pavel Kovalenko >Assignee: Nikolay Izhikov >Priority: Major > Fix For: 2.8 > > > Currently disco-msg-worker thread spend major part of time on disocvery > message unmarshalling before send it to the next node. In most cases this is > unnecessary and message can be send immediately after receiving and notyfing > discovery-event-worker. > Responsibility of unmarshalling should moved to discovery-event-worker thread > and this improvement will significantly reduce latency of sending custom > messages across ring. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9420) Move logical recovery phase outside of PME
[ https://issues.apache.org/jira/browse/IGNITE-9420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov reassigned IGNITE-9420: --- Assignee: Nikolay Izhikov > Move logical recovery phase outside of PME > -- > > Key: IGNITE-9420 > URL: https://issues.apache.org/jira/browse/IGNITE-9420 > Project: Ignite > Issue Type: Improvement > Components: cache >Affects Versions: 2.5 >Reporter: Pavel Kovalenko >Assignee: Nikolay Izhikov >Priority: Major > Fix For: 2.8 > > > Currently, we perform logical recovery in PME here > org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager#restoreState > We should move logical recovery before discovery manager will start. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9793) Deactivation, segmentation of one node, activation may lead to hang activation forever
[
https://issues.apache.org/jira/browse/IGNITE-9793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Voronkin updated IGNITE-9793:
---
Description:
There is coordinator and ring of nodes
coordinator -> 1 -> 2 - > 3 -> 4
coordinator deactivated:
2018-09-24 15:09:01.609 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=e002e011-8d1c-4353-a0f3-b71264c5b0f4, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
2018-09-24 15:09:01.620
[DEBUG][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.l.ExchangeLatchManager]
Server latch is created [latch=CompletableLatchUid{id='exchange',
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]},
participantsSize=160]
2018-09-24 15:09:01.621 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%]
nodes 1, 2, 3, 4 were deactivated:
2018-09-24 15:09:01.609 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=e002e011-8d1c-4353-a0f3-b71264c5b0f4, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
2018-09-24 15:09:03.328 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=22a58223-47b5-43c2-897b-e70e8e50edf7, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
2018-09-24 15:09:03.334 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=973eb8ce-3b8c-463d-a6ab-00ac66d93f13, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
2018-09-24 15:09:03.332 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=a904bac4-aaed-4f69-90f3-c13bc4d331d1, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
Node 2 SEGMENTED
2018-09-24 15:17:50.068 [WARN
][tcp-disco-msg-worker-#2%DPL_GRID%DplGridNodeName%|#2%DPL_GRID%DplGridNodeName%][o.a.i.s.d.tcp.TcpDiscoverySpi]
Node is out of topology (probably, due to short-time network problems).
2018-09-24 15:17:50.069 [WARN
][disco-event-worker-#152%DPL_GRID%DplGridNodeName%|#152%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
Local node SEGMENTED: TcpDiscoveryNode
[id=a904bac4-aaed-4f69-90f3-c13bc4d331d1, addrs=ArrayList [10.116.206.98],
sockAddrs=HashSet [grid724.domain/10.116.206.98:47500], discPort=47500,
order=110, intOrder=110, lastExchangeTime=1537791470063, loc=true,
ver=2.5.1#20180906-sha1:ebde6c79, isClient=false]
Coordinator started activation on topology without node2
2018-09-24 15:19:48.686 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%|#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Start activation process [nodeId=e002e011-8d1c-4353-a0f3-b71264c5b0f4,
client=false, topVer=AffinityTopologyVersion [topVer=188, minorTopVer=1]]
But node 3 which is next to node 2 haven't received activation message.
Coordinator sent activation to all except 3.
Node 3 haven't received activation message.
2018-09-24 15:24:25.911 [INFO
][sys-#28144%DPL_GRID%DplGridNodeName%|#28144%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Coordinator received single message [ver=AffinityTopologyVersion [topVer=188,
minorTopVer=1], node=073f1598-6b70-49df-8f45-126735611775, allReceived=false]
GridDhtPartitionsExchangeFuture hangs forever.
was:
There is coordinator and ring of nodes
coordinator -> 1 -> 2 - > 3 -> 4
coordinator deactivated:
2018-09-24 15:09:01.609 [INFO
][exchange-worker-#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
Successfully deactivated data structures, services and caches
[nodeId=e002e011-8d1c-4353-a0f3-b71264c5b0f4, client=false,
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]]
2018-09-24 15:09:01.620
[DEBUG][exchange-worker-#153%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.l.ExchangeLatchManager]
Server latch is created [latch=CompletableLatchUid\{id='exchange',
topVer=AffinityTopologyVersion [topVer=183, minorTopVer=1]},
participantsSize=160]
2018-09-24 15:09:01.621 [INFO ][exchange-worker-#153%DPL_GRID%DplGridNodeName%]
nodes 1, 2, 3, 4 were deactivated:
2018-09-24 15:09:01.609 [INFO
[jira] [Assigned] (IGNITE-9449) Lazy unmarshalling of discovery events in TcpDiscovery
[ https://issues.apache.org/jira/browse/IGNITE-9449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov reassigned IGNITE-9449: --- Assignee: (was: Nikolay Izhikov) > Lazy unmarshalling of discovery events in TcpDiscovery > -- > > Key: IGNITE-9449 > URL: https://issues.apache.org/jira/browse/IGNITE-9449 > Project: Ignite > Issue Type: Improvement > Components: cache >Affects Versions: 2.4, 2.5, 2.6 >Reporter: Pavel Kovalenko >Priority: Major > Fix For: 2.8 > > > Currently disco-msg-worker thread spend major part of time on disocvery > message unmarshalling before send it to the next node. In most cases this is > unnecessary and message can be send immediately after receiving and notyfing > discovery-event-worker. > Responsibility of unmarshalling should moved to discovery-event-worker thread > and this improvement will significantly reduce latency of sending custom > messages across ring. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9449) Lazy unmarshalling of discovery events in TcpDiscovery
[ https://issues.apache.org/jira/browse/IGNITE-9449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16638168#comment-16638168 ] Nikolay Izhikov commented on IGNITE-9449: - Thanks, [~yzhdanov]. Waiting for your design. > Lazy unmarshalling of discovery events in TcpDiscovery > -- > > Key: IGNITE-9449 > URL: https://issues.apache.org/jira/browse/IGNITE-9449 > Project: Ignite > Issue Type: Improvement > Components: cache >Affects Versions: 2.4, 2.5, 2.6 >Reporter: Pavel Kovalenko >Priority: Major > Fix For: 2.8 > > > Currently disco-msg-worker thread spend major part of time on disocvery > message unmarshalling before send it to the next node. In most cases this is > unnecessary and message can be send immediately after receiving and notyfing > discovery-event-worker. > Responsibility of unmarshalling should moved to discovery-event-worker thread > and this improvement will significantly reduce latency of sending custom > messages across ring. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9449) Lazy unmarshalling of discovery events in TcpDiscovery
[ https://issues.apache.org/jira/browse/IGNITE-9449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16638154#comment-16638154 ] Yakov Zhdanov commented on IGNITE-9449: --- [~NIzhikov] Nikolay, this is pretty complex issue and it seems this requires in-depth understanding of discovery protocol. I also think that this change should be accompanied by some more changes to discovery which may be a subject for new IEP. Can you please switch to another ticket for now and give me couple of weeks to summarize my ideas? Thanks! Yakov > Lazy unmarshalling of discovery events in TcpDiscovery > -- > > Key: IGNITE-9449 > URL: https://issues.apache.org/jira/browse/IGNITE-9449 > Project: Ignite > Issue Type: Improvement > Components: cache >Affects Versions: 2.4, 2.5, 2.6 >Reporter: Pavel Kovalenko >Assignee: Nikolay Izhikov >Priority: Major > Fix For: 2.8 > > > Currently disco-msg-worker thread spend major part of time on disocvery > message unmarshalling before send it to the next node. In most cases this is > unnecessary and message can be send immediately after receiving and notyfing > discovery-event-worker. > Responsibility of unmarshalling should moved to discovery-event-worker thread > and this improvement will significantly reduce latency of sending custom > messages across ring. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9770) Re-run possible blockers from pr.html
[
https://issues.apache.org/jira/browse/IGNITE-9770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16638134#comment-16638134
]
ASF GitHub Bot commented on IGNITE-9770:
SomeFire commented on a change in pull request #27: IGNITE-9770 Add 'Re-run
possible blockers' button
URL: https://github.com/apache/ignite-teamcity-bot/pull/27#discussion_r222643151
##
File path: ignite-tc-helper-web/src/main/webapp/js/testfails-2.1.js
##
@@ -171,9 +170,29 @@ function showChainCurrentStatusData(server, settings) {
if (settings.isJiraAvailable()) {
res += "Comment JIRA";
++ server.branchName + "\")'>Comment JIRA";
}
+var blockersList = "";
+
+for (var i = 0; i < server.suites.length; i++) {
+var suite = server.suites[i];
+
+suite = suiteWithCriticalFailuresOnly(suite);
+
+if (suite != null) {
+if (blockersList.length !== 0)
+blockersList += ",";
+
+blockersList += suite.suiteId;
+}
+}
+
+res += " Re-run
possible blockers";
+
+res += " Re-run
possible blockers & Comment JIRA";
Review comment:
Too long line. Also, add `` tag and move this under
`settings.isJiraAvailable()` check.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Re-run possible blockers from pr.html
> -
>
> Key: IGNITE-9770
> URL: https://issues.apache.org/jira/browse/IGNITE-9770
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Minor
>
> Show button for re-run possible blockers. Also show merged button with re-run
> possible blockers JIRA, so the user re-run the possible tests and
> does not wait for them to complete,but learn about the completed tests from
> the comment to GitHib.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9770) Re-run possible blockers from pr.html
[
https://issues.apache.org/jira/browse/IGNITE-9770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16638137#comment-16638137
]
ASF GitHub Bot commented on IGNITE-9770:
SomeFire commented on a change in pull request #27: IGNITE-9770 Add 'Re-run
possible blockers' button
URL: https://github.com/apache/ignite-teamcity-bot/pull/27#discussion_r222643571
##
File path: ignite-tc-helper-web/src/main/webapp/js/testfails-2.1.js
##
@@ -125,11 +124,11 @@ function showChainCurrentStatusData(server, settings) {
if (suitesFailedList.length !== 0 && isDefinedAndFilled(server.serverId)
&& isDefinedAndFilled(server.branchName)) {
mInfo += "Trigger failed " + cntFailed + " builds";
mInfo += " Re-run possible blockers from pr.html
> -
>
> Key: IGNITE-9770
> URL: https://issues.apache.org/jira/browse/IGNITE-9770
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Minor
>
> Show button for re-run possible blockers. Also show merged button with re-run
> possible blockers JIRA, so the user re-run the possible tests and
> does not wait for them to complete,but learn about the completed tests from
> the comment to GitHib.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9770) Re-run possible blockers from pr.html
[ https://issues.apache.org/jira/browse/IGNITE-9770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16638135#comment-16638135 ] ASF GitHub Bot commented on IGNITE-9770: SomeFire commented on a change in pull request #27: IGNITE-9770 Add 'Re-run possible blockers' button URL: https://github.com/apache/ignite-teamcity-bot/pull/27#discussion_r222642202 ## File path: ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/web/rest/TriggerBuild.java ## @@ -167,7 +167,8 @@ private String observeJira( BuildObserver observer = CtxListener.getInjector(context).getInstance(BuildObserver.class); -observer.observe(build, srvId, prov, "ignite-" + ticketId); +for (Build build : builds) Review comment: We shouldn't observe builds for the same PR separately, because in such case we Bot will comment same ticket for every build. We should wait while all of the builds will be finished and comment only once. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Re-run possible blockers from pr.html > - > > Key: IGNITE-9770 > URL: https://issues.apache.org/jira/browse/IGNITE-9770 > Project: Ignite > Issue Type: Sub-task >Reporter: Nikolai Kulagin >Assignee: Nikolai Kulagin >Priority: Minor > > Show button for re-run possible blockers. Also show merged button with re-run > possible blockers JIRA, so the user re-run the possible tests and > does not wait for them to complete,but learn about the completed tests from > the comment to GitHib. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9770) Re-run possible blockers from pr.html
[
https://issues.apache.org/jira/browse/IGNITE-9770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16638136#comment-16638136
]
ASF GitHub Bot commented on IGNITE-9770:
SomeFire commented on a change in pull request #27: IGNITE-9770 Add 'Re-run
possible blockers' button
URL: https://github.com/apache/ignite-teamcity-bot/pull/27#discussion_r222642946
##
File path: ignite-tc-helper-web/src/main/webapp/js/testfails-2.1.js
##
@@ -171,9 +170,29 @@ function showChainCurrentStatusData(server, settings) {
if (settings.isJiraAvailable()) {
res += "Comment JIRA";
++ server.branchName + "\")'>Comment JIRA";
}
+var blockersList = "";
+
+for (var i = 0; i < server.suites.length; i++) {
+var suite = server.suites[i];
+
+suite = suiteWithCriticalFailuresOnly(suite);
+
+if (suite != null) {
+if (blockersList.length !== 0)
+blockersList += ",";
+
+blockersList += suite.suiteId;
+}
+}
+
+res += " Re-run
possible blockers";
Review comment:
Too long line. Also, add `` tag.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Re-run possible blockers from pr.html
> -
>
> Key: IGNITE-9770
> URL: https://issues.apache.org/jira/browse/IGNITE-9770
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Minor
>
> Show button for re-run possible blockers. Also show merged button with re-run
> possible blockers JIRA, so the user re-run the possible tests and
> does not wait for them to complete,but learn about the completed tests from
> the comment to GitHib.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9770) Re-run possible blockers from pr.html
[
https://issues.apache.org/jira/browse/IGNITE-9770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16638139#comment-16638139
]
ASF GitHub Bot commented on IGNITE-9770:
SomeFire commented on a change in pull request #27: IGNITE-9770 Add 'Re-run
possible blockers' button
URL: https://github.com/apache/ignite-teamcity-bot/pull/27#discussion_r222643602
##
File path: ignite-tc-helper-web/src/main/webapp/js/testfails-2.1.js
##
@@ -125,11 +124,11 @@ function showChainCurrentStatusData(server, settings) {
if (suitesFailedList.length !== 0 && isDefinedAndFilled(server.serverId)
&& isDefinedAndFilled(server.branchName)) {
mInfo += "Trigger failed " + cntFailed + " builds";
mInfo += " Re-run possible blockers from pr.html
> -
>
> Key: IGNITE-9770
> URL: https://issues.apache.org/jira/browse/IGNITE-9770
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Minor
>
> Show button for re-run possible blockers. Also show merged button with re-run
> possible blockers JIRA, so the user re-run the possible tests and
> does not wait for them to complete,but learn about the completed tests from
> the comment to GitHib.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9770) Re-run possible blockers from pr.html
[
https://issues.apache.org/jira/browse/IGNITE-9770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16638138#comment-16638138
]
ASF GitHub Bot commented on IGNITE-9770:
SomeFire commented on a change in pull request #27: IGNITE-9770 Add 'Re-run
possible blockers' button
URL: https://github.com/apache/ignite-teamcity-bot/pull/27#discussion_r222642529
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/web/rest/TriggerBuild.java
##
@@ -195,31 +196,42 @@ private String observeJira(
@GET
@Path("triggerBuilds")
public SimpleResult triggerBuilds(
-@Nullable @QueryParam("serverId") String serverId,
+@Nullable @QueryParam("serverId") String srvId,
@Nullable @QueryParam("branchName") String branchName,
@NotNull @QueryParam("suiteIdList") String suiteIdList,
-@Nullable @QueryParam("top") Boolean top) {
+@Nullable @QueryParam("top") Boolean top,
+@Nullable @QueryParam("observe") Boolean observe,
+@Nullable @QueryParam("ticketId") String ticketId) {
+
+String jiraRes = "";
final ICredentialsProv prov = ICredentialsProv.get(req);
-if (!prov.hasAccess(serverId))
-throw ServiceUnauthorizedException.noCreds(serverId);
+if (!prov.hasAccess(srvId))
+throw ServiceUnauthorizedException.noCreds(srvId);
List strings = Arrays.asList(suiteIdList.split(","));
if (strings.isEmpty())
return new SimpleResult("Error: nothing to run");
-final ITeamcity helper =
CtxListener.getTcHelper(context).server(serverId, prov);
+ITcHelper helper = CtxListener.getTcHelper(context);
+
+final ITeamcity teamcity = helper.server(srvId, prov);
boolean queueToTop = top != null && top;
+List buildList = new ArrayList<>();
+
for (String suiteId : strings) {
System.out.println("Triggering [ " + suiteId + "," + branchName +
"," + "top=" + queueToTop + "]");
-helper.triggerBuild(suiteId, branchName, false, queueToTop);
+buildList.add(teamcity.triggerBuild(suiteId, branchName, false,
queueToTop));
}
-return new SimpleResult("OK");
+if (observe != null && observe)
+jiraRes = observeJira(srvId, branchName, ticketId, helper,
teamcity, prov, buildList.toArray(new Build[0]));
Review comment:
Redundant argument `new Build[0]`.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Re-run possible blockers from pr.html
> -
>
> Key: IGNITE-9770
> URL: https://issues.apache.org/jira/browse/IGNITE-9770
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Minor
>
> Show button for re-run possible blockers. Also show merged button with re-run
> possible blockers JIRA, so the user re-run the possible tests and
> does not wait for them to complete,but learn about the completed tests from
> the comment to GitHib.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9449) Lazy unmarshalling of discovery events in TcpDiscovery
[ https://issues.apache.org/jira/browse/IGNITE-9449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16638124#comment-16638124 ] Nikolay Izhikov commented on IGNITE-9449: - Hello, [~yzhdanov] Can you, please, answer, my questions? See it below ^ > Lazy unmarshalling of discovery events in TcpDiscovery > -- > > Key: IGNITE-9449 > URL: https://issues.apache.org/jira/browse/IGNITE-9449 > Project: Ignite > Issue Type: Improvement > Components: cache >Affects Versions: 2.4, 2.5, 2.6 >Reporter: Pavel Kovalenko >Assignee: Nikolay Izhikov >Priority: Major > Fix For: 2.8 > > > Currently disco-msg-worker thread spend major part of time on disocvery > message unmarshalling before send it to the next node. In most cases this is > unnecessary and message can be send immediately after receiving and notyfing > discovery-event-worker. > Responsibility of unmarshalling should moved to discovery-event-worker thread > and this improvement will significantly reduce latency of sending custom > messages across ring. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9769) IgniteCacheAtomicProtocolTest.testPutReaderUpdate1 is flaky
[
https://issues.apache.org/jira/browse/IGNITE-9769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16638083#comment-16638083
]
Ignite TC Bot commented on IGNITE-9769:
---
{panel:title=No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity Run
All|http://ci.ignite.apache.org/viewLog.html?buildId=1991656buildTypeId=IgniteTests24Java8_RunAll]
> IgniteCacheAtomicProtocolTest.testPutReaderUpdate1 is flaky
> ---
>
> Key: IGNITE-9769
> URL: https://issues.apache.org/jira/browse/IGNITE-9769
> Project: Ignite
> Issue Type: Task
>Reporter: Ryabov Dmitrii
>Assignee: Ryabov Dmitrii
>Priority: Trivial
>
> {{IgniteCacheAtomicProtocolTest.testPutReaderUpdate1}} and
> {{IgniteCacheAtomicProtocolTest.testPutReaderUpdate2}} are flaky.
> In the {{#readerUpdateDhtFails}} method we blocks
> {{GridDhtAtomicNearResponse}} messages and do put operation. Put should hangs
> always, but sometimes it doesn't.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-9792) Setting system property IGNITE_MBEANS_DISABLED to true lead to NPE.
[
https://issues.apache.org/jira/browse/IGNITE-9792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Kuznetsov reassigned IGNITE-9792:
Assignee: Alexey Kuznetsov
> Setting system property IGNITE_MBEANS_DISABLED to true lead to NPE.
> ---
>
> Key: IGNITE-9792
> URL: https://issues.apache.org/jira/browse/IGNITE-9792
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
>Priority: Critical
> Fix For: 2.7
>
>
> Javadocs for IGNITE_MBEANS_DISABLED: "This may be helpful if MBeans are not
> allowed e.g. for security reasons."
> So I set in code:
> {code}
> System.setProperty(IgniteSystemProperties.IGNITE_MBEANS_DISABLED, "true")
> {code}
>
> And on node start node failed with NPE:
> {code}
> Caused by: class org.apache.ignite.IgniteCheckedException: Unexpected
> exception when starting grid.
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2079)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1728)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1156)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:676)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:601)
> at org.apache.ignite.Ignition.start(Ignition.java:323)
> ... 3 more
> Caused by: java.lang.NullPointerException: Ouch! Argument cannot be null:
> cfg.getMBeanServer()
> at
> org.apache.ignite.internal.util.GridArgumentCheck.notNull(GridArgumentCheck.java:48)
> at
> org.apache.ignite.internal.IgniteKernal.validateCommon(IgniteKernal.java:1355)
> at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:833)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2033)
> ... 8 more
> {code}
>
> The fix is trivial: in org.apache.ignite.internal.IgniteKernal#validateCommon
> {code}
> if (!U.IGNITE_MBEANS_DISABLED) // <<< The fix
> A.notNull(cfg.getMBeanServer(), "cfg.getMBeanServer()");
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9792) Setting system property IGNITE_MBEANS_DISABLED to true lead to NPE.
[
https://issues.apache.org/jira/browse/IGNITE-9792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Kuznetsov updated IGNITE-9792:
-
Fix Version/s: 2.7
> Setting system property IGNITE_MBEANS_DISABLED to true lead to NPE.
> ---
>
> Key: IGNITE-9792
> URL: https://issues.apache.org/jira/browse/IGNITE-9792
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexey Kuznetsov
>Priority: Critical
> Fix For: 2.7
>
>
> Javadocs for IGNITE_MBEANS_DISABLED: "This may be helpful if MBeans are not
> allowed e.g. for security reasons."
> So I set in code:
> {code}
> System.setProperty(IgniteSystemProperties.IGNITE_MBEANS_DISABLED, "true")
> {code}
>
> And on node start node failed with NPE:
> {code}
> Caused by: class org.apache.ignite.IgniteCheckedException: Unexpected
> exception when starting grid.
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2079)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1728)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1156)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:676)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:601)
> at org.apache.ignite.Ignition.start(Ignition.java:323)
> ... 3 more
> Caused by: java.lang.NullPointerException: Ouch! Argument cannot be null:
> cfg.getMBeanServer()
> at
> org.apache.ignite.internal.util.GridArgumentCheck.notNull(GridArgumentCheck.java:48)
> at
> org.apache.ignite.internal.IgniteKernal.validateCommon(IgniteKernal.java:1355)
> at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:833)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2033)
> ... 8 more
> {code}
>
> The fix is trivial: in org.apache.ignite.internal.IgniteKernal#validateCommon
> {code}
> if (!U.IGNITE_MBEANS_DISABLED) // <<< The fix
> A.notNull(cfg.getMBeanServer(), "cfg.getMBeanServer()");
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-9789) "Starting Demo" message on top of Web console is rendered with delay,
[ https://issues.apache.org/jira/browse/IGNITE-9789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kalinin reassigned IGNITE-9789: - Assignee: Alexander Kalinin (was: Alexey Kuznetsov) > "Starting Demo" message on top of Web console is rendered with delay, > - > > Key: IGNITE-9789 > URL: https://issues.apache.org/jira/browse/IGNITE-9789 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Alexander Kalinin >Assignee: Alexander Kalinin >Priority: Minor > Original Estimate: 1h > Time Spent: 0.5h > Remaining Estimate: 0.5h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9550) Get operation returns null for a lost partition with READ_SAFE policy
[ https://issues.apache.org/jira/browse/IGNITE-9550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-9550: --- Description: See reproduced attached. (was: See reproducer attached.) > Get operation returns null for a lost partition with READ_SAFE policy > - > > Key: IGNITE-9550 > URL: https://issues.apache.org/jira/browse/IGNITE-9550 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.6 >Reporter: Pavel Vinokurov >Assignee: Dmitriy Govorukhin >Priority: Critical > Fix For: 2.7 > > Attachments: PartitionLostReproducer.java > > > See reproduced attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9449) Lazy unmarshalling of discovery events in TcpDiscovery
[ https://issues.apache.org/jira/browse/IGNITE-9449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16638037#comment-16638037 ] Nikolay Izhikov commented on IGNITE-9449: - Hello, [~agoncharuk]. Can you, please, answer, my questions? > Lazy unmarshalling of discovery events in TcpDiscovery > -- > > Key: IGNITE-9449 > URL: https://issues.apache.org/jira/browse/IGNITE-9449 > Project: Ignite > Issue Type: Improvement > Components: cache >Affects Versions: 2.4, 2.5, 2.6 >Reporter: Pavel Kovalenko >Assignee: Nikolay Izhikov >Priority: Major > Fix For: 2.8 > > > Currently disco-msg-worker thread spend major part of time on disocvery > message unmarshalling before send it to the next node. In most cases this is > unnecessary and message can be send immediately after receiving and notyfing > discovery-event-worker. > Responsibility of unmarshalling should moved to discovery-event-worker thread > and this improvement will significantly reduce latency of sending custom > messages across ring. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9550) Get operation returns null for a lost partition with READ_SAFE policy
[ https://issues.apache.org/jira/browse/IGNITE-9550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-9550: - Description: See reproducer attached. > Get operation returns null for a lost partition with READ_SAFE policy > - > > Key: IGNITE-9550 > URL: https://issues.apache.org/jira/browse/IGNITE-9550 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.6 >Reporter: Pavel Vinokurov >Assignee: Dmitriy Govorukhin >Priority: Critical > Fix For: 2.7 > > Attachments: PartitionLostReproducer.java > > > See reproducer attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9789) "Starting Demo" message on top of Web console is rendered with delay,
[ https://issues.apache.org/jira/browse/IGNITE-9789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kalinin reassigned IGNITE-9789: - Assignee: Alexey Kuznetsov (was: Alexander Kalinin) The best solution to get rid of blinking found so far is to remove bold text. > "Starting Demo" message on top of Web console is rendered with delay, > - > > Key: IGNITE-9789 > URL: https://issues.apache.org/jira/browse/IGNITE-9789 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Alexander Kalinin >Assignee: Alexey Kuznetsov >Priority: Minor > Original Estimate: 1h > Remaining Estimate: 1h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-1023) Need to add more information for startNodes at cmd visor.
[ https://issues.apache.org/jira/browse/IGNITE-1023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16637966#comment-16637966 ] Pavel Konstantinov commented on IGNITE-1023: Re-tested. > Need to add more information for startNodes at cmd visor. > - > > Key: IGNITE-1023 > URL: https://issues.apache.org/jira/browse/IGNITE-1023 > Project: Ignite > Issue Type: Task > Components: visor >Reporter: Artem Shutak >Assignee: Pavel Konstantinov >Priority: Major > Fix For: 2.7 > > Attachments: > #_IGNITE-1023_Additional_information_about_start_node_command.patch, > #_IGNITE-1023_Fixed_reading_of_an_empty_environment_variable.patch > > > See > http://apache-ignite-users.70518.x6.nabble.com/Topology-Specification-INI-td467.html > TODO: > - add note about where to find ignite-startNodes logs > - Successful start attempts - means nothing > - describe ini-file format file > - '-s' option - is it mandatory. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8477) Web console: duration is empty
[ https://issues.apache.org/jira/browse/IGNITE-8477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-8477: Fix Version/s: 2.7 > Web console: duration is empty > -- > > Key: IGNITE-8477 > URL: https://issues.apache.org/jira/browse/IGNITE-8477 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Alexander Kalinin >Priority: Major > Fix For: 2.7 > > Attachments: screenshot-1.png > > > !screenshot-1.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
