[jira] [Resolved] (IGNITE-14780) Thin client test should use versions from globals
[ https://issues.apache.org/jira/browse/IGNITE-14780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Filatov resolved IGNITE-14780. -- Resolution: Won't Do > Thin client test should use versions from globals > - > > Key: IGNITE-14780 > URL: https://issues.apache.org/jira/browse/IGNITE-14780 > Project: Ignite > Issue Type: Task >Reporter: Mikhail Filatov >Assignee: Mikhail Filatov >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > Thin client test use hardcoded versions of Ignite. It's more flexible to have > options of using versions from globals. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (IGNITE-14780) Thin client test should use versions from globals
[ https://issues.apache.org/jira/browse/IGNITE-14780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Filatov closed IGNITE-14780. > Thin client test should use versions from globals > - > > Key: IGNITE-14780 > URL: https://issues.apache.org/jira/browse/IGNITE-14780 > Project: Ignite > Issue Type: Task >Reporter: Mikhail Filatov >Assignee: Mikhail Filatov >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > Thin client test use hardcoded versions of Ignite. It's more flexible to have > options of using versions from globals. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (IGNITE-14780) Thin client test should use versions from globals
[ https://issues.apache.org/jira/browse/IGNITE-14780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Filatov reassigned IGNITE-14780: Assignee: Mikhail Filatov > Thin client test should use versions from globals > - > > Key: IGNITE-14780 > URL: https://issues.apache.org/jira/browse/IGNITE-14780 > Project: Ignite > Issue Type: Task >Reporter: Mikhail Filatov >Assignee: Mikhail Filatov >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > Thin client test use hardcoded versions of Ignite. It's more flexible to have > options of using versions from globals. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (IGNITE-15020) Linearizability test in ducktests
[ https://issues.apache.org/jira/browse/IGNITE-15020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Filatov reassigned IGNITE-15020: Assignee: (was: Mikhail Filatov) > Linearizability test in ducktests > - > > Key: IGNITE-15020 > URL: https://issues.apache.org/jira/browse/IGNITE-15020 > Project: Ignite > Issue Type: Task >Reporter: Mikhail Filatov >Priority: Major > > Add simple linerizability test to Ducktape > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (IGNITE-14780) Thin client test should use versions from globals
[ https://issues.apache.org/jira/browse/IGNITE-14780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Filatov reassigned IGNITE-14780: Assignee: (was: Mikhail Filatov) > Thin client test should use versions from globals > - > > Key: IGNITE-14780 > URL: https://issues.apache.org/jira/browse/IGNITE-14780 > Project: Ignite > Issue Type: Task >Reporter: Mikhail Filatov >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > Thin client test use hardcoded versions of Ignite. It's more flexible to have > options of using versions from globals. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-15169) Client mass reconnection test
[ https://issues.apache.org/jira/browse/IGNITE-15169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Filatov updated IGNITE-15169: - Description: Add Ducktape test to determine the influence of massive thin client connections. > Client mass reconnection test > - > > Key: IGNITE-15169 > URL: https://issues.apache.org/jira/browse/IGNITE-15169 > Project: Ignite > Issue Type: Task >Reporter: Mikhail Filatov >Assignee: Mikhail Filatov >Priority: Major > Labels: IEP-56 > Time Spent: 10m > Remaining Estimate: 0h > > Add Ducktape test to determine the influence of massive thin client > connections. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-15489) Revert IGNITE-15078 changes from CellularAffinity Ducktape test
[ https://issues.apache.org/jira/browse/IGNITE-15489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Filatov closed IGNITE-15489. > Revert IGNITE-15078 changes from CellularAffinity Ducktape test > --- > > Key: IGNITE-15489 > URL: https://issues.apache.org/jira/browse/IGNITE-15489 > Project: Ignite > Issue Type: Task >Reporter: Mikhail Filatov >Assignee: Mikhail Filatov >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > IGNITE-15078 add DateTimeFormatter to IgniteUtils and change custom formater > used in test to it. > The problem is: we don't have this formater in previous versions of ignite, > but we run ducktape on this versions (and even on GridGain) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-15489) Revert IGNITE-15078 changes from CellularAffinity Ducktape test
Mikhail Filatov created IGNITE-15489: Summary: Revert IGNITE-15078 changes from CellularAffinity Ducktape test Key: IGNITE-15489 URL: https://issues.apache.org/jira/browse/IGNITE-15489 Project: Ignite Issue Type: Task Reporter: Mikhail Filatov Assignee: Mikhail Filatov IGNITE-15078 add DateTimeFormatter to IgniteUtils and change custom formater used in test to it. The problem is: we don't have this formater in previous versions of ignite, but we run ducktape on this versions (and even on GridGain) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-15270) Fix rebalance test
Mikhail Filatov created IGNITE-15270: Summary: Fix rebalance test Key: IGNITE-15270 URL: https://issues.apache.org/jira/browse/IGNITE-15270 Project: Ignite Issue Type: Task Reporter: Mikhail Filatov Assignee: Mikhail Filatov Ducktape rebalance test don't work on dev version because it tries to read cache statistics on deactivated cluster. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-15169) Client mass reconnection test
Mikhail Filatov created IGNITE-15169: Summary: Client mass reconnection test Key: IGNITE-15169 URL: https://issues.apache.org/jira/browse/IGNITE-15169 Project: Ignite Issue Type: Task Reporter: Mikhail Filatov Assignee: Mikhail Filatov -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-15020) Linearizability test in ducktests
Mikhail Filatov created IGNITE-15020: Summary: Linearizability test in ducktests Key: IGNITE-15020 URL: https://issues.apache.org/jira/browse/IGNITE-15020 Project: Ignite Issue Type: Task Reporter: Mikhail Filatov Assignee: Mikhail Filatov Add simple linerizability test to Ducktape -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14780) Thin client test should use versions from globals
[ https://issues.apache.org/jira/browse/IGNITE-14780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Filatov updated IGNITE-14780: - Description: Thin client test use hardcoded versions of Ignite. It's more flexible to have options of using versions from globals. > Thin client test should use versions from globals > - > > Key: IGNITE-14780 > URL: https://issues.apache.org/jira/browse/IGNITE-14780 > Project: Ignite > Issue Type: Task >Reporter: Mikhail Filatov >Assignee: Mikhail Filatov >Priority: Major > > Thin client test use hardcoded versions of Ignite. It's more flexible to have > options of using versions from globals. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14780) Thin client test should use versions from globals
[ https://issues.apache.org/jira/browse/IGNITE-14780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Filatov updated IGNITE-14780: - Summary: Thin client test should use versions from globals (was: We should have posibility to override LATEST version param for forks) > Thin client test should use versions from globals > - > > Key: IGNITE-14780 > URL: https://issues.apache.org/jira/browse/IGNITE-14780 > Project: Ignite > Issue Type: Task >Reporter: Mikhail Filatov >Assignee: Mikhail Filatov >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-14786) Authentication ducktest should not use internal api
[ https://issues.apache.org/jira/browse/IGNITE-14786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Filatov closed IGNITE-14786. > Authentication ducktest should not use internal api > --- > > Key: IGNITE-14786 > URL: https://issues.apache.org/jira/browse/IGNITE-14786 > Project: Ignite > Issue Type: Task >Reporter: Mikhail Filatov >Assignee: Mikhail Filatov >Priority: Major > Time Spent: 1h > Remaining Estimate: 0h > > Internal API used in test are different now. > It's better to replace internal api usage to thin client (official > documentation way) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14786) Authentication ducktest should not use internal api
Mikhail Filatov created IGNITE-14786: Summary: Authentication ducktest should not use internal api Key: IGNITE-14786 URL: https://issues.apache.org/jira/browse/IGNITE-14786 Project: Ignite Issue Type: Task Reporter: Mikhail Filatov Assignee: Mikhail Filatov Internal API used in test are different now. It's better to replace internal api usage to thin client (official documentation way) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14780) We should have posibility to override LATEST version param for forks
Mikhail Filatov created IGNITE-14780: Summary: We should have posibility to override LATEST version param for forks Key: IGNITE-14780 URL: https://issues.apache.org/jira/browse/IGNITE-14780 Project: Ignite Issue Type: Task Reporter: Mikhail Filatov Assignee: Mikhail Filatov -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-14727) SSL test should work with custom persistance root
[ https://issues.apache.org/jira/browse/IGNITE-14727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Filatov resolved IGNITE-14727. -- Resolution: Fixed > SSL test should work with custom persistance root > - > > Key: IGNITE-14727 > URL: https://issues.apache.org/jira/browse/IGNITE-14727 > Project: Ignite > Issue Type: Task >Reporter: Mikhail Filatov >Assignee: Mikhail Filatov >Priority: Trivial > Time Spent: 0.5h > Remaining Estimate: 0h > > In test modules/ducktests/tests/ignitetest/tests/ssl_test.py we have > hard-coded path to the folder with certificates. > A situation when this folder does not exist is possible . > We should get a folder through globals in this test -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14727) SSL test should work with custom persistance root
Mikhail Filatov created IGNITE-14727: Summary: SSL test should work with custom persistance root Key: IGNITE-14727 URL: https://issues.apache.org/jira/browse/IGNITE-14727 Project: Ignite Issue Type: Task Reporter: Mikhail Filatov Assignee: Mikhail Filatov In test modules/ducktests/tests/ignitetest/tests/ssl_test.py we have hard-coded path to the folder with certificates. A situation when this folder does not exist is possible . We should get a folder through globals in this test -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14668) SSL certificates generation on parallel run
Mikhail Filatov created IGNITE-14668: Summary: SSL certificates generation on parallel run Key: IGNITE-14668 URL: https://issues.apache.org/jira/browse/IGNITE-14668 Project: Ignite Issue Type: Task Reporter: Mikhail Filatov Assignee: Mikhail Filatov If we run tests in parallel, certificates should be fully generated before any test run. To accomplish this, we need to wait for certificate generation process to finish -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-14521) Plugins support in Ignite configuration
[
https://issues.apache.org/jira/browse/IGNITE-14521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Filatov closed IGNITE-14521.
> Plugins support in Ignite configuration
> ---
>
> Key: IGNITE-14521
> URL: https://issues.apache.org/jira/browse/IGNITE-14521
> Project: Ignite
> Issue Type: Task
>Reporter: Mikhail Filatov
>Assignee: Mikhail Filatov
>Priority: Major
>
> Add support for plugin configuration with custom macros
> It should be possible to add a plugin configuration toIgnite configuration by
> specifying template path and plugin parameters with code like:
> {% if config.plugins %}
>
>
> \{% for plugin in config.plugins %}
> \{{ misc_utils.generate_plugin_config(plugin['template_path'],
> plugin['config'], config) }}
> \{% endfor %}
>
>
> \{% endif %}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (IGNITE-14521) Plugins support in Ignite configuration
[
https://issues.apache.org/jira/browse/IGNITE-14521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Filatov resolved IGNITE-14521.
--
Resolution: Duplicate
> Plugins support in Ignite configuration
> ---
>
> Key: IGNITE-14521
> URL: https://issues.apache.org/jira/browse/IGNITE-14521
> Project: Ignite
> Issue Type: Task
>Reporter: Mikhail Filatov
>Assignee: Mikhail Filatov
>Priority: Major
>
> Add support for plugin configuration with custom macros
> It should be possible to add a plugin configuration toIgnite configuration by
> specifying template path and plugin parameters with code like:
> {% if config.plugins %}
>
>
> \{% for plugin in config.plugins %}
> \{{ misc_utils.generate_plugin_config(plugin['template_path'],
> plugin['config'], config) }}
> \{% endfor %}
>
>
> \{% endif %}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14521) Plugins support in Ignite configuration
Mikhail Filatov created IGNITE-14521:
Summary: Plugins support in Ignite configuration
Key: IGNITE-14521
URL: https://issues.apache.org/jira/browse/IGNITE-14521
Project: Ignite
Issue Type: Task
Reporter: Mikhail Filatov
Assignee: Mikhail Filatov
Add support for plugin configuration with custom macros
It should be possible to add a plugin configuration toIgnite configuration by
specifying template path and plugin parameters with code like:
{% if config.plugins %}
\{% for plugin in config.plugins %}
\{{ misc_utils.generate_plugin_config(plugin['template_path'],
plugin['config'], config) }}
\{% endfor %}
\{% endif %}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14520) Plugins support in Ignite configuration
Mikhail Filatov created IGNITE-14520:
Summary: Plugins support in Ignite configuration
Key: IGNITE-14520
URL: https://issues.apache.org/jira/browse/IGNITE-14520
Project: Ignite
Issue Type: Task
Reporter: Mikhail Filatov
Assignee: Mikhail Filatov
Add support for plugin configuration with custom macros
It should be possible to add a plugin configuration toIgnite configuration by
specifying template path and plugin parameters with code like:
{% if config.plugins %}
\{% for plugin in config.plugins %}
\{{ misc_utils.generate_plugin_config(plugin['template_path'],
plugin['config'], config) }}
\{% endfor %}
\{% endif %}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (IGNITE-14380) Move certificates for ducktape tests to a separate directory
[ https://issues.apache.org/jira/browse/IGNITE-14380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Filatov resolved IGNITE-14380. -- Resolution: Won't Fix > Move certificates for ducktape tests to a separate directory > - > > Key: IGNITE-14380 > URL: https://issues.apache.org/jira/browse/IGNITE-14380 > Project: Ignite > Issue Type: Task >Reporter: Mikhail Filatov >Assignee: Mikhail Filatov >Priority: Trivial > > Looking for certificates in directory > install_root/ignite-dev/modules/ducktests/tests/certs/ seems a bit strange. > If you run a ducktests not using run_tests.sh (for example: in AWS, or > Vagrand env.), certificates are generates in separate step, and have no > connection with Ignite sources. > Seeam more universal if we place them in install_root/certs -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (IGNITE-14380) Move certificates for ducktape tests to a separate directory
[ https://issues.apache.org/jira/browse/IGNITE-14380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Filatov reopened IGNITE-14380: -- > Move certificates for ducktape tests to a separate directory > - > > Key: IGNITE-14380 > URL: https://issues.apache.org/jira/browse/IGNITE-14380 > Project: Ignite > Issue Type: Task >Reporter: Mikhail Filatov >Assignee: Mikhail Filatov >Priority: Trivial > > Looking for certificates in directory > install_root/ignite-dev/modules/ducktests/tests/certs/ seems a bit strange. > If you run a ducktests not using run_tests.sh (for example: in AWS, or > Vagrand env.), certificates are generates in separate step, and have no > connection with Ignite sources. > Seeam more universal if we place them in install_root/certs -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-14380) Move certificates for ducktape tests to a separate directory
[ https://issues.apache.org/jira/browse/IGNITE-14380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Filatov resolved IGNITE-14380. -- Resolution: Abandoned > Move certificates for ducktape tests to a separate directory > - > > Key: IGNITE-14380 > URL: https://issues.apache.org/jira/browse/IGNITE-14380 > Project: Ignite > Issue Type: Task >Reporter: Mikhail Filatov >Assignee: Mikhail Filatov >Priority: Trivial > > Looking for certificates in directory > install_root/ignite-dev/modules/ducktests/tests/certs/ seems a bit strange. > If you run a ducktests not using run_tests.sh (for example: in AWS, or > Vagrand env.), certificates are generates in separate step, and have no > connection with Ignite sources. > Seeam more universal if we place them in install_root/certs -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13605) Ducktests test: PDS compatibility for ignite versions
[ https://issues.apache.org/jira/browse/IGNITE-13605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Filatov updated IGNITE-13605: - Description: A simple test to check PDS compatibility of different Ignite versions Ignite versions "from_version" and "to_version" are set via test parameters # Start Ignite cluster version "from_version" with PDS enabled # Start a client application that puts prepared data looks like User (1, "John Connor") User (2, "Sarah Connor") User (3, "Kyle Reese") # Stop cluster and client # Start Ignite cluster version "to_version" without PDS clearing # Start client that reads data and checks that it can be read and have not changed was: A simple test to check PDS compatibility of different Ignite versions # Start Ignite cluster with version 1, enabled PDS # Start client that put some data into cluster # Stop client and cluster # Start Ignite cluster with version 2, and PDS from previous cluster # Start client that reads data and checks that the data is same > Ducktests test: PDS compatibility for ignite versions > - > > Key: IGNITE-13605 > URL: https://issues.apache.org/jira/browse/IGNITE-13605 > Project: Ignite > Issue Type: New Feature >Reporter: Maksim Timonin >Assignee: Mikhail Filatov >Priority: Major > Time Spent: 40m > Remaining Estimate: 0h > > A simple test to check PDS compatibility of different Ignite versions > Ignite versions "from_version" and "to_version" are set via test parameters > # Start Ignite cluster version "from_version" with PDS enabled > # Start a client application that puts prepared data looks like > User (1, "John Connor") > User (2, "Sarah Connor") > User (3, "Kyle Reese") > # Stop cluster and client > # Start Ignite cluster version "to_version" without PDS clearing > # Start client that reads data and checks that it can be read and have not > changed > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13605) Ducktests test: PDS compatibility for ignite versions
[ https://issues.apache.org/jira/browse/IGNITE-13605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Filatov updated IGNITE-13605: - Description: A simple test to check PDS compatibility of different Ignite versions # Start Ignite cluster with version 1, enabled PDS # Start client that put some data into cluster # Stop client and cluster # Start Ignite cluster with version 2, and PDS from previous cluster # Start client that reads data and checks that the data is same > Ducktests test: PDS compatibility for ignite versions > - > > Key: IGNITE-13605 > URL: https://issues.apache.org/jira/browse/IGNITE-13605 > Project: Ignite > Issue Type: New Feature >Reporter: Maksim Timonin >Assignee: Mikhail Filatov >Priority: Major > Time Spent: 40m > Remaining Estimate: 0h > > A simple test to check PDS compatibility of different Ignite versions > # Start Ignite cluster with version 1, enabled PDS > # Start client that put some data into cluster > # Stop client and cluster > # Start Ignite cluster with version 2, and PDS from previous cluster > # Start client that reads data and checks that the data is same -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14380) Move certificates for ducktape tests to a separate directory
Mikhail Filatov created IGNITE-14380: Summary: Move certificates for ducktape tests to a separate directory Key: IGNITE-14380 URL: https://issues.apache.org/jira/browse/IGNITE-14380 Project: Ignite Issue Type: Task Reporter: Mikhail Filatov Assignee: Mikhail Filatov Looking for certificates in directory install_root/ignite-dev/modules/ducktests/tests/certs/ seems a bit strange. If you run a ducktests not using run_tests.sh (for example: in AWS, or Vagrand env.), certificates are generates in separate step, and have no connection with Ignite sources. Seeam more universal if we place them in install_root/certs -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14023) Password based authentication support in ducktape tests
[
https://issues.apache.org/jira/browse/IGNITE-14023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Filatov updated IGNITE-14023:
-
Description:
There are users with authentication enabled on the cluster
Ducktape tests should work on such clusters.
Tests should work if authentication is enabled on the cluster via a third-party
plugin
Running Ignite node and application with third-party authentication plugin
remains to be implemented by the developers of that plugin.
In this PR we will only implement the ability to tell control.sh how to
connect to the cluster.
connection parameters should be passed through globals with structure like that.
{"authentication":
{ "enabled": true, "username": "admin", "password": "qwe123"}}
was:
There are users with authentication enabled on the cluster
Ducktape tests should work on such clusters.
Tests should work if authentication is enabled on the cluster via a third-party
plugin
Running Ignite node and application with third-party authentication plugin
remains to be implemented by the developers of that plugin.
In this PR we will only implement the ability to tell control.sh how to
connect to the cluster.
connection parameters should be passed through globals with structure like that.
{"authentication": {
"enabled": true,
"default_credentials": [
"admin",
"qwe123"]}}
> Password based authentication support in ducktape tests
> ---
>
> Key: IGNITE-14023
> URL: https://issues.apache.org/jira/browse/IGNITE-14023
> Project: Ignite
> Issue Type: Task
>Reporter: Mikhail Filatov
>Assignee: Mikhail Filatov
>Priority: Minor
> Time Spent: 11h 40m
> Remaining Estimate: 0h
>
> There are users with authentication enabled on the cluster
> Ducktape tests should work on such clusters.
> Tests should work if authentication is enabled on the cluster via a
> third-party plugin
> Running Ignite node and application with third-party authentication plugin
> remains to be implemented by the developers of that plugin.
> In this PR we will only implement the ability to tell control.sh how to
> connect to the cluster.
> connection parameters should be passed through globals with structure like
> that.
> {"authentication":
> { "enabled": true, "username": "admin", "password": "qwe123"}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14023) Password based authentication support in ducktape tests
[
https://issues.apache.org/jira/browse/IGNITE-14023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Filatov updated IGNITE-14023:
-
Description:
There are users with authentication enabled on the cluster
Ducktape tests should work on such clusters.
Tests should work if authentication is enabled on the cluster via a third-party
plugin
Running Ignite node and application with third-party authentication plugin
remains to be implemented by the developers of that plugin.
In this PR we will only implement the ability to tell control.sh how to
connect to the cluster.
connection parameters should be passed through globals with structure like that.
{"authentication": {
"enabled": true,
"default_credentials": [
"admin",
"qwe123"]}}
was:
There are users with authentication enabled on the cluster
Ducktape tests should work on such clusters.
Tests should work if authentication is enabled on the cluster via a third-party
plugin
Running Ignite node and application with third-party authentication plugin
remains to be implemented by the developers of that plugin.
In this PR we will only implement the ability to tell control.sh how to
connect to the cluster.
connection parameters should be passed through globals with structure like that.
{
"use_ssl": True,
"admin": {
"credentials": ["username", "qwerty_123"],
"ssl": {
"key_store_jks":
}
}
}
> Password based authentication support in ducktape tests
> ---
>
> Key: IGNITE-14023
> URL: https://issues.apache.org/jira/browse/IGNITE-14023
> Project: Ignite
> Issue Type: Task
>Reporter: Mikhail Filatov
>Assignee: Mikhail Filatov
>Priority: Minor
> Time Spent: 10h
> Remaining Estimate: 0h
>
> There are users with authentication enabled on the cluster
> Ducktape tests should work on such clusters.
> Tests should work if authentication is enabled on the cluster via a
> third-party plugin
> Running Ignite node and application with third-party authentication plugin
> remains to be implemented by the developers of that plugin.
> In this PR we will only implement the ability to tell control.sh how to
> connect to the cluster.
> connection parameters should be passed through globals with structure like
> that.
> {"authentication": {
> "enabled": true,
> "default_credentials": [
> "admin",
> "qwe123"]}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14023) Password based authentication support in ducktape tests
[
https://issues.apache.org/jira/browse/IGNITE-14023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Filatov updated IGNITE-14023:
-
Description:
There are users with authentication enabled on the cluster
Ducktape tests should work on such clusters.
Tests should work if authentication is enabled on the cluster via a third-party
plugin
Running Ignite node and application with third-party authentication plugin
remains to be implemented by the developers of that plugin.
In this PR we will only implement the ability to tell control.sh how to
connect to the cluster.
connection parameters should be passed through globals with structure like that.
{
"use_ssl": True,
"admin": {
"credentials": ["username", "qwerty_123"],
"ssl": {
"key_store_jks":
}
}
}
was:
There are users with authentication enabled on the cluster
Ducktape tests should work on such clusters.
Tests should work if authentication is enabled on the cluster via a third-party
plugin
Running Ignite node and application with third-party authentication plugin
remains to be implemented by the developers of that plugin.
In this PR we will only implement the ability to tell control.sh how to
connect to the cluster.
connection parameters should be passed through globals
for default parameters: -gj '\{"use_auth":"True"}'
to pass parameters explicitly: -gj '{"use_auth":"True","admin":{"creds":
{"login":"admin1","password":"qwe123"}
}}'
for a cluster with enabled ssl and authentication: -gj
'\{"use_ssl":"True","use_auth":"True"}'
for a cluster with enabled ssl and authentication: -gj
'{"use_ssl":"True","use_auth":"True","admin":{"creds":
{"login":"admin1","password":"qwe123"}
,"ssl":\{"key_store_jks":"admin1.jks","key_store_password":"qwe123","trust_store_jks":"truststore.jks","trust_store_password":"qwe123"}}}'
> Password based authentication support in ducktape tests
> ---
>
> Key: IGNITE-14023
> URL: https://issues.apache.org/jira/browse/IGNITE-14023
> Project: Ignite
> Issue Type: Task
>Reporter: Mikhail Filatov
>Assignee: Mikhail Filatov
>Priority: Minor
> Time Spent: 3h 40m
> Remaining Estimate: 0h
>
> There are users with authentication enabled on the cluster
> Ducktape tests should work on such clusters.
> Tests should work if authentication is enabled on the cluster via a
> third-party plugin
> Running Ignite node and application with third-party authentication plugin
> remains to be implemented by the developers of that plugin.
> In this PR we will only implement the ability to tell control.sh how to
> connect to the cluster.
> connection parameters should be passed through globals with structure like
> that.
> {
> "use_ssl": True,
> "admin": {
> "credentials": ["username", "qwerty_123"],
> "ssl": {
> "key_store_jks":
> }
> }
> }
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14023) Password based authentication support in ducktape tests
[
https://issues.apache.org/jira/browse/IGNITE-14023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Filatov updated IGNITE-14023:
-
Description:
There are users with authentication enabled on the cluster
Ducktape tests should work on such clusters.
Tests should work if authentication is enabled on the cluster via a third-party
plugin
Running Ignite node and application with third-party authentication plugin
remains to be implemented by the developers of that plugin.
In this PR we will only implement the ability to tell control.sh how to
connect to the cluster.
connection parameters should be passed through globals
for default parameters: -gj '\{"use_auth":"True"}'
to pass parameters explicitly: -gj '{"use_auth":"True","admin":{"creds":
{"login":"admin1","password":"qwe123"}
}}'
for a cluster with enabled ssl and authentication: -gj
'\{"use_ssl":"True","use_auth":"True"}'
for a cluster with enabled ssl and authentication: -gj
'{"use_ssl":"True","use_auth":"True","admin":{"creds":
{"login":"admin1","password":"qwe123"}
,"ssl":\{"key_store_jks":"admin1.jks","key_store_password":"qwe123","trust_store_jks":"truststore.jks","trust_store_password":"qwe123"}}}'
was:
Should be able to write tests with built-in authentication enabled
Tests should work if authentication is enabled on the cluster via a third-party
plugin
Running the Ignite node and application with third-party authentication plugin
remains to be implemented by the developers of this plugin.
In this PR we will only implement the ability to tell control.sh how to
connect to the cluster.
connection parameters should be passed through globals
for default parameters: -gj '\{"use_auth":"True"}'
to pass parameters explicitly: -gj '{"use_auth":"True","admin":{"creds":
{"login":"admin1","password":"qwe123"}
}}'
for a cluster with enabled ssl and authentication: -gj
'\{"use_ssl":"True","use_auth":"True"}'
for a cluster with enabled ssl and authentication: -gj
'{"use_ssl":"True","use_auth":"True","admin":{"creds":
{"login":"admin1","password":"qwe123"}
,"ssl":\{"key_store_jks":"admin1.jks","key_store_password":"qwe123","trust_store_jks":"truststore.jks","trust_store_password":"qwe123"}}}'
> Password based authentication support in ducktape tests
> ---
>
> Key: IGNITE-14023
> URL: https://issues.apache.org/jira/browse/IGNITE-14023
> Project: Ignite
> Issue Type: Task
>Reporter: Mikhail Filatov
>Assignee: Mikhail Filatov
>Priority: Minor
> Time Spent: 2h 40m
> Remaining Estimate: 0h
>
> There are users with authentication enabled on the cluster
> Ducktape tests should work on such clusters.
> Tests should work if authentication is enabled on the cluster via a
> third-party plugin
> Running Ignite node and application with third-party authentication plugin
> remains to be implemented by the developers of that plugin.
> In this PR we will only implement the ability to tell control.sh how to
> connect to the cluster.
> connection parameters should be passed through globals
> for default parameters: -gj '\{"use_auth":"True"}'
> to pass parameters explicitly: -gj '{"use_auth":"True","admin":{"creds":
> {"login":"admin1","password":"qwe123"}
> }}'
> for a cluster with enabled ssl and authentication: -gj
> '\{"use_ssl":"True","use_auth":"True"}'
> for a cluster with enabled ssl and authentication: -gj
> '{"use_ssl":"True","use_auth":"True","admin":{"creds":
> {"login":"admin1","password":"qwe123"}
> ,"ssl":\{"key_store_jks":"admin1.jks","key_store_password":"qwe123","trust_store_jks":"truststore.jks","trust_store_password":"qwe123"}}}'
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14023) Password based authentication support in ducktape tests
[
https://issues.apache.org/jira/browse/IGNITE-14023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Filatov updated IGNITE-14023:
-
Description:
Should be able to write tests with built-in authentication enabled
Tests should work if authentication is enabled on the cluster via a third-party
plugin
Running the Ignite node and application with third-party authentication plugin
remains to be implemented by the developers of this plugin.
In this PR we will only implement the ability to tell control.sh how to
connect to the cluster.
connection parameters should be passed through globals
for default parameters: -gj '\{"use_auth":"True"}'
to pass parameters explicitly: -gj '{"use_auth":"True","admin":{"creds":
{"login":"admin1","password":"qwe123"}
}}'
for a cluster with enabled ssl and authentication: -gj
'\{"use_ssl":"True","use_auth":"True"}'
for a cluster with enabled ssl and authentication: -gj
'{"use_ssl":"True","use_auth":"True","admin":{"creds":
{"login":"admin1","password":"qwe123"}
,"ssl":\{"key_store_jks":"admin1.jks","key_store_password":"qwe123","trust_store_jks":"truststore.jks","trust_store_password":"qwe123"}}}'
was:
Should be able to write tests with authentication enabled for built-in
authentication
Tests should work if authentication is enabled on the cluster via a third-party
plugin
Running the Ignite node and application with third-party authentication remains
to be implemented by the developers of this plugin.
In this PR we will only implement the ability to tell control.sh how to
connect to the cluster.
connection parameters should be passed through globals
for default parameters: -gj '\{"use_auth":"True"}'
to pass parameters explicitly: -gj
'\{"use_auth":"True","admin":{"creds":{"login":"admin1","password":"qwe123"}}}'
for a cluster with enabled ssl and authentication: -gj
'\{"use_ssl":"True","use_auth":"True"}'
for a cluster with enabled ssl and authentication: -gj
'\{"use_ssl":"True","use_auth":"True","admin":{"creds":{"login":"admin1","password":"qwe123"},"ssl":\{"key_store_jks":"admin1.jks","key_store_password":"qwe123","trust_store_jks":"truststore.jks","trust_store_password":"qwe123"}}}'
> Password based authentication support in ducktape tests
> ---
>
> Key: IGNITE-14023
> URL: https://issues.apache.org/jira/browse/IGNITE-14023
> Project: Ignite
> Issue Type: Task
>Reporter: Mikhail Filatov
>Assignee: Mikhail Filatov
>Priority: Minor
>
> Should be able to write tests with built-in authentication enabled
> Tests should work if authentication is enabled on the cluster via a
> third-party plugin
> Running the Ignite node and application with third-party authentication
> plugin remains to be implemented by the developers of this plugin.
> In this PR we will only implement the ability to tell control.sh how to
> connect to the cluster.
> connection parameters should be passed through globals
> for default parameters: -gj '\{"use_auth":"True"}'
> to pass parameters explicitly: -gj '{"use_auth":"True","admin":{"creds":
> {"login":"admin1","password":"qwe123"}
> }}'
> for a cluster with enabled ssl and authentication: -gj
> '\{"use_ssl":"True","use_auth":"True"}'
> for a cluster with enabled ssl and authentication: -gj
> '{"use_ssl":"True","use_auth":"True","admin":{"creds":
> {"login":"admin1","password":"qwe123"}
> ,"ssl":\{"key_store_jks":"admin1.jks","key_store_password":"qwe123","trust_store_jks":"truststore.jks","trust_store_password":"qwe123"}}}'
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14023) Password based authentication support in ducktape tests
[
https://issues.apache.org/jira/browse/IGNITE-14023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Filatov updated IGNITE-14023:
-
Description:
Should be able to write tests with authentication enabled for built-in
authentication
Tests should work if authentication is enabled on the cluster via a third-party
plugin
Running the Ignite node and application with third-party authentication remains
to be implemented by the developers of this plugin.
In this PR we will only implement the ability to tell control.sh how to
connect to the cluster.
connection parameters should be passed through globals
for default parameters: -gj '\{"use_auth":"True"}'
to pass parameters explicitly: -gj
'\{"use_auth":"True","admin":{"creds":{"login":"admin1","password":"qwe123"}}}'
for a cluster with enabled ssl and authentication: -gj
'\{"use_ssl":"True","use_auth":"True"}'
for a cluster with enabled ssl and authentication: -gj
'\{"use_ssl":"True","use_auth":"True","admin":{"creds":{"login":"admin1","password":"qwe123"},"ssl":\{"key_store_jks":"admin1.jks","key_store_password":"qwe123","trust_store_jks":"truststore.jks","trust_store_password":"qwe123"}}}'
was:
Should be able to write tests with authentication enabled for built-in
authentication
Tests should work if authentication is enabled on the cluster via a third-party
plugin
Running the Ignite node and application with third-party authentication remains
to be implemented by the developers of this plugin.
In this PR we will only implement the ability to tell control.sh how to connect
to the cluster.
connection parameters should be passed through globals
for default parameters: -gj '\{"use_auth":"True"}'
to pass parameters explicitly: -gj '\{"use_auth":"True",
"admin":{"login":"admin1","password":"qwe123"}}'
for a cluster with enabled ssl and authentication: -gj
'\{"use_ssl":"True","use_auth":"True"}'
for a cluster with enabled ssl and authentication: -gj
'\{"use_ssl":"True","use_auth":"True","admin":{"login":"admin1","password":"qwe123","ssl":{"key_store_jks":"admin1.jks","key_store_password":"qwe123","trust_store_jks":truststore.jks","trust_store_password":"qwe123"}}}'
> Password based authentication support in ducktape tests
> ---
>
> Key: IGNITE-14023
> URL: https://issues.apache.org/jira/browse/IGNITE-14023
> Project: Ignite
> Issue Type: Task
>Reporter: Mikhail Filatov
>Assignee: Mikhail Filatov
>Priority: Minor
>
> Should be able to write tests with authentication enabled for built-in
> authentication
> Tests should work if authentication is enabled on the cluster via a
> third-party plugin
> Running the Ignite node and application with third-party authentication
> remains to be implemented by the developers of this plugin.
> In this PR we will only implement the ability to tell control.sh how to
> connect to the cluster.
> connection parameters should be passed through globals
> for default parameters: -gj '\{"use_auth":"True"}'
> to pass parameters explicitly: -gj
> '\{"use_auth":"True","admin":{"creds":{"login":"admin1","password":"qwe123"}}}'
> for a cluster with enabled ssl and authentication: -gj
> '\{"use_ssl":"True","use_auth":"True"}'
> for a cluster with enabled ssl and authentication: -gj
> '\{"use_ssl":"True","use_auth":"True","admin":{"creds":{"login":"admin1","password":"qwe123"},"ssl":\{"key_store_jks":"admin1.jks","key_store_password":"qwe123","trust_store_jks":"truststore.jks","trust_store_password":"qwe123"}}}'
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14023) Password based authentication support in ducktape tests
[
https://issues.apache.org/jira/browse/IGNITE-14023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Filatov updated IGNITE-14023:
-
Description:
Should be able to write tests with authentication enabled for built-in
authentication
Tests should work if authentication is enabled on the cluster via a third-party
plugin
Running the Ignite node and application with third-party authentication remains
to be implemented by the developers of this plugin.
In this PR we will only implement the ability to tell control.sh how to connect
to the cluster.
connection parameters should be passed through globals
for default parameters: -gj '\{"use_auth":"True"}'
to pass parameters explicitly: -gj '\{"use_auth":"True",
"admin":{"login":"admin1","password":"qwe123"}}'
for a cluster with enabled ssl and authentication: -gj
'\{"use_ssl":"True","use_auth":"True"}'
for a cluster with enabled ssl and authentication: -gj
'\{"use_ssl":"True","use_auth":"True","admin":{"login":"admin1","password":"qwe123","ssl":{"key_store_jks":"admin1.jks","key_store_password":"qwe123","trust_store_jks":truststore.jks","trust_store_password":"qwe123"}}}'
was:
Authentication usage in ducktape tests
If we have cluster with enabled authentication we need to provide
authentication parameters to controls.sh utility
Necessary:
- tests should work on cluster with enabled authentication
- be able to write tests with authentication enabled
- be able to enable authentication for all tests via globals.
- be able to set the authentication parameters for tests via globals.
for run all tests with authentication you may use globals:
> Password based authentication support in ducktape tests
> ---
>
> Key: IGNITE-14023
> URL: https://issues.apache.org/jira/browse/IGNITE-14023
> Project: Ignite
> Issue Type: Task
>Reporter: Mikhail Filatov
>Assignee: Mikhail Filatov
>Priority: Minor
>
> Should be able to write tests with authentication enabled for built-in
> authentication
> Tests should work if authentication is enabled on the cluster via a
> third-party plugin
> Running the Ignite node and application with third-party authentication
> remains to be implemented by the developers of this plugin.
> In this PR we will only implement the ability to tell control.sh how to
> connect to the cluster.
> connection parameters should be passed through globals
> for default parameters: -gj '\{"use_auth":"True"}'
> to pass parameters explicitly: -gj '\{"use_auth":"True",
> "admin":{"login":"admin1","password":"qwe123"}}'
> for a cluster with enabled ssl and authentication: -gj
> '\{"use_ssl":"True","use_auth":"True"}'
> for a cluster with enabled ssl and authentication: -gj
> '\{"use_ssl":"True","use_auth":"True","admin":{"login":"admin1","password":"qwe123","ssl":{"key_store_jks":"admin1.jks","key_store_password":"qwe123","trust_store_jks":truststore.jks","trust_store_password":"qwe123"}}}'
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14023) Password based authentication support in ducktape tests
[ https://issues.apache.org/jira/browse/IGNITE-14023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Filatov updated IGNITE-14023: - Description: Authentication usage in ducktape tests If we have cluster with enabled authentication we need to provide authentication parameters to controls.sh utility Necessary: - tests should work on cluster with enabled authentication - be able to write tests with authentication enabled - be able to enable authentication for all tests via globals. - be able to set the authentication parameters for tests via globals. for run all tests with authentication you may use globals: was:We s > Password based authentication support in ducktape tests > --- > > Key: IGNITE-14023 > URL: https://issues.apache.org/jira/browse/IGNITE-14023 > Project: Ignite > Issue Type: Task >Reporter: Mikhail Filatov >Assignee: Mikhail Filatov >Priority: Minor > > Authentication usage in ducktape tests > If we have cluster with enabled authentication we need to provide > authentication parameters to controls.sh utility > > Necessary: > - tests should work on cluster with enabled authentication > - be able to write tests with authentication enabled > - be able to enable authentication for all tests via globals. > - be able to set the authentication parameters for tests via globals. > > for run all tests with authentication you may use globals: > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14023) Password based authentication support in ducktape tests
[ https://issues.apache.org/jira/browse/IGNITE-14023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Filatov updated IGNITE-14023: - Description: We s (was: [~map7000], please fill the description.) > Password based authentication support in ducktape tests > --- > > Key: IGNITE-14023 > URL: https://issues.apache.org/jira/browse/IGNITE-14023 > Project: Ignite > Issue Type: Task >Reporter: Mikhail Filatov >Assignee: Mikhail Filatov >Priority: Minor > > We s -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-11972) Jepsen tests should check consistency
[ https://issues.apache.org/jira/browse/IGNITE-11972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Filatov reassigned IGNITE-11972: Assignee: (was: Mikhail Filatov) > Jepsen tests should check consistency > - > > Key: IGNITE-11972 > URL: https://issues.apache.org/jira/browse/IGNITE-11972 > Project: Ignite > Issue Type: Task >Reporter: Anton Vinogradov (Obsolete, actual is "av") >Priority: Major > Labels: iep-31 > > We have to check data is consistent during and after the tests. > Good case is to use: > - idle_verify of test finish > - ReadRepair > -- during the test (some/(all?) gets should be with RR proxy) > -- after the test finish. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-14012) Ducktape jmx_utils should consider the possibility of intermediate MBeans
[ https://issues.apache.org/jira/browse/IGNITE-14012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Filatov closed IGNITE-14012. > Ducktape jmx_utils should consider the possibility of intermediate MBeans > - > > Key: IGNITE-14012 > URL: https://issues.apache.org/jira/browse/IGNITE-14012 > Project: Ignite > Issue Type: Task >Reporter: Mikhail Filatov >Assignee: Mikhail Filatov >Priority: Minor > Time Spent: 20m > Remaining Estimate: 0h > > Sometimes MBeans structure looks like: > org.apache:clsLdr=764c12b6,group=Kernal,igniteInstanceName=Server_Example_Xml_-676757500,name=IgniteKernal > but jmx_utils works only if it looks like: > .*group=Kernal,name=IgniteKernal > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14023) Password based authentication support in ducktape tests
Mikhail Filatov created IGNITE-14023: Summary: Password based authentication support in ducktape tests Key: IGNITE-14023 URL: https://issues.apache.org/jira/browse/IGNITE-14023 Project: Ignite Issue Type: Task Reporter: Mikhail Filatov Assignee: Mikhail Filatov -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14012) Ducktape jmx_utils should consider the possibility of intermediate MBeans
Mikhail Filatov created IGNITE-14012: Summary: Ducktape jmx_utils should consider the possibility of intermediate MBeans Key: IGNITE-14012 URL: https://issues.apache.org/jira/browse/IGNITE-14012 Project: Ignite Issue Type: Task Reporter: Mikhail Filatov Assignee: Mikhail Filatov Sometimes MBeans structure looks like: org.apache:clsLdr=764c12b6,group=Kernal,igniteInstanceName=Server_Example_Xml_-676757500,name=IgniteKernal but jmx_utils works only if it looks like: .*group=Kernal,name=IgniteKernal -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-13605) Ducktests test: PDS compatibility for ignite versions
[ https://issues.apache.org/jira/browse/IGNITE-13605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Filatov reassigned IGNITE-13605: Assignee: Mikhail Filatov > Ducktests test: PDS compatibility for ignite versions > - > > Key: IGNITE-13605 > URL: https://issues.apache.org/jira/browse/IGNITE-13605 > Project: Ignite > Issue Type: New Feature >Reporter: Maksim Timonin >Assignee: Mikhail Filatov >Priority: Major > Labels: IEP-56, ducktape > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-10706) SSL engine error in TcpCommunicationSpi connection is interrupted immediately after task send
Mikhail Filatov created IGNITE-10706: Summary: SSL engine error in TcpCommunicationSpi connection is interrupted immediately after task send Key: IGNITE-10706 URL: https://issues.apache.org/jira/browse/IGNITE-10706 Project: Ignite Issue Type: Bug Environment: java version "1.8.0_121" Java(TM) SE Runtime Environment (build 1.8.0_121-b13) Java HotSpot(TM) 64-Bit Server VM (build 25.121-b13, mixed mode) Reporter: Mikhail Filatov Attachments: client.log, server.log Reproduced in test GridTcpCommunicationSpiSslSelfTest#testSendToManyNodes Application logs inclided -- This message was sent by Atlassian JIRA (v7.6.3#76005)
