[jira] [Updated] (IGNITE-13662) Discribe soLinger setting in TCP Discovery and SSL issues.
[ https://issues.apache.org/jira/browse/IGNITE-13662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Steshin updated IGNITE-13662: -- Ignite Flags: (was: Docs Required) > Discribe soLinger setting in TCP Discovery and SSL issues. > -- > > Key: IGNITE-13662 > URL: https://issues.apache.org/jira/browse/IGNITE-13662 > Project: Ignite > Issue Type: Improvement > Components: documentation >Affects Versions: 2.9, 2.8.1 >Reporter: Vladimir Steshin >Assignee: Vladimir Steshin >Priority: Minor > Fix For: 2.10 > > > Discribe soLinger setting in TCP Discovery and SSL issues. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13662) Discribe soLinger setting in TCP Discovery and SSL issues.
[ https://issues.apache.org/jira/browse/IGNITE-13662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Steshin updated IGNITE-13662: -- Component/s: documentation > Discribe soLinger setting in TCP Discovery and SSL issues. > -- > > Key: IGNITE-13662 > URL: https://issues.apache.org/jira/browse/IGNITE-13662 > Project: Ignite > Issue Type: Improvement > Components: documentation >Affects Versions: 2.9, 2.8.1 >Reporter: Vladimir Steshin >Assignee: Vladimir Steshin >Priority: Minor > Fix For: 2.10 > > > Discribe soLinger setting in TCP Discovery and SSL issues. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13662) Discribe soLinger setting in TCP Discovery and SSL issues.
[ https://issues.apache.org/jira/browse/IGNITE-13662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Steshin updated IGNITE-13662: -- Ignite Flags: Docs Required (was: Docs Required,Release Notes Required) > Discribe soLinger setting in TCP Discovery and SSL issues. > -- > > Key: IGNITE-13662 > URL: https://issues.apache.org/jira/browse/IGNITE-13662 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.9, 2.8.1 >Reporter: Vladimir Steshin >Assignee: Vladimir Steshin >Priority: Minor > Fix For: 2.10 > > > Discribe soLinger setting in TCP Discovery and SSL issues. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13643) Disable socket linger dy default in Tcp Discovery Spi
[ https://issues.apache.org/jira/browse/IGNITE-13643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Steshin updated IGNITE-13643: -- Ignite Flags: Release Notes Required (was: Docs Required,Release Notes Required) > Disable socket linger dy default in Tcp Discovery Spi > - > > Key: IGNITE-13643 > URL: https://issues.apache.org/jira/browse/IGNITE-13643 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.9, 2.8.1 >Reporter: Vladimir Steshin >Assignee: Vladimir Steshin >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Current IgniteUtils.closeQuiet(@Nullable Socket sock) can take about 5sec to > close socket. This violates node detection failure. Despite we set > failureDetectionTiemout == 1000, node failure is detected within 6.5 secs in > average. > This time gap was unearther by a discovery integration test on ducktape [1]. > Failure detection timeout is set to 1000ms. > Typical results before the fix for 1 node: > "Detection of node(s) failure (ms)": 6140, "All detection delays (ms):": > "[6140]", "Nodes failed": 1} > Typical results after the fix for 1 node: > "Detection of node(s) failure (ms)": 1034, "All detection delays (ms):": > "[1034]", "Nodes failed": 1} > There is note that 'graceful' socket closing was made to workaround bag in > OpenJDK12 [2]. But as I see it has been fixed. Also, there were SSL issues > like [3] and [4]. > There are various fixes in modern versions of various JDK, supporting TLS 1.3 > ([6]). OpenJDK11 works well as far as I know. > I believe, SSL in discovery is rare in usage. This slows down performance. > With the issues, one could just enable soLiger or update the JDK. There is no > reason to affect all users by default. > [1] > https://github.com/apache/ignite/blob/ignite-ducktape/modules/ducktests/tests/ignitetest/tests/discovery_test.py > [2] https://bugs.openjdk.java.net/browse/JDK-8219658 > [3] https://issues.apache.org/jira/browse/IGNITE-12818 > [4] https://issues.apache.org/jira/browse/IGNITE-11288 > [5] https://bugs.openjdk.java.net/browse/JDK-8245468 > [6] https://www.oracle.com/java/technologies/javase/8u261-relnotes.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13662) Discribe soLinger setting in TCP Discovery and SSL issues.
[ https://issues.apache.org/jira/browse/IGNITE-13662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Steshin updated IGNITE-13662: -- Affects Version/s: 2.9 2.8.1 > Discribe soLinger setting in TCP Discovery and SSL issues. > -- > > Key: IGNITE-13662 > URL: https://issues.apache.org/jira/browse/IGNITE-13662 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.9, 2.8.1 >Reporter: Vladimir Steshin >Assignee: Vladimir Steshin >Priority: Minor > Fix For: 2.10 > > > Discribe soLinger setting in TCP Discovery and SSL issues. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13625) Make network timeout rely on failureDetectionTimeout in TcpDiscovery
[ https://issues.apache.org/jira/browse/IGNITE-13625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Steshin updated IGNITE-13625: -- Ignite Flags: Release Notes Required (was: Docs Required,Release Notes Required) > Make network timeout rely on failureDetectionTimeout in TcpDiscovery > > > Key: IGNITE-13625 > URL: https://issues.apache.org/jira/browse/IGNITE-13625 > Project: Ignite > Issue Type: Improvement >Reporter: Vladimir Steshin >Assignee: Vladimir Steshin >Priority: Minor > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13643) Disable socket linger dy default in Tcp Discovery Spi
[ https://issues.apache.org/jira/browse/IGNITE-13643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Steshin updated IGNITE-13643: -- Affects Version/s: 2.9 2.8.1 > Disable socket linger dy default in Tcp Discovery Spi > - > > Key: IGNITE-13643 > URL: https://issues.apache.org/jira/browse/IGNITE-13643 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.9, 2.8.1 >Reporter: Vladimir Steshin >Assignee: Vladimir Steshin >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Current IgniteUtils.closeQuiet(@Nullable Socket sock) can take about 5sec to > close socket. This violates node detection failure. Despite we set > failureDetectionTiemout == 1000, node failure is detected within 6.5 secs in > average. > This time gap was unearther by a discovery integration test on ducktape [1]. > Failure detection timeout is set to 1000ms. > Typical results before the fix for 1 node: > "Detection of node(s) failure (ms)": 6140, "All detection delays (ms):": > "[6140]", "Nodes failed": 1} > Typical results after the fix for 1 node: > "Detection of node(s) failure (ms)": 1034, "All detection delays (ms):": > "[1034]", "Nodes failed": 1} > There is note that 'graceful' socket closing was made to workaround bag in > OpenJDK12 [2]. But as I see it has been fixed. Also, there were SSL issues > like [3] and [4]. > There are various fixes in modern versions of various JDK, supporting TLS 1.3 > ([6]). OpenJDK11 works well as far as I know. > I believe, SSL in discovery is rare in usage. This slows down performance. > With the issues, one could just enable soLiger or update the JDK. There is no > reason to affect all users by default. > [1] > https://github.com/apache/ignite/blob/ignite-ducktape/modules/ducktests/tests/ignitetest/tests/discovery_test.py > [2] https://bugs.openjdk.java.net/browse/JDK-8219658 > [3] https://issues.apache.org/jira/browse/IGNITE-12818 > [4] https://issues.apache.org/jira/browse/IGNITE-11288 > [5] https://bugs.openjdk.java.net/browse/JDK-8245468 > [6] https://www.oracle.com/java/technologies/javase/8u261-relnotes.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13643) Disable socket linger dy default in Tcp Discovery Spi
[ https://issues.apache.org/jira/browse/IGNITE-13643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Steshin updated IGNITE-13643: -- Fix Version/s: 2.10 > Disable socket linger dy default in Tcp Discovery Spi > - > > Key: IGNITE-13643 > URL: https://issues.apache.org/jira/browse/IGNITE-13643 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.9, 2.8.1 >Reporter: Vladimir Steshin >Assignee: Vladimir Steshin >Priority: Major > Fix For: 2.10 > > Time Spent: 10m > Remaining Estimate: 0h > > Current IgniteUtils.closeQuiet(@Nullable Socket sock) can take about 5sec to > close socket. This violates node detection failure. Despite we set > failureDetectionTiemout == 1000, node failure is detected within 6.5 secs in > average. > This time gap was unearther by a discovery integration test on ducktape [1]. > Failure detection timeout is set to 1000ms. > Typical results before the fix for 1 node: > "Detection of node(s) failure (ms)": 6140, "All detection delays (ms):": > "[6140]", "Nodes failed": 1} > Typical results after the fix for 1 node: > "Detection of node(s) failure (ms)": 1034, "All detection delays (ms):": > "[1034]", "Nodes failed": 1} > There is note that 'graceful' socket closing was made to workaround bag in > OpenJDK12 [2]. But as I see it has been fixed. Also, there were SSL issues > like [3] and [4]. > There are various fixes in modern versions of various JDK, supporting TLS 1.3 > ([6]). OpenJDK11 works well as far as I know. > I believe, SSL in discovery is rare in usage. This slows down performance. > With the issues, one could just enable soLiger or update the JDK. There is no > reason to affect all users by default. > [1] > https://github.com/apache/ignite/blob/ignite-ducktape/modules/ducktests/tests/ignitetest/tests/discovery_test.py > [2] https://bugs.openjdk.java.net/browse/JDK-8219658 > [3] https://issues.apache.org/jira/browse/IGNITE-12818 > [4] https://issues.apache.org/jira/browse/IGNITE-11288 > [5] https://bugs.openjdk.java.net/browse/JDK-8245468 > [6] https://www.oracle.com/java/technologies/javase/8u261-relnotes.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13662) Discribe soLinger setting in TCP Discovery and SSL issues.
[ https://issues.apache.org/jira/browse/IGNITE-13662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Steshin updated IGNITE-13662: -- Fix Version/s: 2.10 > Discribe soLinger setting in TCP Discovery and SSL issues. > -- > > Key: IGNITE-13662 > URL: https://issues.apache.org/jira/browse/IGNITE-13662 > Project: Ignite > Issue Type: Improvement >Reporter: Vladimir Steshin >Assignee: Vladimir Steshin >Priority: Minor > Fix For: 2.10 > > > Discribe soLinger setting in TCP Discovery and SSL issues. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13320) TDE - Phase-3. CLI management
[
https://issues.apache.org/jira/browse/IGNITE-13320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17227221#comment-17227221
]
Pavel Pereslegin commented on IGNITE-13320:
---
[~PetrovMikhail], thanks for the review!
> TDE - Phase-3. CLI management
> -
>
> Key: IGNITE-13320
> URL: https://issues.apache.org/jira/browse/IGNITE-13320
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Pavel Pereslegin
>Assignee: Pavel Pereslegin
>Priority: Major
> Labels: IEP-18, tde-phase-3
> Fix For: 2.10
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Provide the ability to manage the process of key rotation (and cache
> re-encryption) through the command line.
> - Launch cache key rotation
> - View key identifiers of the cache group
> - View re-encryption status for the cache group
> - Suspend/Resume re-encryption
> - View/change re-encryption rate limit
> Command syntax:
> {noformat}
> Change the encryption key of the cache group:
> control.(sh|bat) --encryption change_cache_key cacheGroupName
> View encryption key identifiers of the cache group:
> control.(sh|bat) --encryption cache_key_ids cacheGroupName
> Display re-encryption status of the cache group:
> control.(sh|bat) --encryption reencryption_status cacheGroupName
> Suspend re-encryption of the cache group:
> control.(sh|bat) --encryption suspend_reencryption cacheGroupName
> Resume re-encryption of the cache group:
> control.(sh|bat) --encryption resume_reencryption cacheGroupName
> View/change re-encryption rate limit:
> control.(sh|bat) --encryption reencryption_rate [--limit limit]
> Parameters:
> limit - Decimal value to change re-encryption rate limit
> (MB/s).{noformat}
> Example of output:
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=95652384#TDE.Phase3.Cachekeyrotation.-Processmanagement
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13643) Disable socket linger dy default in Tcp Discovery Spi
[
https://issues.apache.org/jira/browse/IGNITE-13643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17227218#comment-17227218
]
Ignite TC Bot commented on IGNITE-13643:
{panel:title=Branch: [pull/8407/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8407/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5703399buildTypeId=IgniteTests24Java8_RunAll]
> Disable socket linger dy default in Tcp Discovery Spi
> -
>
> Key: IGNITE-13643
> URL: https://issues.apache.org/jira/browse/IGNITE-13643
> Project: Ignite
> Issue Type: Bug
>Reporter: Vladimir Steshin
>Assignee: Vladimir Steshin
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Current IgniteUtils.closeQuiet(@Nullable Socket sock) can take about 5sec to
> close socket. This violates node detection failure. Despite we set
> failureDetectionTiemout == 1000, node failure is detected within 6.5 secs in
> average.
> This time gap was unearther by a discovery integration test on ducktape [1].
> Failure detection timeout is set to 1000ms.
> Typical results before the fix for 1 node:
> "Detection of node(s) failure (ms)": 6140, "All detection delays (ms):":
> "[6140]", "Nodes failed": 1}
> Typical results after the fix for 1 node:
> "Detection of node(s) failure (ms)": 1034, "All detection delays (ms):":
> "[1034]", "Nodes failed": 1}
> There is note that 'graceful' socket closing was made to workaround bag in
> OpenJDK12 [2]. But as I see it has been fixed. Also, there were SSL issues
> like [3] and [4].
> There are various fixes in modern versions of various JDK, supporting TLS 1.3
> ([6]). OpenJDK11 works well as far as I know.
> I believe, SSL in discovery is rare in usage. This slows down performance.
> With the issues, one could just enable soLiger or update the JDK. There is no
> reason to affect all users by default.
> [1]
> https://github.com/apache/ignite/blob/ignite-ducktape/modules/ducktests/tests/ignitetest/tests/discovery_test.py
> [2] https://bugs.openjdk.java.net/browse/JDK-8219658
> [3] https://issues.apache.org/jira/browse/IGNITE-12818
> [4] https://issues.apache.org/jira/browse/IGNITE-11288
> [5] https://bugs.openjdk.java.net/browse/JDK-8245468
> [6] https://www.oracle.com/java/technologies/javase/8u261-relnotes.html
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-13680) Broken formatting rule for vm.swappiness.
[
https://issues.apache.org/jira/browse/IGNITE-13680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stanilovsky Evgeny updated IGNITE-13680:
Labels: newbie (was: )
> Broken formatting rule for vm.swappiness.
> -
>
> Key: IGNITE-13680
> URL: https://issues.apache.org/jira/browse/IGNITE-13680
> Project: Ignite
> Issue Type: Improvement
> Components: general
>Affects Versions: 2.9
>Reporter: Stanilovsky Evgeny
>Priority: Major
> Labels: newbie
>
> Ignite start suggestions use float formatting for int value :
> {noformat}
> ^-- Reduce pages swapping ratio (set vm.swappiness=10.00 or less)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-13680) Broken formatting rule for vm.swappiness.
Stanilovsky Evgeny created IGNITE-13680:
---
Summary: Broken formatting rule for vm.swappiness.
Key: IGNITE-13680
URL: https://issues.apache.org/jira/browse/IGNITE-13680
Project: Ignite
Issue Type: Improvement
Components: general
Affects Versions: 2.9
Reporter: Stanilovsky Evgeny
Ignite start suggestions use float formatting for int value :
{noformat}
^-- Reduce pages swapping ratio (set vm.swappiness=10.00 or less)
{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-13679) Entryprocessor cannot be hot deployed properly via UriDeploymentSpi
YuJue Li created IGNITE-13679: - Summary: Entryprocessor cannot be hot deployed properly via UriDeploymentSpi Key: IGNITE-13679 URL: https://issues.apache.org/jira/browse/IGNITE-13679 Project: Ignite Issue Type: Bug Components: cache Affects Versions: 2.9 Reporter: YuJue Li Fix For: 2.9.1 Attachments: ignite-deploy.zip Entryprocessor cannot be hot deployed properly via UriDeploymentSpi,the operation steps are as follows: 1.put jar in the specified folder of uriList; 2.Use example-deploy.xml,start two ignite nodes; 3.Use the DeployClient to deploy the service named "deployService"; 4.Execute the test through ThickClientTest, and the result is correct; 5.Modify the code of DeployServiceImpl and DeployEntryProcessor, for example, change "Hello" to "Hi", then repackage it and put it into the specified folder of uriList; 6.Redeploy services by RedeployClient; 7.Execute the test again through ThickClientTest, and the result is incorrect,we will find that if the Entryprocessor accessed by the service is on another node, the Entryprocessor uses the old version of the class definition. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13320) TDE - Phase-3. CLI management
[
https://issues.apache.org/jira/browse/IGNITE-13320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin updated IGNITE-13320:
--
Description:
Provide the ability to manage the process of key rotation (and cache
re-encryption) through the command line.
- Launch cache key rotation
- View key identifiers of the cache group
- View re-encryption status for the cache group
- Suspend/Resume re-encryption
- View/change re-encryption rate limit
Command syntax:
{noformat}
Change the encryption key of the cache group:
control.(sh|bat) --encryption change_cache_key cacheGroupName
View encryption key identifiers of the cache group:
control.(sh|bat) --encryption cache_key_ids cacheGroupName
Display re-encryption status of the cache group:
control.(sh|bat) --encryption reencryption_status cacheGroupName
Suspend re-encryption of the cache group:
control.(sh|bat) --encryption suspend_reencryption cacheGroupName
Resume re-encryption of the cache group:
control.(sh|bat) --encryption resume_reencryption cacheGroupName
View/change re-encryption rate limit:
control.(sh|bat) --encryption reencryption_rate [--limit limit]
Parameters:
limit - Decimal value to change re-encryption rate limit
(MB/s).{noformat}
Example of output:
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=95652384#TDE.Phase3.Cachekeyrotation.-Processmanagement
was:
Provide the ability to manage the process of key rotation (and cache
re-encryption) through the command line.
- Launch cache key rotation
- View key identifiers of the cache group
- View re-encryption status for the cache group
- Suspend/Resume re-encryption
- View/change re-encryption rate limit
Command syntax:
{noformat}
Change the encryption key of the cache group:
control.(sh|bat) --encryption change_cache_key cacheGroupName
View encryption key identifiers of the cache group:
control.(sh|bat) --encryption cache_key_ids cacheGroupName
Display re-encryption status of the cache group:
control.(sh|bat) --encryption reencryption_status cacheGroupName
Suspend re-encryption of the cache group:
control.(sh|bat) --encryption suspend_reencryption cacheGroupName
Resume re-encryption of the cache group:
control.(sh|bat) --encryption resume_reencryption cacheGroupName
View/change re-encryption rate limit:
control.(sh|bat) --encryption reencryption_rate [--limit limit]
Parameters:
limit - Decimal value to change re-encryption rate limit
(MB/s).{noformat}
> TDE - Phase-3. CLI management
> -
>
> Key: IGNITE-13320
> URL: https://issues.apache.org/jira/browse/IGNITE-13320
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Pavel Pereslegin
>Assignee: Pavel Pereslegin
>Priority: Major
> Labels: IEP-18, tde-phase-3
> Fix For: 2.10
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Provide the ability to manage the process of key rotation (and cache
> re-encryption) through the command line.
> - Launch cache key rotation
> - View key identifiers of the cache group
> - View re-encryption status for the cache group
> - Suspend/Resume re-encryption
> - View/change re-encryption rate limit
> Command syntax:
> {noformat}
> Change the encryption key of the cache group:
> control.(sh|bat) --encryption change_cache_key cacheGroupName
> View encryption key identifiers of the cache group:
> control.(sh|bat) --encryption cache_key_ids cacheGroupName
> Display re-encryption status of the cache group:
> control.(sh|bat) --encryption reencryption_status cacheGroupName
> Suspend re-encryption of the cache group:
> control.(sh|bat) --encryption suspend_reencryption cacheGroupName
> Resume re-encryption of the cache group:
> control.(sh|bat) --encryption resume_reencryption cacheGroupName
> View/change re-encryption rate limit:
> control.(sh|bat) --encryption reencryption_rate [--limit limit]
> Parameters:
> limit - Decimal value to change re-encryption rate limit
> (MB/s).{noformat}
> Example of output:
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=95652384#TDE.Phase3.Cachekeyrotation.-Processmanagement
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-13320) TDE - Phase-3. CLI management
[
https://issues.apache.org/jira/browse/IGNITE-13320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin updated IGNITE-13320:
--
Description:
Provide the ability to manage the process of key rotation (and cache
re-encryption) through the command line.
- Launch cache key rotation
- View key identifiers of the cache group
- View re-encryption status for the cache group
- Suspend/Resume re-encryption
- View/change re-encryption rate limit
Command syntax:
{noformat}
Change the encryption key of the cache group:
control.(sh|bat) --encryption change_cache_key cacheGroupName
View encryption key identifiers of the cache group:
control.(sh|bat) --encryption cache_key_ids cacheGroupName
Display re-encryption status of the cache group:
control.(sh|bat) --encryption reencryption_status cacheGroupName
Suspend re-encryption of the cache group:
control.(sh|bat) --encryption suspend_reencryption cacheGroupName
Resume re-encryption of the cache group:
control.(sh|bat) --encryption resume_reencryption cacheGroupName
View/change re-encryption rate limit:
control.(sh|bat) --encryption reencryption_rate [--limit limit]
Parameters:
limit - Decimal value to change re-encryption rate limit
(MB/s).{noformat}
was:
Provide the ability to manage the process of key rotation (and cache
re-encryption) through the command line.
- Launch cache key rotation
- View key identifiers of the cache group
- View re-encryption status for the cache group
- Suspend/Resume re-encryption
- View/change re-encryption rate limit
Command syntax:
{noformat}
Change the encryption key of the cache group:
control.(sh|bat) --encryption change_cache_key cacheGroupName
View encryption key identifiers of the cache group:
control.(sh|bat) --encryption cache_key_ids cacheGroupName
Control the process of re-encryption of the cache group:
control.(sh|bat) --encryption group_reencryption cacheGroupName [--status
--suspend --resume]
Parameters:
--status - Display re-encryption status.
--suspend - Suspend re-encryption.
--resume - Resume re-encryption.
View/change re-encryption rate limit:
control.(sh|bat) --encryption reencryption_rate [--limit limit]
Parameters:
limit - Decimal value to change re-encryption rate limit
(MB/s).{noformat}
> TDE - Phase-3. CLI management
> -
>
> Key: IGNITE-13320
> URL: https://issues.apache.org/jira/browse/IGNITE-13320
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Pavel Pereslegin
>Assignee: Pavel Pereslegin
>Priority: Major
> Labels: IEP-18, tde-phase-3
> Fix For: 2.10
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Provide the ability to manage the process of key rotation (and cache
> re-encryption) through the command line.
> - Launch cache key rotation
> - View key identifiers of the cache group
> - View re-encryption status for the cache group
> - Suspend/Resume re-encryption
> - View/change re-encryption rate limit
> Command syntax:
> {noformat}
> Change the encryption key of the cache group:
> control.(sh|bat) --encryption change_cache_key cacheGroupName
> View encryption key identifiers of the cache group:
> control.(sh|bat) --encryption cache_key_ids cacheGroupName
> Display re-encryption status of the cache group:
> control.(sh|bat) --encryption reencryption_status cacheGroupName
> Suspend re-encryption of the cache group:
> control.(sh|bat) --encryption suspend_reencryption cacheGroupName
> Resume re-encryption of the cache group:
> control.(sh|bat) --encryption resume_reencryption cacheGroupName
> View/change re-encryption rate limit:
> control.(sh|bat) --encryption reencryption_rate [--limit limit]
> Parameters:
> limit - Decimal value to change re-encryption rate limit
> (MB/s).{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-13676) Java thin client: Message not fully read by client after SECURITY_VIOLATION error
[ https://issues.apache.org/jira/browse/IGNITE-13676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Plekhanov updated IGNITE-13676: --- Component/s: thin client > Java thin client: Message not fully read by client after SECURITY_VIOLATION > error > - > > Key: IGNITE-13676 > URL: https://issues.apache.org/jira/browse/IGNITE-13676 > Project: Ignite > Issue Type: Bug > Components: thin client >Affects Versions: 2.9 >Reporter: Aleksey Plekhanov >Assignee: Aleksey Plekhanov >Priority: Major > Fix For: 2.10, 2.9.1 > > Time Spent: 20m > Remaining Estimate: 0h > > In case of SECURITY_VIOLATION error client does not fully read message, these > leads to phantom messages and client hang. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13676) Java thin client: Message not fully read by client after SECURITY_VIOLATION error
[ https://issues.apache.org/jira/browse/IGNITE-13676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Plekhanov updated IGNITE-13676: --- Affects Version/s: 2.9 > Java thin client: Message not fully read by client after SECURITY_VIOLATION > error > - > > Key: IGNITE-13676 > URL: https://issues.apache.org/jira/browse/IGNITE-13676 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.9 >Reporter: Aleksey Plekhanov >Assignee: Aleksey Plekhanov >Priority: Major > Fix For: 2.10, 2.9.1 > > Time Spent: 20m > Remaining Estimate: 0h > > In case of SECURITY_VIOLATION error client does not fully read message, these > leads to phantom messages and client hang. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13676) Java thin client: Message not fully read by client after SECURITY_VIOLATION error
[
https://issues.apache.org/jira/browse/IGNITE-13676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17226939#comment-17226939
]
Ignite TC Bot commented on IGNITE-13676:
{panel:title=Branch: [pull/8428/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8428/head] Base: [master] : New Tests
(3)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Security{color} [[tests
3|https://ci.ignite.apache.org/viewLog.html?buildId=5715868]]
* {color:#013220}SecurityTestSuite:
ThinClientPermissionCheckTest.testAllowedOperationAfterSecurityViolation -
PASSED{color}
* {color:#013220}SecurityTestSuite:
ThinClientSecurityContextOnRemoteNodeTest.testAllowedOperationAfterSecurityViolation
- PASSED{color}
* {color:#013220}SecurityTestSuite:
ThinClientPermissionCheckSecurityTest.testAllowedOperationAfterSecurityViolation
- PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5715876buildTypeId=IgniteTests24Java8_RunAll]
> Java thin client: Message not fully read by client after SECURITY_VIOLATION
> error
> -
>
> Key: IGNITE-13676
> URL: https://issues.apache.org/jira/browse/IGNITE-13676
> Project: Ignite
> Issue Type: Bug
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Fix For: 2.10, 2.9.1
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In case of SECURITY_VIOLATION error client does not fully read message, these
> leads to phantom messages and client hang.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13320) TDE - Phase-3. CLI management
[
https://issues.apache.org/jira/browse/IGNITE-13320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17226874#comment-17226874
]
Mikhail Petrov commented on IGNITE-13320:
-
[~xtern], LGTM.
> TDE - Phase-3. CLI management
> -
>
> Key: IGNITE-13320
> URL: https://issues.apache.org/jira/browse/IGNITE-13320
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Pavel Pereslegin
>Assignee: Pavel Pereslegin
>Priority: Major
> Labels: IEP-18, tde-phase-3
> Fix For: 2.10
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Provide the ability to manage the process of key rotation (and cache
> re-encryption) through the command line.
> - Launch cache key rotation
> - View key identifiers of the cache group
> - View re-encryption status for the cache group
> - Suspend/Resume re-encryption
> - View/change re-encryption rate limit
> Command syntax:
> {noformat}
> Change the encryption key of the cache group:
> control.(sh|bat) --encryption change_cache_key cacheGroupName
> View encryption key identifiers of the cache group:
> control.(sh|bat) --encryption cache_key_ids cacheGroupName
> Control the process of re-encryption of the cache group:
> control.(sh|bat) --encryption group_reencryption cacheGroupName [--status
> --suspend --resume]
> Parameters:
> --status - Display re-encryption status.
> --suspend - Suspend re-encryption.
> --resume - Resume re-encryption.
> View/change re-encryption rate limit:
> control.(sh|bat) --encryption reencryption_rate [--limit limit]
> Parameters:
> limit - Decimal value to change re-encryption rate limit
> (MB/s).{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-13666) Disable socket linger in discovery ducktape test.
[ https://issues.apache.org/jira/browse/IGNITE-13666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Steshin updated IGNITE-13666: -- Ignite Flags: (was: Docs Required,Release Notes Required) > Disable socket linger in discovery ducktape test. > - > > Key: IGNITE-13666 > URL: https://issues.apache.org/jira/browse/IGNITE-13666 > Project: Ignite > Issue Type: Improvement >Reporter: Vladimir Steshin >Assignee: Vladimir Steshin >Priority: Minor > Time Spent: 40m > Remaining Estimate: 0h > > soLinger might be disabled to fasten the discovery tests. Additionally, we > could reduce failureDetectionTimeout. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13577) Add support to graceful shutdown for ZookeeperDiscoverySpi
[ https://issues.apache.org/jira/browse/IGNITE-13577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yaroslav Molochkov updated IGNITE-13577: Fix Version/s: 2.9.1 > Add support to graceful shutdown for ZookeeperDiscoverySpi > -- > > Key: IGNITE-13577 > URL: https://issues.apache.org/jira/browse/IGNITE-13577 > Project: Ignite > Issue Type: Improvement > Components: zookeeper >Reporter: Ivan Daschinskiy >Assignee: Ivan Daschinskiy >Priority: Major > Labels: zookeeper > Fix For: 2.10, 2.9.1 > > Time Spent: 20m > Remaining Estimate: 0h > > Proposed design: > *LN* -- node that performs graceful shutdown > *CRD* -- Leader (coordinator) of Ignite cluster > *N* -- Other nodes of Ignite cluster. > # *LN* create PERSISTENT *flag* znode with path //sf/ > # *LN* delete own znode in //n as usual. > # *CRD* receives notification and check if exists *flag* for this node > # *CRD* generate NODE_LEFT event with flag fail=false, otherwise fail=true > # *CRD* save event as usual, then delete *flag*. > # *CRD* and *N* process events as usual. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13678) Extend test coverage for persistence files dir and WAL page snapshot records compression
Sergey Uttsel created IGNITE-13678: -- Summary: Extend test coverage for persistence files dir and WAL page snapshot records compression Key: IGNITE-13678 URL: https://issues.apache.org/jira/browse/IGNITE-13678 Project: Ignite Issue Type: Test Reporter: Sergey Uttsel Assignee: Sergey Uttsel -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13643) Disable socket linger dy default in Tcp Discovery Spi
[
https://issues.apache.org/jira/browse/IGNITE-13643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17226781#comment-17226781
]
Ignite TC Bot commented on IGNITE-13643:
{panel:title=Branch: [pull/8407/head] Base: [master] : Possible Blockers
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache (Expiry Policy){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5703332]]
* IgniteCacheExpiryPolicyTestSuite:
GridCacheTtlManagerNotificationTest.testThatNotificationWorkAsExpectedManyCaches
- Test has low fail rate in base branch 0,0% and is not flaky
{panel}
{panel:title=Branch: [pull/8407/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5703399buildTypeId=IgniteTests24Java8_RunAll]
> Disable socket linger dy default in Tcp Discovery Spi
> -
>
> Key: IGNITE-13643
> URL: https://issues.apache.org/jira/browse/IGNITE-13643
> Project: Ignite
> Issue Type: Bug
>Reporter: Vladimir Steshin
>Assignee: Vladimir Steshin
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Current IgniteUtils.closeQuiet(@Nullable Socket sock) can take about 5sec to
> close socket. This violates node detection failure. Despite we set
> failureDetectionTiemout == 1000, node failure is detected within 6.5 secs in
> average.
> This time gap was unearther by a discovery integration test on ducktape [1].
> Failure detection timeout is set to 1000ms.
> Typical results before the fix for 1 node:
> "Detection of node(s) failure (ms)": 6140, "All detection delays (ms):":
> "[6140]", "Nodes failed": 1}
> Typical results after the fix for 1 node:
> "Detection of node(s) failure (ms)": 1034, "All detection delays (ms):":
> "[1034]", "Nodes failed": 1}
> There is note that 'graceful' socket closing was made to workaround bag in
> OpenJDK12 [2]. But as I see it has been fixed. Also, there were SSL issues
> like [3] and [4].
> There are various fixes in modern versions of various JDK, supporting TLS 1.3
> ([6]). OpenJDK11 works well as far as I know.
> I believe, SSL in discovery is rare in usage. This slows down performance.
> With the issues, one could just enable soLiger or update the JDK. There is no
> reason to affect all users by default.
> [1]
> https://github.com/apache/ignite/blob/ignite-ducktape/modules/ducktests/tests/ignitetest/tests/discovery_test.py
> [2] https://bugs.openjdk.java.net/browse/JDK-8219658
> [3] https://issues.apache.org/jira/browse/IGNITE-12818
> [4] https://issues.apache.org/jira/browse/IGNITE-11288
> [5] https://bugs.openjdk.java.net/browse/JDK-8245468
> [6] https://www.oracle.com/java/technologies/javase/8u261-relnotes.html
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-13645) Discovery ducktape test should detect failed nodes by asking the cluster.
[ https://issues.apache.org/jira/browse/IGNITE-13645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-13645: -- Labels: IEP-56 ducktape (was: ) > Discovery ducktape test should detect failed nodes by asking the cluster. > - > > Key: IGNITE-13645 > URL: https://issues.apache.org/jira/browse/IGNITE-13645 > Project: Ignite > Issue Type: Bug >Reporter: Vladimir Steshin >Assignee: Vladimir Steshin >Priority: Major > Labels: IEP-56, ducktape > Time Spent: 10m > Remaining Estimate: 0h > > Discovery ducktape test should measure detection time of failed nodes by > asking whole rest of the cluster. Currently, we measure by asking only one > watching node. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13645) Discovery ducktape test should detect failed nodes by asking the cluster.
[ https://issues.apache.org/jira/browse/IGNITE-13645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17226768#comment-17226768 ] Anton Vinogradov commented on IGNITE-13645: --- Merged to ignite-ducktape. Thanks for your contribution. > Discovery ducktape test should detect failed nodes by asking the cluster. > - > > Key: IGNITE-13645 > URL: https://issues.apache.org/jira/browse/IGNITE-13645 > Project: Ignite > Issue Type: Bug >Reporter: Vladimir Steshin >Assignee: Vladimir Steshin >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Discovery ducktape test should measure detection time of failed nodes by > asking whole rest of the cluster. Currently, we measure by asking only one > watching node. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-13545) Calcite integration. Index spool
[ https://issues.apache.org/jira/browse/IGNITE-13545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taras Ledkov reassigned IGNITE-13545: - Assignee: (was: Taras Ledkov) > Calcite integration. Index spool > > > Key: IGNITE-13545 > URL: https://issues.apache.org/jira/browse/IGNITE-13545 > Project: Ignite > Issue Type: New Feature > Components: sql >Reporter: Yury Gerzhedovich >Priority: Major > Original Estimate: 80h > Remaining Estimate: 80h > > To have a performance boost need to implement index spools. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-13545) Calcite integration. Index spool
[ https://issues.apache.org/jira/browse/IGNITE-13545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taras Ledkov reassigned IGNITE-13545: - Assignee: Taras Ledkov > Calcite integration. Index spool > > > Key: IGNITE-13545 > URL: https://issues.apache.org/jira/browse/IGNITE-13545 > Project: Ignite > Issue Type: New Feature > Components: sql >Reporter: Yury Gerzhedovich >Assignee: Taras Ledkov >Priority: Major > Original Estimate: 80h > Remaining Estimate: 80h > > To have a performance boost need to implement index spools. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13677) Calcite integration. TableSpool
Taras Ledkov created IGNITE-13677:
-
Summary: Calcite integration. TableSpool
Key: IGNITE-13677
URL: https://issues.apache.org/jira/browse/IGNITE-13677
Project: Ignite
Issue Type: Bug
Components: sql
Reporter: Taras Ledkov
Assignee: Taras Ledkov
The first step of the IGNITE-13545: adds TableSpool.
We have to add new trait: {{CorretlationTrait}} to check stream correlation.
Without check this trait Filter with correlated variables may be places under
Exchange.
So, {{IgniteCorrelatedNestedLoopJoin}} requires correlated stream from the
right input and {{Exchange}} may produce only uncorrelated stream.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-13658) Volatile cache writes to persistent storage.
[
https://issues.apache.org/jira/browse/IGNITE-13658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Kasnacheev updated IGNITE-13658:
-
Fix Version/s: 2.10
> Volatile cache writes to persistent storage.
>
>
> Key: IGNITE-13658
> URL: https://issues.apache.org/jira/browse/IGNITE-13658
> Project: Ignite
> Issue Type: Bug
> Components: data structures
>Affects Versions: 2.9
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Major
> Fix For: 2.10
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Various cluster synchronization primitives (latch, lock, semaphore e.t.c) are
> using volatile cache (`default-volatile-ds-group`). State of this primitives
> does not make sense on storage (restore, recovery), primitive's state is
> useful only for process in action.
> But it was stored in system data region.
> {noformat}
> if (cacheType != CacheType.USER && cfg.getDataRegionName() == null)
>
>
> cfg.setDataRegionName(cacheProcessor.context().database().systemDateRegionName());
> {noformat}
> Which persisted if cluster have any persistent region:
> {noformat}
> addDataRegion(
> memCfg,
> createSystemDataRegion(
> memCfg.getSystemRegionInitialSize(),
> memCfg.getSystemRegionMaxSize(),
> CU.isPersistenceEnabled(memCfg)
> ),
> CU.isPersistenceEnabled(memCfg)
> );
> {noformat}
> Should to have dedicate system region for volatile cache, and it should be
> in-memory.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-13676) Java thin client: Message not fully read by client after SECURITY_VIOLATION error
[ https://issues.apache.org/jira/browse/IGNITE-13676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Plekhanov updated IGNITE-13676: --- Fix Version/s: 2.9.1 2.10 > Java thin client: Message not fully read by client after SECURITY_VIOLATION > error > - > > Key: IGNITE-13676 > URL: https://issues.apache.org/jira/browse/IGNITE-13676 > Project: Ignite > Issue Type: Bug >Reporter: Aleksey Plekhanov >Assignee: Aleksey Plekhanov >Priority: Major > Fix For: 2.10, 2.9.1 > > Time Spent: 10m > Remaining Estimate: 0h > > In case of SECURITY_VIOLATION error client does not fully read message, these > leads to phantom messages and client hang. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13676) Java thin client: Message not fully read by client after SECURITY_VIOLATION error
[ https://issues.apache.org/jira/browse/IGNITE-13676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Plekhanov updated IGNITE-13676: --- Description: In case of SECURITY_VIOLATION error client does not fully read message, these leads to phantom messages and client hang. (was: In case of SECURITY_VIOLATION error client does not fully read message, these leads to phantom messages and connection drop.) > Java thin client: Message not fully read by client after SECURITY_VIOLATION > error > - > > Key: IGNITE-13676 > URL: https://issues.apache.org/jira/browse/IGNITE-13676 > Project: Ignite > Issue Type: Bug >Reporter: Aleksey Plekhanov >Assignee: Aleksey Plekhanov >Priority: Major > > In case of SECURITY_VIOLATION error client does not fully read message, these > leads to phantom messages and client hang. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13676) Java thin client: Message not fully read by client after SECURITY_VIOLATION error
Aleksey Plekhanov created IGNITE-13676: -- Summary: Java thin client: Message not fully read by client after SECURITY_VIOLATION error Key: IGNITE-13676 URL: https://issues.apache.org/jira/browse/IGNITE-13676 Project: Ignite Issue Type: Bug Reporter: Aleksey Plekhanov Assignee: Aleksey Plekhanov In case of SECURITY_VIOLATION error client does not fully read message, these leads to phantom messages and connection drop. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13660) Unexpected NODE_LEFT on graceful stop (at ducktests)
[ https://issues.apache.org/jira/browse/IGNITE-13660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17226633#comment-17226633 ] Anton Vinogradov commented on IGNITE-13660: --- Merged to ignite-ducktape. > Unexpected NODE_LEFT on graceful stop (at ducktests) > > > Key: IGNITE-13660 > URL: https://issues.apache.org/jira/browse/IGNITE-13660 > Project: Ignite > Issue Type: Bug >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Critical > Labels: IEP-56, ducktape > Time Spent: 20m > Remaining Estimate: 0h > > 1) Graceful shutdown may cause NODE_LEFT. > 2) Self-termination apps have logs till the end. > Apps terminated by ducktape with SIGTERM stop their logging at node stop. > Seems, shutdown hook stops kill the application before the Ignite stops. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13633) thin clients cannot access the Ignite Service deployed through UriDeploymentSpi( java.lang.ClassNotFoundException)
[
https://issues.apache.org/jira/browse/IGNITE-13633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17226631#comment-17226631
]
Aleksey Plekhanov commented on IGNITE-13633:
Root cause: Implementations of {{ServiceDescriptor}} know nothing about
deployment SPI, every {{ServiceDescriptor.serviceClass()}} usage is prone to
this error (thin client services, .NET services, services system view, public
API). Simlified reproducer:
{code:java}
public class ServiceWithDeploymentSpiTest extends GridCommonAbstractTest {
private Path srcTmpDir;
@Override protected IgniteConfiguration getConfiguration(String
igniteInstanceName) throws Exception {
IgniteConfiguration cfg = super.getConfiguration(igniteInstanceName);
cfg.setDeploymentSpi(new LocalDeploymentSpi());
return cfg;
}
@Before
public void prepare() throws IOException {
srcTmpDir = Files.createTempDirectory(getClass().getSimpleName());
}
@After
public void cleanup() {
U.delete(srcTmpDir);
}
@Test
public void testServiceWithDeploymentSpi() throws Exception {
URLClassLoader clsLdr = prepareClassLoader();
Class cls = clsLdr.loadClass("MyServiceImpl");
Service srvc = (Service)cls.newInstance();
Ignite ignite = startGrid(0);
DeploymentSpi depSpi = ignite.configuration().getDeploymentSpi();
depSpi.register(clsLdr, srvc.getClass());
ignite.services().deployClusterSingleton("test-service", srvc);
for (ServiceDescriptor desc : ignite.services().serviceDescriptors()) {
if ("test-service".equals(desc.name()))
assertEquals(cls, desc.serviceClass());
}
}
private URLClassLoader prepareClassLoader() throws Exception {
String src = "import org.apache.ignite.services.Service;\n" +
"import org.apache.ignite.services.ServiceContext;\n" +
"public class MyServiceImpl implements Service {\n" +
"@Override public void cancel(ServiceContext ctx) {}\n" +
"@Override public void init(ServiceContext ctx) throws
Exception {}\n" +
"@Override public void execute(ServiceContext ctx) throws
Exception {}\n" +
"}";
Files.createDirectories(srcTmpDir);
File srcFile = new File(srcTmpDir.toFile(), "MyServiceImpl.java");
Path srcFilePath = Files.write(srcFile.toPath(),
src.getBytes(StandardCharsets.UTF_8));
JavaCompiler compiler = ToolProvider.getSystemJavaCompiler();
compiler.run(null, null, null, srcFilePath.toString());
assertTrue("Failed to remove source file.", srcFile.delete());
return new URLClassLoader(new URL[] {srcTmpDir.toUri().toURL()});
}
}
{code}
> thin clients cannot access the Ignite Service deployed through
> UriDeploymentSpi( java.lang.ClassNotFoundException)
> --
>
> Key: IGNITE-13633
> URL: https://issues.apache.org/jira/browse/IGNITE-13633
> Project: Ignite
> Issue Type: Bug
> Components: managed services, thin client
>Affects Versions: 2.9
>Reporter: xingzhou
>Assignee: Aleksey Plekhanov
>Priority: Critical
> Fix For: 2.9.1
>
> Attachments: ignite-deploy.zip
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> When the thin client is used to call the ignite service（ use ignite-urideploy
> ）, the clientserviceinvokerequest will get the service classes, the local
> classloader is used, and the classes cannot be found. Therefore, the
> ignite-urideploy classloader should be added
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-13633) thin clients cannot access the Ignite Service deployed through UriDeploymentSpi( java.lang.ClassNotFoundException)
[ https://issues.apache.org/jira/browse/IGNITE-13633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Plekhanov reassigned IGNITE-13633: -- Assignee: Aleksey Plekhanov > thin clients cannot access the Ignite Service deployed through > UriDeploymentSpi( java.lang.ClassNotFoundException) > -- > > Key: IGNITE-13633 > URL: https://issues.apache.org/jira/browse/IGNITE-13633 > Project: Ignite > Issue Type: Bug > Components: managed services, thin client >Affects Versions: 2.9 >Reporter: xingzhou >Assignee: Aleksey Plekhanov >Priority: Critical > Fix For: 2.9.1 > > Attachments: ignite-deploy.zip > > Original Estimate: 24h > Remaining Estimate: 24h > > When the thin client is used to call the ignite service（ use ignite-urideploy > ）, the clientserviceinvokerequest will get the service classes, the local > classloader is used, and the classes cannot be found. Therefore, the > ignite-urideploy classloader should be added -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-13675) Devnotes in C++ platforms pointed that windows cmake not yet supported
[ https://issues.apache.org/jira/browse/IGNITE-13675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego reassigned IGNITE-13675: Assignee: Igor Sapego > Devnotes in C++ platforms pointed that windows cmake not yet supported > -- > > Key: IGNITE-13675 > URL: https://issues.apache.org/jira/browse/IGNITE-13675 > Project: Ignite > Issue Type: Bug > Components: documentation, platforms >Reporter: Stepan Pilschikov >Assignee: Igor Sapego >Priority: Major > > Currently in devnotes written that windows cmake not yet supported which is > wrong > https://github.com/apache/ignite/blob/b986cf6f2250858b92e4eda52f9269077659229c/modules/platforms/cpp/DEVNOTES.txt#L11 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13675) Devnotes in C++ platforms pointed that windows cmake not yet supported
Stepan Pilschikov created IGNITE-13675: -- Summary: Devnotes in C++ platforms pointed that windows cmake not yet supported Key: IGNITE-13675 URL: https://issues.apache.org/jira/browse/IGNITE-13675 Project: Ignite Issue Type: Bug Components: documentation, platforms Reporter: Stepan Pilschikov Currently in devnotes written that windows cmake not yet supported which is wrong https://github.com/apache/ignite/blob/b986cf6f2250858b92e4eda52f9269077659229c/modules/platforms/cpp/DEVNOTES.txt#L11 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13244) Transaction commit completes successfully if partition is lost on commit phase
[ https://issues.apache.org/jira/browse/IGNITE-13244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Scherbakov updated IGNITE-13244: --- Reviewer: Alexey Scherbakov > Transaction commit completes successfully if partition is lost on commit phase > -- > > Key: IGNITE-13244 > URL: https://issues.apache.org/jira/browse/IGNITE-13244 > Project: Ignite > Issue Type: Bug >Reporter: Sergey Uttsel >Assignee: Sergey Uttsel >Priority: Major > Attachments: tx_commit_partition_loss.patch > > Time Spent: 10m > Remaining Estimate: 0h > > Reproducer is attached. > Steps: > 1) Run startNode() > 2) Run poorTransaction() in a separate JVM > 3) Hang first node in GridCacheMapEntry#innerSet with a breakpoint > 4) kill -9 first node while hanging on breakpoint > 5) Result: tx.commit() succeeds, data is commited in partition 1 and not > commited in partition 2 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-12489) Error during purges by expiration: Unknown page type
[
https://issues.apache.org/jira/browse/IGNITE-12489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17226574#comment-17226574
]
Nikita Tolstunov edited comment on IGNITE-12489 at 11/5/20, 8:26 AM:
-
[~alex_pl], [~agoncharuk], [~ibessonov] Can you take a look on these changes?
Point with javadocs/naming is still actual.
was (Author: nikita t):
[~alex_pl], [~agoncharuk], [~ibessonov] Can you take a look on these changes?
> Error during purges by expiration: Unknown page type
>
>
> Key: IGNITE-12489
> URL: https://issues.apache.org/jira/browse/IGNITE-12489
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7, 2.7.6
>Reporter: Ruslan Kamashev
>Assignee: Nikita Tolstunov
>Priority: Blocker
> Fix For: 2.10
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {{*logger*}}
> {code:java}
> org.apache.ignite.internal.processors.cache.GridCacheIoManager
> {code}
> {{*message*}}
> {code:java}
> Failed to process message [senderId=969d56ba-4b46-40cf-886e-ac445cf6a95d,
> messageType=class
> o.a.i.i.processors.cache.distributed.dht.atomic.GridDhtAtomicUpdateRequest]{code}
> {{*thread*}}
> {code:java}
> sys-stripe-19-#20{code}
> {{*trace*}}
> {code:java}
> java.lang.IllegalStateException: Unknown page type: 1 pageId: 00010303117d
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.io(BPlusTree.java:5058)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.access$200(BPlusTree.java:90)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$AbstractForwardCursor.nextPage(BPlusTree.java:5330)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$ForwardCursor.next(BPlusTree.java:5566)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.purgeExpiredInternal(GridCacheOffheapManager.java:2232)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.purgeExpired(GridCacheOffheapManager.java:2157)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager.expire(GridCacheOffheapManager.java:845)
> at
> org.apache.ignite.internal.processors.cache.GridCacheTtlManager.expire(GridCacheTtlManager.java:207)
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.unwindEvicts(GridCacheUtils.java:888)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessageProcessed(GridCacheIoManager.java:1103)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1076)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:581)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:380)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:306)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:101)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:295)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1569)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1197)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:127)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1093)
> at
> org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:505)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at java.lang.Thread.run(Thread.java:748)
> Dec 23, 2019 @ 18:28:28.457 {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12489) Error during purges by expiration: Unknown page type
[
https://issues.apache.org/jira/browse/IGNITE-12489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17226574#comment-17226574
]
Nikita Tolstunov commented on IGNITE-12489:
---
[~alex_pl], [~agoncharuk], [~ibessonov] Can you take a look on these changes?
> Error during purges by expiration: Unknown page type
>
>
> Key: IGNITE-12489
> URL: https://issues.apache.org/jira/browse/IGNITE-12489
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7, 2.7.6
>Reporter: Ruslan Kamashev
>Assignee: Nikita Tolstunov
>Priority: Blocker
> Fix For: 2.10
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {{*logger*}}
> {code:java}
> org.apache.ignite.internal.processors.cache.GridCacheIoManager
> {code}
> {{*message*}}
> {code:java}
> Failed to process message [senderId=969d56ba-4b46-40cf-886e-ac445cf6a95d,
> messageType=class
> o.a.i.i.processors.cache.distributed.dht.atomic.GridDhtAtomicUpdateRequest]{code}
> {{*thread*}}
> {code:java}
> sys-stripe-19-#20{code}
> {{*trace*}}
> {code:java}
> java.lang.IllegalStateException: Unknown page type: 1 pageId: 00010303117d
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.io(BPlusTree.java:5058)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.access$200(BPlusTree.java:90)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$AbstractForwardCursor.nextPage(BPlusTree.java:5330)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$ForwardCursor.next(BPlusTree.java:5566)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.purgeExpiredInternal(GridCacheOffheapManager.java:2232)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.purgeExpired(GridCacheOffheapManager.java:2157)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager.expire(GridCacheOffheapManager.java:845)
> at
> org.apache.ignite.internal.processors.cache.GridCacheTtlManager.expire(GridCacheTtlManager.java:207)
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.unwindEvicts(GridCacheUtils.java:888)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessageProcessed(GridCacheIoManager.java:1103)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1076)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:581)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:380)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:306)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:101)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:295)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1569)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1197)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:127)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1093)
> at
> org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:505)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at java.lang.Thread.run(Thread.java:748)
> Dec 23, 2019 @ 18:28:28.457 {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
