[jira] [Updated] (IGNITE-17061) Invalid detection of SPI on configuration validation.
[ https://issues.apache.org/jira/browse/IGNITE-17061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko updated IGNITE-17061: --- Description: When I configure different deployment SPI for different nodes I receive the next message _Remote SPI with the same name is not configured_ when I expect to get the message _Remote SPI with the same name is of different type_ I got it because *org.apache.ignite.spi.IgniteSpiAdapter* use *U.getSimpleName(getClass())* for SPI name generation in org.apache.ignite.spi.IgniteSpiAdapter#IgniteSpiAdapter`, that looks like a mistake. was: When I configure different deployment SPI for different nodes I receive the next message Remote SPI with the same name is not configured when I expect to get the message Remote SPI with the same name is of different type I got it because *org.apache.ignite.spi.IgniteSpiAdapter* use *U.getSimpleName(getClass())* for SPI name generation in org.apache.ignite.spi.IgniteSpiAdapter#IgniteSpiAdapter`, that looks like a mistake. > Invalid detection of SPI on configuration validation. > - > > Key: IGNITE-17061 > URL: https://issues.apache.org/jira/browse/IGNITE-17061 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 2.13 >Reporter: Vasiliy Sisko >Priority: Major > > When I configure different deployment SPI for different nodes I receive the > next message > _Remote SPI with the same name is not configured_ > when I expect to get the message > _Remote SPI with the same name is of different type_ > I got it because *org.apache.ignite.spi.IgniteSpiAdapter* use > *U.getSimpleName(getClass())* for SPI name generation in > org.apache.ignite.spi.IgniteSpiAdapter#IgniteSpiAdapter`, that looks like a > mistake. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IGNITE-17061) Invalid detection of SPI on configuration validation.
Vasiliy Sisko created IGNITE-17061: -- Summary: Invalid detection of SPI on configuration validation. Key: IGNITE-17061 URL: https://issues.apache.org/jira/browse/IGNITE-17061 Project: Ignite Issue Type: Bug Components: general Affects Versions: 2.13 Reporter: Vasiliy Sisko When I configure different deployment SPI for different nodes I receive the next message Remote SPI with the same name is not configured when I expect to get the message Remote SPI with the same name is of different type I got it because *org.apache.ignite.spi.IgniteSpiAdapter* use *U.getSimpleName(getClass())* for SPI name generation in org.apache.ignite.spi.IgniteSpiAdapter#IgniteSpiAdapter`, that looks like a mistake. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (IGNITE-12613) Scala (Visor Console) test failed on Java 9+
[ https://issues.apache.org/jira/browse/IGNITE-12613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko reassigned IGNITE-12613: -- Assignee: Alexey Kuznetsov (was: Vasiliy Sisko) > Scala (Visor Console) test failed on Java 9+ > > > Key: IGNITE-12613 > URL: https://issues.apache.org/jira/browse/IGNITE-12613 > Project: Ignite > Issue Type: Improvement > Components: visor >Affects Versions: mas >Reporter: Vasiliy Sisko >Assignee: Alexey Kuznetsov >Priority: Major > Fix For: mas > > Time Spent: 10m > Remaining Estimate: 0h > > Failed test on TC agents with Java 9+ > [https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_ScalaVisorConsole/4975900] > Noticed that Scala libraries and scalatest library are different for > different java versions. > Scala libraries and scalatest library should be updated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12613) Scala (Visor Console) test failed on Java 8+
Vasiliy Sisko created IGNITE-12613: -- Summary: Scala (Visor Console) test failed on Java 8+ Key: IGNITE-12613 URL: https://issues.apache.org/jira/browse/IGNITE-12613 Project: Ignite Issue Type: Improvement Components: visor Affects Versions: mas Reporter: Vasiliy Sisko Assignee: Vasiliy Sisko Fix For: mas Failed test on TC agents with Java 9+ [https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_ScalaVisorConsole/4975900] Noticed that Scala libraries and scalatest library are different for different java versions. Scala libraries and scalatest library should be updated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12613) Scala (Visor Console) test failed on Java 9+
[ https://issues.apache.org/jira/browse/IGNITE-12613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko updated IGNITE-12613: --- Summary: Scala (Visor Console) test failed on Java 9+ (was: Scala (Visor Console) test failed on Java 8+) > Scala (Visor Console) test failed on Java 9+ > > > Key: IGNITE-12613 > URL: https://issues.apache.org/jira/browse/IGNITE-12613 > Project: Ignite > Issue Type: Improvement > Components: visor >Affects Versions: mas >Reporter: Vasiliy Sisko >Assignee: Vasiliy Sisko >Priority: Major > Fix For: mas > > > Failed test on TC agents with Java 9+ > [https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_ScalaVisorConsole/4975900] > Noticed that Scala libraries and scalatest library are different for > different java versions. > Scala libraries and scalatest library should be updated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-8996) Web console: Dropdown pupup menu is scrolled with page body on modal dialog.
[ https://issues.apache.org/jira/browse/IGNITE-8996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16834355#comment-16834355 ] Vasiliy Sisko commented on IGNITE-8996: --- Still reproduced. > Web console: Dropdown pupup menu is scrolled with page body on modal dialog. > > > Key: IGNITE-8996 > URL: https://issues.apache.org/jira/browse/IGNITE-8996 > Project: Ignite > Issue Type: Bug > Components: wizards >Affects Versions: 2.6 >Reporter: Vasiliy Sisko >Assignee: Vasiliy Sisko >Priority: Major > > # Open *Cluster* configuration of *Advanced* tab of *Configure* page. > # Open *Import from database* dialog > # On *Tables* step expand any dropdown > # Try to scroll mouse on area instead of import dialog. > On scroll the dropdown popup is scrolled together with background content. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-10847) Web console: failed to download the mongodb on Ubuntu 18.04
[
https://issues.apache.org/jira/browse/IGNITE-10847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasiliy Sisko reassigned IGNITE-10847:
--
Assignee: Andrey Novikov (was: Vasiliy Sisko)
> Web console: failed to download the mongodb on Ubuntu 18.04
> ---
>
> Key: IGNITE-10847
> URL: https://issues.apache.org/jira/browse/IGNITE-10847
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7
>Reporter: Pavel Konstantinov
>Assignee: Andrey Novikov
>Priority: Major
>
> I tried to run 'web console direct install' and faced with an error
> downloading of MongoDB due to there is no corresponding version for that OS.
> {code}
> name: 'StatusCodeError',
> statusCode: 403,
> message: '403 - " encoding=\\"UTF-8\\"?>\\nAccessDeniedAccess
> Denied4B7715F9CDA5127BzuhNAWP7FGOgDLjkNJ3y71iU+wxcWKR5F5kI4LoO1SqCdt+aPeLZXnJko5S0ji2zx5zkJaCZX3g="',
> error: ' encoding="UTF-8"?>\nAccessDeniedAccess
> Denied4B7715F9CDA5127BzuhNAWP7FGOgDLjkNJ3y71iU+wxcWKR5F5kI4LoO1SqCdt+aPeLZXnJko5S0ji2zx5zkJaCZX3g=',
> options:
>{ uri:
> 'https://fastdl.mongodb.org/linux/mongodb-linux-x86_64-ubuntu1804-3.4.7.tgz.md5',
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10847) Web console: failed to download the mongodb on Ubuntu 18.04
[
https://issues.apache.org/jira/browse/IGNITE-10847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16822859#comment-16822859
]
Vasiliy Sisko commented on IGNITE-10847:
Fixed Tests.
Removed deprecated method usages.
> Web console: failed to download the mongodb on Ubuntu 18.04
> ---
>
> Key: IGNITE-10847
> URL: https://issues.apache.org/jira/browse/IGNITE-10847
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7
>Reporter: Pavel Konstantinov
>Assignee: Vasiliy Sisko
>Priority: Major
>
> I tried to run 'web console direct install' and faced with an error
> downloading of MongoDB due to there is no corresponding version for that OS.
> {code}
> name: 'StatusCodeError',
> statusCode: 403,
> message: '403 - " encoding=\\"UTF-8\\"?>\\nAccessDeniedAccess
> Denied4B7715F9CDA5127BzuhNAWP7FGOgDLjkNJ3y71iU+wxcWKR5F5kI4LoO1SqCdt+aPeLZXnJko5S0ji2zx5zkJaCZX3g="',
> error: ' encoding="UTF-8"?>\nAccessDeniedAccess
> Denied4B7715F9CDA5127BzuhNAWP7FGOgDLjkNJ3y71iU+wxcWKR5F5kI4LoO1SqCdt+aPeLZXnJko5S0ji2zx5zkJaCZX3g=',
> options:
>{ uri:
> 'https://fastdl.mongodb.org/linux/mongodb-linux-x86_64-ubuntu1804-3.4.7.tgz.md5',
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10847) Web console: failed to download the mongodb on Ubuntu 18.04
[
https://issues.apache.org/jira/browse/IGNITE-10847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16820927#comment-16820927
]
Vasiliy Sisko commented on IGNITE-10847:
[~anovikov] Please review my changes.
> Web console: failed to download the mongodb on Ubuntu 18.04
> ---
>
> Key: IGNITE-10847
> URL: https://issues.apache.org/jira/browse/IGNITE-10847
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7
>Reporter: Pavel Konstantinov
>Assignee: Andrey Novikov
>Priority: Major
>
> I tried to run 'web console direct install' and faced with an error
> downloading of MongoDB due to there is no corresponding version for that OS.
> {code}
> name: 'StatusCodeError',
> statusCode: 403,
> message: '403 - " encoding=\\"UTF-8\\"?>\\nAccessDeniedAccess
> Denied4B7715F9CDA5127BzuhNAWP7FGOgDLjkNJ3y71iU+wxcWKR5F5kI4LoO1SqCdt+aPeLZXnJko5S0ji2zx5zkJaCZX3g="',
> error: ' encoding="UTF-8"?>\nAccessDeniedAccess
> Denied4B7715F9CDA5127BzuhNAWP7FGOgDLjkNJ3y71iU+wxcWKR5F5kI4LoO1SqCdt+aPeLZXnJko5S0ji2zx5zkJaCZX3g=',
> options:
>{ uri:
> 'https://fastdl.mongodb.org/linux/mongodb-linux-x86_64-ubuntu1804-3.4.7.tgz.md5',
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-10847) Web console: failed to download the mongodb on Ubuntu 18.04
[
https://issues.apache.org/jira/browse/IGNITE-10847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasiliy Sisko reassigned IGNITE-10847:
--
Assignee: Andrey Novikov (was: Vasiliy Sisko)
> Web console: failed to download the mongodb on Ubuntu 18.04
> ---
>
> Key: IGNITE-10847
> URL: https://issues.apache.org/jira/browse/IGNITE-10847
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7
>Reporter: Pavel Konstantinov
>Assignee: Andrey Novikov
>Priority: Major
>
> I tried to run 'web console direct install' and faced with an error
> downloading of MongoDB due to there is no corresponding version for that OS.
> {code}
> name: 'StatusCodeError',
> statusCode: 403,
> message: '403 - " encoding=\\"UTF-8\\"?>\\nAccessDeniedAccess
> Denied4B7715F9CDA5127BzuhNAWP7FGOgDLjkNJ3y71iU+wxcWKR5F5kI4LoO1SqCdt+aPeLZXnJko5S0ji2zx5zkJaCZX3g="',
> error: ' encoding="UTF-8"?>\nAccessDeniedAccess
> Denied4B7715F9CDA5127BzuhNAWP7FGOgDLjkNJ3y71iU+wxcWKR5F5kI4LoO1SqCdt+aPeLZXnJko5S0ji2zx5zkJaCZX3g=',
> options:
>{ uri:
> 'https://fastdl.mongodb.org/linux/mongodb-linux-x86_64-ubuntu1804-3.4.7.tgz.md5',
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10847) Web console: failed to download the mongodb on Ubuntu 18.04
[
https://issues.apache.org/jira/browse/IGNITE-10847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16818748#comment-16818748
]
Vasiliy Sisko commented on IGNITE-10847:
Failed to run backend tests:
{code:java}
fireUp# ERROR Loading the module through
require('/home/vsisko/gridgain/incubator-ignite/modules/web-console/backend/test/app/mockgoose.js')
failed: Cannot find module 'mockgoose'
Error: Cannot find module 'mockgoose'
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:581:15)
at Function.Module._load (internal/modules/cjs/loader.js:507:25)
at Module.require (internal/modules/cjs/loader.js:637:17)
at require (internal/modules/cjs/helpers.js:22:18)
at Object.
(/home/vsisko/gridgain/incubator-ignite/modules/web-console/backend/test/app/mockgoose.js:21:19)
at Module._compile (internal/modules/cjs/loader.js:689:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
at Module.load (internal/modules/cjs/loader.js:599:32)
at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
at Function.Module._load (internal/modules/cjs/loader.js:530:3)
at Module.require (internal/modules/cjs/loader.js:637:17)
at require (internal/modules/cjs/helpers.js:22:18)
at registerModulesFromPaths
(/home/vsisko/gridgain/incubator-ignite/modules/web-console/backend/node_modules/fire-up/lib/core/loader.js:63:18)
at Object.registerModules
(/home/vsisko/gridgain/incubator-ignite/modules/web-console/backend/node_modules/fire-up/lib/core/loader.js:24:5)
at Object.createNewInjector
(/home/vsisko/gridgain/incubator-ignite/modules/web-console/backend/node_modules/fire-up/lib/core/core.js:70:18)
at Object.newInjector
(/home/vsisko/gridgain/incubator-ignite/modules/web-console/backend/node_modules/fire-up/lib/index.js:9:17)
at Object.
(/home/vsisko/gridgain/incubator-ignite/modules/web-console/backend/test/injector.js:21:25)
at Module._compile (internal/modules/cjs/loader.js:689:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
at Module.load (internal/modules/cjs/loader.js:599:32)
at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
at Function.Module._load (internal/modules/cjs/loader.js:530:3)
at Module.require (internal/modules/cjs/loader.js:637:17)
at require (internal/modules/cjs/helpers.js:22:18)
at Object.
(/home/vsisko/gridgain/incubator-ignite/modules/web-console/backend/test/unit/ActivitiesService.test.js:19:18)
at Module._compile (internal/modules/cjs/loader.js:689:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
at Module.load (internal/modules/cjs/loader.js:599:32)
{ err:
{ ModuleLoadingError: Loading the module through
require('/home/vsisko/gridgain/incubator-ignite/modules/web-console/backend/test/app/mockgoose.js')
failed: Cannot find module 'mockgoose'
at new ModuleLoadingError
(/home/vsisko/gridgain/incubator-ignite/modules/web-console/backend/node_modules/fire-up/lib/definitions/errors.js:25:9)
at registerModulesFromPaths
(/home/vsisko/gridgain/incubator-ignite/modules/web-console/backend/node_modules/fire-up/lib/core/loader.js:69:26)
at Object.registerModules
(/home/vsisko/gridgain/incubator-ignite/modules/web-console/backend/node_modules/fire-up/lib/core/loader.js:24:5)
at Object.createNewInjector
(/home/vsisko/gridgain/incubator-ignite/modules/web-console/backend/node_modules/fire-up/lib/core/core.js:70:18)
at Object.newInjector
(/home/vsisko/gridgain/incubator-ignite/modules/web-console/backend/node_modules/fire-up/lib/index.js:9:17)
at Object.
(/home/vsisko/gridgain/incubator-ignite/modules/web-console/backend/test/injector.js:21:25)
at Module._compile (internal/modules/cjs/loader.js:689:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
at Module.load (internal/modules/cjs/loader.js:599:32)
at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
at Function.Module._load (internal/modules/cjs/loader.js:530:3)
at Module.require (internal/modules/cjs/loader.js:637:17)
at require (internal/modules/cjs/helpers.js:22:18)
at Object.
(/home/vsisko/gridgain/incubator-ignite/modules/web-console/backend/test/unit/ActivitiesService.test.js:19:18)
at Module._compile (internal/modules/cjs/loader.js:689:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
at Module.load (internal/modules/cjs/loader.js:599:32)
at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
at Function.Module._load (internal/modules/cjs/loader.js:530:3)
at Module.require (internal/modules/cjs/loader.js:637:17)
at require (internal/modules/cjs/helpers.js:22:18)
at
/home/vsisko/gridgain/incubator-ignite/modules/web-console/backend/node_mod
[jira] [Assigned] (IGNITE-10847) Web console: failed to download the mongodb on Ubuntu 18.04
[
https://issues.apache.org/jira/browse/IGNITE-10847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasiliy Sisko reassigned IGNITE-10847:
--
Assignee: Vasiliy Sisko (was: Andrey Novikov)
> Web console: failed to download the mongodb on Ubuntu 18.04
> ---
>
> Key: IGNITE-10847
> URL: https://issues.apache.org/jira/browse/IGNITE-10847
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7
>Reporter: Pavel Konstantinov
>Assignee: Vasiliy Sisko
>Priority: Major
>
> I tried to run 'web console direct install' and faced with an error
> downloading of MongoDB due to there is no corresponding version for that OS.
> {code}
> name: 'StatusCodeError',
> statusCode: 403,
> message: '403 - " encoding=\\"UTF-8\\"?>\\nAccessDeniedAccess
> Denied4B7715F9CDA5127BzuhNAWP7FGOgDLjkNJ3y71iU+wxcWKR5F5kI4LoO1SqCdt+aPeLZXnJko5S0ji2zx5zkJaCZX3g="',
> error: ' encoding="UTF-8"?>\nAccessDeniedAccess
> Denied4B7715F9CDA5127BzuhNAWP7FGOgDLjkNJ3y71iU+wxcWKR5F5kI4LoO1SqCdt+aPeLZXnJko5S0ji2zx5zkJaCZX3g=',
> options:
>{ uri:
> 'https://fastdl.mongodb.org/linux/mongodb-linux-x86_64-ubuntu1804-3.4.7.tgz.md5',
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11154) Web Console "Save and Download" Button downloads incorrect configuration
[ https://issues.apache.org/jira/browse/IGNITE-11154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16817630#comment-16817630 ] Vasiliy Sisko commented on IGNITE-11154: Looks like the same problem as in IGNITE-11601. [~Klaster_1] Please try to fix IGNITE-11601 and try to reproduce current error with that fix. > Web Console "Save and Download" Button downloads incorrect configuration > > > Key: IGNITE-11154 > URL: https://issues.apache.org/jira/browse/IGNITE-11154 > Project: Ignite > Issue Type: Bug > Components: wizards >Affects Versions: 2.7 >Reporter: Glenn Wiebe >Assignee: Vasiliy Sisko >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > When navigating through the Web Console's Configuration pages to a particular > configuration and then selecting the "save" button's drop down alternate link > function: "Save and Download", the configuration zip that is actually > downloaded, is: > a. named incorrectly (not the name of hte config), and > b. may be another configuration (depending on ordering of all configurations > managed. > Opening the zip, one can find the name of the configuration in the root > pom.xml or in the > src/main/resources/META-INF folder *-client.xml and *-server.xml > configuration files. > In my test case, I was editing the first configuration in my list of three > configs, and when I was under advanced I hit the "save" button's drop-down > list option and the subsequent "Save and Download" link and got a zip file > that was named "ImportedCluster-project.zip" instead of the actual name that > I was editing, and it was also not the name of the actual project downloaded. > Regards, > Glenn -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11154) Web Console "Save and Download" Button downloads incorrect configuration
[ https://issues.apache.org/jira/browse/IGNITE-11154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko reassigned IGNITE-11154: -- Assignee: Ilya Borisov (was: Vasiliy Sisko) > Web Console "Save and Download" Button downloads incorrect configuration > > > Key: IGNITE-11154 > URL: https://issues.apache.org/jira/browse/IGNITE-11154 > Project: Ignite > Issue Type: Bug > Components: wizards >Affects Versions: 2.7 >Reporter: Glenn Wiebe >Assignee: Ilya Borisov >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > When navigating through the Web Console's Configuration pages to a particular > configuration and then selecting the "save" button's drop down alternate link > function: "Save and Download", the configuration zip that is actually > downloaded, is: > a. named incorrectly (not the name of hte config), and > b. may be another configuration (depending on ordering of all configurations > managed. > Opening the zip, one can find the name of the configuration in the root > pom.xml or in the > src/main/resources/META-INF folder *-client.xml and *-server.xml > configuration files. > In my test case, I was editing the first configuration in my list of three > configs, and when I was under advanced I hit the "save" button's drop-down > list option and the subsequent "Save and Download" link and got a zip file > that was named "ImportedCluster-project.zip" instead of the actual name that > I was editing, and it was also not the name of the actual project downloaded. > Regards, > Glenn -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11601) The 'Save and Download' action saves wrong cluster
[ https://issues.apache.org/jira/browse/IGNITE-11601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16817628#comment-16817628 ] Vasiliy Sisko commented on IGNITE-11601: To reproduce: # Open advanced configuration of any cluster and *Save* it. # Open advanced configuration of other cluster and *Save and Download* it. First opened and saved cluster is downloaded in that case. I notice that ConfigEffects.advancedDownloadAfterSaveEffect$ get result of previous ADVANCED_SAVE_COMPLETE_CONFIGURATION_OK event before ADVANCED_SAVE_COMPLETE_CONFIGURATION action is finished. [~Klaster_1] Please try to fix that issue. > The 'Save and Download' action saves wrong cluster > -- > > Key: IGNITE-11601 > URL: https://issues.apache.org/jira/browse/IGNITE-11601 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Konstantinov >Assignee: Vasiliy Sisko >Priority: Major > Fix For: 2.8 > > Attachments: screenshot-1.png > > Time Spent: 0.25h > Remaining Estimate: 0h > > Create the first cluster, save and download - all works right > Create a second cluster, save and download - a first cluster actually saved > !screenshot-1.png! > The workaround is to click on 'See project structure' before saving the > project -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11601) The 'Save and Download' action saves wrong cluster
[ https://issues.apache.org/jira/browse/IGNITE-11601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko reassigned IGNITE-11601: -- Assignee: Ilya Borisov (was: Vasiliy Sisko) > The 'Save and Download' action saves wrong cluster > -- > > Key: IGNITE-11601 > URL: https://issues.apache.org/jira/browse/IGNITE-11601 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Konstantinov >Assignee: Ilya Borisov >Priority: Major > Fix For: 2.8 > > Attachments: screenshot-1.png > > Time Spent: 0.25h > Remaining Estimate: 0h > > Create the first cluster, save and download - all works right > Create a second cluster, save and download - a first cluster actually saved > !screenshot-1.png! > The workaround is to click on 'See project structure' before saving the > project -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11717) Web console: project generation runtime error caused by IGFS
[ https://issues.apache.org/jira/browse/IGNITE-11717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko reassigned IGNITE-11717: -- Assignee: Alexey Kuznetsov (was: Vasiliy Sisko) > Web console: project generation runtime error caused by IGFS > > > Key: IGNITE-11717 > URL: https://issues.apache.org/jira/browse/IGNITE-11717 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Ilya Borisov >Assignee: Alexey Kuznetsov >Priority: Major > Attachments: image-2019-04-10-17-52-48-599.png > > > *What happens:* > Runtime error in console. > !image-2019-04-10-17-52-48-599.png! > How to reproduce: > 1. Go to cluster configuration/create igfs. > 2. Choose "Caching" FS factory. > 3. Choose "Chained" user name mapper. > 4. Open new mapper sub form, choose custom. > 5. Change FS factory a couple of time, change it back to "Caching". > 6. Do the same with with "Name mapper" select, change it back to "Custom". > 7. If the error does not happen, play around by changing other select values. > *Expected behavior:* > Run time error should not happen. > This happens in master. [~vsisko] I think you should look into why `bean` is > `null` or handle this case gracefully. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11717) Web console: project generation runtime error caused by IGFS
[ https://issues.apache.org/jira/browse/IGNITE-11717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16816139#comment-16816139 ] Vasiliy Sisko commented on IGNITE-11717: Fixed generation of Custom user name mapper of IGFS Secondary file system when class name is not configured. Fixed generation of Custom file system factory of IGFS Secondary file system when class name is not configured. > Web console: project generation runtime error caused by IGFS > > > Key: IGNITE-11717 > URL: https://issues.apache.org/jira/browse/IGNITE-11717 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Ilya Borisov >Assignee: Vasiliy Sisko >Priority: Major > Attachments: image-2019-04-10-17-52-48-599.png > > > *What happens:* > Runtime error in console. > !image-2019-04-10-17-52-48-599.png! > How to reproduce: > 1. Go to cluster configuration/create igfs. > 2. Choose "Caching" FS factory. > 3. Choose "Chained" user name mapper. > 4. Open new mapper sub form, choose custom. > 5. Change FS factory a couple of time, change it back to "Caching". > 6. Do the same with with "Name mapper" select, change it back to "Custom". > 7. If the error does not happen, play around by changing other select values. > *Expected behavior:* > Run time error should not happen. > This happens in master. [~vsisko] I think you should look into why `bean` is > `null` or handle this case gracefully. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-11711) Web console: MS SQL server missing JDBC download link
[ https://issues.apache.org/jira/browse/IGNITE-11711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16815212#comment-16815212 ] Vasiliy Sisko edited comment on IGNITE-11711 at 4/11/19 9:12 AM: - Fixed showing of the link. Now it is shown only for data sources, which have the link. Link to JDBC driver for MS SQL server is removed because now JDBC driver is available on central Maven repository. https://search.maven.org/search?q=g:com.microsoft.sqlserver%20AND%20a:mssql-jdbc&core=gav was (Author: vsisko): Fixed showing of the link. Now it is shown only for data sources, which have the link. [https://github.com/apache/ignite/pull/6436] > Web console: MS SQL server missing JDBC download link > - > > Key: IGNITE-11711 > URL: https://issues.apache.org/jira/browse/IGNITE-11711 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Ilya Borisov >Assignee: Alexey Kuznetsov >Priority: Minor > Attachments: image-2019-04-10-12-54-22-561.png > > Time Spent: 10m > Remaining Estimate: 0h > > *What happens:* > In configuration / advanced / caches / store if user selects "JDBC Pojo store > factory" and "MS SQL Server" dialect, a link labeled "Download JDBC drivers?" > is displayed. When "oracle" or "IBM" dialects are selected, the link leads to > a proper download page, while "MS" dialect link leads nowhere. > !image-2019-04-10-12-54-22-561.png! > *Expected behavior:* > If there is a download page for MS JDBC driver, add it's URL to JDBC_LINKS > provider. If there's none, maybe don't show the link or show appropriate > plain text? > The issue was reproduced in master. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11711) Web console: MS SQL server missing JDBC download link
[ https://issues.apache.org/jira/browse/IGNITE-11711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko reassigned IGNITE-11711: -- Assignee: Alexey Kuznetsov (was: Vasiliy Sisko) > Web console: MS SQL server missing JDBC download link > - > > Key: IGNITE-11711 > URL: https://issues.apache.org/jira/browse/IGNITE-11711 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Ilya Borisov >Assignee: Alexey Kuznetsov >Priority: Minor > Attachments: image-2019-04-10-12-54-22-561.png > > Time Spent: 10m > Remaining Estimate: 0h > > *What happens:* > In configuration / advanced / caches / store if user selects "JDBC Pojo store > factory" and "MS SQL Server" dialect, a link labeled "Download JDBC drivers?" > is displayed. When "oracle" or "IBM" dialects are selected, the link leads to > a proper download page, while "MS" dialect link leads nowhere. > !image-2019-04-10-12-54-22-561.png! > *Expected behavior:* > If there is a download page for MS JDBC driver, add it's URL to JDBC_LINKS > provider. If there's none, maybe don't show the link or show appropriate > plain text? > The issue was reproduced in master. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-11711) Web console: MS SQL server missing JDBC download link
[ https://issues.apache.org/jira/browse/IGNITE-11711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16815212#comment-16815212 ] Vasiliy Sisko edited comment on IGNITE-11711 at 4/11/19 8:53 AM: - Fixed showing of the link. Now it is shown only for data sources, which have the link. [https://github.com/apache/ignite/pull/6436] was (Author: vsisko): Fixed showing of the link. Now it is shown only for data sources, which have the link. > Web console: MS SQL server missing JDBC download link > - > > Key: IGNITE-11711 > URL: https://issues.apache.org/jira/browse/IGNITE-11711 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Ilya Borisov >Assignee: Vasiliy Sisko >Priority: Minor > Attachments: image-2019-04-10-12-54-22-561.png > > Time Spent: 10m > Remaining Estimate: 0h > > *What happens:* > In configuration / advanced / caches / store if user selects "JDBC Pojo store > factory" and "MS SQL Server" dialect, a link labeled "Download JDBC drivers?" > is displayed. When "oracle" or "IBM" dialects are selected, the link leads to > a proper download page, while "MS" dialect link leads nowhere. > !image-2019-04-10-12-54-22-561.png! > *Expected behavior:* > If there is a download page for MS JDBC driver, add it's URL to JDBC_LINKS > provider. If there's none, maybe don't show the link or show appropriate > plain text? > The issue was reproduced in master. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11711) Web console: MS SQL server missing JDBC download link
[ https://issues.apache.org/jira/browse/IGNITE-11711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16815212#comment-16815212 ] Vasiliy Sisko commented on IGNITE-11711: Fixed showing of the link. Now it is shown only for data sources, which have the link. > Web console: MS SQL server missing JDBC download link > - > > Key: IGNITE-11711 > URL: https://issues.apache.org/jira/browse/IGNITE-11711 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Ilya Borisov >Assignee: Vasiliy Sisko >Priority: Minor > Attachments: image-2019-04-10-12-54-22-561.png > > > *What happens:* > In configuration / advanced / caches / store if user selects "JDBC Pojo store > factory" and "MS SQL Server" dialect, a link labeled "Download JDBC drivers?" > is displayed. When "oracle" or "IBM" dialects are selected, the link leads to > a proper download page, while "MS" dialect link leads nowhere. > !image-2019-04-10-12-54-22-561.png! > *Expected behavior:* > If there is a download page for MS JDBC driver, add it's URL to JDBC_LINKS > provider. If there's none, maybe don't show the link or show appropriate > plain text? > The issue was reproduced in master. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11716) Web console: can't select cluster memory eviction mode
[ https://issues.apache.org/jira/browse/IGNITE-11716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko reassigned IGNITE-11716: -- Assignee: Vasiliy Sisko (was: Alexey Kuznetsov) > Web console: can't select cluster memory eviction mode > -- > > Key: IGNITE-11716 > URL: https://issues.apache.org/jira/browse/IGNITE-11716 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Ilya Borisov >Assignee: Vasiliy Sisko >Priority: Minor > Attachments: image-2019-04-10-17-02-17-310.png > > Time Spent: 10m > Remaining Estimate: 0h > > What happens: > Memory eviction mode select has no options to choose from and there's an > error in console. > !image-2019-04-10-17-02-17-310.png! > Expected behavior: > The error should not happen, user should be able to select eviction mode. > Note: select configuration version 2.1 to see "memory" section in advanced > cluster configuration. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11601) The 'Save and Download' action saves wrong cluster
[ https://issues.apache.org/jira/browse/IGNITE-11601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko reassigned IGNITE-11601: -- Assignee: Vasiliy Sisko > The 'Save and Download' action saves wrong cluster > -- > > Key: IGNITE-11601 > URL: https://issues.apache.org/jira/browse/IGNITE-11601 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Konstantinov >Assignee: Vasiliy Sisko >Priority: Major > Fix For: 2.8 > > Attachments: screenshot-1.png > > > Create the first cluster, save and download - all works right > Create a second cluster, save and download - a first cluster actually saved > !screenshot-1.png! > The workaround is to click on 'See project structure' before saving the > project -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11636) Web console: incorrect value is restored after Refresh
[ https://issues.apache.org/jira/browse/IGNITE-11636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802657#comment-16802657 ] Vasiliy Sisko commented on IGNITE-11636: Changes looks good. > Web console: incorrect value is restored after Refresh > -- > > Key: IGNITE-11636 > URL: https://issues.apache.org/jira/browse/IGNITE-11636 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.8 >Reporter: Pavel Konstantinov >Assignee: Andrey Novikov >Priority: Major > Labels: wizard > Time Spent: 10m > Remaining Estimate: 0h > > Start two clusters with the same caches. > Load some data in the first. > Leave caches in the second cluster empty. > Open SQL, select the first cluster, execute any select > Press F5 to refresh the page > Expected - the first cluster must be selected > Actual - the second cluster is selected -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-11638) Web console: 'Export All' in query result table doesn't work
[ https://issues.apache.org/jira/browse/IGNITE-11638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802651#comment-16802651 ] Vasiliy Sisko edited comment on IGNITE-11638 at 3/27/19 10:46 AM: -- Looks good. Tested. was (Author: vsisko): Looks good. Checked. > Web console: 'Export All' in query result table doesn't work > > > Key: IGNITE-11638 > URL: https://issues.apache.org/jira/browse/IGNITE-11638 > Project: Ignite > Issue Type: Test > Components: wizards >Affects Versions: 2.8 >Reporter: Andrey Novikov >Assignee: Andrey Novikov >Priority: Minor > Fix For: 2.8 > > Attachments: image.png > > > Execute any EXPLAIN > Try to 'Export All' -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11638) Web console: 'Export All' in query result table doesn't work
[ https://issues.apache.org/jira/browse/IGNITE-11638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802651#comment-16802651 ] Vasiliy Sisko commented on IGNITE-11638: Looks good. Checked. > Web console: 'Export All' in query result table doesn't work > > > Key: IGNITE-11638 > URL: https://issues.apache.org/jira/browse/IGNITE-11638 > Project: Ignite > Issue Type: Test > Components: wizards >Affects Versions: 2.8 >Reporter: Andrey Novikov >Assignee: Andrey Novikov >Priority: Minor > Fix For: 2.8 > > Attachments: image.png > > > Execute any EXPLAIN > Try to 'Export All' -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11283) Web console: Actualize grid configuration. Check deprecated fields
[ https://issues.apache.org/jira/browse/IGNITE-11283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko reassigned IGNITE-11283: -- Assignee: Pavel Konstantinov (was: Vasiliy Sisko) > Web console: Actualize grid configuration. Check deprecated fields > -- > > Key: IGNITE-11283 > URL: https://issues.apache.org/jira/browse/IGNITE-11283 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Vasiliy Sisko >Assignee: Pavel Konstantinov >Priority: Major > Attachments: screenshot-1.png > > > Result for class: > org.apache.ignite.cache.affinity.rendezvous.RendezvousAffinityFunction > Deprecated > backupFilter > Result for class: org.apache.ignite.configuration.PersistentStoreConfiguration > Deprecated > walBufferSize > writeThrottlingEnabled > checkpointWriteOrder > fileIOFactory > walMode > walAutoArchiveAfterInactivity > Result for class: org.apache.ignite.configuration.TransactionConfiguration > Missed > deadlockTimeout > useJtaSynchronization > txTimeoutOnPartitionMapExchange > Deprecated > txSerializableEnabled > txManagerLookupClassName > Result for class: org.apache.ignite.configuration.ConnectorConfiguration > Deprecated > sslContextFactory -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11182) Web console: Actualize grid configurator
[ https://issues.apache.org/jira/browse/IGNITE-11182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko reassigned IGNITE-11182: -- Assignee: Pavel Konstantinov (was: Vasiliy Sisko) > Web console: Actualize grid configurator > > > Key: IGNITE-11182 > URL: https://issues.apache.org/jira/browse/IGNITE-11182 > Project: Ignite > Issue Type: Improvement >Reporter: Vasiliy Sisko >Assignee: Pavel Konstantinov >Priority: Major > > WebConsoleConfigurationSelfTest has found the next difference: > Result for class: org.apache.ignite.hadoop.fs.CachingHadoopFileSystemFactory > Missed > userNameMapper > Result for class: org.apache.ignite.ssl.SslContextFactory > Missed > cipherSuites > protocols > Result for class: org.apache.ignite.configuration.CacheConfiguration > Missed > cacheWriterFactory > expiryPolicyFactory > storeConcurrentLoadAllThreshold > sqlIndexMaxInlineSize > sqlOnheapCacheEnabled > interceptor > invalidate > diskPageCompression > storeByValue > sqlOnheapCacheMaxSize > eagerTtl > evictionPolicyFactory > encryptionEnabled > eventsDisabled > cacheLoaderFactory > keyConfiguration > cacheStoreSessionListenerFactories > diskPageCompressionLevel > maxQueryIteratorsCount > affinity > Deprecated > rebalanceThreadPoolSize > transactionManagerLookupClassName > Removed > isInvalidate -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-11182) Web console: Actualize grid configurator
[ https://issues.apache.org/jira/browse/IGNITE-11182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802536#comment-16802536 ] Vasiliy Sisko edited comment on IGNITE-11182 at 3/27/19 8:17 AM: - invalidate/isInvalidate field available in General section for PARTITIONED TRANSACTIONAL cache. See affinity in Affinity collocation section of cache configuration. rebalanceThreadPoolSize was removed early. Moved to IgniteConfiguration#rebalanceThreadPoolSize transactionManagerLookupClassName was removed early. was (Author: vsisko): ++invalidate/isInvalidate field available in General section for PARTITIONED TRANSACTIONAL cache. rebalanceThreadPoolSize was removed early. Moved to IgniteConfiguration#rebalanceThreadPoolSize transactionManagerLookupClassName was removed early. > Web console: Actualize grid configurator > > > Key: IGNITE-11182 > URL: https://issues.apache.org/jira/browse/IGNITE-11182 > Project: Ignite > Issue Type: Improvement >Reporter: Vasiliy Sisko >Assignee: Vasiliy Sisko >Priority: Major > > WebConsoleConfigurationSelfTest has found the next difference: > Result for class: org.apache.ignite.hadoop.fs.CachingHadoopFileSystemFactory > Missed > userNameMapper > Result for class: org.apache.ignite.ssl.SslContextFactory > Missed > cipherSuites > protocols > Result for class: org.apache.ignite.configuration.CacheConfiguration > Missed > cacheWriterFactory > expiryPolicyFactory > storeConcurrentLoadAllThreshold > sqlIndexMaxInlineSize > sqlOnheapCacheEnabled > interceptor > invalidate > diskPageCompression > storeByValue > sqlOnheapCacheMaxSize > eagerTtl > evictionPolicyFactory > encryptionEnabled > eventsDisabled > cacheLoaderFactory > keyConfiguration > cacheStoreSessionListenerFactories > diskPageCompressionLevel > maxQueryIteratorsCount > affinity > Deprecated > rebalanceThreadPoolSize > transactionManagerLookupClassName > Removed > isInvalidate -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11182) Web console: Actualize grid configurator
[ https://issues.apache.org/jira/browse/IGNITE-11182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802536#comment-16802536 ] Vasiliy Sisko commented on IGNITE-11182: ++invalidate/isInvalidate field available in General section for PARTITIONED TRANSACTIONAL cache. rebalanceThreadPoolSize was removed early. Moved to IgniteConfiguration#rebalanceThreadPoolSize transactionManagerLookupClassName was removed early. > Web console: Actualize grid configurator > > > Key: IGNITE-11182 > URL: https://issues.apache.org/jira/browse/IGNITE-11182 > Project: Ignite > Issue Type: Improvement >Reporter: Vasiliy Sisko >Assignee: Vasiliy Sisko >Priority: Major > > WebConsoleConfigurationSelfTest has found the next difference: > Result for class: org.apache.ignite.hadoop.fs.CachingHadoopFileSystemFactory > Missed > userNameMapper > Result for class: org.apache.ignite.ssl.SslContextFactory > Missed > cipherSuites > protocols > Result for class: org.apache.ignite.configuration.CacheConfiguration > Missed > cacheWriterFactory > expiryPolicyFactory > storeConcurrentLoadAllThreshold > sqlIndexMaxInlineSize > sqlOnheapCacheEnabled > interceptor > invalidate > diskPageCompression > storeByValue > sqlOnheapCacheMaxSize > eagerTtl > evictionPolicyFactory > encryptionEnabled > eventsDisabled > cacheLoaderFactory > keyConfiguration > cacheStoreSessionListenerFactories > diskPageCompressionLevel > maxQueryIteratorsCount > affinity > Deprecated > rebalanceThreadPoolSize > transactionManagerLookupClassName > Removed > isInvalidate -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-11283) Web console: Actualize grid configuration. Check deprecated fields
[ https://issues.apache.org/jira/browse/IGNITE-11283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802516#comment-16802516 ] Vasiliy Sisko edited comment on IGNITE-11283 at 3/27/19 7:40 AM: - # Disabled fields for PersistentStoreConfiguration. # transactionConfiguration.setDeadlockTimeout - implemented in IGNITE-11029 that is marked for 2.8 version. was (Author: vsisko): # Disabled fields for PersistentStoreConfiguration. # transactionConfiguration.setDeadlockTimeout - implemented in IGNITE-11029 that marked for 2.8 version. > Web console: Actualize grid configuration. Check deprecated fields > -- > > Key: IGNITE-11283 > URL: https://issues.apache.org/jira/browse/IGNITE-11283 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Vasiliy Sisko >Assignee: Vasiliy Sisko >Priority: Major > Attachments: screenshot-1.png > > > Result for class: > org.apache.ignite.cache.affinity.rendezvous.RendezvousAffinityFunction > Deprecated > backupFilter > Result for class: org.apache.ignite.configuration.PersistentStoreConfiguration > Deprecated > walBufferSize > writeThrottlingEnabled > checkpointWriteOrder > fileIOFactory > walMode > walAutoArchiveAfterInactivity > Result for class: org.apache.ignite.configuration.TransactionConfiguration > Missed > deadlockTimeout > useJtaSynchronization > txTimeoutOnPartitionMapExchange > Deprecated > txSerializableEnabled > txManagerLookupClassName > Result for class: org.apache.ignite.configuration.ConnectorConfiguration > Deprecated > sslContextFactory -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11283) Web console: Actualize grid configuration. Check deprecated fields
[ https://issues.apache.org/jira/browse/IGNITE-11283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802516#comment-16802516 ] Vasiliy Sisko commented on IGNITE-11283: # Disabled fields for PersistentStoreConfiguration. # transactionConfiguration.setDeadlockTimeout - implemented in IGNITE-11029 that marked for 2.8 version. > Web console: Actualize grid configuration. Check deprecated fields > -- > > Key: IGNITE-11283 > URL: https://issues.apache.org/jira/browse/IGNITE-11283 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Vasiliy Sisko >Assignee: Vasiliy Sisko >Priority: Major > Attachments: screenshot-1.png > > > Result for class: > org.apache.ignite.cache.affinity.rendezvous.RendezvousAffinityFunction > Deprecated > backupFilter > Result for class: org.apache.ignite.configuration.PersistentStoreConfiguration > Deprecated > walBufferSize > writeThrottlingEnabled > checkpointWriteOrder > fileIOFactory > walMode > walAutoArchiveAfterInactivity > Result for class: org.apache.ignite.configuration.TransactionConfiguration > Missed > deadlockTimeout > useJtaSynchronization > txTimeoutOnPartitionMapExchange > Deprecated > txSerializableEnabled > txManagerLookupClassName > Result for class: org.apache.ignite.configuration.ConnectorConfiguration > Deprecated > sslContextFactory -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11354) Web console: Actualize grid configurator discovery, store, atomic, communication
[ https://issues.apache.org/jira/browse/IGNITE-11354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802497#comment-16802497 ] Vasiliy Sisko commented on IGNITE-11354: # walCompactionLevel - moved # nodeAttributes - See my previous comment # discoveryStartupDelay - See in Communication section for versions: [1.0 - 2.3) # setReconnectDelay - Created issue IGNITE-11635 # groupName - failed to reproduce # setSoLinger - failed to reproduce > Web console: Actualize grid configurator discovery, store, atomic, > communication > > > Key: IGNITE-11354 > URL: https://issues.apache.org/jira/browse/IGNITE-11354 > Project: Ignite > Issue Type: Improvement >Reporter: Vasiliy Sisko >Assignee: Vasiliy Sisko >Priority: Major > Attachments: image-2019-03-20-13-15-22-387.png > > > Result for class: org.apache.ignite.configuration.DataStorageConfiguration > Missed > maxWalArchiveSize > checkpointReadLockTimeout > walCompactionLevel > Result for class: org.apache.ignite.configuration.AtomicConfiguration > Missed > groupName > Result for class: org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi > Missed > nodeAttributes > connectionRecoveryTimeout > reconnectDelay > soLinger > Result for class: org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi > Missed > usePairedConnections > connectionsPerNode > selectorSpins > filterReachableAddresses > Removed > discoveryStartupDelay -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11354) Web console: Actualize grid configurator discovery, store, atomic, communication
[ https://issues.apache.org/jira/browse/IGNITE-11354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko reassigned IGNITE-11354: -- Assignee: Pavel Konstantinov (was: Vasiliy Sisko) > Web console: Actualize grid configurator discovery, store, atomic, > communication > > > Key: IGNITE-11354 > URL: https://issues.apache.org/jira/browse/IGNITE-11354 > Project: Ignite > Issue Type: Improvement >Reporter: Vasiliy Sisko >Assignee: Pavel Konstantinov >Priority: Major > Attachments: image-2019-03-20-13-15-22-387.png > > > Result for class: org.apache.ignite.configuration.DataStorageConfiguration > Missed > maxWalArchiveSize > checkpointReadLockTimeout > walCompactionLevel > Result for class: org.apache.ignite.configuration.AtomicConfiguration > Missed > groupName > Result for class: org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi > Missed > nodeAttributes > connectionRecoveryTimeout > reconnectDelay > soLinger > Result for class: org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi > Missed > usePairedConnections > connectionsPerNode > selectorSpins > filterReachableAddresses > Removed > discoveryStartupDelay -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11635) Wrong type of setter argument for TcpDiscoverySpi#reconDelay
Vasiliy Sisko created IGNITE-11635: -- Summary: Wrong type of setter argument for TcpDiscoverySpi#reconDelay Key: IGNITE-11635 URL: https://issues.apache.org/jira/browse/IGNITE-11635 Project: Ignite Issue Type: Improvement Components: general Affects Versions: 2.4 Reporter: Vasiliy Sisko org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi#reconDelay variable has long type but org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi#setReconnectDelay accept argument with int type. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11361) Web console: Actualize grid configurator IgniteConfiguration
[ https://issues.apache.org/jira/browse/IGNITE-11361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko reassigned IGNITE-11361: -- Assignee: Pavel Konstantinov (was: Vasiliy Sisko) > Web console: Actualize grid configurator IgniteConfiguration > > > Key: IGNITE-11361 > URL: https://issues.apache.org/jira/browse/IGNITE-11361 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Vasiliy Sisko >Assignee: Pavel Konstantinov >Priority: Major > Attachments: image-2019-03-21-13-10-03-170.png, screenshot-1.png > > > Result for class: org.apache.ignite.configuration.IgniteConfiguration > Missed > failureHandler IGNITE-11385 > authenticationEnabled > autoActivationEnabled > sqlQueryHistorySize > lifecycleBeans > sqlSchemas > igniteInstanceName > addressResolver > igniteHome > localEventListeners IGNITE-11386 > mBeanServer > networkCompressionLevel > communicationFailureResolver > systemWorkerBlockedTimeout > platformConfiguration > includeProperties > cacheStoreSessionListenerFactories > encryptionSpi IGNITE-11387 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11361) Web console: Actualize grid configurator IgniteConfiguration
[ https://issues.apache.org/jira/browse/IGNITE-11361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802439#comment-16802439 ] Vasiliy Sisko commented on IGNITE-11361: # setSqlQueryHistorySize is implemented in IGNITE-10754 that is marked in 2.8. That changes is not merged from master yet. # Please describe what field has BigDecimal type. # Removed field igniteInstanceName from Miscellaneous section. Configure cluster name instead. # Added in Miscellaneous section. # See Communication section for version 2.8. > Web console: Actualize grid configurator IgniteConfiguration > > > Key: IGNITE-11361 > URL: https://issues.apache.org/jira/browse/IGNITE-11361 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Vasiliy Sisko >Assignee: Vasiliy Sisko >Priority: Major > Attachments: image-2019-03-21-13-10-03-170.png, screenshot-1.png > > > Result for class: org.apache.ignite.configuration.IgniteConfiguration > Missed > failureHandler IGNITE-11385 > authenticationEnabled > autoActivationEnabled > sqlQueryHistorySize > lifecycleBeans > sqlSchemas > igniteInstanceName > addressResolver > igniteHome > localEventListeners IGNITE-11386 > mBeanServer > networkCompressionLevel > communicationFailureResolver > systemWorkerBlockedTimeout > platformConfiguration > includeProperties > cacheStoreSessionListenerFactories > encryptionSpi IGNITE-11387 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11385) Web console: Actualize configuragion for failureHandler field of IgniteConfiguration
[ https://issues.apache.org/jira/browse/IGNITE-11385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko reassigned IGNITE-11385: -- Assignee: Pavel Konstantinov (was: Vasiliy Sisko) > Web console: Actualize configuragion for failureHandler field of > IgniteConfiguration > > > Key: IGNITE-11385 > URL: https://issues.apache.org/jira/browse/IGNITE-11385 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Vasiliy Sisko >Assignee: Pavel Konstantinov >Priority: Major > > Missed in configurator. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11385) Web console: Actualize configuragion for failureHandler field of IgniteConfiguration
[ https://issues.apache.org/jira/browse/IGNITE-11385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16801545#comment-16801545 ] Vasiliy Sisko commented on IGNITE-11385: Added constructor arguments for StopNodeOrHaltFailureHandler Fixed ignoredFailureTypes property name. > Web console: Actualize configuragion for failureHandler field of > IgniteConfiguration > > > Key: IGNITE-11385 > URL: https://issues.apache.org/jira/browse/IGNITE-11385 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Vasiliy Sisko >Assignee: Vasiliy Sisko >Priority: Major > > Missed in configurator. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11386) Web console: Actualize configuragion for localEventListeners field of IgniteConfiguration
[ https://issues.apache.org/jira/browse/IGNITE-11386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16801360#comment-16801360 ] Vasiliy Sisko commented on IGNITE-11386: Fixed project generation. > Web console: Actualize configuragion for localEventListeners field of > IgniteConfiguration > - > > Key: IGNITE-11386 > URL: https://issues.apache.org/jira/browse/IGNITE-11386 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Vasiliy Sisko >Assignee: Vasiliy Sisko >Priority: Major > Time Spent: 1h 20m > Remaining Estimate: 0h > > Missed field in configurator. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11386) Web console: Actualize configuragion for localEventListeners field of IgniteConfiguration
[ https://issues.apache.org/jira/browse/IGNITE-11386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko reassigned IGNITE-11386: -- Assignee: Pavel Konstantinov (was: Vasiliy Sisko) > Web console: Actualize configuragion for localEventListeners field of > IgniteConfiguration > - > > Key: IGNITE-11386 > URL: https://issues.apache.org/jira/browse/IGNITE-11386 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Vasiliy Sisko >Assignee: Pavel Konstantinov >Priority: Major > Time Spent: 1h 20m > Remaining Estimate: 0h > > Missed field in configurator. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11284) Web console: Actualize grid configuration: query entity and Pojo store
[ https://issues.apache.org/jira/browse/IGNITE-11284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16801334#comment-16801334 ] Vasiliy Sisko commented on IGNITE-11284: Types fields is generated when domain models for cache with store is configured. > Web console: Actualize grid configuration: query entity and Pojo store > -- > > Key: IGNITE-11284 > URL: https://issues.apache.org/jira/browse/IGNITE-11284 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Vasiliy Sisko >Assignee: Vasiliy Sisko >Priority: Major > Fix For: 2.8 > > Attachments: image-2019-03-20-14-09-36-634.png > > > Result for class: org.apache.ignite.cache.QueryEntity > Missed > fieldsPrecision > notNullFields > fieldsScale > defaultFieldValues > Result for class: org.apache.ignite.cache.store.jdbc.CacheJdbcPojoStoreFactory > Missed > types > Result for class: org.apache.ignite.cache.QueryIndex > Missed > inlineSize -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11284) Web console: Actualize grid configuration: query entity and Pojo store
[ https://issues.apache.org/jira/browse/IGNITE-11284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko reassigned IGNITE-11284: -- Assignee: Pavel Konstantinov (was: Vasiliy Sisko) > Web console: Actualize grid configuration: query entity and Pojo store > -- > > Key: IGNITE-11284 > URL: https://issues.apache.org/jira/browse/IGNITE-11284 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Vasiliy Sisko >Assignee: Pavel Konstantinov >Priority: Major > Fix For: 2.8 > > Attachments: image-2019-03-20-14-09-36-634.png > > > Result for class: org.apache.ignite.cache.QueryEntity > Missed > fieldsPrecision > notNullFields > fieldsScale > defaultFieldValues > Result for class: org.apache.ignite.cache.store.jdbc.CacheJdbcPojoStoreFactory > Missed > types > Result for class: org.apache.ignite.cache.QueryIndex > Missed > inlineSize -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11496) Long running SQL queries could be randomly canceled from WC
[
https://issues.apache.org/jira/browse/IGNITE-11496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasiliy Sisko reassigned IGNITE-11496:
--
Assignee: Alexey Kuznetsov (was: Vasiliy Sisko)
> Long running SQL queries could be randomly canceled from WC
> ---
>
> Key: IGNITE-11496
> URL: https://issues.apache.org/jira/browse/IGNITE-11496
> Project: Ignite
> Issue Type: Bug
> Components: wizards
>Affects Versions: 2.5
>Reporter: Evgenii Zhuravlev
>Assignee: Alexey Kuznetsov
>Priority: Major
> Fix For: 2.8
>
>
> I've tried to run some long-running queries from WC(more than a couple of
> minutes) and I've faced a behavior when the query was canceled without
> clicking on the cancel button.
> I've opened different browser tabs at this moment, maybe it could be the
> reason.
> {code}
> javax.cache.CacheException: Failed to run reduce query locally.
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:883)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$7.iterator(IgniteH2Indexing.java:1494)
> at
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:95)
> at
> org.apache.ignite.internal.visor.query.VisorQueryHolder.getIterator(VisorQueryHolder.java:97)
> at
> org.apache.ignite.internal.visor.query.VisorQueryFetchFirstPageTask$VisorQueryFetchFirstPageJob.run(VisorQueryFetchFirstPageTask.java:85)
> at
> org.apache.ignite.internal.visor.query.VisorQueryFetchFirstPageTask$VisorQueryFetchFirstPageJob.run(VisorQueryFetchFirstPageTask.java:51)
> at org.apache.ignite.internal.visor.VisorJob.execute(VisorJob.java:69)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:568)
> at
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6750)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:562)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:491)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at
> org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1123)
> at
> org.apache.ignite.internal.processors.job.GridJobProcessor$JobExecutionListener.onMessage(GridJobProcessor.java:1921)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1556)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1184)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:125)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1091)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class org.apache.ignite.cache.query.QueryCancelledException: The
> query was cancelled while executing.
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQuery(IgniteH2Indexing.java:1240)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQueryWithTimer(IgniteH2Indexing.java:1303)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQueryWithTimer(IgniteH2Indexing.java:1281)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:835)
> ... 20 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-11519) Web Console: Pack configuration tests in test-jar
[ https://issues.apache.org/jira/browse/IGNITE-11519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko reassigned IGNITE-11519: -- Assignee: Alexey Kuznetsov (was: Vasiliy Sisko) > Web Console: Pack configuration tests in test-jar > - > > Key: IGNITE-11519 > URL: https://issues.apache.org/jira/browse/IGNITE-11519 > Project: Ignite > Issue Type: Test > Components: wizards >Affects Versions: 2.7 >Reporter: Andrey Novikov >Assignee: Alexey Kuznetsov >Priority: Major > Fix For: 2.8 > > Time Spent: 20m > Remaining Estimate: 0h > > IGNITE-8145 has introduced tests for covering the configuration. I think it > would be better to pack these tests into a test-jar, in order to be able to > expand in other modules. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11035) Web console: Implemement improvements for query page controller.
[
https://issues.apache.org/jira/browse/IGNITE-11035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasiliy Sisko reassigned IGNITE-11035:
--
Assignee: Andrey Novikov (was: Vasiliy Sisko)
> Web console: Implemement improvements for query page controller.
>
>
> Key: IGNITE-11035
> URL: https://issues.apache.org/jira/browse/IGNITE-11035
> Project: Ignite
> Issue Type: Improvement
>Reporter: Vasiliy Sisko
>Assignee: Andrey Novikov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 5h 35m
> Remaining Estimate: 0h
>
> # Implement processing of query result task without one level recursion.
> # Explicit serialization to JSON of Paragraph object. Possible
> {{Paragraph.prototype.toJSON should be implemented.}}
> # {{Try to use RXJS operator chain instead of direct usage of subscription
> object.}}
> # {{On query cancel task unlock UI in Promise.prototype.finally.}}
> # {{Check initialization of queryId and resultNodeId on execute of refresh
> in auto refresh mode.}}
> # {{Some paragraph manipulation methods should be moved into Paragraph
> class: _initQueryResult}}{{{color:#00}_, _showLoading._
> {color}}}{{{color:#00}Check other methods with paragraph as
> argument.{color}}}
> # {{{color:#00}Check clearing of data in _initQueryResult method.
> {color}}}{{{color:#00}Try to not use direct calling of grid
> API{color}}}{{{color:#00}. Possible we should show
> “{color}}}{{{color:#00}Query execution{color}}}{{{color:#00}” stub
> {color}}}{{{color:#00}instead.{color}}}
> # {{{color:#00}Remove “beforeunload” listener on leave of Queries
> page.{color}}}
> # {{{color:#00}Possible we should cancel queries when client session is
> over.{color}}}
> # {{{color:#00}Add docs for return values of queries task in agent
> manager. F.e:{color}}}
> {code:java}
> /*
> @returns {Promise}
> */{code}
> # Confirm on leaving of Queries page when running queries exist:
> {code:java}
> You have running queries. Are you sure you want to cancel them?
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11519) Web Console: Pack configuration tests in test-jar
[ https://issues.apache.org/jira/browse/IGNITE-11519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16789696#comment-16789696 ] Vasiliy Sisko commented on IGNITE-11519: configuration test is packed to test jar > Web Console: Pack configuration tests in test-jar > - > > Key: IGNITE-11519 > URL: https://issues.apache.org/jira/browse/IGNITE-11519 > Project: Ignite > Issue Type: Test > Components: wizards >Affects Versions: 2.7 >Reporter: Andrey Novikov >Assignee: Vasiliy Sisko >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > IGNITE-8145 has introduced tests for covering the configuration. I think it > would be better to pack these tests into a test-jar, in order to be able to > expand in other modules. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11519) Web Console: Pack configuration tests in test-jar
[ https://issues.apache.org/jira/browse/IGNITE-11519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko reassigned IGNITE-11519: -- Assignee: Vasiliy Sisko > Web Console: Pack configuration tests in test-jar > - > > Key: IGNITE-11519 > URL: https://issues.apache.org/jira/browse/IGNITE-11519 > Project: Ignite > Issue Type: Test > Components: wizards >Affects Versions: 2.7 >Reporter: Andrey Novikov >Assignee: Vasiliy Sisko >Priority: Major > Fix For: 2.8 > > > IGNITE-8145 has introduced tests for covering the configuration. I think it > would be better to pack these tests into a test-jar, in order to be able to > expand in other modules. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11496) Long running SQL queries could be randomly canceled from WC
[
https://issues.apache.org/jira/browse/IGNITE-11496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16789124#comment-16789124
]
Vasiliy Sisko commented on IGNITE-11496:
Based on fixes of IGNITE-11035. Please test that issues together.
> Long running SQL queries could be randomly canceled from WC
> ---
>
> Key: IGNITE-11496
> URL: https://issues.apache.org/jira/browse/IGNITE-11496
> Project: Ignite
> Issue Type: Bug
> Components: wizards
>Affects Versions: 2.5
>Reporter: Evgenii Zhuravlev
>Assignee: Andrey Novikov
>Priority: Major
>
> I've tried to run some long-running queries from WC(more than a couple of
> minutes) and I've faced a behavior when the query was canceled without
> clicking on the cancel button.
> I've opened different browser tabs at this moment, maybe it could be the
> reason.
> {code}
> javax.cache.CacheException: Failed to run reduce query locally.
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:883)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$7.iterator(IgniteH2Indexing.java:1494)
> at
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:95)
> at
> org.apache.ignite.internal.visor.query.VisorQueryHolder.getIterator(VisorQueryHolder.java:97)
> at
> org.apache.ignite.internal.visor.query.VisorQueryFetchFirstPageTask$VisorQueryFetchFirstPageJob.run(VisorQueryFetchFirstPageTask.java:85)
> at
> org.apache.ignite.internal.visor.query.VisorQueryFetchFirstPageTask$VisorQueryFetchFirstPageJob.run(VisorQueryFetchFirstPageTask.java:51)
> at org.apache.ignite.internal.visor.VisorJob.execute(VisorJob.java:69)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:568)
> at
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6750)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:562)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:491)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at
> org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1123)
> at
> org.apache.ignite.internal.processors.job.GridJobProcessor$JobExecutionListener.onMessage(GridJobProcessor.java:1921)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1556)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1184)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:125)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1091)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class org.apache.ignite.cache.query.QueryCancelledException: The
> query was cancelled while executing.
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQuery(IgniteH2Indexing.java:1240)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQueryWithTimer(IgniteH2Indexing.java:1303)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQueryWithTimer(IgniteH2Indexing.java:1281)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:835)
> ... 20 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-11496) Long running SQL queries could be randomly canceled from WC
[
https://issues.apache.org/jira/browse/IGNITE-11496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasiliy Sisko reassigned IGNITE-11496:
--
Assignee: Andrey Novikov (was: Sergey Kozlov)
> Long running SQL queries could be randomly canceled from WC
> ---
>
> Key: IGNITE-11496
> URL: https://issues.apache.org/jira/browse/IGNITE-11496
> Project: Ignite
> Issue Type: Bug
> Components: wizards
>Affects Versions: 2.5
>Reporter: Evgenii Zhuravlev
>Assignee: Andrey Novikov
>Priority: Major
>
> I've tried to run some long-running queries from WC(more than a couple of
> minutes) and I've faced a behavior when the query was canceled without
> clicking on the cancel button.
> I've opened different browser tabs at this moment, maybe it could be the
> reason.
> {code}
> javax.cache.CacheException: Failed to run reduce query locally.
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:883)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$7.iterator(IgniteH2Indexing.java:1494)
> at
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:95)
> at
> org.apache.ignite.internal.visor.query.VisorQueryHolder.getIterator(VisorQueryHolder.java:97)
> at
> org.apache.ignite.internal.visor.query.VisorQueryFetchFirstPageTask$VisorQueryFetchFirstPageJob.run(VisorQueryFetchFirstPageTask.java:85)
> at
> org.apache.ignite.internal.visor.query.VisorQueryFetchFirstPageTask$VisorQueryFetchFirstPageJob.run(VisorQueryFetchFirstPageTask.java:51)
> at org.apache.ignite.internal.visor.VisorJob.execute(VisorJob.java:69)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:568)
> at
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6750)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:562)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:491)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at
> org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1123)
> at
> org.apache.ignite.internal.processors.job.GridJobProcessor$JobExecutionListener.onMessage(GridJobProcessor.java:1921)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1556)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1184)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:125)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1091)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class org.apache.ignite.cache.query.QueryCancelledException: The
> query was cancelled while executing.
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQuery(IgniteH2Indexing.java:1240)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQueryWithTimer(IgniteH2Indexing.java:1303)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQueryWithTimer(IgniteH2Indexing.java:1281)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:835)
> ... 20 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11496) Long running SQL queries could be randomly canceled from WC
[
https://issues.apache.org/jira/browse/IGNITE-11496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16786618#comment-16786618
]
Vasiliy Sisko commented on IGNITE-11496:
Implemented notification of node when extraction of query results is long.
> Long running SQL queries could be randomly canceled from WC
> ---
>
> Key: IGNITE-11496
> URL: https://issues.apache.org/jira/browse/IGNITE-11496
> Project: Ignite
> Issue Type: Bug
> Components: wizards
>Affects Versions: 2.5
>Reporter: Evgenii Zhuravlev
>Assignee: Vasiliy Sisko
>Priority: Major
>
> I've tried to run some long-running queries from WC(more than a couple of
> minutes) and I've faced a behavior when the query was canceled without
> clicking on the cancel button.
> I've opened different browser tabs at this moment, maybe it could be the
> reason.
> {code}
> javax.cache.CacheException: Failed to run reduce query locally.
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:883)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$7.iterator(IgniteH2Indexing.java:1494)
> at
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:95)
> at
> org.apache.ignite.internal.visor.query.VisorQueryHolder.getIterator(VisorQueryHolder.java:97)
> at
> org.apache.ignite.internal.visor.query.VisorQueryFetchFirstPageTask$VisorQueryFetchFirstPageJob.run(VisorQueryFetchFirstPageTask.java:85)
> at
> org.apache.ignite.internal.visor.query.VisorQueryFetchFirstPageTask$VisorQueryFetchFirstPageJob.run(VisorQueryFetchFirstPageTask.java:51)
> at org.apache.ignite.internal.visor.VisorJob.execute(VisorJob.java:69)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:568)
> at
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6750)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:562)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:491)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at
> org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1123)
> at
> org.apache.ignite.internal.processors.job.GridJobProcessor$JobExecutionListener.onMessage(GridJobProcessor.java:1921)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1556)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1184)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:125)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1091)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class org.apache.ignite.cache.query.QueryCancelledException: The
> query was cancelled while executing.
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQuery(IgniteH2Indexing.java:1240)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQueryWithTimer(IgniteH2Indexing.java:1303)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQueryWithTimer(IgniteH2Indexing.java:1281)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:835)
> ... 20 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-11496) Long running SQL queries could be randomly canceled from WC
[
https://issues.apache.org/jira/browse/IGNITE-11496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasiliy Sisko reassigned IGNITE-11496:
--
Assignee: Sergey Kozlov (was: Vasiliy Sisko)
> Long running SQL queries could be randomly canceled from WC
> ---
>
> Key: IGNITE-11496
> URL: https://issues.apache.org/jira/browse/IGNITE-11496
> Project: Ignite
> Issue Type: Bug
> Components: wizards
>Affects Versions: 2.5
>Reporter: Evgenii Zhuravlev
>Assignee: Sergey Kozlov
>Priority: Major
>
> I've tried to run some long-running queries from WC(more than a couple of
> minutes) and I've faced a behavior when the query was canceled without
> clicking on the cancel button.
> I've opened different browser tabs at this moment, maybe it could be the
> reason.
> {code}
> javax.cache.CacheException: Failed to run reduce query locally.
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:883)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$7.iterator(IgniteH2Indexing.java:1494)
> at
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:95)
> at
> org.apache.ignite.internal.visor.query.VisorQueryHolder.getIterator(VisorQueryHolder.java:97)
> at
> org.apache.ignite.internal.visor.query.VisorQueryFetchFirstPageTask$VisorQueryFetchFirstPageJob.run(VisorQueryFetchFirstPageTask.java:85)
> at
> org.apache.ignite.internal.visor.query.VisorQueryFetchFirstPageTask$VisorQueryFetchFirstPageJob.run(VisorQueryFetchFirstPageTask.java:51)
> at org.apache.ignite.internal.visor.VisorJob.execute(VisorJob.java:69)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:568)
> at
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6750)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:562)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:491)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at
> org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1123)
> at
> org.apache.ignite.internal.processors.job.GridJobProcessor$JobExecutionListener.onMessage(GridJobProcessor.java:1921)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1556)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1184)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:125)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1091)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class org.apache.ignite.cache.query.QueryCancelledException: The
> query was cancelled while executing.
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQuery(IgniteH2Indexing.java:1240)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQueryWithTimer(IgniteH2Indexing.java:1303)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQueryWithTimer(IgniteH2Indexing.java:1281)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:835)
> ... 20 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-11496) Long running SQL queries could be randomly canceled from WC
[ https://issues.apache.org/jira/browse/IGNITE-11496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko reassigned IGNITE-11496: -- Assignee: Vasiliy Sisko (was: Alexey Kuznetsov) > Long running SQL queries could be randomly canceled from WC > --- > > Key: IGNITE-11496 > URL: https://issues.apache.org/jira/browse/IGNITE-11496 > Project: Ignite > Issue Type: Bug > Components: wizards >Affects Versions: 2.5 >Reporter: Evgenii Zhuravlev >Assignee: Vasiliy Sisko >Priority: Major > > I've tried to run some long-running queries from WC(more than a couple of > minutes) and I've faced a behavior when the query was canceled without > clicking on the cancel button. > I've opened different browser tabs at this moment, maybe it could be the > reason. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11354) Web console: Actualize grid configurator discovery, store, abomic, communication
[ https://issues.apache.org/jira/browse/IGNITE-11354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko reassigned IGNITE-11354: -- Assignee: Pavel Konstantinov (was: Vasiliy Sisko) > Web console: Actualize grid configurator discovery, store, abomic, > communication > > > Key: IGNITE-11354 > URL: https://issues.apache.org/jira/browse/IGNITE-11354 > Project: Ignite > Issue Type: Improvement >Reporter: Vasiliy Sisko >Assignee: Pavel Konstantinov >Priority: Major > > Result for class: org.apache.ignite.configuration.DataStorageConfiguration > Missed > maxWalArchiveSize > checkpointReadLockTimeout > walCompactionLevel > Result for class: org.apache.ignite.configuration.AtomicConfiguration > Missed > groupName > Result for class: org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi > Missed > nodeAttributes > connectionRecoveryTimeout > reconnectDelay > soLinger > Result for class: org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi > Missed > usePairedConnections > connectionsPerNode > selectorSpins > filterReachableAddresses > Removed > discoveryStartupDelay -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11386) Web console: Actualize configuragion for localEventListeners field of IgniteConfiguration
[ https://issues.apache.org/jira/browse/IGNITE-11386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko reassigned IGNITE-11386: -- Assignee: Pavel Konstantinov (was: Vasiliy Sisko) > Web console: Actualize configuragion for localEventListeners field of > IgniteConfiguration > - > > Key: IGNITE-11386 > URL: https://issues.apache.org/jira/browse/IGNITE-11386 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Vasiliy Sisko >Assignee: Pavel Konstantinov >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Missed field in configurator. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11386) Web console: Actualize configuragion for localEventListeners field of IgniteConfiguration
[ https://issues.apache.org/jira/browse/IGNITE-11386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16777657#comment-16777657 ] Vasiliy Sisko commented on IGNITE-11386: Actualized configuration of localEventListener. [~pkonstantinov] Please test. > Web console: Actualize configuragion for localEventListeners field of > IgniteConfiguration > - > > Key: IGNITE-11386 > URL: https://issues.apache.org/jira/browse/IGNITE-11386 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Vasiliy Sisko >Assignee: Vasiliy Sisko >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Missed field in configurator. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-11386) Web console: Actualize configuragion for localEventListeners field of IgniteConfiguration
[ https://issues.apache.org/jira/browse/IGNITE-11386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16777657#comment-16777657 ] Vasiliy Sisko edited comment on IGNITE-11386 at 2/26/19 7:05 AM: - Actualized configuration of localEventListener. [~pkonstantinov] Please test. [~anovikov] Please review. was (Author: vsisko): Actualized configuration of localEventListener. [~pkonstantinov] Please test. > Web console: Actualize configuragion for localEventListeners field of > IgniteConfiguration > - > > Key: IGNITE-11386 > URL: https://issues.apache.org/jira/browse/IGNITE-11386 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Vasiliy Sisko >Assignee: Vasiliy Sisko >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Missed field in configurator. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11385) Web console: Actualize configuragion for failureHandler field of IgniteConfiguration
[ https://issues.apache.org/jira/browse/IGNITE-11385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16776591#comment-16776591 ] Vasiliy Sisko commented on IGNITE-11385: Implemented configuration of failure handler. [~pkonstantinov] Please check. Also check other places with collection field. [~pkonstantinov] Please create separated issues for combobox with very long values. > Web console: Actualize configuragion for failureHandler field of > IgniteConfiguration > > > Key: IGNITE-11385 > URL: https://issues.apache.org/jira/browse/IGNITE-11385 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Vasiliy Sisko >Assignee: Vasiliy Sisko >Priority: Major > > Missed in configurator. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11385) Web console: Actualize configuragion for failureHandler field of IgniteConfiguration
[ https://issues.apache.org/jira/browse/IGNITE-11385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko reassigned IGNITE-11385: -- Assignee: Pavel Konstantinov (was: Vasiliy Sisko) > Web console: Actualize configuragion for failureHandler field of > IgniteConfiguration > > > Key: IGNITE-11385 > URL: https://issues.apache.org/jira/browse/IGNITE-11385 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Vasiliy Sisko >Assignee: Pavel Konstantinov >Priority: Major > > Missed in configurator. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11387) Web console: Actualize configuragion for encryptionSpi field of IgniteConfiguration
[ https://issues.apache.org/jira/browse/IGNITE-11387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16775004#comment-16775004 ] Vasiliy Sisko commented on IGNITE-11387: Implemented configuration of encryption SPI. > Web console: Actualize configuragion for encryptionSpi field of > IgniteConfiguration > --- > > Key: IGNITE-11387 > URL: https://issues.apache.org/jira/browse/IGNITE-11387 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Vasiliy Sisko >Assignee: Vasiliy Sisko >Priority: Major > > Missed in configurator. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11387) Web console: Actualize configuragion for encryptionSpi field of IgniteConfiguration
[ https://issues.apache.org/jira/browse/IGNITE-11387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko reassigned IGNITE-11387: -- Assignee: Pavel Konstantinov (was: Vasiliy Sisko) > Web console: Actualize configuragion for encryptionSpi field of > IgniteConfiguration > --- > > Key: IGNITE-11387 > URL: https://issues.apache.org/jira/browse/IGNITE-11387 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Vasiliy Sisko >Assignee: Pavel Konstantinov >Priority: Major > > Missed in configurator. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11361) Web console: Actualize grid configurator IgniteConfiguration
[ https://issues.apache.org/jira/browse/IGNITE-11361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko updated IGNITE-11361: --- Description: Result for class: org.apache.ignite.configuration.IgniteConfiguration Missed failureHandler IGNITE-11385 authenticationEnabled autoActivationEnabled sqlQueryHistorySize lifecycleBeans sqlSchemas igniteInstanceName addressResolver igniteHome localEventListeners IGNITE-11386 mBeanServer networkCompressionLevel communicationFailureResolver systemWorkerBlockedTimeout platformConfiguration includeProperties cacheStoreSessionListenerFactories encryptionSpi IGNITE-11387 was: Result for class: org.apache.ignite.configuration.IgniteConfiguration Missed failureHandler IGNITE-11385 authenticationEnabled autoActivationEnabled sqlQueryHistorySize lifecycleBeans sqlSchemas igniteInstanceName addressResolver igniteHome localEventListeners IGNITE-11386 mBeanServer networkCompressionLevel communicationFailureResolver systemWorkerBlockedTimeout platformConfiguration includeProperties cacheStoreSessionListenerFactories encryptionSpi > Web console: Actualize grid configurator IgniteConfiguration > > > Key: IGNITE-11361 > URL: https://issues.apache.org/jira/browse/IGNITE-11361 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Vasiliy Sisko >Assignee: Vasiliy Sisko >Priority: Major > > Result for class: org.apache.ignite.configuration.IgniteConfiguration > Missed > failureHandler IGNITE-11385 > authenticationEnabled > autoActivationEnabled > sqlQueryHistorySize > lifecycleBeans > sqlSchemas > igniteInstanceName > addressResolver > igniteHome > localEventListeners IGNITE-11386 > mBeanServer > networkCompressionLevel > communicationFailureResolver > systemWorkerBlockedTimeout > platformConfiguration > includeProperties > cacheStoreSessionListenerFactories > encryptionSpi IGNITE-11387 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11361) Web console: Actualize grid configurator IgniteConfiguration
[ https://issues.apache.org/jira/browse/IGNITE-11361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko updated IGNITE-11361: --- Description: Result for class: org.apache.ignite.configuration.IgniteConfiguration Missed failureHandler IGNITE-11385 authenticationEnabled autoActivationEnabled sqlQueryHistorySize lifecycleBeans sqlSchemas igniteInstanceName addressResolver igniteHome localEventListeners IGNITE-11386 mBeanServer networkCompressionLevel communicationFailureResolver systemWorkerBlockedTimeout platformConfiguration includeProperties cacheStoreSessionListenerFactories encryptionSpi was: Result for class: org.apache.ignite.configuration.IgniteConfiguration Missed failureHandler IGNITE-11385 authenticationEnabled autoActivationEnabled sqlQueryHistorySize lifecycleBeans sqlSchemas igniteInstanceName addressResolver igniteHome localEventListeners mBeanServer networkCompressionLevel communicationFailureResolver systemWorkerBlockedTimeout platformConfiguration includeProperties cacheStoreSessionListenerFactories encryptionSpi > Web console: Actualize grid configurator IgniteConfiguration > > > Key: IGNITE-11361 > URL: https://issues.apache.org/jira/browse/IGNITE-11361 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Vasiliy Sisko >Assignee: Vasiliy Sisko >Priority: Major > > Result for class: org.apache.ignite.configuration.IgniteConfiguration > Missed > failureHandler IGNITE-11385 > authenticationEnabled > autoActivationEnabled > sqlQueryHistorySize > lifecycleBeans > sqlSchemas > igniteInstanceName > addressResolver > igniteHome > localEventListeners IGNITE-11386 > mBeanServer > networkCompressionLevel > communicationFailureResolver > systemWorkerBlockedTimeout > platformConfiguration > includeProperties > cacheStoreSessionListenerFactories > encryptionSpi -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11361) Web console: Actualize grid configurator IgniteConfiguration
[ https://issues.apache.org/jira/browse/IGNITE-11361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16774927#comment-16774927 ] Vasiliy Sisko commented on IGNITE-11361: Configurator actualized. [~pkonstantinov] Please test. For failureHandler, localEventListeners, encryptionSpi created separated issules. platformConfiguration doesn't has fields to configure. > Web console: Actualize grid configurator IgniteConfiguration > > > Key: IGNITE-11361 > URL: https://issues.apache.org/jira/browse/IGNITE-11361 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Vasiliy Sisko >Assignee: Vasiliy Sisko >Priority: Major > > Result for class: org.apache.ignite.configuration.IgniteConfiguration > Missed > failureHandler IGNITE-11385 > authenticationEnabled > autoActivationEnabled > sqlQueryHistorySize > lifecycleBeans > sqlSchemas > igniteInstanceName > addressResolver > igniteHome > localEventListeners IGNITE-11386 > mBeanServer > networkCompressionLevel > communicationFailureResolver > systemWorkerBlockedTimeout > platformConfiguration > includeProperties > cacheStoreSessionListenerFactories > encryptionSpi IGNITE-11387 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11361) Web console: Actualize grid configurator IgniteConfiguration
[ https://issues.apache.org/jira/browse/IGNITE-11361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko reassigned IGNITE-11361: -- Assignee: Pavel Konstantinov (was: Vasiliy Sisko) > Web console: Actualize grid configurator IgniteConfiguration > > > Key: IGNITE-11361 > URL: https://issues.apache.org/jira/browse/IGNITE-11361 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Vasiliy Sisko >Assignee: Pavel Konstantinov >Priority: Major > > Result for class: org.apache.ignite.configuration.IgniteConfiguration > Missed > failureHandler IGNITE-11385 > authenticationEnabled > autoActivationEnabled > sqlQueryHistorySize > lifecycleBeans > sqlSchemas > igniteInstanceName > addressResolver > igniteHome > localEventListeners IGNITE-11386 > mBeanServer > networkCompressionLevel > communicationFailureResolver > systemWorkerBlockedTimeout > platformConfiguration > includeProperties > cacheStoreSessionListenerFactories > encryptionSpi IGNITE-11387 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11385) Web console: Actualize configuragion for failureHandler field of IgniteConfiguration
[ https://issues.apache.org/jira/browse/IGNITE-11385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko updated IGNITE-11385: --- Description: Missed in configurator. > Web console: Actualize configuragion for failureHandler field of > IgniteConfiguration > > > Key: IGNITE-11385 > URL: https://issues.apache.org/jira/browse/IGNITE-11385 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Vasiliy Sisko >Assignee: Vasiliy Sisko >Priority: Major > > Missed in configurator. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11387) Web console: Actualize configuragion for encryptionSpi field of IgniteConfiguration
Vasiliy Sisko created IGNITE-11387: -- Summary: Web console: Actualize configuragion for encryptionSpi field of IgniteConfiguration Key: IGNITE-11387 URL: https://issues.apache.org/jira/browse/IGNITE-11387 Project: Ignite Issue Type: Improvement Components: wizards Reporter: Vasiliy Sisko Assignee: Vasiliy Sisko Missed in configurator. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11386) Web console: Actualize configuragion for localEventListeners field of IgniteConfiguration
Vasiliy Sisko created IGNITE-11386: -- Summary: Web console: Actualize configuragion for localEventListeners field of IgniteConfiguration Key: IGNITE-11386 URL: https://issues.apache.org/jira/browse/IGNITE-11386 Project: Ignite Issue Type: Improvement Components: wizards Reporter: Vasiliy Sisko Assignee: Vasiliy Sisko Missed field in configurator. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11361) Web console: Actualize grid configurator IgniteConfiguration
[ https://issues.apache.org/jira/browse/IGNITE-11361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko updated IGNITE-11361: --- Description: Result for class: org.apache.ignite.configuration.IgniteConfiguration Missed failureHandler IGNITE-11385 authenticationEnabled autoActivationEnabled sqlQueryHistorySize lifecycleBeans sqlSchemas igniteInstanceName addressResolver igniteHome localEventListeners mBeanServer networkCompressionLevel communicationFailureResolver systemWorkerBlockedTimeout platformConfiguration includeProperties cacheStoreSessionListenerFactories encryptionSpi was: Result for class: org.apache.ignite.configuration.IgniteConfiguration Missed failureHandler authenticationEnabled autoActivationEnabled sqlQueryHistorySize lifecycleBeans sqlSchemas igniteInstanceName addressResolver igniteHome localEventListeners mBeanServer networkCompressionLevel communicationFailureResolver systemWorkerBlockedTimeout platformConfiguration includeProperties cacheStoreSessionListenerFactories encryptionSpi > Web console: Actualize grid configurator IgniteConfiguration > > > Key: IGNITE-11361 > URL: https://issues.apache.org/jira/browse/IGNITE-11361 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Vasiliy Sisko >Assignee: Vasiliy Sisko >Priority: Major > > Result for class: org.apache.ignite.configuration.IgniteConfiguration > Missed > failureHandler IGNITE-11385 > authenticationEnabled > autoActivationEnabled > sqlQueryHistorySize > lifecycleBeans > sqlSchemas > igniteInstanceName > addressResolver > igniteHome > localEventListeners > mBeanServer > networkCompressionLevel > communicationFailureResolver > systemWorkerBlockedTimeout > platformConfiguration > includeProperties > cacheStoreSessionListenerFactories > encryptionSpi -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11385) Web console: Actualize configuragion for failureHandler field of IgniteConfiguration
Vasiliy Sisko created IGNITE-11385: -- Summary: Web console: Actualize configuragion for failureHandler field of IgniteConfiguration Key: IGNITE-11385 URL: https://issues.apache.org/jira/browse/IGNITE-11385 Project: Ignite Issue Type: Improvement Components: wizards Reporter: Vasiliy Sisko Assignee: Vasiliy Sisko -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11361) Web console: Actualize grid configurator IgniteConfiguration
[ https://issues.apache.org/jira/browse/IGNITE-11361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko updated IGNITE-11361: --- Description: Result for class: org.apache.ignite.configuration.IgniteConfiguration Missed failureHandler authenticationEnabled autoActivationEnabled sqlQueryHistorySize lifecycleBeans sqlSchemas igniteInstanceName addressResolver igniteHome localEventListeners mBeanServer networkCompressionLevel communicationFailureResolver systemWorkerBlockedTimeout platformConfiguration includeProperties cacheStoreSessionListenerFactories encryptionSpi was: Result for class: org.apache.ignite.configuration.IgniteConfiguration Missed authenticationEnabled sqlQueryHistorySize lifecycleBeans addressResolver allSegmentationResolversPassRequired localEventListeners mBeanServer networkCompressionLevel segmentCheckFrequency systemWorkerBlockedTimeout includeProperties cacheStoreSessionListenerFactories initBaselineAutoAdjustEnabled failureHandler initBaselineAutoAdjustTimeout autoActivationEnabled sqlSchemas segmentationPolicy segmentationResolveAttempts igniteInstanceName waitForSegmentOnStart igniteHome initBaselineAutoAdjustMaxTimeout communicationFailureResolver segmentationResolvers platformConfiguration encryptionSpi > Web console: Actualize grid configurator IgniteConfiguration > > > Key: IGNITE-11361 > URL: https://issues.apache.org/jira/browse/IGNITE-11361 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Vasiliy Sisko >Assignee: Vasiliy Sisko >Priority: Major > > Result for class: org.apache.ignite.configuration.IgniteConfiguration > Missed > failureHandler > authenticationEnabled > autoActivationEnabled > sqlQueryHistorySize > lifecycleBeans > sqlSchemas > igniteInstanceName > addressResolver > igniteHome > localEventListeners > mBeanServer > networkCompressionLevel > communicationFailureResolver > systemWorkerBlockedTimeout > platformConfiguration > includeProperties > cacheStoreSessionListenerFactories > encryptionSpi -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11096) Webagent: flag --disable-demo doesn't work
[ https://issues.apache.org/jira/browse/IGNITE-11096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko reassigned IGNITE-11096: -- Assignee: Alexey Kuznetsov (was: Pavel Konstantinov) > Webagent: flag --disable-demo doesn't work > -- > > Key: IGNITE-11096 > URL: https://issues.apache.org/jira/browse/IGNITE-11096 > Project: Ignite > Issue Type: Bug > Components: wizards >Affects Versions: 2.7 > Environment: After enabling this flag it's still possible to start > demo >Reporter: Evgenii Zhuravlev >Assignee: Alexey Kuznetsov >Priority: Major > Fix For: 2.8 > > Attachments: image-2019-02-13-13-55-51-248.png, screenshot-1.png > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11375) Web console: Show appropriate message in no data component when demo is disabled on agent
Vasiliy Sisko created IGNITE-11375: -- Summary: Web console: Show appropriate message in no data component when demo is disabled on agent Key: IGNITE-11375 URL: https://issues.apache.org/jira/browse/IGNITE-11375 Project: Ignite Issue Type: Improvement Components: wizards Reporter: Vasiliy Sisko Assignee: Alexander Kalinin If the demo is opened and stay only an agent with disabled demo The no data component should show appropriate message. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11354) Web console: Actualize grid configurator discovery, store, abomic, communication
[ https://issues.apache.org/jira/browse/IGNITE-11354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16772709#comment-16772709 ] Vasiliy Sisko commented on IGNITE-11354: Implemented missed fields in configurator. nodeAttributes field is not part of TcpDiscoverySpi configuration. Not implemented. > Web console: Actualize grid configurator discovery, store, abomic, > communication > > > Key: IGNITE-11354 > URL: https://issues.apache.org/jira/browse/IGNITE-11354 > Project: Ignite > Issue Type: Improvement >Reporter: Vasiliy Sisko >Assignee: Vasiliy Sisko >Priority: Major > > Result for class: org.apache.ignite.configuration.DataStorageConfiguration > Missed > maxWalArchiveSize > checkpointReadLockTimeout > walCompactionLevel > Result for class: org.apache.ignite.configuration.AtomicConfiguration > Missed > groupName > Result for class: org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi > Missed > nodeAttributes > connectionRecoveryTimeout > reconnectDelay > soLinger > Result for class: org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi > Missed > usePairedConnections > connectionsPerNode > selectorSpins > filterReachableAddresses > Removed > discoveryStartupDelay -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11361) Web console: Actualize grid configurator IgniteConfiguration
Vasiliy Sisko created IGNITE-11361: -- Summary: Web console: Actualize grid configurator IgniteConfiguration Key: IGNITE-11361 URL: https://issues.apache.org/jira/browse/IGNITE-11361 Project: Ignite Issue Type: Improvement Components: wizards Reporter: Vasiliy Sisko Assignee: Vasiliy Sisko Result for class: org.apache.ignite.configuration.IgniteConfiguration Missed authenticationEnabled sqlQueryHistorySize lifecycleBeans addressResolver allSegmentationResolversPassRequired localEventListeners mBeanServer networkCompressionLevel segmentCheckFrequency systemWorkerBlockedTimeout includeProperties cacheStoreSessionListenerFactories initBaselineAutoAdjustEnabled failureHandler initBaselineAutoAdjustTimeout autoActivationEnabled sqlSchemas segmentationPolicy segmentationResolveAttempts igniteInstanceName waitForSegmentOnStart igniteHome initBaselineAutoAdjustMaxTimeout communicationFailureResolver segmentationResolvers platformConfiguration encryptionSpi -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11354) Web console: Actualize grid configurator discovery, store, abomic, communication
[ https://issues.apache.org/jira/browse/IGNITE-11354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko updated IGNITE-11354: --- Description: Result for class: org.apache.ignite.configuration.DataStorageConfiguration Missed maxWalArchiveSize checkpointReadLockTimeout walCompactionLevel Result for class: org.apache.ignite.configuration.AtomicConfiguration Missed groupName Result for class: org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi Missed nodeAttributes connectionRecoveryTimeout reconnectDelaysoLinger Result for class: org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi Missed usePairedConnections connectionsPerNode selectorSpins filterReachableAddresses Removed discoveryStartupDelay was: Result for class: org.apache.ignite.configuration.DataStorageConfiguration Missed maxWalArchiveSize checkpointReadLockTimeout walCompactionLevel Result for class: org.apache.ignite.configuration.AtomicConfiguration Missed groupName Result for class: org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi Missed nodeAttributes connectionRecoveryTimeout reconnectDelay Result for class: org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi Missed usePairedConnections connectionsPerNode selectorSpins filterReachableAddresses Removed discoveryStartupDelay > Web console: Actualize grid configurator discovery, store, abomic, > communication > > > Key: IGNITE-11354 > URL: https://issues.apache.org/jira/browse/IGNITE-11354 > Project: Ignite > Issue Type: Improvement >Reporter: Vasiliy Sisko >Assignee: Vasiliy Sisko >Priority: Major > > Result for class: org.apache.ignite.configuration.DataStorageConfiguration > Missed > maxWalArchiveSize > checkpointReadLockTimeout > walCompactionLevel > Result for class: org.apache.ignite.configuration.AtomicConfiguration > Missed > groupName > Result for class: org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi > Missed > nodeAttributes > connectionRecoveryTimeout > reconnectDelaysoLinger > Result for class: org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi > Missed > usePairedConnections > connectionsPerNode > selectorSpins > filterReachableAddresses > Removed > discoveryStartupDelay -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11354) Web console: Actualize grid configurator discovery, store, abomic, communication
[ https://issues.apache.org/jira/browse/IGNITE-11354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko updated IGNITE-11354: --- Description: Result for class: org.apache.ignite.configuration.DataStorageConfiguration Missed maxWalArchiveSize checkpointReadLockTimeout walCompactionLevel Result for class: org.apache.ignite.configuration.AtomicConfiguration Missed groupName Result for class: org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi Missed nodeAttributes connectionRecoveryTimeout reconnectDelay soLinger Result for class: org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi Missed usePairedConnections connectionsPerNode selectorSpins filterReachableAddresses Removed discoveryStartupDelay was: Result for class: org.apache.ignite.configuration.DataStorageConfiguration Missed maxWalArchiveSize checkpointReadLockTimeout walCompactionLevel Result for class: org.apache.ignite.configuration.AtomicConfiguration Missed groupName Result for class: org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi Missed nodeAttributes connectionRecoveryTimeout reconnectDelaysoLinger Result for class: org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi Missed usePairedConnections connectionsPerNode selectorSpins filterReachableAddresses Removed discoveryStartupDelay > Web console: Actualize grid configurator discovery, store, abomic, > communication > > > Key: IGNITE-11354 > URL: https://issues.apache.org/jira/browse/IGNITE-11354 > Project: Ignite > Issue Type: Improvement >Reporter: Vasiliy Sisko >Assignee: Vasiliy Sisko >Priority: Major > > Result for class: org.apache.ignite.configuration.DataStorageConfiguration > Missed > maxWalArchiveSize > checkpointReadLockTimeout > walCompactionLevel > Result for class: org.apache.ignite.configuration.AtomicConfiguration > Missed > groupName > Result for class: org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi > Missed > nodeAttributes > connectionRecoveryTimeout > reconnectDelay > soLinger > Result for class: org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi > Missed > usePairedConnections > connectionsPerNode > selectorSpins > filterReachableAddresses > Removed > discoveryStartupDelay -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11354) Web console: Actualize grid configurator discovery, store, abomic, communication
Vasiliy Sisko created IGNITE-11354: -- Summary: Web console: Actualize grid configurator discovery, store, abomic, communication Key: IGNITE-11354 URL: https://issues.apache.org/jira/browse/IGNITE-11354 Project: Ignite Issue Type: Improvement Reporter: Vasiliy Sisko Assignee: Vasiliy Sisko Result for class: org.apache.ignite.configuration.DataStorageConfiguration Missed maxWalArchiveSize checkpointReadLockTimeout walCompactionLevel Result for class: org.apache.ignite.configuration.AtomicConfiguration Missed groupName Result for class: org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi Missed nodeAttributes connectionRecoveryTimeout reconnectDelay Result for class: org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi Missed usePairedConnections connectionsPerNode selectorSpins filterReachableAddresses Removed discoveryStartupDelay -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10214) Web console: dependency to open source JDBC driver is not generated in the project's pom file
[ https://issues.apache.org/jira/browse/IGNITE-10214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16771680#comment-16771680 ] Vasiliy Sisko commented on IGNITE-10214: 2-5 fixed. [~pkonstantinov]. Please test dependencies generation for different datasources. Especially after import of domain model. Check work with JDBC drivers that has JRE specification. Test loading of JDBC driver from central Maven repository for MS SQL Server. > Web console: dependency to open source JDBC driver is not generated in the > project's pom file > - > > Key: IGNITE-10214 > URL: https://issues.apache.org/jira/browse/IGNITE-10214 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Konstantinov >Assignee: Vasiliy Sisko >Priority: Major > Attachments: mysql-connector-java-8.0.13.jar, screenshot-1.png > > > Steps to reproduce: > # import caches from for example MySql DB > # check generated pom file -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-10214) Web console: dependency to open source JDBC driver is not generated in the project's pom file
[ https://issues.apache.org/jira/browse/IGNITE-10214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko reassigned IGNITE-10214: -- Assignee: Pavel Konstantinov (was: Vasiliy Sisko) > Web console: dependency to open source JDBC driver is not generated in the > project's pom file > - > > Key: IGNITE-10214 > URL: https://issues.apache.org/jira/browse/IGNITE-10214 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Konstantinov >Assignee: Pavel Konstantinov >Priority: Major > Attachments: mysql-connector-java-8.0.13.jar, screenshot-1.png > > > Steps to reproduce: > # import caches from for example MySql DB > # check generated pom file -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11096) Webagent: flag --disable-demo doesn't work
[ https://issues.apache.org/jira/browse/IGNITE-11096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko reassigned IGNITE-11096: -- Assignee: Pavel Konstantinov (was: Vasiliy Sisko) > Webagent: flag --disable-demo doesn't work > -- > > Key: IGNITE-11096 > URL: https://issues.apache.org/jira/browse/IGNITE-11096 > Project: Ignite > Issue Type: Bug > Components: wizards >Affects Versions: 2.7 > Environment: After enabling this flag it's still possible to start > demo >Reporter: Evgenii Zhuravlev >Assignee: Pavel Konstantinov >Priority: Major > Fix For: 2.8 > > Attachments: image-2019-02-13-13-55-51-248.png, screenshot-1.png > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11096) Webagent: flag --disable-demo doesn't work
[ https://issues.apache.org/jira/browse/IGNITE-11096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16770820#comment-16770820 ] Vasiliy Sisko commented on IGNITE-11096: ++Fixed launch of demo mode when agent in not connected to Web console. > Webagent: flag --disable-demo doesn't work > -- > > Key: IGNITE-11096 > URL: https://issues.apache.org/jira/browse/IGNITE-11096 > Project: Ignite > Issue Type: Bug > Components: wizards >Affects Versions: 2.7 > Environment: After enabling this flag it's still possible to start > demo >Reporter: Evgenii Zhuravlev >Assignee: Vasiliy Sisko >Priority: Major > Fix For: 2.8 > > Attachments: image-2019-02-13-13-55-51-248.png, screenshot-1.png > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-11096) Webagent: flag --disable-demo doesn't work
[ https://issues.apache.org/jira/browse/IGNITE-11096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16770820#comment-16770820 ] Vasiliy Sisko edited comment on IGNITE-11096 at 2/18/19 7:01 AM: - Fixed launch of demo mode when agent in not connected to Web console. was (Author: vsisko): ++Fixed launch of demo mode when agent in not connected to Web console. > Webagent: flag --disable-demo doesn't work > -- > > Key: IGNITE-11096 > URL: https://issues.apache.org/jira/browse/IGNITE-11096 > Project: Ignite > Issue Type: Bug > Components: wizards >Affects Versions: 2.7 > Environment: After enabling this flag it's still possible to start > demo >Reporter: Evgenii Zhuravlev >Assignee: Vasiliy Sisko >Priority: Major > Fix For: 2.8 > > Attachments: image-2019-02-13-13-55-51-248.png, screenshot-1.png > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11096) Webagent: flag --disable-demo doesn't work
[ https://issues.apache.org/jira/browse/IGNITE-11096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko reassigned IGNITE-11096: -- Assignee: Pavel Konstantinov (was: Vasiliy Sisko) > Webagent: flag --disable-demo doesn't work > -- > > Key: IGNITE-11096 > URL: https://issues.apache.org/jira/browse/IGNITE-11096 > Project: Ignite > Issue Type: Bug > Components: wizards >Affects Versions: 2.7 > Environment: After enabling this flag it's still possible to start > demo >Reporter: Evgenii Zhuravlev >Assignee: Pavel Konstantinov >Priority: Major > Fix For: 2.8 > > Attachments: image-2019-02-13-13-55-51-248.png > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11096) Webagent: flag --disable-demo doesn't work
[ https://issues.apache.org/jira/browse/IGNITE-11096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16770737#comment-16770737 ] Vasiliy Sisko commented on IGNITE-11096: Fixed. > Webagent: flag --disable-demo doesn't work > -- > > Key: IGNITE-11096 > URL: https://issues.apache.org/jira/browse/IGNITE-11096 > Project: Ignite > Issue Type: Bug > Components: wizards >Affects Versions: 2.7 > Environment: After enabling this flag it's still possible to start > demo >Reporter: Evgenii Zhuravlev >Assignee: Vasiliy Sisko >Priority: Major > Fix For: 2.8 > > Attachments: image-2019-02-13-13-55-51-248.png > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11284) Web console: Actualize grid configuration: query entity and Pojo store
[ https://issues.apache.org/jira/browse/IGNITE-11284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko reassigned IGNITE-11284: -- Assignee: Pavel Konstantinov (was: Vasiliy Sisko) > Web console: Actualize grid configuration: query entity and Pojo store > -- > > Key: IGNITE-11284 > URL: https://issues.apache.org/jira/browse/IGNITE-11284 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Vasiliy Sisko >Assignee: Pavel Konstantinov >Priority: Major > > Result for class: org.apache.ignite.cache.QueryEntity > Missed > fieldsPrecision > notNullFields > fieldsScale > defaultFieldValues > Result for class: org.apache.ignite.cache.store.jdbc.CacheJdbcPojoStoreFactory > Missed > types > Result for class: org.apache.ignite.cache.QueryIndex > Missed > inlineSize -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11284) Web console: Actualize grid configuration: query entity and Pojo store
[ https://issues.apache.org/jira/browse/IGNITE-11284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16770734#comment-16770734 ] Vasiliy Sisko commented on IGNITE-11284: Fixed generation of missed fields. Field types of CacheJdbcPojoStoreFactory class is already generated. > Web console: Actualize grid configuration: query entity and Pojo store > -- > > Key: IGNITE-11284 > URL: https://issues.apache.org/jira/browse/IGNITE-11284 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Vasiliy Sisko >Assignee: Vasiliy Sisko >Priority: Major > > Result for class: org.apache.ignite.cache.QueryEntity > Missed > fieldsPrecision > notNullFields > fieldsScale > defaultFieldValues > Result for class: org.apache.ignite.cache.store.jdbc.CacheJdbcPojoStoreFactory > Missed > types > Result for class: org.apache.ignite.cache.QueryIndex > Missed > inlineSize -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10214) Web console: dependency to open source JDBC driver is not generated in the project's pom file
[ https://issues.apache.org/jira/browse/IGNITE-10214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16769152#comment-16769152 ] Vasiliy Sisko commented on IGNITE-10214: Removed code duplication. > Web console: dependency to open source JDBC driver is not generated in the > project's pom file > - > > Key: IGNITE-10214 > URL: https://issues.apache.org/jira/browse/IGNITE-10214 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Konstantinov >Assignee: Vasiliy Sisko >Priority: Major > Attachments: mysql-connector-java-8.0.13.jar, screenshot-1.png > > > Steps to reproduce: > # import caches from for example MySql DB > # check generated pom file -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-10214) Web console: dependency to open source JDBC driver is not generated in the project's pom file
[ https://issues.apache.org/jira/browse/IGNITE-10214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko reassigned IGNITE-10214: -- Assignee: Alexey Kuznetsov (was: Vasiliy Sisko) > Web console: dependency to open source JDBC driver is not generated in the > project's pom file > - > > Key: IGNITE-10214 > URL: https://issues.apache.org/jira/browse/IGNITE-10214 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Konstantinov >Assignee: Alexey Kuznetsov >Priority: Major > Attachments: mysql-connector-java-8.0.13.jar, screenshot-1.png > > > Steps to reproduce: > # import caches from for example MySql DB > # check generated pom file -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-10214) Web console: dependency to open source JDBC driver is not generated in the project's pom file
[ https://issues.apache.org/jira/browse/IGNITE-10214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko reassigned IGNITE-10214: -- Assignee: Pavel Konstantinov (was: Vasiliy Sisko) > Web console: dependency to open source JDBC driver is not generated in the > project's pom file > - > > Key: IGNITE-10214 > URL: https://issues.apache.org/jira/browse/IGNITE-10214 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Konstantinov >Assignee: Pavel Konstantinov >Priority: Major > Attachments: mysql-connector-java-8.0.13.jar, screenshot-1.png > > > Steps to reproduce: > # import caches from for example MySql DB > # check generated pom file -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10214) Web console: dependency to open source JDBC driver is not generated in the project's pom file
[ https://issues.apache.org/jira/browse/IGNITE-10214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16767810#comment-16767810 ] Vasiliy Sisko commented on IGNITE-10214: [~pkonstantinov] Please check you use last version of Web agent. > Web console: dependency to open source JDBC driver is not generated in the > project's pom file > - > > Key: IGNITE-10214 > URL: https://issues.apache.org/jira/browse/IGNITE-10214 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Konstantinov >Assignee: Vasiliy Sisko >Priority: Major > Attachments: mysql-connector-java-8.0.13.jar, screenshot-1.png > > > Steps to reproduce: > # import caches from for example MySql DB > # check generated pom file -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-10214) Web console: dependency to open source JDBC driver is not generated in the project's pom file
[ https://issues.apache.org/jira/browse/IGNITE-10214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko reassigned IGNITE-10214: -- Assignee: Pavel Konstantinov (was: Vasiliy Sisko) > Web console: dependency to open source JDBC driver is not generated in the > project's pom file > - > > Key: IGNITE-10214 > URL: https://issues.apache.org/jira/browse/IGNITE-10214 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Konstantinov >Assignee: Pavel Konstantinov >Priority: Major > > Steps to reproduce: > # import caches from for example MySql DB > # check generated pom file -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10214) Web console: dependency to open source JDBC driver is not generated in the project's pom file
[ https://issues.apache.org/jira/browse/IGNITE-10214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16767019#comment-16767019 ] Vasiliy Sisko commented on IGNITE-10214: Fixed generated version of MysqlDataSource > Web console: dependency to open source JDBC driver is not generated in the > project's pom file > - > > Key: IGNITE-10214 > URL: https://issues.apache.org/jira/browse/IGNITE-10214 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Konstantinov >Assignee: Vasiliy Sisko >Priority: Major > > Steps to reproduce: > # import caches from for example MySql DB > # check generated pom file -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11284) Web console: Actualize grid configuration: query entity and Pojo store
Vasiliy Sisko created IGNITE-11284: -- Summary: Web console: Actualize grid configuration: query entity and Pojo store Key: IGNITE-11284 URL: https://issues.apache.org/jira/browse/IGNITE-11284 Project: Ignite Issue Type: Improvement Components: wizards Environment: Result for class: org.apache.ignite.cache.QueryEntity Missed fieldsPrecision notNullFields fieldsScale defaultFieldValues Result for class: org.apache.ignite.cache.store.jdbc.CacheJdbcPojoStoreFactory Missed types Result for class: org.apache.ignite.cache.QueryIndex Missed inlineSize Reporter: Vasiliy Sisko Assignee: Vasiliy Sisko -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11284) Web console: Actualize grid configuration: query entity and Pojo store
[ https://issues.apache.org/jira/browse/IGNITE-11284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko updated IGNITE-11284: --- Environment: (was: Result for class: org.apache.ignite.cache.QueryEntity Missed fieldsPrecision notNullFields fieldsScale defaultFieldValues Result for class: org.apache.ignite.cache.store.jdbc.CacheJdbcPojoStoreFactory Missed types Result for class: org.apache.ignite.cache.QueryIndex Missed inlineSize) > Web console: Actualize grid configuration: query entity and Pojo store > -- > > Key: IGNITE-11284 > URL: https://issues.apache.org/jira/browse/IGNITE-11284 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Vasiliy Sisko >Assignee: Vasiliy Sisko >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11284) Web console: Actualize grid configuration: query entity and Pojo store
[ https://issues.apache.org/jira/browse/IGNITE-11284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko updated IGNITE-11284: --- Description: Result for class: org.apache.ignite.cache.QueryEntity Missed fieldsPrecision notNullFields fieldsScale defaultFieldValues Result for class: org.apache.ignite.cache.store.jdbc.CacheJdbcPojoStoreFactory Missed types Result for class: org.apache.ignite.cache.QueryIndex Missed inlineSize > Web console: Actualize grid configuration: query entity and Pojo store > -- > > Key: IGNITE-11284 > URL: https://issues.apache.org/jira/browse/IGNITE-11284 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Vasiliy Sisko >Assignee: Vasiliy Sisko >Priority: Major > > Result for class: org.apache.ignite.cache.QueryEntity > Missed > fieldsPrecision > notNullFields > fieldsScale > defaultFieldValues > Result for class: org.apache.ignite.cache.store.jdbc.CacheJdbcPojoStoreFactory > Missed > types > Result for class: org.apache.ignite.cache.QueryIndex > Missed > inlineSize -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11283) Web console: Actualize grid configuration. Check deprecated fields
[ https://issues.apache.org/jira/browse/IGNITE-11283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16764732#comment-16764732 ] Vasiliy Sisko commented on IGNITE-11283: Actualized configuration: RendezvousAffinityFunction - already used actual field *affinityBackupFilter* PersistentStoreConfiguration - Added missed fields *walAutoArchiveAfterInactivity* and *walMode* for Ignite 2.1. TransactionConfiguration - Added missed fields. Deprecated fields not used since Ignite 1.5 ConnectorConfiguration - already used actual field *sslFactory* > Web console: Actualize grid configuration. Check deprecated fields > -- > > Key: IGNITE-11283 > URL: https://issues.apache.org/jira/browse/IGNITE-11283 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Vasiliy Sisko >Assignee: Vasiliy Sisko >Priority: Major > > Result for class: > org.apache.ignite.cache.affinity.rendezvous.RendezvousAffinityFunction > Deprecated > backupFilter > Result for class: org.apache.ignite.configuration.PersistentStoreConfiguration > Deprecated > walBufferSize > writeThrottlingEnabled > checkpointWriteOrder > fileIOFactory > walMode > walAutoArchiveAfterInactivity > Result for class: org.apache.ignite.configuration.TransactionConfiguration > Missed > deadlockTimeout > useJtaSynchronization > txTimeoutOnPartitionMapExchange > Deprecated > txSerializableEnabled > txManagerLookupClassName > Result for class: org.apache.ignite.configuration.ConnectorConfiguration > Deprecated > sslContextFactory -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11283) Web console: Actualize grid configuration. Check deprecated fields
[ https://issues.apache.org/jira/browse/IGNITE-11283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko reassigned IGNITE-11283: -- Assignee: Pavel Konstantinov (was: Vasiliy Sisko) > Web console: Actualize grid configuration. Check deprecated fields > -- > > Key: IGNITE-11283 > URL: https://issues.apache.org/jira/browse/IGNITE-11283 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Vasiliy Sisko >Assignee: Pavel Konstantinov >Priority: Major > > Result for class: > org.apache.ignite.cache.affinity.rendezvous.RendezvousAffinityFunction > Deprecated > backupFilter > Result for class: org.apache.ignite.configuration.PersistentStoreConfiguration > Deprecated > walBufferSize > writeThrottlingEnabled > checkpointWriteOrder > fileIOFactory > walMode > walAutoArchiveAfterInactivity > Result for class: org.apache.ignite.configuration.TransactionConfiguration > Missed > deadlockTimeout > useJtaSynchronization > txTimeoutOnPartitionMapExchange > Deprecated > txSerializableEnabled > txManagerLookupClassName > Result for class: org.apache.ignite.configuration.ConnectorConfiguration > Deprecated > sslContextFactory -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11283) Web console: Actualize grid configuration. Check deprecated fields
Vasiliy Sisko created IGNITE-11283: -- Summary: Web console: Actualize grid configuration. Check deprecated fields Key: IGNITE-11283 URL: https://issues.apache.org/jira/browse/IGNITE-11283 Project: Ignite Issue Type: Improvement Components: wizards Reporter: Vasiliy Sisko Assignee: Vasiliy Sisko Result for class: org.apache.ignite.cache.affinity.rendezvous.RendezvousAffinityFunction Deprecated backupFilter Result for class: org.apache.ignite.configuration.PersistentStoreConfiguration Deprecated walBufferSize writeThrottlingEnabled checkpointWriteOrder fileIOFactory walMode walAutoArchiveAfterInactivity Result for class: org.apache.ignite.configuration.TransactionConfiguration Missed deadlockTimeout useJtaSynchronization txTimeoutOnPartitionMapExchange Deprecated txSerializableEnabled txManagerLookupClassName Result for class: org.apache.ignite.configuration.ConnectorConfiguration Deprecated sslContextFactory -- This message was sent by Atlassian JIRA (v7.6.3#76005)
