[jira] [Assigned] (IGNITE-9118) Web console: something wrong with Load balancing configuration
[ https://issues.apache.org/jira/browse/IGNITE-9118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov reassigned IGNITE-9118: Assignee: Vasiliy Sisko (was: Alexey Kuznetsov) > Web console: something wrong with Load balancing configuration > -- > > Key: IGNITE-9118 > URL: https://issues.apache.org/jira/browse/IGNITE-9118 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Vasiliy Sisko >Priority: Minor > Fix For: 2.7 > > Attachments: screenshot-1.png > > > Please see attachment > !screenshot-1.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9118) Web console: something wrong with Load balancing configuration
[ https://issues.apache.org/jira/browse/IGNITE-9118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov updated IGNITE-9118: --- Description: Please see attachment !screenshot-1.png! was:Please see attachment > Web console: something wrong with Load balancing configuration > -- > > Key: IGNITE-9118 > URL: https://issues.apache.org/jira/browse/IGNITE-9118 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Priority: Minor > Fix For: 2.7 > > Attachments: screenshot-1.png > > > Please see attachment > !screenshot-1.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9118) Web console: something wrong with Load balancing configuration
[ https://issues.apache.org/jira/browse/IGNITE-9118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov reassigned IGNITE-9118: -- Assignee: Alexey Kuznetsov > Web console: something wrong with Load balancing configuration > -- > > Key: IGNITE-9118 > URL: https://issues.apache.org/jira/browse/IGNITE-9118 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Alexey Kuznetsov >Priority: Minor > Fix For: 2.7 > > Attachments: screenshot-1.png > > > Please see attachment > !screenshot-1.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9118) Web console: something wrong with Load balancing configuration
[ https://issues.apache.org/jira/browse/IGNITE-9118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov updated IGNITE-9118: --- Fix Version/s: 2.7 > Web console: something wrong with Load balancing configuration > -- > > Key: IGNITE-9118 > URL: https://issues.apache.org/jira/browse/IGNITE-9118 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Alexey Kuznetsov >Priority: Minor > Fix For: 2.7 > > Attachments: screenshot-1.png > > > Please see attachment > !screenshot-1.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9118) Web console: something wrong with Load balancing configuration
[ https://issues.apache.org/jira/browse/IGNITE-9118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov updated IGNITE-9118: --- Attachment: screenshot-1.png > Web console: something wrong with Load balancing configuration > -- > > Key: IGNITE-9118 > URL: https://issues.apache.org/jira/browse/IGNITE-9118 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Priority: Minor > Fix For: 2.7 > > Attachments: screenshot-1.png > > > Please see attachment -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9118) Web console: something wrong with Load balancing configuration
Pavel Konstantinov created IGNITE-9118: -- Summary: Web console: something wrong with Load balancing configuration Key: IGNITE-9118 URL: https://issues.apache.org/jira/browse/IGNITE-9118 Project: Ignite Issue Type: Bug Components: wizards Reporter: Pavel Konstantinov Please see attchment -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9118) Web console: something wrong with Load balancing configuration
[ https://issues.apache.org/jira/browse/IGNITE-9118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov updated IGNITE-9118: --- Description: Please see attachment (was: Please see attchment) > Web console: something wrong with Load balancing configuration > -- > > Key: IGNITE-9118 > URL: https://issues.apache.org/jira/browse/IGNITE-9118 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Priority: Minor > > Please see attachment -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8915) NPE during executing local SqlQuery from client node
[
https://issues.apache.org/jira/browse/IGNITE-8915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16561119#comment-16561119
]
Stanilovsky Evgeny commented on IGNITE-8915:
[~NIzhikov], thanks, is it works properly well for LOCAL cache created on
client side too?
> NPE during executing local SqlQuery from client node
>
>
> Key: IGNITE-8915
> URL: https://issues.apache.org/jira/browse/IGNITE-8915
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Vyacheslav Daradur
>Assignee: Nikolay Izhikov
>Priority: Major
> Fix For: 2.7
>
> Attachments: IgniteCacheReplicatedClientLocalQuerySelfTest.java
>
>
> NPE when trying to execute {{SqlQuery}} with {{setLocal(true)}} from client
> node.
> [Reproducer|^IgniteCacheReplicatedClientLocalQuerySelfTest.java].
> UPD:
> Right behavior:
> Local query should be forbidden and a sensible exception should be thrown if
> it is executed on client node.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IGNITE-9117) Need to log GridReduceQueryExecutor#query long execution
[ https://issues.apache.org/jira/browse/IGNITE-9117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgenii Zagumennov resolved IGNITE-9117. Resolution: Duplicate > Need to log GridReduceQueryExecutor#query long execution > > > Key: IGNITE-9117 > URL: https://issues.apache.org/jira/browse/IGNITE-9117 > Project: Ignite > Issue Type: Improvement > Components: compute, sql >Reporter: Evgenii Zagumennov >Priority: Major > > In case of long query execution *GridReduceQueryExecutor.query()* should log > the root cause and throw an exception by timeout. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9117) Need to log GridReduceQueryExecutor#query long execution
Evgenii Zagumennov created IGNITE-9117: -- Summary: Need to log GridReduceQueryExecutor#query long execution Key: IGNITE-9117 URL: https://issues.apache.org/jira/browse/IGNITE-9117 Project: Ignite Issue Type: Improvement Components: compute, sql Reporter: Evgenii Zagumennov In case of long query execution *GridReduceQueryExecutor.query()* should log the root cause and throw an exception by timeout. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-7783) Thin Client lib: PHP
[ https://issues.apache.org/jira/browse/IGNITE-7783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kosenchuk reassigned IGNITE-7783: Assignee: ekaterina.vergizova (was: Alexey Kosenchuk) > Thin Client lib: PHP > > > Key: IGNITE-7783 > URL: https://issues.apache.org/jira/browse/IGNITE-7783 > Project: Ignite > Issue Type: New Feature > Components: thin client >Reporter: Alexey Kosenchuk >Assignee: ekaterina.vergizova >Priority: Major > > Implement Thin (lightweight) Client lib in PHP programming language for > Ignite Binary Client Protocol. > Functionality: > -- > Support all operations of the Ignite Binary Client Protocol 2.6: > [https://apacheignite.readme.io/v2.6/docs/binary-client-protocol] > Except the following features which are not applicable to PHP client: > - Filter object for OP_QUERY_SCAN operation (OP_QUERY_SCAN operation itself > will be supported). > - OP_REGISTER_BINARY_TYPE_NAME and OP_GET_BINARY_TYPE_NAME operations. > - Registration of a new Ignite Enum type (reading and writing items of the > existing Ignite Enum types will be supported). > Additionally support: > - SSL/TLS connection. > - "Failover re-connection algorithm": > https://issues.apache.org/jira/browse/IGNITE-7282 > Ignite Binary Client Protocol handshake versions: 1.1.0 only. > Minimal required PHP version: 7.2 > [http://php.net/supported-versions.php] > PHP code-style standards: [https://www.php-fig.org/psr/] > Synchronous API will be supported (asynchronous operations are not supported > by the standard PHP). > The API will not be thread-safe (threads are not available in the standard > PHP; pthreads extension is not available for the latest PHP version; > thread-safety is possible to support by an application). > Examples: > - > The set of examples will cover: > - cache get/create/destroy operations > - cache put/get operations > - SQL operations (create table/index, insert/select/drop) > - SQL Fields query and Scan query > - Authentication and TLS connection > - working with primitive and complex data types > Tests: > -- > PHPUnit tests [https://phpunit.de|https://phpunit.de/] for all API methods > and all basic features. Including simple tests to start examples. > Tests will be integrated into the TeamCity with the help from the community. > Docs: > -- > The provided docs will include: > - Auto-generated API spec using Doxygen: > [http://www.doxygen.org|http://www.doxygen.org/] > - Instruction how to generate the API spec. > - Instruction how to release PHP library on Packagist: > [https://packagist.org/] > - Readme for user with info how to install and use the client. > - Simple instruction how to setup/run examples. > - Simple instruction how to setup/run tests. > All docs will be provided separately from the source code and will not be > merged to the target repository. Before the release all instructions and > readme will be moved to the readme.io with the help from the community. > Release: > > Location of the client: > /modules/platforms/php > Will be released as PHP library on Packagist: [https://packagist.org/] by the > community. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7783) Thin Client lib: PHP
[ https://issues.apache.org/jira/browse/IGNITE-7783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kosenchuk updated IGNITE-7783: - Description: Implement Thin (lightweight) Client lib in PHP programming language for Ignite Binary Client Protocol. Functionality: -- Support all operations of the Ignite Binary Client Protocol 2.6: [https://apacheignite.readme.io/v2.6/docs/binary-client-protocol] Except the following features which are not applicable to PHP client: - Filter object for OP_QUERY_SCAN operation (OP_QUERY_SCAN operation itself will be supported). - OP_REGISTER_BINARY_TYPE_NAME and OP_GET_BINARY_TYPE_NAME operations. - Registration of a new Ignite Enum type (reading and writing items of the existing Ignite Enum types will be supported). Additionally support: - SSL/TLS connection. - "Failover re-connection algorithm": https://issues.apache.org/jira/browse/IGNITE-7282 Ignite Binary Client Protocol handshake versions: 1.1.0 only. Minimal required PHP version: 7.2 [http://php.net/supported-versions.php] PHP code-style standards: [https://www.php-fig.org/psr/] Synchronous API will be supported (asynchronous operations are not supported by the standard PHP). The API will not be thread-safe (threads are not available in the standard PHP; pthreads extension is not available for the latest PHP version; thread-safety is possible to support by an application). Examples: - The set of examples will cover: - cache get/create/destroy operations - cache put/get operations - SQL operations (create table/index, insert/select/drop) - SQL Fields query and Scan query - Authentication and TLS connection - working with primitive and complex data types Tests: -- PHPUnit tests [https://phpunit.de|https://phpunit.de/] for all API methods and all basic features. Including simple tests to start examples. Tests will be integrated into the TeamCity with the help from the community. Docs: -- The provided docs will include: - Auto-generated API spec using Doxygen: [http://www.doxygen.org|http://www.doxygen.org/] - Instruction how to generate the API spec. - Instruction how to release PHP library on Packagist: [https://packagist.org/] - Readme for user with info how to install and use the client. - Simple instruction how to setup/run examples. - Simple instruction how to setup/run tests. All docs will be provided separately from the source code and will not be merged to the target repository. Before the release all instructions and readme will be moved to the readme.io with the help from the community. Release: Location of the client: /modules/platforms/php Will be released as PHP library on Packagist: [https://packagist.org/] by the community. was: Implement Thin (lightweight) Client lib in PHP programming language for Ignite Binary Client Protocol. Functionality: -- Support all operations of the Ignite Binary Client Protocol 2.6: [https://apacheignite.readme.io/v2.6/docs/binary-client-protocol] Except the following features which are not applicable to PHP client: - Filter object for OP_QUERY_SCAN operation (OP_QUERY_SCAN operation itself will be supported). - OP_REGISTER_BINARY_TYPE_NAME and OP_GET_BINARY_TYPE_NAME operations. - Registration of a new Ignite Enum type (reading and writing items of the existing Ignite Enum types will be supported). Additionally support: - SSL/TLS connection. - "Failover re-connection algorithm": https://issues.apache.org/jira/browse/IGNITE-7282 Ignite Binary Client Protocol handshake versions: 1.1.0 only. Minimal required PHP version: 7.2 [http://php.net/supported-versions.php] PHP code-style standards: [https://www.php-fig.org/psr/] Synchronous API will be supported. The API will not be thread-safe. Examples: - The set of examples will cover: - cache get/create/destroy operations - cache put/get operations - SQL operations (create table/index, insert/select/drop) - SQL Fields query and Scan query - Authentication and TLS connection - working with primitive and complex data types Tests: -- PHPUnit tests [https://phpunit.de|https://phpunit.de/] for all API methods and all basic features. Including simple tests to start examples. Tests will be integrated into the TeamCity with the help from the community. Docs: -- The provided docs will include: - Auto-generated API spec using Doxygen: [http://www.doxygen.org|http://www.doxygen.org/] - Instruction how to generate the API spec. - Instruction how to release PHP library on Packagist: [https://packagist.org/] - Readme for user with info how to install and use the client. - Simple instruction how to setup/run examples. - Simple instruction how to setup/run tests. All docs will be provided separately from the source code and will not be merged to the target repository. Before the release all instructions
[jira] [Updated] (IGNITE-7783) Thin Client lib: PHP
[ https://issues.apache.org/jira/browse/IGNITE-7783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kosenchuk updated IGNITE-7783: - Description: Implement Thin (lightweight) Client lib in PHP programming language for Ignite Binary Client Protocol. Functionality: -- Support all operations of the Ignite Binary Client Protocol 2.6: [https://apacheignite.readme.io/v2.6/docs/binary-client-protocol] Except the following features which are not applicable to PHP client: - Filter object for OP_QUERY_SCAN operation (OP_QUERY_SCAN operation itself will be supported). - OP_REGISTER_BINARY_TYPE_NAME and OP_GET_BINARY_TYPE_NAME operations. - Registration of a new Ignite Enum type (reading and writing items of the existing Ignite Enum types will be supported). Additionally support: - SSL/TLS connection. - "Failover re-connection algorithm": https://issues.apache.org/jira/browse/IGNITE-7282 Ignite Binary Client Protocol handshake versions: 1.1.0 only. Minimal required PHP version: 7.2 [http://php.net/supported-versions.php] PHP code-style standards: [https://www.php-fig.org/psr/] Synchronous API will be supported. The API will not be thread-safe. Examples: - The set of examples will cover: - cache get/create/destroy operations - cache put/get operations - SQL operations (create table/index, insert/select/drop) - SQL Fields query and Scan query - Authentication and TLS connection - working with primitive and complex data types Tests: -- PHPUnit tests [https://phpunit.de|https://phpunit.de/] for all API methods and all basic features. Including simple tests to start examples. Tests will be integrated into the TeamCity with the help from the community. Docs: -- The provided docs will include: - Auto-generated API spec using Doxygen: [http://www.doxygen.org|http://www.doxygen.org/] - Instruction how to generate the API spec. - Instruction how to release PHP library on Packagist: [https://packagist.org/] - Readme for user with info how to install and use the client. - Simple instruction how to setup/run examples. - Simple instruction how to setup/run tests. All docs will be provided separately from the source code and will not be merged to the target repository. Before the release all instructions and readme will be moved to the readme.io with the help from the community. Release: Location of the client: /modules/platforms/php Will be released as PHP library on Packagist: [https://packagist.org/] by the community. was: Implement Thin (lightweight) Client lib in PHP programming language for Ignite Binary Client Protocol. Functionality: -- Support all operations of the Ignite Binary Client Protocol 2.6: [https://apacheignite.readme.io/v2.6/docs/binary-client-protocol] Except: - Filter object for OP_QUERY_SCAN operation (OP_QUERY_SCAN operation itself will be supported). - OP_REGISTER_BINARY_TYPE_NAME and OP_GET_BINARY_TYPE_NAME operations. - Registration of a new Ignite Enum type (reading and writing items of the existing Ignite Enum types will be supported). Additionally support: - SSL/TLS connection. - "Failover re-connection algorithm": https://issues.apache.org/jira/browse/IGNITE-7282 Ignite Binary Client Protocol handshake versions: 1.1.0 only. Minimal PHP version: 7.2 PHP code-style standards: [https://www.php-fig.org/psr/] Synchronous API will be supported. The API will not be thread-safe. Examples: - The set of examples will cover: - cache get/create/destroy operations - cache put/get operations - SQL operations (create table/index, insert/select/drop) - SQL Fields query and Scan query - Authentication and TLS connection - working with primitive and complex data types Tests: -- PHPUnit tests [https://phpunit.de|https://phpunit.de/] for all API methods and all basic features. Including simple tests to start examples. Tests will be integrated into the TeamCity with the help from the community. Docs: -- The provided docs will include: - Auto-generated API spec using Doxygen: [http://www.doxygen.org|http://www.doxygen.org/] - Instruction how to generate the API spec. - Instruction how to release PHP library on Packagist: [https://packagist.org/] - Readme for user with info how to install and use the client. - Simple instruction how to setup/run examples. - Simple instruction how to setup/run tests. All docs will be provided separately from the source code and will not be merged to the target repository. Before the release all instructions and readme will be moved to the readme.io with the help from the community. Release: Location of the client: /modules/platforms/php Will be released as PHP library on Packagist: [https://packagist.org/] by the community. > Thin Client lib: PHP > > > Key: IGNITE-7783 > URL:
[jira] [Commented] (IGNITE-7165) Re-balancing is cancelled if client node joins
[
https://issues.apache.org/jira/browse/IGNITE-7165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16561092#comment-16561092
]
Maxim Muzafarov commented on IGNITE-7165:
-
h5. Changes ready
* TC: [#3025 (27 Jul 18
20:00)|https://ci.ignite.apache.org/viewLog.html?buildId=1554633=buildResultsDiv=IgniteTests24Java8_RunAll]
* PR: [#4442|https://github.com/apache/ignite/pull/4442]
* Upsource:
[IGNT-CR-699|https://reviews.ignite.apache.org/ignite/review/IGNT-CR-699]
h5. Implementation details
# _Keep rebalance version_
Now it's not the last affinity topology version. To calculate affinity
assignment difference with the last topology version we should save version on
which rebalance is being currently running. Keep it in exchange thread.
# _{{LEFT\FAIL}} events triggers rebalance_
Each cache group have collection of supplier nodes to be retrieved for
partitions -- {{Map<> remaining}}. If some nodes of this collection
{{LEFT\FAIL}} cluster, rebalance must be restarted.
# _{{onLocalJoin}} event triggers rebalance_
Partition state changed OWNING → MOVING on coordinator due to obsolete
partititon update counter. Coordinator performs PME and after megre all
SingleMessages marks partitions with obsolete update sequence to be demanded
from remote nodes (by change OWNING -> MOVING partition state).
# _{{empty}} affinity history triggers rebalance_
Cache group can be started much later (not at local join event). So, this
cache group wouldn't have affinity history to compare with latest affinity.
# _Clear suppy contex map changed_
Previously, supply context map have been cleared after each topology version
change occurs. Since we can preform rebalance not on the latest topology
version this behavior should be changed. Clear context only for nodes
left\failed from topology.
# _topologyChanged() method new condition_
PME prepares partition to be {{RENTED}} or {{EVICTED}} if they are not assign
on local node regarding new affinity calculation. Processing stale supply
message (on previous versions) can lead to exceptions with getting partitions
on local node with incorrect state. Thats why stale
{{GridDhtPartitionSupplyMessage}} must be ignored by {{Demander}}.
# _REPLICATED cache processing_
Affinity assignment for this type of cache groups always not changed.
> Re-balancing is cancelled if client node joins
> --
>
> Key: IGNITE-7165
> URL: https://issues.apache.org/jira/browse/IGNITE-7165
> Project: Ignite
> Issue Type: Bug
>Reporter: Mikhail Cherkasov
>Assignee: Maxim Muzafarov
>Priority: Critical
> Labels: rebalance
> Fix For: 2.7
>
>
> Re-balancing is canceled if client node joins. Re-balancing can take hours
> and each time when client node joins it starts again:
> [15:10:05,700][INFO][disco-event-worker-#61%statement_grid%][GridDiscoveryManager]
> Added new node to topology: TcpDiscoveryNode
> [id=979cf868-1c37-424a-9ad1-12db501f32ef, addrs=[0:0:0:0:0:0:0:1, 127.0.0.1,
> 172.31.16.213], sockAddrs=[/0:0:0:0:0:0:0:1:0, /127.0.0.1:0,
> /172.31.16.213:0], discPort=0, order=36, intOrder=24,
> lastExchangeTime=1512907805688, loc=false, ver=2.3.1#20171129-sha1:4b1ec0fe,
> isClient=true]
> [15:10:05,701][INFO][disco-event-worker-#61%statement_grid%][GridDiscoveryManager]
> Topology snapshot [ver=36, servers=7, clients=5, CPUs=128, heap=160.0GB]
> [15:10:05,702][INFO][exchange-worker-#62%statement_grid%][time] Started
> exchange init [topVer=AffinityTopologyVersion [topVer=36, minorTopVer=0],
> crd=false, evt=NODE_JOINED, evtNode=979cf868-1c37-424a-9ad1-12db501f32ef,
> customEvt=null, allowMerge=true]
> [15:10:05,702][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionsExchangeFuture]
> Finish exchange future [startVer=AffinityTopologyVersion [topVer=36,
> minorTopVer=0], resVer=AffinityTopologyVersion [topVer=36, minorTopVer=0],
> err=null]
> [15:10:05,702][INFO][exchange-worker-#62%statement_grid%][time] Finished
> exchange init [topVer=AffinityTopologyVersion [topVer=36, minorTopVer=0],
> crd=false]
> [15:10:05,703][INFO][exchange-worker-#62%statement_grid%][GridCachePartitionExchangeManager]
> Skipping rebalancing (nothing scheduled) [top=AffinityTopologyVersion
> [topVer=36, minorTopVer=0], evt=NODE_JOINED,
> node=979cf868-1c37-424a-9ad1-12db501f32ef]
> [15:10:08,706][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander]
> Cancelled rebalancing from all nodes [topology=AffinityTopologyVersion
> [topVer=35, minorTopVer=0]]
> [15:10:08,707][INFO][exchange-worker-#62%statement_grid%][GridCachePartitionExchangeManager]
> Rebalancing scheduled [order=[statementp]]
> [15:10:08,707][INFO][exchange-worker-#62%statement_grid%][GridCachePartitionExchangeManager]
> Rebalancing started [top=null, evt=NODE_JOINED,
>
[jira] [Issue Comment Deleted] (IGNITE-7165) Re-balancing is cancelled if client node joins
[
https://issues.apache.org/jira/browse/IGNITE-7165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-7165:
Comment: was deleted
(was: h5. Changes ready
* TC:
* PR: [#4442|https://github.com/apache/ignite/pull/4442]
* Upsource:
[IGNT-CR-699|https://reviews.ignite.apache.org/ignite/review/IGNT-CR-699]
h5. Implementation details
# _Keep topology version to rebalance (now it's not the last topology version)_
To calculate affinity assignment difference with the last topology version we
should save version on which rebalance is being currently running.
# _REPLICATED cache processing_
Affinity assignment for this type of cache always not changed. We don't need
to stop rebalance for this cache each time new topology version arrived.
Rebalance should be run only once, except situations when nodes {{LEFT}} or
{{FAIL}} cluster from which cache partition being demanded for this group.
# _EMPTY assignments handling_
Each time {{generateAssignments}} method determind no difference with current
topology version (return empty map) no matter how affinity changed we should
return successfull result as fast as possible.
# _RENTING\EVICTING partiton after PME_
PME prepares partition to be {{RENTED}} or {{EVICTED}} if they are not assign
on local node regarding new affinity calculation. Processing stale supply
message (on previous versions) can lead to exceptions with getting partitions
on local node with incorrect state. Thats why stale
{{GridDhtPartitionSupplyMessage}} must be ignored by {{Demander}}.
# _Clear suppy contex map changed_
Previously, supply context map have been cleared after each topology version
change occurs. Since we can preform rebalance not on the latest topology
version this behavior should be changed. Clear context only for nodes
left\failed from topology.
# _{{LEFT}} or {{FAIL}} nodes from cluster (rebalance restart)_
If rebalance future demand partitions from nodes which have left the cluster
rebalance must be restarted.
# _OWNING → MOVING on coordinator due to obsolete partititon update counter_
Affinity assingment can have no chanes and rebalance is currently running.
Coordinator performs PME and after megre all SingleMessages marks partitions
with obsolete update sequence to be demanded from remote nodes (by change
OWNING -> MOVING partition state). We should schedule new rebalance in this
case.)
> Re-balancing is cancelled if client node joins
> --
>
> Key: IGNITE-7165
> URL: https://issues.apache.org/jira/browse/IGNITE-7165
> Project: Ignite
> Issue Type: Bug
>Reporter: Mikhail Cherkasov
>Assignee: Maxim Muzafarov
>Priority: Critical
> Labels: rebalance
> Fix For: 2.7
>
>
> Re-balancing is canceled if client node joins. Re-balancing can take hours
> and each time when client node joins it starts again:
> [15:10:05,700][INFO][disco-event-worker-#61%statement_grid%][GridDiscoveryManager]
> Added new node to topology: TcpDiscoveryNode
> [id=979cf868-1c37-424a-9ad1-12db501f32ef, addrs=[0:0:0:0:0:0:0:1, 127.0.0.1,
> 172.31.16.213], sockAddrs=[/0:0:0:0:0:0:0:1:0, /127.0.0.1:0,
> /172.31.16.213:0], discPort=0, order=36, intOrder=24,
> lastExchangeTime=1512907805688, loc=false, ver=2.3.1#20171129-sha1:4b1ec0fe,
> isClient=true]
> [15:10:05,701][INFO][disco-event-worker-#61%statement_grid%][GridDiscoveryManager]
> Topology snapshot [ver=36, servers=7, clients=5, CPUs=128, heap=160.0GB]
> [15:10:05,702][INFO][exchange-worker-#62%statement_grid%][time] Started
> exchange init [topVer=AffinityTopologyVersion [topVer=36, minorTopVer=0],
> crd=false, evt=NODE_JOINED, evtNode=979cf868-1c37-424a-9ad1-12db501f32ef,
> customEvt=null, allowMerge=true]
> [15:10:05,702][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionsExchangeFuture]
> Finish exchange future [startVer=AffinityTopologyVersion [topVer=36,
> minorTopVer=0], resVer=AffinityTopologyVersion [topVer=36, minorTopVer=0],
> err=null]
> [15:10:05,702][INFO][exchange-worker-#62%statement_grid%][time] Finished
> exchange init [topVer=AffinityTopologyVersion [topVer=36, minorTopVer=0],
> crd=false]
> [15:10:05,703][INFO][exchange-worker-#62%statement_grid%][GridCachePartitionExchangeManager]
> Skipping rebalancing (nothing scheduled) [top=AffinityTopologyVersion
> [topVer=36, minorTopVer=0], evt=NODE_JOINED,
> node=979cf868-1c37-424a-9ad1-12db501f32ef]
> [15:10:08,706][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander]
> Cancelled rebalancing from all nodes [topology=AffinityTopologyVersion
> [topVer=35, minorTopVer=0]]
> [15:10:08,707][INFO][exchange-worker-#62%statement_grid%][GridCachePartitionExchangeManager]
> Rebalancing scheduled [order=[statementp]]
>
[jira] [Commented] (IGNITE-584) Need to make sure that scan query returns consistent results on topology changes
[ https://issues.apache.org/jira/browse/IGNITE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16561057#comment-16561057 ] Stanilovsky Evgeny commented on IGNITE-584: --- i remove suspicious optimization backups > 0, rerun TC (linked above). > Need to make sure that scan query returns consistent results on topology > changes > > > Key: IGNITE-584 > URL: https://issues.apache.org/jira/browse/IGNITE-584 > Project: Ignite > Issue Type: Sub-task > Components: data structures >Affects Versions: 1.9, 2.0, 2.1 >Reporter: Artem Shutak >Assignee: Stanilovsky Evgeny >Priority: Major > Labels: MakeTeamcityGreenAgain, Muted_test > Fix For: 2.7 > > Attachments: tc1.png > > > Consistent results on topology changes was implemented for sql queries, but > looks like it still does not work for scan queries. > This affects 'cache set' tests since set uses scan query for set iteration > (to be unmuted on TC): > GridCacheSetAbstractSelfTest testNodeJoinsAndLeaves and > testNodeJoinsAndLeavesCollocated; > Also see todos here GridCacheSetFailoverAbstractSelfTest -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-8939) Transaction string reprsentation unhandled exception
[
https://issues.apache.org/jira/browse/IGNITE-8939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Evgenii Zagumennov reassigned IGNITE-8939:
--
Assignee: Stanilovsky Evgeny (was: Evgenii Zagumennov)
> Transaction string reprsentation unhandled exception
>
>
> Key: IGNITE-8939
> URL: https://issues.apache.org/jira/browse/IGNITE-8939
> Project: Ignite
> Issue Type: Bug
> Components: binary
>Reporter: Evgenii Zagumennov
>Assignee: Stanilovsky Evgeny
>Priority: Major
>
> IgniteTxHandler.finishDhtLocal() (IgniteTxHandler.java:957)
> {code:java}
> U.error(log, "Failed completing transaction [commit=" + req.commit() + ",
> tx=" + *tx* + ']', e);{code}
> tx.toString() can lead to excepion (in GridToStringBuilder.toStringImpl()),
> and original exception in transaction will be lost. We need to log original
> exception and catch probable tx.toString() exception.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
