[jira] [Created] (IGNITE-11614) Transaction with timeout on cache with near configuration hangs after cache store failure indefinitely
Anton Kurbanov created IGNITE-11614: --- Summary: Transaction with timeout on cache with near configuration hangs after cache store failure indefinitely Key: IGNITE-11614 URL: https://issues.apache.org/jira/browse/IGNITE-11614 Project: Ignite Issue Type: Bug Affects Versions: 2.7 Reporter: Anton Kurbanov -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: Ignite 2.7.5 Release scope
Hi Igniters, Let me share a couple more links related to release https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.7.5 Tests (now tests use Java 8): https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAllNightly=ignite-2.7=ignite-2.7.5=Latest TC bot had corruption, so for now, it is a number of blockers tests, I hope runs during the weekend will help to re-collect stat for 2.7 https://mtcga.gridgain.com/current.html?branch=ignite-2.7.5-nightly Also, I've changed scripts to allow to run Ignite under Java 12+, please review/test changes https://issues.apache.org/jira/browse/IGNITE-11600 https://github.com/apache/ignite/pull/6326 Sincerely, Dmitriy Pavlov пт, 22 мар. 2019 г. в 17:00, Ilya Kasnacheev : > Hello! > > Basically there is a test that explicitly highlights this problem, that is > running SSL tests on Windows + Java 11. They will hang on Master but pass > with this patch. > > I have started that on TC, results will probably be available later today: > > https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_SpiWindows=buildTypeStatusDiv_IgniteTests24Java8=__all_branches__ > (mind the Java version). > > Regards, > -- > Ilya Kasnacheev > > > пт, 22 мар. 2019 г. в 14:13, Maxim Muzafarov : > > > Dmitry, Ilya, > > > > Yes, I've looked through those changes [1] as they can affect my local > > PR. Basically, changes look good to me. > > > > I'm not an expert with CommunicationSpi component, so can miss some > > details and I haven't tested these changes under Java 11. One more > > thing I'd like to say, I would add additional tests to PR that will > > explicitly highlight the problem being solved. > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-11299 > > > > On Thu, 21 Mar 2019 at 22:57, Dmitriy Pavlov wrote: > > > > > > Hi Igniters, > > > > > > fix https://issues.apache.org/jira/browse/IGNITE-11299 Avoid busy wait > > on > > > processWrite during SSL handshake. > > > seems to be blocker cause it is related to Java 11 > > > > > > I see Maxim M left some comments. Ilya K., Maxim M.were these comments > > > addressed? > > > > > > The ticket is in Patch Available. Reviewer needed. Changes located in > > > GridNioServer. > > > > > > Sincerely, > > > Dmitriy Pavlov > > > > > > P.S. a quite obvious ticket came to sope, as well: > > > https://issues.apache.org/jira/browse/IGNITE-11600 > > > > > > > > > чт, 21 мар. 2019 г. в 16:55, Petr Ivanov : > > > > > > > Huge +1 > > > > > > > > Will try to add new JDK in nearest time to our Teamcity. > > > > > > > > > > > > > On 21 Mar 2019, at 16:27, Dmitriy Pavlov > wrote: > > > > > > > > > > Hi Igniters, > > > > > > > > > > Meanwhile, Java 12 GA is available. I suggest at least test our new > > tests > > > > > scripts with a couple of Java builds. WDYT? > > > > > > > > > > Sincerely, > > > > > Dmitriy Pavlov > > > > > > > > > > ср, 20 мар. 2019 г. в 19:21, Dmitriy Pavlov : > > > > > > > > > >> Hi Ignite Developers, > > > > >> > > > > >> In a separate discussion, I've shared a log with all commits. > > > > >> > > > > >> As far as I can see, nobody removed commits from this sheet, so > the > > > > scope > > > > >> of release will be discussed in another way: only explicitly > > declared > > > > >> commits will be cherry-picked. > > > > >> > > > > >> Sincerely, > > > > >> Dmitriy Pavlov > > > > >> > > > > > > > > > > >
[jira] [Created] (IGNITE-11613) GridSpringBeanSerializationSelfTest fails in master
Alexey Goncharuk created IGNITE-11613: - Summary: GridSpringBeanSerializationSelfTest fails in master Key: IGNITE-11613 URL: https://issues.apache.org/jira/browse/IGNITE-11613 Project: Ignite Issue Type: Test Reporter: Alexey Goncharuk >From the logs it's clear that the test fails because the node being started >picks up some other nodes through multicast and fails because of an >incompatible configuration. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11612) http.GridHttpDeploymentSelfTest always fails
Ivan Bessonov created IGNITE-11612: -- Summary: http.GridHttpDeploymentSelfTest always fails Key: IGNITE-11612 URL: https://issues.apache.org/jira/browse/IGNITE-11612 Project: Ignite Issue Type: Test Reporter: Ivan Bessonov Assignee: Ivan Bessonov Fix For: 2.8 [https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=8313984068492573325=testDetails] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11611) If partition cannot be recovered during rebalance it should be moved to LOST state.
Alexei Scherbakov created IGNITE-11611: -- Summary: If partition cannot be recovered during rebalance it should be moved to LOST state. Key: IGNITE-11611 URL: https://issues.apache.org/jira/browse/IGNITE-11611 Project: Ignite Issue Type: Improvement Reporter: Alexei Scherbakov Fix For: 2.8 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11610) Add note to the DROP TABLE doc that it can be used only for table created with DDL
Evgenii Zhuravlev created IGNITE-11610: -- Summary: Add note to the DROP TABLE doc that it can be used only for table created with DDL Key: IGNITE-11610 URL: https://issues.apache.org/jira/browse/IGNITE-11610 Project: Ignite Issue Type: Bug Components: documentation Reporter: Evgenii Zhuravlev Assignee: Artem Budnikov -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11609) Add support of authentication and SSL in yardstick IgniteThinClient benchmark
Dmitry Sherstobitov created IGNITE-11609: Summary: Add support of authentication and SSL in yardstick IgniteThinClient benchmark Key: IGNITE-11609 URL: https://issues.apache.org/jira/browse/IGNITE-11609 Project: Ignite Issue Type: New Feature Affects Versions: 2.7 Reporter: Dmitry Sherstobitov Fix For: 2.8 Add support of following keys: Mandatory authentication: USER PASSWORD Mandatory SSL: SSL_KEY_PASSWORD SSL_KEY_PATH Optional SSL: SSL_CLIENT_STORE_TYPE (default JKS) SSL_SERVER_STORE_TYPE (default JKS) SSL_KEY_ALGORITHM (default SunX509) SSL_TRUST_ALL (default false) SSL_PROTOCOL (default TLS) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: Ignite 2.7.5 Release scope
Hello! Basically there is a test that explicitly highlights this problem, that is running SSL tests on Windows + Java 11. They will hang on Master but pass with this patch. I have started that on TC, results will probably be available later today: https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_SpiWindows=buildTypeStatusDiv_IgniteTests24Java8=__all_branches__ (mind the Java version). Regards, -- Ilya Kasnacheev пт, 22 мар. 2019 г. в 14:13, Maxim Muzafarov : > Dmitry, Ilya, > > Yes, I've looked through those changes [1] as they can affect my local > PR. Basically, changes look good to me. > > I'm not an expert with CommunicationSpi component, so can miss some > details and I haven't tested these changes under Java 11. One more > thing I'd like to say, I would add additional tests to PR that will > explicitly highlight the problem being solved. > > > [1] https://issues.apache.org/jira/browse/IGNITE-11299 > > On Thu, 21 Mar 2019 at 22:57, Dmitriy Pavlov wrote: > > > > Hi Igniters, > > > > fix https://issues.apache.org/jira/browse/IGNITE-11299 Avoid busy wait > on > > processWrite during SSL handshake. > > seems to be blocker cause it is related to Java 11 > > > > I see Maxim M left some comments. Ilya K., Maxim M.were these comments > > addressed? > > > > The ticket is in Patch Available. Reviewer needed. Changes located in > > GridNioServer. > > > > Sincerely, > > Dmitriy Pavlov > > > > P.S. a quite obvious ticket came to sope, as well: > > https://issues.apache.org/jira/browse/IGNITE-11600 > > > > > > чт, 21 мар. 2019 г. в 16:55, Petr Ivanov : > > > > > Huge +1 > > > > > > Will try to add new JDK in nearest time to our Teamcity. > > > > > > > > > > On 21 Mar 2019, at 16:27, Dmitriy Pavlov wrote: > > > > > > > > Hi Igniters, > > > > > > > > Meanwhile, Java 12 GA is available. I suggest at least test our new > tests > > > > scripts with a couple of Java builds. WDYT? > > > > > > > > Sincerely, > > > > Dmitriy Pavlov > > > > > > > > ср, 20 мар. 2019 г. в 19:21, Dmitriy Pavlov : > > > > > > > >> Hi Ignite Developers, > > > >> > > > >> In a separate discussion, I've shared a log with all commits. > > > >> > > > >> As far as I can see, nobody removed commits from this sheet, so the > > > scope > > > >> of release will be discussed in another way: only explicitly > declared > > > >> commits will be cherry-picked. > > > >> > > > >> Sincerely, > > > >> Dmitriy Pavlov > > > >> > > > > > > >
[jira] [Created] (IGNITE-11608) Document static persistent caches and DDL behavior
Alexey Goncharuk created IGNITE-11608: - Summary: Document static persistent caches and DDL behavior Key: IGNITE-11608 URL: https://issues.apache.org/jira/browse/IGNITE-11608 Project: Ignite Issue Type: Task Components: documentation Reporter: Alexey Goncharuk In IGNITE-11541 we changed the logic to ignore static cache configuration in favor of persisted cache config because the old behavior was incorrect in regards with DDL. A system property was introduced to keep the old behavior. These changes should be documented in https://apacheignite.readme.io/docs/cache-configuration -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11607) Historical rebalance is not possible from partition which was recently rebalanced itself
Alexei Scherbakov created IGNITE-11607: -- Summary: Historical rebalance is not possible from partition which was recently rebalanced itself Key: IGNITE-11607 URL: https://issues.apache.org/jira/browse/IGNITE-11607 Project: Ignite Issue Type: Improvement Reporter: Alexei Scherbakov Fix For: 2.8 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11606) Index could not contain all values from cache after full rebuild
Eduard Shangareev created IGNITE-11606:
--
Summary: Index could not contain all values from cache after full
rebuild
Key: IGNITE-11606
URL: https://issues.apache.org/jira/browse/IGNITE-11606
Project: Ignite
Issue Type: Bug
Reporter: Eduard Shangareev
If index.bin was deleted, we would rebuild it on node start.
But it could cause to the situation when a key is in the cache but SQL query
doesn't return it.
{code}
[18:29:07][:363] idle_verify check has finished, found 1194 conflict
partitions: [counterConflicts=0, hashConflicts=1194]
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11605) Incorrect check condition in BinaryTypeRegistrationTest.shouldSendOnlyOneMetadataMessage
Anton Kalashnikov created IGNITE-11605:
--
Summary: Incorrect check condition in
BinaryTypeRegistrationTest.shouldSendOnlyOneMetadataMessage
Key: IGNITE-11605
URL: https://issues.apache.org/jira/browse/IGNITE-11605
Project: Ignite
Issue Type: Bug
Reporter: Anton Kalashnikov
Assignee: Anton Kalashnikov
BinaryTypeRegistrationTest.shouldSendOnlyOneMetadataMessage is flaky.
{noformat}
java.lang.AssertionError:
Expected :1
Actual :2
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:743)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:555)
at org.junit.Assert.assertEquals(Assert.java:542)
at
org.apache.ignite.testframework.junits.JUnitAssertAware.assertEquals(JUnitAssertAware.java:94)
at
org.apache.ignite.internal.processors.cache.BinaryTypeRegistrationTest.shouldSendOnlyOneMetadataMessage(BinaryTypeRegistrationTest.java:106)
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.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:2102)
at java.lang.Thread.run(Thread.java:748)
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
Re: Ignite 2.7.5 Release scope
Dmitry, Ilya, Yes, I've looked through those changes [1] as they can affect my local PR. Basically, changes look good to me. I'm not an expert with CommunicationSpi component, so can miss some details and I haven't tested these changes under Java 11. One more thing I'd like to say, I would add additional tests to PR that will explicitly highlight the problem being solved. [1] https://issues.apache.org/jira/browse/IGNITE-11299 On Thu, 21 Mar 2019 at 22:57, Dmitriy Pavlov wrote: > > Hi Igniters, > > fix https://issues.apache.org/jira/browse/IGNITE-11299 Avoid busy wait on > processWrite during SSL handshake. > seems to be blocker cause it is related to Java 11 > > I see Maxim M left some comments. Ilya K., Maxim M.were these comments > addressed? > > The ticket is in Patch Available. Reviewer needed. Changes located in > GridNioServer. > > Sincerely, > Dmitriy Pavlov > > P.S. a quite obvious ticket came to sope, as well: > https://issues.apache.org/jira/browse/IGNITE-11600 > > > чт, 21 мар. 2019 г. в 16:55, Petr Ivanov : > > > Huge +1 > > > > Will try to add new JDK in nearest time to our Teamcity. > > > > > > > On 21 Mar 2019, at 16:27, Dmitriy Pavlov wrote: > > > > > > Hi Igniters, > > > > > > Meanwhile, Java 12 GA is available. I suggest at least test our new tests > > > scripts with a couple of Java builds. WDYT? > > > > > > Sincerely, > > > Dmitriy Pavlov > > > > > > ср, 20 мар. 2019 г. в 19:21, Dmitriy Pavlov : > > > > > >> Hi Ignite Developers, > > >> > > >> In a separate discussion, I've shared a log with all commits. > > >> > > >> As far as I can see, nobody removed commits from this sheet, so the > > scope > > >> of release will be discussed in another way: only explicitly declared > > >> commits will be cherry-picked. > > >> > > >> Sincerely, > > >> Dmitriy Pavlov > > >> > > > >
[jira] [Created] (IGNITE-11604) Drop column does not remove column from internal schema
Alexey Goncharuk created IGNITE-11604:
-
Summary: Drop column does not remove column from internal schema
Key: IGNITE-11604
URL: https://issues.apache.org/jira/browse/IGNITE-11604
Project: Ignite
Issue Type: Bug
Reporter: Alexey Goncharuk
Discovered this during the work on IGNITE-11541 (see
{{StaticCacheDdlTest.testDropColumn}}).
After a quick debug I see the following: in
{{GridQueryProcessor#onSchemaFinishDiscovery}} we call
{{DynamicCacheDescriptor.schemaChangeFinish(msg)}}, which eventually calls
{{QuerySchema.finish(op)}}.
Inside that method we have the following: the {{message.columns()}} collection
has the field name in upper case (in the test it's "FIELD_TO_DROP"), but the
entity's fields map contains lower-case names ("field_to_drop"). As a result,
we do not remove the field from the query entity, this query entity is saved to
the stored cache data and field re-appears after restart.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11603) ESCAPE key word in combination with LIKE statement seems to be prohibited
Emanuel Warga created IGNITE-11603:
--
Summary: ESCAPE key word in combination with LIKE statement seems
to be prohibited
Key: IGNITE-11603
URL: https://issues.apache.org/jira/browse/IGNITE-11603
Project: Ignite
Issue Type: Bug
Components: odbc
Affects Versions: 2.7
Reporter: Emanuel Warga
As described in
https://stackoverflow.com/questions/55283492/like-statement-causes-unsupported-query-on-ignite-2-7-with-querydsl
Ignite seems to have a problem when I use LIKE with the ESCAPE key word.
Example:
{{ select * from mytable mt where (mt.c1 LIKE 'Abc%' ESCAPE '!');}}
I get an error announcing this is an unsupported query.
The error doesn't show up if I don't use '% inside the search string so the
problem doesn't seem to be a general one like "we don't support the ESCAPE key
word."
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
Re: beforeTest, afterTest JUnit scenario implementation
Hi Ivan, Thank you for your response. In this way, I will finish IGNITE-11411-13 tickets with Rule annotation and minimal changes. чт, 21 мар. 2019 г. в 21:19, Павлухин Иван : > Hi Ivan, > > During migration from junit 3 to 4 multiple options was discussed [1]. > And the main decision about before/after test method was making as > less as possible changes in already existing tests with adding an > ability to write new tests using common junit 4 style (i.e. using > annotations in new tests). > > And it seems that mentioned above correlates with your approach. > > [1] > http://apache-ignite-developers.2346864.n4.nabble.com/Is-it-time-to-move-forward-to-JUnit4-5-td29608.html > > ср, 20 мар. 2019 г. в 17:38, Ivan Fedotov : > > > > Hi Igniters! > > > > I have a questions according to beforeTest(s)/afterTest(s) methods. I > tried > > to make them correspond to JUnit 4+ semantics in the context of iep30 > [1]. > > And I see there two solutions: > > > > 1. Place test scenario under the Rule annotation as it has already done > in > > GridAbstractTest [2]. It is a built-in opportunity to extend JUnit > > framework. Such case already implemented and demands minimal changes. To > > add before and after test logic in the other classes, it is necessary to > > override corresponding methods. > > > > 2. Write before and after test logic with annotations in GridAbstractTest > > and all other classes. Such solution is less flexible in comparison with > > rules. Moreover, under annotation, a code will be less readable than > under > > rule. But such approach decreases coupling between classes. > > > > The main argumentation in favor of the first approach is that there are > > minimal changes in code. According to this during migration on other > JUnit > > versions, there is no need to fix all test files to change imports and > > annotations (for instance, in JUnit5 Before/BeforeClass, After/AfterClass > > annotations were changed). Changes will affect only GridAbstractTest > > class. At the same time, the possibility to use annotations remains. > > > > Now I started to implement the first approach [3] - specify test scenario > > under the Rule annotation and override methods if it is necessary. > > Such functionality is similar to the third version, but with 4+ semantics > > and with minimal changes during migration. > > > > What do you think, which approach will be better for the community? > > > > [1] > > > https://cwiki.apache.org/confluence/display/IGNITE/IEP-30%3A+Migration+to+JUnit+5 > > [2] > > > https://github.com/apache/ignite/blob/master/modules/core/src/test/java/org/apache/ignite/testframework/junits/GridAbstractTest.java#L181 > > [3]https://github.com/apache/ignite/pull/6227/files > > > > -- > > Ivan Fedotov. > > > > ivanan...@gmail.com > > > > -- > Best regards, > Ivan Pavlukhin > -- Ivan Fedotov. ivanan...@gmail.com
