[jira] [Commented] (IGNITE-9845) Web Console: Add support of two way ssl authentication in Web Console agent
[
https://issues.apache.org/jira/browse/IGNITE-9845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16730588#comment-16730588
]
Vasiliy Sisko commented on IGNITE-9845:
---
Failed to launch web agent to unsafe cluster with *-Dtrust.all=true* option
{code:java}
Exception in thread "main" java.lang.NullPointerException
at
okhttp3.internal.tls.BasicTrustRootIndex.(BasicTrustRootIndex.java:32)
at okhttp3.internal.platform.Platform.buildTrustRootIndex(Platform.java:288)
at
okhttp3.internal.platform.Platform.buildCertificateChainCleaner(Platform.java:172)
at
okhttp3.internal.tls.CertificateChainCleaner.get(CertificateChainCleaner.java:41)
at okhttp3.OkHttpClient$Builder.sslSocketFactory(OkHttpClient.java:807)
at
org.apache.ignite.console.agent.AgentLauncher.main(AgentLauncher.java:367)
{code}
> Web Console: Add support of two way ssl authentication in Web Console agent
> ---
>
> Key: IGNITE-9845
> URL: https://issues.apache.org/jira/browse/IGNITE-9845
> Project: Ignite
> Issue Type: Improvement
> Components: wizards
>Affects Versions: 2.6
>Reporter: Andrey Novikov
>Assignee: Alexey Kuznetsov
>Priority: Major
> Fix For: 2.8
>
> Attachments: Selection_274.png, generate.bat, generate.sh, ssl.pdf
>
>
> RestExecutor should not be shared between different users requests in case of
> two way ssl authentication:
> * For each token with ssl we need create separated RestExecutor and set up
> socketFactory and trustManager.
> * RestExecutor should be removed if token expired.
> Add program arguments for passing client certificate, client password, trust
> store, trust store password for ignite node connection and web console
> backend.
> Example on okhttp:
> [https://github.com/square/okhttp/blob/cd872fd83824512c128dcd80c04d445c8a2fc8eb/okhttp-tests/src/test/java/okhttp3/internal/tls/ClientAuthTest.java]
> Upgrade socket-io from 1.x to 2.x.
> Add support for SSL cipher suites
> Add tests.
> ---
> *How to do local testing:*
> On Windows
> # Download Open SSL: Download Open SSL for Windows from
> [https://wiki.openssl.org/index.php/Binaries]
> # Unpack it.
> On Linux - it is usually built-in.
> Generate keys with provided script (see attached generate.bat, it could be
> easily adapted for Linux).
>
> Add to etc/hosts:
> 127.0.0.1 localhost console.test.local
>
> After that configure SSL for:
> # Web Console back-end.
> # Web Agent.
> # Cluster.
> *Configure Web Console back-end settings:*
> "ssl": true,
> "key": "some_path/server.key",
> "cert": "some_path/server.crt",
> "ca": "some_path/ca.crt",
> "keyPassphrase": "p123456",
> *Configure Web Agent parameters (see parameters descriptions):*
> -t your_token
> -s [https://console.test.local:3000|https://console.test.local:3000/] -n
> [https://console.test.local:11443|https://console.test.local:11443/]
> -nks client.jks -nkp p123456
> -nts ca.jks -ntp p123456
> -sks client.jks -skp p123456
> -sts ca.jks -stp p123456
> *Configure cluster JETTY config:*
>
> https
> default="11443"/>
> true
> true
> class="org.eclipse.jetty.server.SecureRequestCustomizer"/>
>
> class="org.eclipse.jetty.util.ssl.SslContextFactory">
> some_path/server.jks
> p123456
> some_path/ca.jks
> p123456
> true
>
> *How to start secure web console in direct install edition in Ubuntu:*
> # Download ignite web console direct install for linux ZIP archive .
> # Unpack downloaded archive to goal folder.
> # Generate SSL certificates.
> # Copy generated certificates to folder with unpacked web console direct
> install.
> # Open terminal and navigate to folder with unpacked web console direct
> install.
> # Run web console with the next command:
> {code:java}
> ignite-web-console-linux --server:port 11443 --server:ssl true
> --server:requestCert true --server:key "server.key" --server:cert
> "server.crt" --server:ca "ca.crt" --server:passphrase "p123456"{code}
> 7. Import client.p12 certificate into your browser. See attached
> screenstot in Chrome browser.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (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
]
Pavel Konstantinov updated IGNITE-10847:
Description:
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 - "\\nAccessDeniedAccess
Denied4B7715F9CDA5127BzuhNAWP7FGOgDLjkNJ3y71iU+wxcWKR5F5kI4LoO1SqCdt+aPeLZXnJko5S0ji2zx5zkJaCZX3g="',
error: '\nAccessDeniedAccess
Denied4B7715F9CDA5127BzuhNAWP7FGOgDLjkNJ3y71iU+wxcWKR5F5kI4LoO1SqCdt+aPeLZXnJko5S0ji2zx5zkJaCZX3g=',
options:
{ uri:
'https://fastdl.mongodb.org/linux/mongodb-linux-x86_64-ubuntu1804-3.4.7.tgz.md5',
{code}
was: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.
> 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
>Reporter: Pavel Konstantinov
>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] [Created] (IGNITE-10847) Web console: failed to download the mongodb on Ubuntu 18.04
Pavel Konstantinov created IGNITE-10847: --- Summary: 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 Reporter: Pavel Konstantinov 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. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8558) Provide an opportunity to stop grids and cancel tasks after execution all tests
[
https://issues.apache.org/jira/browse/IGNITE-8558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16730576#comment-16730576
]
Ignite TC Bot commented on IGNITE-8558:
---
{panel:title=-- Run :: All: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2671509buildTypeId=IgniteTests24Java8_RunAll]
> Provide an opportunity to stop grids and cancel tasks after execution all
> tests
> ---
>
> Key: IGNITE-8558
> URL: https://issues.apache.org/jira/browse/IGNITE-8558
> Project: Ignite
> Issue Type: Sub-task
>Affects Versions: 2.6
>Reporter: Maxim Muzafarov
>Assignee: Rodion
>Priority: Minor
> Fix For: 2.8
>
>
> The -IGNITE-6842- issue provides an ability gracefully shutdown all ignite
> instances by default after execution of tests. Ignite instances are stopped
> by calling the method - {{stopAllGrids}} ({{cancel = false}} is used). You
> can refer to these lines of code for the details of how the node stopped:
> {code:java|title=GridAbstractTest.java:1789}
> if (isSafeTopology()) {
> stopAllGrids(false);
> if (stopGridErr) {
> err = new RuntimeException("Not all Ignite instances has been
> stopped. " +
> "Please, see log for details.", err);
> }
> }
> {code}
> As part of IGNITE-8266 a lot of boilerplate code have been successfully
> removed. For instance,
> {code:java}
> /** {@inheritDoc} */
> @Override protected void afterTestsStopped() throws Exception {
> super.afterTestsStopped();
> stopAllGrids();
> }
> {code}
> We need to,
> * Provide the ability to override the behaviour of gracefully instance
> shutdown and use {{stopAllGirds(true)}} after all tests execution. Assume a
> new method would be introduced like {{GridAbstractTest#isSafeTopology}}, so
> the behaviour can be overridden in subclasses.
> * Remove the other boilerplate parts of the code. For instance,
> {code:java}
> /** {@inheritDoc} */
> @Override protected void afterTestsStopped() throws Exception {
> stopAllGrids(true);
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Reopened] (IGNITE-10839) Web Console: Email confirmation
[ https://issues.apache.org/jira/browse/IGNITE-10839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov reopened IGNITE-10839: --- Assignee: Andrey Novikov (was: Pavel Konstantinov) [~anovikov], I found one corner case - when admin enable e-mail confirmation, some user register account, but not confirmed and admin disable e-mail confirmation, we need to cleanup e-mail confirmation flags in DB. > Web Console: Email confirmation > --- > > Key: IGNITE-10839 > URL: https://issues.apache.org/jira/browse/IGNITE-10839 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Andrey Novikov >Priority: Major > Fix For: 2.8 > > > Any user can register on Web Console, but it may be not desired behavior. > Lets add an option to enable registration via e-mail confirmation. > This will also ensure that e-mail is correct and can be used for password > reset. > By default, this option should be disabled. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9845) Web Console: Add support of two way ssl authentication in Web Console agent
[
https://issues.apache.org/jira/browse/IGNITE-9845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16730553#comment-16730553
]
Alexey Kuznetsov commented on IGNITE-9845:
--
[~pkonstantinov], Fixed, please retest in branch ignite-9845
> Web Console: Add support of two way ssl authentication in Web Console agent
> ---
>
> Key: IGNITE-9845
> URL: https://issues.apache.org/jira/browse/IGNITE-9845
> Project: Ignite
> Issue Type: Improvement
> Components: wizards
>Affects Versions: 2.6
>Reporter: Andrey Novikov
>Assignee: Alexey Kuznetsov
>Priority: Major
> Fix For: 2.8
>
> Attachments: Selection_274.png, generate.bat, generate.sh, ssl.pdf
>
>
> RestExecutor should not be shared between different users requests in case of
> two way ssl authentication:
> * For each token with ssl we need create separated RestExecutor and set up
> socketFactory and trustManager.
> * RestExecutor should be removed if token expired.
> Add program arguments for passing client certificate, client password, trust
> store, trust store password for ignite node connection and web console
> backend.
> Example on okhttp:
> [https://github.com/square/okhttp/blob/cd872fd83824512c128dcd80c04d445c8a2fc8eb/okhttp-tests/src/test/java/okhttp3/internal/tls/ClientAuthTest.java]
> Upgrade socket-io from 1.x to 2.x.
> Add support for SSL cipher suites
> Add tests.
> ---
> *How to do local testing:*
> On Windows
> # Download Open SSL: Download Open SSL for Windows from
> [https://wiki.openssl.org/index.php/Binaries]
> # Unpack it.
> On Linux - it is usually built-in.
> Generate keys with provided script (see attached generate.bat, it could be
> easily adapted for Linux).
>
> Add to etc/hosts:
> 127.0.0.1 localhost console.test.local
>
> After that configure SSL for:
> # Web Console back-end.
> # Web Agent.
> # Cluster.
> *Configure Web Console back-end settings:*
> "ssl": true,
> "key": "some_path/server.key",
> "cert": "some_path/server.crt",
> "ca": "some_path/ca.crt",
> "keyPassphrase": "p123456",
> *Configure Web Agent parameters (see parameters descriptions):*
> -t your_token
> -s [https://console.test.local:3000|https://console.test.local:3000/] -n
> [https://console.test.local:11443|https://console.test.local:11443/]
> -nks client.jks -nkp p123456
> -nts ca.jks -ntp p123456
> -sks client.jks -skp p123456
> -sts ca.jks -stp p123456
> *Configure cluster JETTY config:*
>
> https
> default="11443"/>
> true
> true
> class="org.eclipse.jetty.server.SecureRequestCustomizer"/>
>
> class="org.eclipse.jetty.util.ssl.SslContextFactory">
> some_path/server.jks
> p123456
> some_path/ca.jks
> p123456
> true
>
> *How to start secure web console in direct install edition in Ubuntu:*
> # Download ignite web console direct install for linux ZIP archive .
> # Unpack downloaded archive to goal folder.
> # Generate SSL certificates.
> # Copy generated certificates to folder with unpacked web console direct
> install.
> # Open terminal and navigate to folder with unpacked web console direct
> install.
> # Run web console with the next command:
> {code:java}
> ignite-web-console-linux --server:port 11443 --server:ssl true
> --server:requestCert true --server:key "server.key" --server:cert
> "server.crt" --server:ca "ca.crt" --server:passphrase "p123456"{code}
> 7. Import client.p12 certificate into your browser. See attached
> screenstot in Chrome browser.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IGNITE-9817) Update documentation and examples for Spark SQL Table Specification
[ https://issues.apache.org/jira/browse/IGNITE-9817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prachi Garg resolved IGNITE-9817. - Resolution: Fixed > Update documentation and examples for Spark SQL Table Specification > --- > > Key: IGNITE-9817 > URL: https://issues.apache.org/jira/browse/IGNITE-9817 > Project: Ignite > Issue Type: Sub-task > Components: documentation >Reporter: Nikolay Izhikov >Assignee: Prachi Garg >Priority: Major > Fix For: 2.8 > > > We should update documentation and examples according to the results of > IGNITE-9228. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-9817) Update documentation and examples for Spark SQL Table Specification
[ https://issues.apache.org/jira/browse/IGNITE-9817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prachi Garg closed IGNITE-9817. --- > Update documentation and examples for Spark SQL Table Specification > --- > > Key: IGNITE-9817 > URL: https://issues.apache.org/jira/browse/IGNITE-9817 > Project: Ignite > Issue Type: Sub-task > Components: documentation >Reporter: Nikolay Izhikov >Assignee: Prachi Garg >Priority: Major > Fix For: 2.8 > > > We should update documentation and examples according to the results of > IGNITE-9228. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10846) Improve docs for "Disabling WAL Archiving"
Prachi Garg created IGNITE-10846: Summary: Improve docs for "Disabling WAL Archiving" Key: IGNITE-10846 URL: https://issues.apache.org/jira/browse/IGNITE-10846 Project: Ignite Issue Type: Task Components: documentation Reporter: Prachi Garg Assignee: Prachi Garg Fix For: 2.8 Provide pros and cons of disabling WAL Archiving. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10845) Ignite Production Readiness Section Enhancement
Denis Magda created IGNITE-10845: Summary: Ignite Production Readiness Section Enhancement Key: IGNITE-10845 URL: https://issues.apache.org/jira/browse/IGNITE-10845 Project: Ignite Issue Type: Task Components: documentation Reporter: Denis Magda Assignee: Prachi Garg Fix For: 2.8 Enhance Ignite production readiness section with points from here: https://www.gridgain.com/resources/blog/checklist-assembling-your-first-apacher-ignitetm-cluster -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10537) MVCC: Client reconnect tests became unstable after mvcc coordinator reassign fix.
[
https://issues.apache.org/jira/browse/IGNITE-10537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16730369#comment-16730369
]
Ignite TC Bot commented on IGNITE-10537:
{panel:title=-- Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}MVCC Queries{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2669489]]
* IgniteCacheMvccSqlTestSuite:
CacheMvccPartitionedSqlCoordinatorFailoverTest.testPutAllGetAll_ClientServer_Backups0_RestartCoordinator_ScanDml
- 0,0% fails in last 388 master runs.
{color:#d04437}Service Grid (legacy mode){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2669541]]
* IgniteServiceGridTestSuite:
GridServiceProcessorBatchDeploySelfTest.testDeployAllTopologyChange - 0,0%
fails in last 12 master runs.
{color:#d04437}MVCC Cache{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2669487]]
* IgniteCacheMvccTestSuite:
CacheMvccTransactionsTest.testPutAllGetAll_ClientServer_Backups1_RestartCoordinator_Scan
- 0,0% fails in last 397 master runs.
{color:#d04437}Cache (Restarts) 1{color} [[tests
3|https://ci.ignite.apache.org/viewLog.html?buildId=2669501]]
* IgniteCacheRestartTestSuite: GridCachePartitionedNodeRestartTest.testRestart
- 0,0% fails in last 395 master runs.
* IgniteCacheRestartTestSuite:
GridCachePartitionedNodeRestartTest.testRestartWithPutTwoNodesNoBackups - 0,0%
fails in last 395 master runs.
* IgniteCacheRestartTestSuite:
GridCachePartitionedNodeRestartTest.testRestartWithPutSixNodesTwoBackups - 0,0%
fails in last 395 master runs.
{color:#d04437}PDS 2{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2669523]]
* IgnitePdsTestSuite2:
LocalWalModeChangeDuringRebalancingSelfTest.testParallelExchangeDuringCheckpoint
- 0,0% fails in last 387 master runs.
{color:#d04437}Cache (Restarts) 2{color} [[tests
5|https://ci.ignite.apache.org/viewLog.html?buildId=2669502]]
* IgniteCacheRestartTestSuite2:
IgniteCacheAtomicReplicatedNodeRestartSelfTest.testRestartWithPutSixNodesTwoBackups
- 0,0% fails in last 419 master runs.
* IgniteCacheRestartTestSuite2:
IgniteCacheAtomicReplicatedNodeRestartSelfTest.testRestartWithPutTenNodesTwoBackups
- 0,0% fails in last 419 master runs.
* IgniteCacheRestartTestSuite2:
IgniteCacheAtomicReplicatedNodeRestartSelfTest.testRestartWithPutFourNodesNoBackups
- 0,0% fails in last 419 master runs.
* IgniteCacheRestartTestSuite2:
IgniteCacheAtomicReplicatedNodeRestartSelfTest.testRestartWithTxPutAllTenNodesTwoBackups
- 0,0% fails in last 419 master runs.
{color:#d04437}Cache 1{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2669504]]
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2669542buildTypeId=IgniteTests24Java8_RunAll]
> MVCC: Client reconnect tests became unstable after mvcc coordinator reassign
> fix.
> -
>
> Key: IGNITE-10537
> URL: https://issues.apache.org/jira/browse/IGNITE-10537
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Assignee: Igor Seliverstov
>Priority: Major
> Labels: CQ, mvcc_stabilization_stage_1
> Fix For: 2.8
>
>
> It looks like tests
> [CacheMvccContinuousQueryClientReconnectTest.testReconnectClient|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=7778544852295951300=testDetails]
> and
> [CacheMvccContinuousQueryClientReconnectTest.testReconnectClientAndLeftRouter|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-8370258276605466922=testDetails]
> became flaky after commit _5477048 rkondakov on
> 22.11.18 at 14:35_. Weshould investigate and fix this problem.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IGNITE-10725) Push Initial Commit to repository
[ https://issues.apache.org/jira/browse/IGNITE-10725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk resolved IGNITE-10725. --- Resolution: Done Initial commit is pushed. > Push Initial Commit to repository > - > > Key: IGNITE-10725 > URL: https://issues.apache.org/jira/browse/IGNITE-10725 > Project: Ignite > Issue Type: Sub-task >Reporter: Ilya Kasnacheev >Assignee: Alexey Goncharuk >Priority: Major > > Unfortunately, empty repository cannot be forked or offered pull requests. > Therefore there is a need of direct push of commit > 4b30c1a2cff4ee4a615bc0940327035705198cbc to repository > https://gitbox.apache.org/repos/asf?p=ignite-abbrev-plugin.git as 'master' > Source code licenses are not proper in this commit, but it will be fixed in > following commits. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10844) Improved abbreviation code pack 2
Ilya Kasnacheev created IGNITE-10844: Summary: Improved abbreviation code pack 2 Key: IGNITE-10844 URL: https://issues.apache.org/jira/browse/IGNITE-10844 Project: Ignite Issue Type: Sub-task Reporter: Ilya Kasnacheev Assignee: Dmitriy Pavlov https://github.com/dspavlov/ignite-abbrev-plugin/tree/ignite-vkazakov-contrib should be PRd to https://github.com/apache/ignite-abbrev-plugin by vkazakov if he agrees. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10725) Push Initial Commit to repository
[ https://issues.apache.org/jira/browse/IGNITE-10725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Kasnacheev updated IGNITE-10725: - Ignite Flags: (was: Docs Required) > Push Initial Commit to repository > - > > Key: IGNITE-10725 > URL: https://issues.apache.org/jira/browse/IGNITE-10725 > Project: Ignite > Issue Type: Sub-task >Reporter: Ilya Kasnacheev >Assignee: Alexey Goncharuk >Priority: Major > > Unfortunately, empty repository cannot be forked or offered pull requests. > Therefore there is a need of direct push of commit > 4b30c1a2cff4ee4a615bc0940327035705198cbc to repository > https://gitbox.apache.org/repos/asf?p=ignite-abbrev-plugin.git as 'master' > Source code licenses are not proper in this commit, but it will be fixed in > following commits. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10307) SQL: Extract partition info from JOINs
[
https://issues.apache.org/jira/browse/IGNITE-10307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16730333#comment-16730333
]
Vladimir Ozerov commented on IGNITE-10307:
--
Implementation is ready. Now working on tests.
> SQL: Extract partition info from JOINs
> --
>
> Key: IGNITE-10307
> URL: https://issues.apache.org/jira/browse/IGNITE-10307
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Major
> Labels: iep-24
> Fix For: 2.8
>
>
> Currently we do not extract partitions when JOINs are involved. Let's
> implement it. We may start with relatively simple rules:
> # No subqueries
> # No GROUP BY
> Then walk through JOINed tables and extract partitions from AND clauses.
> There are some tricky things to consider:
> # Resulting model (tree) must be craefted carefully so that we can reuse it
> later in thin clients for efficient co-location.
> # Resulting model may affect how we group tables during push-down phase.
> Probably this would be huuuge thing, so may be it is better to implement it
> in separate ticket
> # When JOIN is performed partition info might be "transferred" between
> tables. E.g.:
> {code}
> a INNER JOIN b ON a.id = b.affinity_id WHERE a.id = :1
> {code}
> In this case if tables are co-located (we may infer it automatically in some
> cases), then {{a.id=:1}} partition rule can be "transferred" to
> {{b.affinity_id=:1}}.
> Very good test coverage would be needed here.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10720) Decrease time to save metadata during checkpoint
[
https://issues.apache.org/jira/browse/IGNITE-10720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16730317#comment-16730317
]
Ignite TC Bot commented on IGNITE-10720:
{panel:title=-- Run :: All: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2667686buildTypeId=IgniteTests24Java8_RunAll]
> Decrease time to save metadata during checkpoint
>
>
> Key: IGNITE-10720
> URL: https://issues.apache.org/jira/browse/IGNITE-10720
> Project: Ignite
> Issue Type: Improvement
>Reporter: Anton Kalashnikov
>Assignee: Anton Kalashnikov
>Priority: Major
>
> Looks like it's not neccessery save all metadata(like free list) under write
> checkpoint lock because sometimes it's too long.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10842) Exception during node stopping
e.spi.communication.tcp.TcpCommunicationSpi.sendMessage(TcpCommunicationSpi.java:2702)
*<-->*at
org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1652)
*<-->*at
org.apache.ignite.internal.managers.communication.GridIoManager.sendToGridTopic(GridIoManager.java:1726)
*<-->*at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1240)
*<-->*at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1279)
*<-->*at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.sendDeferredUpdateResponse(GridDhtAtomicCache.java:3548)
*<-->*at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$3300(GridDhtAtomicCache.java:139)
*<-->*at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$DeferredUpdateTimeout.run(GridDhtAtomicCache.java:3794)
*<-->*at
org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:508)
*<-->*at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
*<-->*at java.lang.Thread.run(Thread.java:745)
[2018-12-28 12:30:06,658][ERROR][sys-stripe-12-#13][TcpCommunicationSpi] Failed
to send message to remote node [node=TcpDiscoveryNode
[id=8e884f80-f55d-4b32-9dcd-39e1af0ed2ef, addrs=ArrayList
class org.apache.ignite.spi.IgniteSpiException: Node is stopping.
*<-->*at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.reserveClient(TcpCommunicationSpi.java:2883)
*<-->*at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage0(TcpCommunicationSpi.java:2743)
*<-->*at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage(TcpCommunicationSpi.java:2702)
*<-->*at
org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1652)
*<-->*at
org.apache.ignite.internal.managers.communication.GridIoManager.sendToGridTopic(GridIoManager.java:1726)
*<-->*at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1240)
*<-->*at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1279)
*<-->*at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.sendDeferredUpdateResponse(GridDhtAtomicCache.java:3548)
*<-->*at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$3300(GridDhtAtomicCache.java:139)
*<-->*at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$DeferredUpdateTimeout.run(GridDhtAtomicCache.java:3794)
*<-->*at
org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:508)
*<-->*at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
*<-->*at java.lang.Thread.run(Thread.java:745)
{noformat}
I guess it is redundant information on *Node stopping* stage.
Please take a look at logs in the attachement.
> Exception during node stopping
> --
>
> Key: IGNITE-10842
> URL: https://issues.apache.org/jira/browse/IGNITE-10842
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7
> Environment: branch: master
> ver. 2.8.0-SNAPSHOT#20181228-sha1:e2edf41b
>Reporter: Ilya Suntsov
>Priority: Minor
> Fix For: 2.8
>
> Attachments: ticket-logs.zip
>
>
> Steps:
> # Start 3 nodes: 1 yardstick driver and 2 servers
> # Almost simultaneously start all nodes. ( kill -9 -f "Dyardstick.server"/
> "Dyardstick.driver")
> Result:
> I see the following messages in log:
> {noformat}
> 2018-12-28 12:30:06,606][ERROR][sys-stripe-8-#9][TcpCommunicationSpi] Failed
> to send message to remote node [node=TcpDiscoveryNode
> [id=8e884f80-f55d-4b32-9dcd-39e1af0ed2ef, addrs=ArrayList [1
> class org.apache.ignite.spi.IgniteSpiException: Node is stopping.
> *<-->*at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.reserveClient(TcpCommunicationSpi.java:2883)
> *<-->*at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage0(TcpCommunicationSpi.java:2743)
> *<-->*at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage(TcpCommunicationSpi.java:2702)
> *<-->*at
> org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1652)
> *<-->*at
> org.apache.ignite.internal.managers.communication.GridIoManager.sendToGridTopic(GridIoManager.java:1726)
> *<--
[jira] [Created] (IGNITE-10843) [ML] In stacking add filter on features kept.
Artem Malykh created IGNITE-10843: - Summary: [ML] In stacking add filter on features kept. Key: IGNITE-10843 URL: https://issues.apache.org/jira/browse/IGNITE-10843 Project: Ignite Issue Type: Improvement Components: ml Reporter: Artem Malykh -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10385) NPE in CachePartitionPartialCountersMap.toString
[
https://issues.apache.org/jira/browse/IGNITE-10385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16730282#comment-16730282
]
Ilya Kasnacheev commented on IGNITE-10385:
--
[~antkr] thank you for this contribution! I have merged it to master.
> NPE in CachePartitionPartialCountersMap.toString
>
>
> Key: IGNITE-10385
> URL: https://issues.apache.org/jira/browse/IGNITE-10385
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.4
>Reporter: Anton Kurbanov
>Assignee: Anton Kurbanov
>Priority: Blocker
> Fix For: 2.8
>
>
> {noformat}
> Failed to reinitialize local partitions (preloading will be stopped)
> org.apache.ignite.IgniteException: null
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:1032)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:868)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.managers.communication.GridIoMessage.toString(GridIoMessage.java:358)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at java.lang.String.valueOf(String.java:2994) ~[?:1.8.0_171]
> at java.lang.StringBuilder.append(StringBuilder.java:131) ~[?:1.8.0_171]
> at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage0(TcpCommunicationSpi.java:2653)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage(TcpCommunicationSpi.java:2586)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1642)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.sendToGridTopic(GridIoManager.java:1714)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1160)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.sendLocalPartitions(GridDhtPartitionsExchangeFuture.java:1399)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.sendPartitions(GridDhtPartitionsExchangeFuture.java:1506)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.distributedExchange(GridDhtPartitionsExchangeFuture.java:1139)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:703)
> [ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2379)
> [ignite-core-2.4.10.jar:2.4.10]
> at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> [ignite-core-2.4.10.jar:2.4.10]
> at java.lang.Thread.run(Thread.java:748) [?:1.8.0_171]
> Caused by: org.apache.ignite.IgniteException
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:1032)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:830)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:787)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:889)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsSingleMessage.toString(GridDhtPartitionsSingleMessage.java:551)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at java.lang.String.valueOf(String.java:2994) ~[?:1.8.0_171]
> at
> org.apache.ignite.internal.util.GridStringBuilder.a(GridStringBuilder.java:101)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.util.tostring.SBLimitedLength.a(SBLimitedLength.java:88)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:943)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:1009)
> ~[ignite-core-2.4.10.jar:2.4.10]
> ... 16 more
> Caused by: java.lang.NullPointerException
> at
>
[jira] [Commented] (IGNITE-10415) MVCC: TxRollbackOnIncorrectParamsTest fails if Mvcc enabled.
[
https://issues.apache.org/jira/browse/IGNITE-10415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16730280#comment-16730280
]
Ivan Pavlukhin commented on IGNITE-10415:
-
{{CacheException}} is expected it test but {{IgniteSQLException}} is thrown
when MVCC is enabled.
> MVCC: TxRollbackOnIncorrectParamsTest fails if Mvcc enabled.
>
>
> Key: IGNITE-10415
> URL: https://issues.apache.org/jira/browse/IGNITE-10415
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Andrew Mashenkov
>Assignee: Ivan Pavlukhin
>Priority: Major
> Labels: mvcc_stabilization_stage_1, transactions
> Fix For: 2.8
>
>
> {noformat}
> class org.apache.ignite.internal.processors.query.IgniteSQLException:
> Transaction is already completed.
> at
> org.apache.ignite.internal.processors.cache.mvcc.MvccUtils.checkActive(MvccUtils.java:660)
> at
> org.apache.ignite.internal.processors.cache.mvcc.MvccUtils.requestSnapshot(MvccUtils.java:816)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.mvccPutAllAsync0(GridNearTxLocal.java:740)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.putAsync0(GridNearTxLocal.java:580)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.putAsync(GridNearTxLocal.java:446)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter$22.op(GridCacheAdapter.java:2504)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter$22.op(GridCacheAdapter.java:2502)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.syncOp(GridCacheAdapter.java:4323)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.put0(GridCacheAdapter.java:2502)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:2483)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:2460)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.put(IgniteCacheProxyImpl.java:1105)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.put(GatewayProtectedCacheProxy.java:820)
> at
> org.apache.ignite.internal.processors.cache.transactions.TxRollbackOnIncorrectParamsTest.testLabelFilledLocalGuarantee(TxRollbackOnIncorrectParamsTest.java:122)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2166)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:144)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:2082)
> at java.lang.Thread.run(Thread.java:748){noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10385) NPE in CachePartitionPartialCountersMap.toString
[
https://issues.apache.org/jira/browse/IGNITE-10385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16730281#comment-16730281
]
ASF GitHub Bot commented on IGNITE-10385:
-
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5487
> NPE in CachePartitionPartialCountersMap.toString
>
>
> Key: IGNITE-10385
> URL: https://issues.apache.org/jira/browse/IGNITE-10385
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.4
>Reporter: Anton Kurbanov
>Assignee: Anton Kurbanov
>Priority: Blocker
> Fix For: 2.8
>
>
> {noformat}
> Failed to reinitialize local partitions (preloading will be stopped)
> org.apache.ignite.IgniteException: null
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:1032)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:868)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.managers.communication.GridIoMessage.toString(GridIoMessage.java:358)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at java.lang.String.valueOf(String.java:2994) ~[?:1.8.0_171]
> at java.lang.StringBuilder.append(StringBuilder.java:131) ~[?:1.8.0_171]
> at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage0(TcpCommunicationSpi.java:2653)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage(TcpCommunicationSpi.java:2586)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1642)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.sendToGridTopic(GridIoManager.java:1714)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1160)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.sendLocalPartitions(GridDhtPartitionsExchangeFuture.java:1399)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.sendPartitions(GridDhtPartitionsExchangeFuture.java:1506)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.distributedExchange(GridDhtPartitionsExchangeFuture.java:1139)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:703)
> [ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2379)
> [ignite-core-2.4.10.jar:2.4.10]
> at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> [ignite-core-2.4.10.jar:2.4.10]
> at java.lang.Thread.run(Thread.java:748) [?:1.8.0_171]
> Caused by: org.apache.ignite.IgniteException
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:1032)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:830)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:787)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:889)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsSingleMessage.toString(GridDhtPartitionsSingleMessage.java:551)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at java.lang.String.valueOf(String.java:2994) ~[?:1.8.0_171]
> at
> org.apache.ignite.internal.util.GridStringBuilder.a(GridStringBuilder.java:101)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.util.tostring.SBLimitedLength.a(SBLimitedLength.java:88)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:943)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:1009)
> ~[ignite-core-2.4.10.jar:2.4.10]
> ... 16 more
> Caused by: java.lang.NullPointerException
> at
>
[jira] [Comment Edited] (IGNITE-10415) MVCC: TxRollbackOnIncorrectParamsTest fails if Mvcc enabled.
[
https://issues.apache.org/jira/browse/IGNITE-10415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16730280#comment-16730280
]
Ivan Pavlukhin edited comment on IGNITE-10415 at 12/28/18 1:56 PM:
---
{{CacheException}} is expected in test but {{IgniteSQLException}} is thrown
when MVCC is enabled.
was (Author: pavlukhin):
{{CacheException}} is expected it test but {{IgniteSQLException}} is thrown
when MVCC is enabled.
> MVCC: TxRollbackOnIncorrectParamsTest fails if Mvcc enabled.
>
>
> Key: IGNITE-10415
> URL: https://issues.apache.org/jira/browse/IGNITE-10415
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Andrew Mashenkov
>Assignee: Ivan Pavlukhin
>Priority: Major
> Labels: mvcc_stabilization_stage_1, transactions
> Fix For: 2.8
>
>
> {noformat}
> class org.apache.ignite.internal.processors.query.IgniteSQLException:
> Transaction is already completed.
> at
> org.apache.ignite.internal.processors.cache.mvcc.MvccUtils.checkActive(MvccUtils.java:660)
> at
> org.apache.ignite.internal.processors.cache.mvcc.MvccUtils.requestSnapshot(MvccUtils.java:816)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.mvccPutAllAsync0(GridNearTxLocal.java:740)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.putAsync0(GridNearTxLocal.java:580)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.putAsync(GridNearTxLocal.java:446)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter$22.op(GridCacheAdapter.java:2504)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter$22.op(GridCacheAdapter.java:2502)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.syncOp(GridCacheAdapter.java:4323)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.put0(GridCacheAdapter.java:2502)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:2483)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:2460)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.put(IgniteCacheProxyImpl.java:1105)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.put(GatewayProtectedCacheProxy.java:820)
> at
> org.apache.ignite.internal.processors.cache.transactions.TxRollbackOnIncorrectParamsTest.testLabelFilledLocalGuarantee(TxRollbackOnIncorrectParamsTest.java:122)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2166)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:144)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:2082)
> at java.lang.Thread.run(Thread.java:748){noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10385) NPE in CachePartitionPartialCountersMap.toString
[
https://issues.apache.org/jira/browse/IGNITE-10385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16730271#comment-16730271
]
Ignite TC Bot commented on IGNITE-10385:
{panel:title=-- Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform .NET (Long Running){color} [[tests 1 TIMEOUT
|https://ci.ignite.apache.org/viewLog.html?buildId=2660391]]
* exe: PersistentStoreTestObsolete.TestCacheDataSurvivesNodeRestart - 6,3%
fails in last 383 master runs.
{color:#d04437}Cache (Restarts) 1{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=2667996]]
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithPutFourNodesNoBackups -
0,0% fails in last 394 master runs.
{color:#d04437}Activate / Deactivate Cluster{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2667940]]
* IgniteStandByClusterSuite: IgniteNoParrallelClusterIsAllowedTest.testSimple -
0,0% fails in last 412 master runs.
{color:#d04437}ZooKeeper (Discovery) 2{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2667974]]
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2668037buildTypeId=IgniteTests24Java8_RunAll]
> NPE in CachePartitionPartialCountersMap.toString
>
>
> Key: IGNITE-10385
> URL: https://issues.apache.org/jira/browse/IGNITE-10385
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.4
>Reporter: Anton Kurbanov
>Assignee: Anton Kurbanov
>Priority: Blocker
>
> {noformat}
> Failed to reinitialize local partitions (preloading will be stopped)
> org.apache.ignite.IgniteException: null
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:1032)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:868)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.managers.communication.GridIoMessage.toString(GridIoMessage.java:358)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at java.lang.String.valueOf(String.java:2994) ~[?:1.8.0_171]
> at java.lang.StringBuilder.append(StringBuilder.java:131) ~[?:1.8.0_171]
> at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage0(TcpCommunicationSpi.java:2653)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage(TcpCommunicationSpi.java:2586)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1642)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.sendToGridTopic(GridIoManager.java:1714)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1160)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.sendLocalPartitions(GridDhtPartitionsExchangeFuture.java:1399)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.sendPartitions(GridDhtPartitionsExchangeFuture.java:1506)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.distributedExchange(GridDhtPartitionsExchangeFuture.java:1139)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:703)
> [ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2379)
> [ignite-core-2.4.10.jar:2.4.10]
> at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> [ignite-core-2.4.10.jar:2.4.10]
> at java.lang.Thread.run(Thread.java:748) [?:1.8.0_171]
> Caused by: org.apache.ignite.IgniteException
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:1032)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:830)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:787)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:889)
>
[jira] [Updated] (IGNITE-10346) Improve TcpDiscoveryVmIpFinder usability in Yardstick
[
https://issues.apache.org/jira/browse/IGNITE-10346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-10346:
--
Fix Version/s: 2.8
> Improve TcpDiscoveryVmIpFinder usability in Yardstick
> -
>
> Key: IGNITE-10346
> URL: https://issues.apache.org/jira/browse/IGNITE-10346
> Project: Ignite
> Issue Type: Improvement
>Reporter: Oleg Ostanin
>Assignee: Oleg Ostanin
>Priority: Major
> Fix For: 2.8
>
>
>
> Currently we have to set IP address list in both property file and Ignite XML
> config. However using
> cfg.customProperties().get("SERVER_HOSTS")
> before starting the node we can get that list, set it to
> TcpDiscoveryVmIpFinder and start node. I think it will improve Yardstick
> usability a little bit.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10346) Improve TcpDiscoveryVmIpFinder usability in Yardstick
[
https://issues.apache.org/jira/browse/IGNITE-10346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16730251#comment-16730251
]
ASF GitHub Bot commented on IGNITE-10346:
-
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5632
> Improve TcpDiscoveryVmIpFinder usability in Yardstick
> -
>
> Key: IGNITE-10346
> URL: https://issues.apache.org/jira/browse/IGNITE-10346
> Project: Ignite
> Issue Type: Improvement
>Reporter: Oleg Ostanin
>Assignee: Oleg Ostanin
>Priority: Major
> Fix For: 2.8
>
>
>
> Currently we have to set IP address list in both property file and Ignite XML
> config. However using
> cfg.customProperties().get("SERVER_HOSTS")
> before starting the node we can get that list, set it to
> TcpDiscoveryVmIpFinder and start node. I think it will improve Yardstick
> usability a little bit.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10346) Improve TcpDiscoveryVmIpFinder usability in Yardstick
[
https://issues.apache.org/jira/browse/IGNITE-10346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-10346:
--
Ignite Flags: (was: Docs Required)
> Improve TcpDiscoveryVmIpFinder usability in Yardstick
> -
>
> Key: IGNITE-10346
> URL: https://issues.apache.org/jira/browse/IGNITE-10346
> Project: Ignite
> Issue Type: Improvement
>Reporter: Oleg Ostanin
>Assignee: Oleg Ostanin
>Priority: Major
> Fix For: 2.8
>
>
>
> Currently we have to set IP address list in both property file and Ignite XML
> config. However using
> cfg.customProperties().get("SERVER_HOSTS")
> before starting the node we can get that list, set it to
> TcpDiscoveryVmIpFinder and start node. I think it will improve Yardstick
> usability a little bit.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10346) Improve TcpDiscoveryVmIpFinder usability in Yardstick
[
https://issues.apache.org/jira/browse/IGNITE-10346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16730249#comment-16730249
]
Alexey Goncharuk commented on IGNITE-10346:
---
Thanks, merged to master.
> Improve TcpDiscoveryVmIpFinder usability in Yardstick
> -
>
> Key: IGNITE-10346
> URL: https://issues.apache.org/jira/browse/IGNITE-10346
> Project: Ignite
> Issue Type: Improvement
>Reporter: Oleg Ostanin
>Assignee: Oleg Ostanin
>Priority: Major
> Fix For: 2.8
>
>
>
> Currently we have to set IP address list in both property file and Ignite XML
> config. However using
> cfg.customProperties().get("SERVER_HOSTS")
> before starting the node we can get that list, set it to
> TcpDiscoveryVmIpFinder and start node. I think it will improve Yardstick
> usability a little bit.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10800) Add wal_mode parameter to yardstick properties file
[ https://issues.apache.org/jira/browse/IGNITE-10800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16730247#comment-16730247 ] ASF GitHub Bot commented on IGNITE-10800: - Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5734 > Add wal_mode parameter to yardstick properties file > --- > > Key: IGNITE-10800 > URL: https://issues.apache.org/jira/browse/IGNITE-10800 > Project: Ignite > Issue Type: Improvement > Components: yardstick >Affects Versions: 2.7 >Reporter: Ilya Suntsov >Assignee: Oleg Ostanin >Priority: Major > Attachments: wal_mode.zip > > > As I understand we can enable persistence with properties file parameter. I > guess we need to add a parameter for WAL mode. > Expected behavior: > * When we have in configuration region with persistence should be used this > configuration and wal_mode value from properties should be ignored. Also > should be added warnings in all nodes logs with configuration details. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10800) Add wal_mode parameter to yardstick properties file
[ https://issues.apache.org/jira/browse/IGNITE-10800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-10800: -- Ignite Flags: (was: Docs Required) > Add wal_mode parameter to yardstick properties file > --- > > Key: IGNITE-10800 > URL: https://issues.apache.org/jira/browse/IGNITE-10800 > Project: Ignite > Issue Type: Improvement > Components: yardstick >Affects Versions: 2.7 >Reporter: Ilya Suntsov >Assignee: Oleg Ostanin >Priority: Major > Attachments: wal_mode.zip > > > As I understand we can enable persistence with properties file parameter. I > guess we need to add a parameter for WAL mode. > Expected behavior: > * When we have in configuration region with persistence should be used this > configuration and wal_mode value from properties should be ignored. Also > should be added warnings in all nodes logs with configuration details. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10842) Exception during node stopping
Ilya Suntsov created IGNITE-10842:
-
Summary: Exception during node stopping
Key: IGNITE-10842
URL: https://issues.apache.org/jira/browse/IGNITE-10842
Project: Ignite
Issue Type: Bug
Affects Versions: 2.7
Environment: branch: master
ver. 2.8.0-SNAPSHOT#20181228-sha1:e2edf41b
Reporter: Ilya Suntsov
Fix For: 2.8
Attachments: ticket-logs.zip
Steps:
# Start 3 nodes
# Almost simultaneously start all nodes
Result:
I see the following messages in log:
{noformat}
2018-12-28 12:30:06,606][ERROR][sys-stripe-8-#9][TcpCommunicationSpi] Failed to
send message to remote node [node=TcpDiscoveryNode
[id=8e884f80-f55d-4b32-9dcd-39e1af0ed2ef, addrs=ArrayList [1
class org.apache.ignite.spi.IgniteSpiException: Node is stopping.
*<-->*at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.reserveClient(TcpCommunicationSpi.java:2883)
*<-->*at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage0(TcpCommunicationSpi.java:2743)
*<-->*at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage(TcpCommunicationSpi.java:2702)
*<-->*at
org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1652)
*<-->*at
org.apache.ignite.internal.managers.communication.GridIoManager.sendToGridTopic(GridIoManager.java:1726)
*<-->*at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1240)
*<-->*at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1279)
*<-->*at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.sendDeferredUpdateResponse(GridDhtAtomicCache.java:3548)
*<-->*at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$3300(GridDhtAtomicCache.java:139)
*<-->*at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$DeferredUpdateTimeout.run(GridDhtAtomicCache.java:3794)
*<-->*at
org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:508)
*<-->*at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
*<-->*at java.lang.Thread.run(Thread.java:745)
[2018-12-28 12:30:06,658][ERROR][sys-stripe-12-#13][TcpCommunicationSpi] Failed
to send message to remote node [node=TcpDiscoveryNode
[id=8e884f80-f55d-4b32-9dcd-39e1af0ed2ef, addrs=ArrayList
class org.apache.ignite.spi.IgniteSpiException: Node is stopping.
*<-->*at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.reserveClient(TcpCommunicationSpi.java:2883)
*<-->*at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage0(TcpCommunicationSpi.java:2743)
*<-->*at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage(TcpCommunicationSpi.java:2702)
*<-->*at
org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1652)
*<-->*at
org.apache.ignite.internal.managers.communication.GridIoManager.sendToGridTopic(GridIoManager.java:1726)
*<-->*at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1240)
*<-->*at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1279)
*<-->*at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.sendDeferredUpdateResponse(GridDhtAtomicCache.java:3548)
*<-->*at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$3300(GridDhtAtomicCache.java:139)
*<-->*at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$DeferredUpdateTimeout.run(GridDhtAtomicCache.java:3794)
*<-->*at
org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:508)
*<-->*at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
*<-->*at java.lang.Thread.run(Thread.java:745)
{noformat}
I guess it is redundant information on *Node stopping* stage.
Please take a look at logs in the attachement.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9989) JDBC v2: getPrimaryKeys always returns constant COLUMN_NAME, KEY_SEQ, PK_NAME
[ https://issues.apache.org/jira/browse/IGNITE-9989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-9989: Ignite Flags: (was: Docs Required) > JDBC v2: getPrimaryKeys always returns constant COLUMN_NAME, KEY_SEQ, PK_NAME > - > > Key: IGNITE-9989 > URL: https://issues.apache.org/jira/browse/IGNITE-9989 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.6 >Reporter: Pavel Kuznetsov >Assignee: Pavel Kuznetsov >Priority: Major > Labels: jdbc > Fix For: 2.8 > > > Jdbc v2 driver has hardcoded values for meta attibutes : > COLUMN_NAME = _KEY > KEY_SEQ = 1 > PK_NAME = _KEY > But this values should be different for different tables. > how to reproduce: > 1) connect to the cluser using jdbcv2 driver > 2) CREATE TABLE TAB (ID LONG, SEC_ID LONG, VAL LONG, PRIMARY KEY(ID, SEC_ID)) > 3) check result of connection.getMetadata().getPrimaryKeys() -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9989) JDBC v2: getPrimaryKeys always returns constant COLUMN_NAME, KEY_SEQ, PK_NAME
[ https://issues.apache.org/jira/browse/IGNITE-9989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-9989: Fix Version/s: 2.8 > JDBC v2: getPrimaryKeys always returns constant COLUMN_NAME, KEY_SEQ, PK_NAME > - > > Key: IGNITE-9989 > URL: https://issues.apache.org/jira/browse/IGNITE-9989 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.6 >Reporter: Pavel Kuznetsov >Assignee: Pavel Kuznetsov >Priority: Major > Labels: jdbc > Fix For: 2.8 > > > Jdbc v2 driver has hardcoded values for meta attibutes : > COLUMN_NAME = _KEY > KEY_SEQ = 1 > PK_NAME = _KEY > But this values should be different for different tables. > how to reproduce: > 1) connect to the cluser using jdbcv2 driver > 2) CREATE TABLE TAB (ID LONG, SEC_ID LONG, VAL LONG, PRIMARY KEY(ID, SEC_ID)) > 3) check result of connection.getMetadata().getPrimaryKeys() -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-5439) JDBC thin: support query cancel
[
https://issues.apache.org/jira/browse/IGNITE-5439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16730233#comment-16730233
]
ASF GitHub Bot commented on IGNITE-5439:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5441
> JDBC thin: support query cancel
> ---
>
> Key: IGNITE-5439
> URL: https://issues.apache.org/jira/browse/IGNITE-5439
> Project: Ignite
> Issue Type: Task
> Components: jdbc
>Affects Versions: 2.0
>Reporter: Taras Ledkov
>Assignee: Alexander Lapin
>Priority: Major
> Fix For: 2.8
>
>
> The JDBC {{Statement.cancel}} method must be supported.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10645) SQL properties ownership flag should be set at configuration parsing, not query execution.
[ https://issues.apache.org/jira/browse/IGNITE-10645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16730235#comment-16730235 ] Vladimir Ozerov commented on IGNITE-10645: -- [~pkouznet], looks like we have new failures, are we? Please re-run and confirm that all above mentioned failures are not regressions. > SQL properties ownership flag should be set at configuration parsing, not > query execution. > -- > > Key: IGNITE-10645 > URL: https://issues.apache.org/jira/browse/IGNITE-10645 > Project: Ignite > Issue Type: Bug > Components: sql >Reporter: Pavel Kuznetsov >Assignee: Pavel Kuznetsov >Priority: Major > Fix For: 2.8 > > > At processing time, query entities are transformed and validated, table > descriptors with properties are created. > Now in some case (thre's no keyFields and key is of complex non-sql type), > ownership flag of query property is calculated at execution time (for example > at first put()): > https://github.com/apache/ignite/blob/dcdb27a24a450f63487290360b265e1570534629/modules/core/src/main/java/org/apache/ignite/internal/processors/query/property/QueryBinaryProperty.java#L132 > So we can't access metadata, that uses this not-yet-initialized field before > we put the data. > But we already have all necessary info to set this field at processing time. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10830) Return back semantic of GridServiceProcessor$ServiceTopologyCallable to avoid possible serialization issues
[
https://issues.apache.org/jira/browse/IGNITE-10830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16730225#comment-16730225
]
ASF GitHub Bot commented on IGNITE-10830:
-
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5760
> Return back semantic of GridServiceProcessor$ServiceTopologyCallable to avoid
> possible serialization issues
> ---
>
> Key: IGNITE-10830
> URL: https://issues.apache.org/jira/browse/IGNITE-10830
> Project: Ignite
> Issue Type: Task
> Components: managed services
>Reporter: Vyacheslav Daradur
>Assignee: Vyacheslav Daradur
>Priority: Major
> Fix For: 2.8
>
>
> It's necessary to revert changes of
> {{GridServiceProcessor$ServiceTopologyCallable}} introduced within
> IGNITE-9607.
> This may lead to serialization issues in some cases.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10823) Close all open cursors for running queries on Ignite stop
[ https://issues.apache.org/jira/browse/IGNITE-10823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16730213#comment-16730213 ] ASF GitHub Bot commented on IGNITE-10823: - Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5754 > Close all open cursors for running queries on Ignite stop > - > > Key: IGNITE-10823 > URL: https://issues.apache.org/jira/browse/IGNITE-10823 > Project: Ignite > Issue Type: Task > Components: sql >Affects Versions: 2.8 >Reporter: Yury Gerzhedovich >Assignee: Yury Gerzhedovich >Priority: Major > Labels: iep-29 > Fix For: 2.8 > > > Currently we can have situation when user doesn't close a cursors after use > it or don't full read it. In this case we have potential memory leak with > opened cursors. Need to close and set as null for all such running queries. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-10434) MVCC: Transaction asynchronous rollback bug.
[
https://issues.apache.org/jira/browse/IGNITE-10434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Seliverstov resolved IGNITE-10434.
---
Resolution: Fixed
Merged to master.
> MVCC: Transaction asynchronous rollback bug.
>
>
> Key: IGNITE-10434
> URL: https://issues.apache.org/jira/browse/IGNITE-10434
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Assignee: Igor Seliverstov
>Priority: Major
> Labels: mvcc_stabilization_stage_1, transactions
> Fix For: 2.8
>
>
> There is some bug in mvcc tx asynchronous rollback flow. Sometimes
> transaction is not rolled back completely: Remote transactions remain alive
> while Near and Dht transactions are terminated locally and on MVCC
> coordinator.
> Reproducer: {{MvccTxRollbackAsyncTest#testMixedAsyncRollbackTypes}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10379) SQL: Extract partition info from BETWEEN and range conditions for integer types
[
https://issues.apache.org/jira/browse/IGNITE-10379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-10379:
-
Fix Version/s: 2.8
> SQL: Extract partition info from BETWEEN and range conditions for integer
> types
> ---
>
> Key: IGNITE-10379
> URL: https://issues.apache.org/jira/browse/IGNITE-10379
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Alexander Lapin
>Priority: Major
> Labels: iep-24
> Fix For: 2.8
>
>
> If there is a range condition on affinity column of integer type, we may try
> to extract partition info from it in a way similar to IN clause [1]:
> {{x BETWEEN 1 and 5}} -> {{x IN (1, 2, 3, 4, 5)}}
> {{x > 1 and x <= 5}} -> {{x IN (2, 3, 4, 5)}}
> [1] IGNITE-9632
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10434) MVCC: Transaction asynchronous rollback bug.
[
https://issues.apache.org/jira/browse/IGNITE-10434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16730200#comment-16730200
]
ASF GitHub Bot commented on IGNITE-10434:
-
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5569
> MVCC: Transaction asynchronous rollback bug.
>
>
> Key: IGNITE-10434
> URL: https://issues.apache.org/jira/browse/IGNITE-10434
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Assignee: Igor Seliverstov
>Priority: Major
> Labels: mvcc_stabilization_stage_1, transactions
> Fix For: 2.8
>
>
> There is some bug in mvcc tx asynchronous rollback flow. Sometimes
> transaction is not rolled back completely: Remote transactions remain alive
> while Near and Dht transactions are terminated locally and on MVCC
> coordinator.
> Reproducer: {{MvccTxRollbackAsyncTest#testMixedAsyncRollbackTypes}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10748) Remove dead code in TcpCommunicationSpi for the tcp client creation flow
[
https://issues.apache.org/jira/browse/IGNITE-10748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16730192#comment-16730192
]
Maxim Muzafarov commented on IGNITE-10748:
--
[~NIzhikov]
Can you review my changes?
> Remove dead code in TcpCommunicationSpi for the tcp client creation flow
>
>
> Key: IGNITE-10748
> URL: https://issues.apache.org/jira/browse/IGNITE-10748
> Project: Ignite
> Issue Type: Task
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Minor
> Fix For: 2.8
>
>
> Currently, a batch of changes can be applied over {{TcpCommunicationSpi}}
> class implementation due to:
> # {{safeTcpHandshake(..)}}
> #* {{handshakeConnIdx}} - parameter is always not null
> #* {{recovery}} - parameter is always not null
> #* {{HandhakeMessage}} - is not used in current flow at all
> # {{HandshakeMessage2}}
> #* Message size must be defined in the message class as constant
> # {{createTcpClient(..)}}
> #* Instantiation of {{GridTcpNioCommunicationClient}} must be performed
> outside the while-loop
> # Code-style issues. Fix one-liner if statements.
> # Extract internal {{HandshakeException}}, {{HandshakeTimeoutException}} from
> class.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10379) SQL: Extract partition info from BETWEEN and range conditions for integer types
[
https://issues.apache.org/jira/browse/IGNITE-10379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16730196#comment-16730196
]
Vladimir Ozerov commented on IGNITE-10379:
--
[~alapin], my comments:
# There is no need for {{equals}} and {{hashCode}} methods for
{{GridSqlColumn}}. Columns are equal if they have the same {{schema, tblAlias,
colName}}
# {{IGNITE_PARTITIONS_PRUNNING_MAX_PARTIONS_BETWEEN}} value should be set to
{{MAX_PARTITIONS_COUNT_BETWEEN}} right away. No need to re-read it on every
query split
# {{tryExtractBetween}} method is overly complex. Ther is no need to re-check
various invariants over and over again. Instead, we can simply go ahead with
normal flow and return {{null}} as soon as found that no further processing is
possible.
# Final partition extraction is inefficient - why do we call {{extractSingle}}
over and over again, while we already have all necessary info to get partition
in two lines of code?
> SQL: Extract partition info from BETWEEN and range conditions for integer
> types
> ---
>
> Key: IGNITE-10379
> URL: https://issues.apache.org/jira/browse/IGNITE-10379
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Alexander Lapin
>Priority: Major
> Labels: iep-24
>
> If there is a range condition on affinity column of integer type, we may try
> to extract partition info from it in a way similar to IN clause [1]:
> {{x BETWEEN 1 and 5}} -> {{x IN (1, 2, 3, 4, 5)}}
> {{x > 1 and x <= 5}} -> {{x IN (2, 3, 4, 5)}}
> [1] IGNITE-9632
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-10776) Migrate from JUnit 3 to 4 config variations test suites
[
https://issues.apache.org/jira/browse/IGNITE-10776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Ignatenko reassigned IGNITE-10776:
---
Assignee: Oleg Ignatenko
> Migrate from JUnit 3 to 4 config variations test suites
> ---
>
> Key: IGNITE-10776
> URL: https://issues.apache.org/jira/browse/IGNITE-10776
> Project: Ignite
> Issue Type: Sub-task
>Affects Versions: 2.8
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
>Priority: Major
> Labels: MakeTeamcityGreenAgain
>
> This task is to migrate config variations test suites from JUnit 3 to 4.
> If needed, refer parent task comments for more details.
> Note this might be somewhat tough nut to crack design wise since
> {{JUnit4TestAdapter}} plays a special role in config variations tests, see
> IGNITE-10739.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10775) Migrate from JUnit 3 to 4 test suites of simple dynamic lists that use addTestIfNeeded API
[
https://issues.apache.org/jira/browse/IGNITE-10775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16730193#comment-16730193
]
Ignite TC Bot commented on IGNITE-10775:
{panel:title=-- Run :: All (Nightly): No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All (Nightly)*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2665473buildTypeId=IgniteTests24Java8_RunAllNightly]
> Migrate from JUnit 3 to 4 test suites of simple dynamic lists that use
> addTestIfNeeded API
> --
>
> Key: IGNITE-10775
> URL: https://issues.apache.org/jira/browse/IGNITE-10775
> Project: Ignite
> Issue Type: Sub-task
>Affects Versions: 2.8
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
>Priority: Major
> Labels: MakeTeamcityGreenAgain
>
> This task is to migrate from JUnit 3 to 4 test suites of simple dynamic lists
> that use {{GridTestUtils.addTestIfNeeded}} API.
> If needed, refer parent task comments for more details.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10727) [ML] InfModel and Model merging
[ https://issues.apache.org/jira/browse/IGNITE-10727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16730183#comment-16730183 ] ASF GitHub Bot commented on IGNITE-10727: - Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5723 > [ML] InfModel and Model merging > > > Key: IGNITE-10727 > URL: https://issues.apache.org/jira/browse/IGNITE-10727 > Project: Ignite > Issue Type: Improvement > Components: ml >Reporter: Alexey Platonov >Assignee: Anton Dmitriev >Priority: Major > Fix For: 2.8 > > > Currently "InfModel" and "Model" provide parallel architecture in terms of > using of "InfModels" in after-learning steps like compositions, estimations > etc. I propose to move "InfModel" to top of models hierarchy and rename it to > just "Model" and current "Model" rename to > "LearnedModel/LocalModel/Your_ad_may_be_here". So in this way "InfModel" will > be just model with apply-function for generic I-O values and "Model" will be > serializable thing on Vector-Double. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10379) SQL: Extract partition info from BETWEEN and range conditions for integer types
[
https://issues.apache.org/jira/browse/IGNITE-10379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16730170#comment-16730170
]
Alexander Lapin commented on IGNITE-10379:
--
[~Pavlukhin], [~jooger]Thanks, all fixed/answered.
> SQL: Extract partition info from BETWEEN and range conditions for integer
> types
> ---
>
> Key: IGNITE-10379
> URL: https://issues.apache.org/jira/browse/IGNITE-10379
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Alexander Lapin
>Priority: Major
> Labels: iep-24
>
> If there is a range condition on affinity column of integer type, we may try
> to extract partition info from it in a way similar to IN clause [1]:
> {{x BETWEEN 1 and 5}} -> {{x IN (1, 2, 3, 4, 5)}}
> {{x > 1 and x <= 5}} -> {{x IN (2, 3, 4, 5)}}
> [1] IGNITE-9632
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10841) Edge-chasing deadlock detection monitoring
Ivan Pavlukhin created IGNITE-10841: --- Summary: Edge-chasing deadlock detection monitoring Key: IGNITE-10841 URL: https://issues.apache.org/jira/browse/IGNITE-10841 Project: Ignite Issue Type: Bug Components: mvcc Reporter: Ivan Pavlukhin A deadlock detection process introduces several effects in the system which should be visible for an administrator. Here are couple of such effects: 1. Rolling back deadlocked transactions. 2. Introducing messaging overhead even in case when there are not deadlocks. Several metrics can be exposed via JMX and/or SQL view. Here are some candidates: 1. Number of detected deadlocks and involved transactions. 2. Sent/received deadlock detection messages count. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10840) Disabling WAL Archiving via setting walArchivePath to walPath isn't worked as expected
Andrey Aleksandrov created IGNITE-10840:
---
Summary: Disabling WAL Archiving via setting walArchivePath to
walPath isn't worked as expected
Key: IGNITE-10840
URL: https://issues.apache.org/jira/browse/IGNITE-10840
Project: Ignite
Issue Type: Bug
Components: general
Affects Versions: 2.6
Reporter: Andrey Aleksandrov
Fix For: 2.8
Attachments: Result.png, config1.xml, config2.xml
Description:
1)start the server node with separate wal and walArchive wait for the first
archived segment.
See config1.xml
Code:
Ignite ign = Ignition.start("examples/config/config1.xml");
ign.cluster().active(true);
IgniteCache cache = ign.getOrCreateCache("default");
for (int i = 0;; i++) {
cache.put(i, i);
if(i % 1000 == 0) {
System.out.println(i);
}
}
2) Wait for the first archived segment.
[2018-12-28 12:28:44,426][INFO
][wal-file-archiver%null-#47][FileWriteAheadLogManager] Starting to copy WAL
segment [absIdx=0, segIdx=0,
origFile=C:\test\wal\node00-db91fc4b-0b9f-4253-8dd0-ab1ca221331a\.wal,
dstFile=C:\test\walAr\node00-db91fc4b-0b9f-4253-8dd0-ab1ca221331a\.wal]
[2018-12-28 12:28:44,465][INFO
][wal-file-archiver%null-#47][FileWriteAheadLogManager] Copied file
[src=C:\test\wal\node00-db91fc4b-0b9f-4253-8dd0-ab1ca221331a\.wal,
dst=C:\test\walAr\node00-db91fc4b-0b9f-4253-8dd0-ab1ca221331a\.wal]
3)stop the node
4)Change the walArchivePath to walPath as it described here:
See config2.xml
https://apacheignite.readme.io/docs/write-ahead-log#section-disabling-wal-archiving
5)Restart the node with updated configuration
Ignite ign = Ignition.start("examples/config/config2.xml");
ign.cluster().active(true);
IgniteCache cache = ign.getOrCreateCache("default");
for (int i = 0;; i++) {
cache.put(i, i);
if(i % 1000 == 0) {
System.out.println(i);
}
}
As a result, walArchive will not be disabled and new segments will be store in
WAL directory.
In Ignite 2.6 it will be a reason for the next exception on next node restart:
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to
initialize wal (work directory contains incorrect number of segments)
[cur=357, expected=10]
at
org.apache.ignite.internal.processors.cache.persistence.wal.FsyncModeFileWriteAheadLogManager.checkOrPrepareFiles(FsyncModeFileWriteAheadLogManager.java:1112)
at
org.apache.ignite.internal.processors.cache.persistence.wal.FsyncModeFileWriteAheadLogManager.start0(FsyncModeFileWriteAheadLogManager.java:348)
at
org.apache.ignite.internal.processors.cache.GridCacheSharedManagerAdapter.start(GridCacheSharedManagerAdapter.java:61)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.start(GridCacheProcessor.java:700)
at
org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1739)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10379) SQL: Extract partition info from BETWEEN and range conditions for integer types
[
https://issues.apache.org/jira/browse/IGNITE-10379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16730160#comment-16730160
]
Yury Gerzhedovich commented on IGNITE-10379:
[~alapin] please see also my comments on Github
> SQL: Extract partition info from BETWEEN and range conditions for integer
> types
> ---
>
> Key: IGNITE-10379
> URL: https://issues.apache.org/jira/browse/IGNITE-10379
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Alexander Lapin
>Priority: Major
> Labels: iep-24
>
> If there is a range condition on affinity column of integer type, we may try
> to extract partition info from it in a way similar to IN clause [1]:
> {{x BETWEEN 1 and 5}} -> {{x IN (1, 2, 3, 4, 5)}}
> {{x > 1 and x <= 5}} -> {{x IN (2, 3, 4, 5)}}
> [1] IGNITE-9632
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10655) .NET client should have peerClassLoading property in IgniteConfiguration class
[ https://issues.apache.org/jira/browse/IGNITE-10655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16730149#comment-16730149 ] ASF GitHub Bot commented on IGNITE-10655: - GitHub user DirectXceriD opened a pull request: https://github.com/apache/ignite/pull/5769 IGNITE-10655 add p2pEnabled to .NET You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10655 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5769.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #5769 commit b78b1a9630eb0c258812ace098b975139b3f4813 Author: Vladimir Pligin Date: 2018-12-27T10:01:11Z IGNITE-10655 add p2pEnabled to .NET client > .NET client should have peerClassLoading property in IgniteConfiguration class > -- > > Key: IGNITE-10655 > URL: https://issues.apache.org/jira/browse/IGNITE-10655 > Project: Ignite > Issue Type: Improvement > Components: platforms >Affects Versions: 2.7 >Reporter: Andrey Aleksandrov >Assignee: Vladimir Pligin >Priority: Major > Fix For: 2.8 > > > In case if java server nodes in a cluster were set up with peerClassLoading > set to true then there is no way to start node via .NET client using > IgniteConfiguration (because the default value is false). > The only way to do it is using of the XML configuration. > Possibility to set this property from .Net client programmatically should be > added. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10379) SQL: Extract partition info from BETWEEN and range conditions for integer types
[
https://issues.apache.org/jira/browse/IGNITE-10379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16730146#comment-16730146
]
Ivan Pavlukhin commented on IGNITE-10379:
-
[~alapin] please see my comments on GitHub.
> SQL: Extract partition info from BETWEEN and range conditions for integer
> types
> ---
>
> Key: IGNITE-10379
> URL: https://issues.apache.org/jira/browse/IGNITE-10379
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Alexander Lapin
>Priority: Major
> Labels: iep-24
>
> If there is a range condition on affinity column of integer type, we may try
> to extract partition info from it in a way similar to IN clause [1]:
> {{x BETWEEN 1 and 5}} -> {{x IN (1, 2, 3, 4, 5)}}
> {{x > 1 and x <= 5}} -> {{x IN (2, 3, 4, 5)}}
> [1] IGNITE-9632
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10811) Add new TC build-config to test Service Grid new and old implementations
[ https://issues.apache.org/jira/browse/IGNITE-10811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16730145#comment-16730145 ] ASF GitHub Bot commented on IGNITE-10811: - Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5759 > Add new TC build-config to test Service Grid new and old implementations > > > Key: IGNITE-10811 > URL: https://issues.apache.org/jira/browse/IGNITE-10811 > Project: Ignite > Issue Type: Task > Components: managed services >Reporter: Vyacheslav Daradur >Assignee: Vyacheslav Daradur >Priority: Major > Labels: iep-17 > Fix For: 2.8 > > > It's necessary to add new build configuration on TeamCity (after merge > IGNITE-9607) to have ability testing new and old implementations of the > service processor. > In general, new build plan should contain 2 test suites: > 1) To place Service Grid related tests which *do not depend on* service > processor's implementation (like classic unit tests) and *should be executed > once*; > 2) To place Service Grid related tests which *depend* *on* service > processor's implementation and *should be executed twice* in the new mode and > old mode (-DIGNITE_EVENT_DRIVEN_SERVICE_PROCESSOR_ENABLED=false) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10811) Add new TC build-config to test Service Grid new and old implementations
[ https://issues.apache.org/jira/browse/IGNITE-10811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16730114#comment-16730114 ] Ryabov Dmitrii commented on IGNITE-10811: - Tests looks good, no test is lost. [~NIzhikov], let's merge! > Add new TC build-config to test Service Grid new and old implementations > > > Key: IGNITE-10811 > URL: https://issues.apache.org/jira/browse/IGNITE-10811 > Project: Ignite > Issue Type: Task > Components: managed services >Reporter: Vyacheslav Daradur >Assignee: Vyacheslav Daradur >Priority: Major > Labels: iep-17 > Fix For: 2.8 > > > It's necessary to add new build configuration on TeamCity (after merge > IGNITE-9607) to have ability testing new and old implementations of the > service processor. > In general, new build plan should contain 2 test suites: > 1) To place Service Grid related tests which *do not depend on* service > processor's implementation (like classic unit tests) and *should be executed > once*; > 2) To place Service Grid related tests which *depend* *on* service > processor's implementation and *should be executed twice* in the new mode and > old mode (-DIGNITE_EVENT_DRIVEN_SERVICE_PROCESSOR_ENABLED=false) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-10180) Investigate migration from Junit 4 to 5
[ https://issues.apache.org/jira/browse/IGNITE-10180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Fedotov reassigned IGNITE-10180: - Assignee: Ivan Fedotov > Investigate migration from Junit 4 to 5 > --- > > Key: IGNITE-10180 > URL: https://issues.apache.org/jira/browse/IGNITE-10180 > Project: Ignite > Issue Type: Sub-task >Reporter: Oleg Ignatenko >Assignee: Ivan Fedotov >Priority: Major > > If needed, refer parent task for more details. > Find out if Junit 5 is mature enough - specifically why maven still uses > Junit 4 as default, are there serious reasons for that or not. If it looks > okay, create a new JIRA task to migrate. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10379) SQL: Extract partition info from BETWEEN and range conditions for integer types
[
https://issues.apache.org/jira/browse/IGNITE-10379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16730097#comment-16730097
]
Alexander Lapin commented on IGNITE-10379:
--
First iteration of extracting partitions from between and similar range
operation. For now works only with constants (parameters not supported).
> SQL: Extract partition info from BETWEEN and range conditions for integer
> types
> ---
>
> Key: IGNITE-10379
> URL: https://issues.apache.org/jira/browse/IGNITE-10379
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Alexander Lapin
>Priority: Major
> Labels: iep-24
>
> If there is a range condition on affinity column of integer type, we may try
> to extract partition info from it in a way similar to IN clause [1]:
> {{x BETWEEN 1 and 5}} -> {{x IN (1, 2, 3, 4, 5)}}
> {{x > 1 and x <= 5}} -> {{x IN (2, 3, 4, 5)}}
> [1] IGNITE-9632
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10763) MVCC: Transaction already completed error in some tests
[
https://issues.apache.org/jira/browse/IGNITE-10763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16730113#comment-16730113
]
Ivan Pavlukhin commented on IGNITE-10763:
-
It seems that error in
{{CacheMvccReplicatedSqlTxQueriesTest.testReplicatedAndPartitionedUpdateSingleTransaction}}
is caused by leaked tx stored in {{ThreadLocal}}
({{IgniteTxManager.txContext}}).
> MVCC: Transaction already completed error in some tests
> ---
>
> Key: IGNITE-10763
> URL: https://issues.apache.org/jira/browse/IGNITE-10763
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Assignee: Ivan Pavlukhin
>Priority: Major
> Labels: MakeTeamcityGreenAgain, mvcc_stabilization_stage_1,
> transactions
> Fix For: 2.8
>
>
> "Transaction is already completed" error occurs time to time in some tests.
> Reproducer:
> {{CacheMvccReplicatedSqlTxQueriesTest.testReplicatedAndPartitionedUpdateSingleTransaction}}
> {{CacheMvccPartitionedSqlTxQueriesWithReducerTest.testQueryReducerDeadlockInsertWithTxTimeout}}
>
> {noformat}
> class org.apache.ignite.internal.processors.query.IgniteSQLException:
> Transaction is already completed.
> at
> org.apache.ignite.internal.processors.cache.mvcc.MvccUtils.checkActive(MvccUtils.java:660)
> at
> org.apache.ignite.internal.processors.cache.mvcc.MvccUtils.requestSnapshot(MvccUtils.java:832)
> at
> org.apache.ignite.internal.processors.cache.mvcc.MvccUtils.mvccTracker(MvccUtils.java:813)
> at
> org.apache.ignite.internal.processors.cache.mvcc.MvccUtils.mvccTracker(MvccUtils.java:796)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.runQueryTwoStep(IgniteH2Indexing.java:1131)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.doRunDistributedQuery(IgniteH2Indexing.java:1990)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.doRunPrepared(IgniteH2Indexing.java:1636)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.querySqlFields(IgniteH2Indexing.java:1526)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$3.applyx(GridQueryProcessor.java:2167)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$3.applyx(GridQueryProcessor.java:2162)
> at
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2670)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.lambda$querySqlFields$1(GridQueryProcessor.java:2176)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuerySafe(GridQueryProcessor.java:2196)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2157)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2118)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2091)
> at
> org.apache.ignite.internal.processors.cache.mvcc.CacheMvccReplicatedSqlTxQueriesTest.runSql(CacheMvccReplicatedSqlTxQueriesTest.java:234)
> at
> org.apache.ignite.internal.processors.cache.mvcc.CacheMvccReplicatedSqlTxQueriesTest.testReplicatedAndPartitionedUpdateSingleTransaction(CacheMvccReplicatedSqlTxQueriesTest.java:202)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2121)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
