[jira] [Commented] (IGNITE-12823) .NET: Service method with user type array parameter can't be found
[
https://issues.apache.org/jira/browse/IGNITE-12823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17119476#comment-17119476
]
Nikolai Kulagin commented on IGNITE-12823:
--
LGTM
> .NET: Service method with user type array parameter can't be found
> --
>
> Key: IGNITE-12823
> URL: https://issues.apache.org/jira/browse/IGNITE-12823
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Reporter: Alexey Kukushkin
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: .NET, sbcf
> Attachments: ignite-12823-vs-2.8.patch
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> *+Setup+*
> * Ignite Java service with a method having an array of user types as a
> parameters, for example, caclulate(Parameter[] params)
> *+Actions+*
> * .NET client calls the Ignite Java service, for example,
> ignite.GetServices().GetServiceProxy().calculate(new[] \{new
> Parameter()});
> *+Expected+*
> * The service method is called
> *+Actual+*
> * Exception "Could not find proxy method 'calculate' in class ICalculator"
> *+Workaround+*
> * Replace array of user types with array of objects in the service methods
> signatures, for example, caclulate(Object[] params)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12823) .NET: Service method with user type array parameter can't be found
[
https://issues.apache.org/jira/browse/IGNITE-12823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17116517#comment-17116517
]
Nikolai Kulagin commented on IGNITE-12823:
--
[~ptupitsyn], reading arrays as BinaryObject can be done in Ignite 3.0.
> .NET: Service method with user type array parameter can't be found
> --
>
> Key: IGNITE-12823
> URL: https://issues.apache.org/jira/browse/IGNITE-12823
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Reporter: Alexey Kukushkin
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: .NET, sbcf
> Attachments: ignite-12823-vs-2.8.patch
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> *+Setup+*
> * Ignite Java service with a method having an array of user types as a
> parameters, for example, caclulate(Parameter[] params)
> *+Actions+*
> * .NET client calls the Ignite Java service, for example,
> ignite.GetServices().GetServiceProxy().calculate(new[] \{new
> Parameter()});
> *+Expected+*
> * The service method is called
> *+Actual+*
> * Exception "Could not find proxy method 'calculate' in class ICalculator"
> *+Workaround+*
> * Replace array of user types with array of objects in the service methods
> signatures, for example, caclulate(Object[] params)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-12823) .NET: Service method with user type array parameter can't be found
[
https://issues.apache.org/jira/browse/IGNITE-12823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolai Kulagin reassigned IGNITE-12823:
Assignee: Pavel Tupitsyn (was: Nikolai Kulagin)
> .NET: Service method with user type array parameter can't be found
> --
>
> Key: IGNITE-12823
> URL: https://issues.apache.org/jira/browse/IGNITE-12823
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Reporter: Alexey Kukushkin
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: .NET, sbcf
> Attachments: ignite-12823-vs-2.8.patch
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> *+Setup+*
> * Ignite Java service with a method having an array of user types as a
> parameters, for example, caclulate(Parameter[] params)
> *+Actions+*
> * .NET client calls the Ignite Java service, for example,
> ignite.GetServices().GetServiceProxy().calculate(new[] \{new
> Parameter()});
> *+Expected+*
> * The service method is called
> *+Actual+*
> * Exception "Could not find proxy method 'calculate' in class ICalculator"
> *+Workaround+*
> * Replace array of user types with array of objects in the service methods
> signatures, for example, caclulate(Object[] params)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-12823) .NET: Service method with user type array parameter can't be found
[
https://issues.apache.org/jira/browse/IGNITE-12823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17116157#comment-17116157
]
Nikolai Kulagin edited comment on IGNITE-12823 at 5/25/20, 5:41 PM:
[~ptupitsyn], Yes, your decision is better. Unfortunately, I did not think of
this. But I came up with one crazy case (maybe he is not alone) in which your
decision needs to be fixed.
As I understand it, do you take a ticket to yourself?
{code:java}
Assert.AreEqual("PlatformComputeBinarizable2", prx.TestBinarizableArray(new[]
{10, 11, 12}.Select(x => new PlatformComputeBinarizable2 {Field =
x}).ToArray()));
public string TestBinarizableArray(object[] x)
{
if (x.GetType() == typeof(PlatformComputeBinarizable[]))
return "PlatformComputeBinarizable";
if (x.GetType() == typeof(PlatformComputeBinarizable2[]))
return "PlatformComputeBinarizable2";
return "object";
}
...
Expected string length 27 but was 6. Strings differ at index 0.
Expected: "PlatformComputeBinarizable2"
But was: "object"
{code}
was (Author: zzzadruga):
[~ptupitsyn], Yes, your decision is better. Unfortunately, I did not think of
this. But I came up with one crazy case (maybe he is not alone) in which your
decision needs to be finalized.
As I understand it, do you take a ticket to yourself?
{code:java}
Assert.AreEqual("PlatformComputeBinarizable2", prx.TestBinarizableArray(new[]
{10, 11, 12}.Select(x => new PlatformComputeBinarizable2 {Field =
x}).ToArray()));
public string TestBinarizableArray(object[] x)
{
if (x.GetType() == typeof(PlatformComputeBinarizable[]))
return "PlatformComputeBinarizable";
if (x.GetType() == typeof(PlatformComputeBinarizable2[]))
return "PlatformComputeBinarizable2";
return "object";
}
...
Expected string length 27 but was 6. Strings differ at index 0.
Expected: "PlatformComputeBinarizable2"
But was: "object"
{code}
> .NET: Service method with user type array parameter can't be found
> --
>
> Key: IGNITE-12823
> URL: https://issues.apache.org/jira/browse/IGNITE-12823
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Reporter: Alexey Kukushkin
>Assignee: Nikolai Kulagin
>Priority: Major
> Labels: .NET, sbcf
> Attachments: ignite-12823-vs-2.8.patch
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> *+Setup+*
> * Ignite Java service with a method having an array of user types as a
> parameters, for example, caclulate(Parameter[] params)
> *+Actions+*
> * .NET client calls the Ignite Java service, for example,
> ignite.GetServices().GetServiceProxy().calculate(new[] \{new
> Parameter()});
> *+Expected+*
> * The service method is called
> *+Actual+*
> * Exception "Could not find proxy method 'calculate' in class ICalculator"
> *+Workaround+*
> * Replace array of user types with array of objects in the service methods
> signatures, for example, caclulate(Object[] params)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12823) .NET: Service method with user type array parameter can't be found
[
https://issues.apache.org/jira/browse/IGNITE-12823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17116157#comment-17116157
]
Nikolai Kulagin commented on IGNITE-12823:
--
[~ptupitsyn], Yes, your decision is better. Unfortunately, I did not think of
this. But I came up with one crazy case (maybe he is not alone) in which your
decision needs to be finalized.
As I understand it, do you take a ticket to yourself?
{code:java}
Assert.AreEqual("PlatformComputeBinarizable2", prx.TestBinarizableArray(new[]
{10, 11, 12}.Select(x => new PlatformComputeBinarizable2 {Field =
x}).ToArray()));
public string TestBinarizableArray(object[] x)
{
if (x.GetType() == typeof(PlatformComputeBinarizable[]))
return "PlatformComputeBinarizable";
if (x.GetType() == typeof(PlatformComputeBinarizable2[]))
return "PlatformComputeBinarizable2";
return "object";
}
...
Expected string length 27 but was 6. Strings differ at index 0.
Expected: "PlatformComputeBinarizable2"
But was: "object"
{code}
> .NET: Service method with user type array parameter can't be found
> --
>
> Key: IGNITE-12823
> URL: https://issues.apache.org/jira/browse/IGNITE-12823
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Reporter: Alexey Kukushkin
>Assignee: Nikolai Kulagin
>Priority: Major
> Labels: .NET, sbcf
> Attachments: ignite-12823-vs-2.8.patch
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> *+Setup+*
> * Ignite Java service with a method having an array of user types as a
> parameters, for example, caclulate(Parameter[] params)
> *+Actions+*
> * .NET client calls the Ignite Java service, for example,
> ignite.GetServices().GetServiceProxy().calculate(new[] \{new
> Parameter()});
> *+Expected+*
> * The service method is called
> *+Actual+*
> * Exception "Could not find proxy method 'calculate' in class ICalculator"
> *+Workaround+*
> * Replace array of user types with array of objects in the service methods
> signatures, for example, caclulate(Object[] params)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12823) .NET: Service method with user type array parameter can't be found
[
https://issues.apache.org/jira/browse/IGNITE-12823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17116044#comment-17116044
]
Nikolai Kulagin commented on IGNITE-12823:
--
[~ptupitsyn], yes, but we have a problem when we start .NET services from .NET
on the remote node with method parameters that have an array of user types.
Local node send an array to remote node, and we cannot deserialize it, because
it don't have this class on Java. But if it only unmarshal the array in
Object[], we lose .NET user type.
Run your POC on this test [1].
[1]
https://github.com/apache/ignite/pull/7788/commits/c654e66caf130bdf9df3a99979b363ba6b80ff37#diff-c0ec0308d69151e8b10db00c15158d29R420
> .NET: Service method with user type array parameter can't be found
> --
>
> Key: IGNITE-12823
> URL: https://issues.apache.org/jira/browse/IGNITE-12823
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Reporter: Alexey Kukushkin
>Assignee: Nikolai Kulagin
>Priority: Major
> Labels: .NET, sbcf
> Attachments: ignite-12823-vs-2.8.patch
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> *+Setup+*
> * Ignite Java service with a method having an array of user types as a
> parameters, for example, caclulate(Parameter[] params)
> *+Actions+*
> * .NET client calls the Ignite Java service, for example,
> ignite.GetServices().GetServiceProxy().calculate(new[] \{new
> Parameter()});
> *+Expected+*
> * The service method is called
> *+Actual+*
> * Exception "Could not find proxy method 'calculate' in class ICalculator"
> *+Workaround+*
> * Replace array of user types with array of objects in the service methods
> signatures, for example, caclulate(Object[] params)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-10075) .NET: Avoid binary configurations of Ignite Java service params and result when calling it from Ignite.NET
[
https://issues.apache.org/jira/browse/IGNITE-10075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolai Kulagin reassigned IGNITE-10075:
Assignee: Nikolai Kulagin (was: Pavel Tupitsyn)
> .NET: Avoid binary configurations of Ignite Java service params and result
> when calling it from Ignite.NET
> --
>
> Key: IGNITE-10075
> URL: https://issues.apache.org/jira/browse/IGNITE-10075
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Affects Versions: 2.6
>Reporter: Alexey Kukushkin
>Assignee: Nikolai Kulagin
>Priority: Major
> Labels: .NET, sbcf
> Attachments: MyTest.cs, ignite-10075-vs-2.8.patch
>
>
> Presently if there is an Ignite Java service taking parameters of complex
> (composite) types and returning a result of complex type then all the complex
> types must be explicitly specified in the binary configuration.
> We need to enhance Ignite not to require binary configuration assuming that
> we use the same type, package/namespace and field/property names on both the
> .NET and Java sides (or provide a custom name mapper for relaxed naming
> conventions).
> h2. Reproducer
> h3. ICalculator.java
> {code:java}
> package Sandbox.Net;
> public interface ICalculator {
> Result Calculate(Parameter p);
> }
> {code}
> h3. Parameter.java
> {code:java}
> package Sandbox.Net;
> public class Parameter {
> private int id;
> private double val;
> public int getId() {
> return id;
> }
> public Parameter setId(int id) {
> this.id = id;
> return this;
> }
> public double getValue() {
> return val;
> }
> public Parameter setValue(double val) {
> this.val = val;
> return this;
> }
> }
> {code}
> h3. Result .java
> {code:java}
> package Sandbox.Net;
> public class Result {
> private int id;
> private double value;
> public int getId() {
> return id;
> }
> public Result setId(int id) {
> this.id = id;
> return this;
> }
> public double getValue() {
> return value;
> }
> public Result setValue(double val) {
> this.value = val;
> return this;
> }
> }
> {code}
> h3. IgniteCalculatorService.java
> {code:java}
> package Sandbox.Net;
> import org.apache.ignite.services.Service;
> import org.apache.ignite.services.ServiceContext;
> public class IgniteCalculatorService implements Service, ICalculator {
> @Override public Result Calculate(Parameter p) {
> return new Result().setId(p.getId()).setValue(p.getValue() *
> p.getValue());
> }
> @Override public void cancel(ServiceContext ctx) {
> }
> @Override public void init(ServiceContext ctx) {
> }
> @Override public void execute(ServiceContext ctx) {
> }
> }
> {code}
> h3. build.gradle
> {code:groovy}
> plugins {
> id 'java'
> }
> group 'sandbox.net'
> version '1.0-SNAPSHOT'
> sourceCompatibility = 1.8
> repositories {
> mavenLocal()
> mavenCentral()
> }
> def igniteVer='2.8.0'
> dependencies {
> compile group: 'org.apache.ignite', name: 'ignite-core', version:
> igniteVer
> testCompile group: 'junit', name: 'junit', version: '4.12'
> }
> {code}
> h3. ignite-config.xml
> {code:xml}
>
> http://www.springframework.org/schema/beans;
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>xsi:schemaLocation="
> http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans.xsd;>
> class="org.apache.ignite.configuration.IgniteConfiguration">
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">
>
>
> 127.0.0.1:47500
>
>
>
>
>
>
>
>
> {code}
> h3. ICalculator.cs
> {code:c#}
> namespace Sandbox.Net
> {
> public interface ICalculator
> {
> Result Calculate(Parameter p);
> }
> }
> {code}
> h3. Parameter.cs
> {code:c#}
> namespace Sandbox.Net
> {
> public class Parameter
> {
> public int Id { get; set; }
> public double Value { get; set; }
> }
> }
> {code}
> h3. Result.cs
> {code:c#}
> namespace Sandbox.Net
> {
> public class Result
> {
> public int Id { get; set; }
>
[jira] [Commented] (IGNITE-10075) .NET: Avoid binary configurations of Ignite Java service params and result when calling it from Ignite.NET
[
https://issues.apache.org/jira/browse/IGNITE-10075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17113973#comment-17113973
]
Nikolai Kulagin commented on IGNITE-10075:
--
[~ptupitsyn], are you working on this ticket? If not, can I assign it to myself?
> .NET: Avoid binary configurations of Ignite Java service params and result
> when calling it from Ignite.NET
> --
>
> Key: IGNITE-10075
> URL: https://issues.apache.org/jira/browse/IGNITE-10075
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Affects Versions: 2.6
>Reporter: Alexey Kukushkin
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: .NET, sbcf
> Attachments: MyTest.cs, ignite-10075-vs-2.8.patch
>
>
> Presently if there is an Ignite Java service taking parameters of complex
> (composite) types and returning a result of complex type then all the complex
> types must be explicitly specified in the binary configuration.
> We need to enhance Ignite not to require binary configuration assuming that
> we use the same type, package/namespace and field/property names on both the
> .NET and Java sides (or provide a custom name mapper for relaxed naming
> conventions).
> h2. Reproducer
> h3. ICalculator.java
> {code:java}
> package Sandbox.Net;
> public interface ICalculator {
> Result Calculate(Parameter p);
> }
> {code}
> h3. Parameter.java
> {code:java}
> package Sandbox.Net;
> public class Parameter {
> private int id;
> private double val;
> public int getId() {
> return id;
> }
> public Parameter setId(int id) {
> this.id = id;
> return this;
> }
> public double getValue() {
> return val;
> }
> public Parameter setValue(double val) {
> this.val = val;
> return this;
> }
> }
> {code}
> h3. Result .java
> {code:java}
> package Sandbox.Net;
> public class Result {
> private int id;
> private double value;
> public int getId() {
> return id;
> }
> public Result setId(int id) {
> this.id = id;
> return this;
> }
> public double getValue() {
> return value;
> }
> public Result setValue(double val) {
> this.value = val;
> return this;
> }
> }
> {code}
> h3. IgniteCalculatorService.java
> {code:java}
> package Sandbox.Net;
> import org.apache.ignite.services.Service;
> import org.apache.ignite.services.ServiceContext;
> public class IgniteCalculatorService implements Service, ICalculator {
> @Override public Result Calculate(Parameter p) {
> return new Result().setId(p.getId()).setValue(p.getValue() *
> p.getValue());
> }
> @Override public void cancel(ServiceContext ctx) {
> }
> @Override public void init(ServiceContext ctx) {
> }
> @Override public void execute(ServiceContext ctx) {
> }
> }
> {code}
> h3. build.gradle
> {code:groovy}
> plugins {
> id 'java'
> }
> group 'sandbox.net'
> version '1.0-SNAPSHOT'
> sourceCompatibility = 1.8
> repositories {
> mavenLocal()
> mavenCentral()
> }
> def igniteVer='2.8.0'
> dependencies {
> compile group: 'org.apache.ignite', name: 'ignite-core', version:
> igniteVer
> testCompile group: 'junit', name: 'junit', version: '4.12'
> }
> {code}
> h3. ignite-config.xml
> {code:xml}
>
> http://www.springframework.org/schema/beans;
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>xsi:schemaLocation="
> http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans.xsd;>
> class="org.apache.ignite.configuration.IgniteConfiguration">
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">
>
>
> 127.0.0.1:47500
>
>
>
>
>
>
>
>
> {code}
> h3. ICalculator.cs
> {code:c#}
> namespace Sandbox.Net
> {
> public interface ICalculator
> {
> Result Calculate(Parameter p);
> }
> }
> {code}
> h3. Parameter.cs
> {code:c#}
> namespace Sandbox.Net
> {
> public class Parameter
> {
> public int Id { get; set; }
> public double Value { get; set; }
> }
> }
> {code}
> h3. Result.cs
> {code:c#}
> namespace Sandbox.Net
> {
> public
[jira] [Commented] (IGNITE-12823) .NET: Service method with user type array parameter can't be found
[
https://issues.apache.org/jira/browse/IGNITE-12823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17113872#comment-17113872
]
Nikolai Kulagin commented on IGNITE-12823:
--
[~ptupitsyn], please, review my change.
> .NET: Service method with user type array parameter can't be found
> --
>
> Key: IGNITE-12823
> URL: https://issues.apache.org/jira/browse/IGNITE-12823
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Reporter: Alexey Kukushkin
>Assignee: Nikolai Kulagin
>Priority: Major
> Labels: .NET, sbcf
> Attachments: ignite-12823-vs-2.8.patch
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> *+Setup+*
> * Ignite Java service with a method having an array of user types as a
> parameters, for example, caclulate(Parameter[] params)
> *+Actions+*
> * .NET client calls the Ignite Java service, for example,
> ignite.GetServices().GetServiceProxy().calculate(new[] \{new
> Parameter()});
> *+Expected+*
> * The service method is called
> *+Actual+*
> * Exception "Could not find proxy method 'calculate' in class ICalculator"
> *+Workaround+*
> * Replace array of user types with array of objects in the service methods
> signatures, for example, caclulate(Object[] params)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12823) .NET: Service method with user type array parameter can't be found
[
https://issues.apache.org/jira/browse/IGNITE-12823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17113256#comment-17113256
]
Nikolai Kulagin commented on IGNITE-12823:
--
PR: https://github.com/apache/ignite/pull/7788
> .NET: Service method with user type array parameter can't be found
> --
>
> Key: IGNITE-12823
> URL: https://issues.apache.org/jira/browse/IGNITE-12823
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Reporter: Alexey Kukushkin
>Assignee: Nikolai Kulagin
>Priority: Major
> Labels: .NET, sbcf
> Attachments: ignite-12823-vs-2.8.patch
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> *+Setup+*
> * Ignite Java service with a method having an array of user types as a
> parameters, for example, caclulate(Parameter[] params)
> *+Actions+*
> * .NET client calls the Ignite Java service, for example,
> ignite.GetServices().GetServiceProxy().calculate(new[] \{new
> Parameter()});
> *+Expected+*
> * The service method is called
> *+Actual+*
> * Exception "Could not find proxy method 'calculate' in class ICalculator"
> *+Workaround+*
> * Replace array of user types with array of objects in the service methods
> signatures, for example, caclulate(Object[] params)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12252) Unchecked exceptions during rebalancing should be handled
[
https://issues.apache.org/jira/browse/IGNITE-12252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17095566#comment-17095566
]
Nikolai Kulagin commented on IGNITE-12252:
--
[~avinogradov], thanks for the review. I created [new
PR|https://github.com/apache/ignite/pull/7761] for Ignite 2.8.1.
> Unchecked exceptions during rebalancing should be handled
> -
>
> Key: IGNITE-12252
> URL: https://issues.apache.org/jira/browse/IGNITE-12252
> Project: Ignite
> Issue Type: Bug
>Reporter: Aleksey Plekhanov
>Assignee: Nikolai Kulagin
>Priority: Critical
> Fix For: 2.9, 2.8.1
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Rebalancing should handle unchecked exceptions by failure handler. In current
> implementation unchecked exceptions just ignored. They were handled by IO
> worker before IGNITE-3195.
> Reproducer:
> {code:java}
> @Test
> public void testRebalanceUncheckedError() throws Exception {
> IgniteEx ignite0 = startGrid(new
> IgniteConfiguration().setIgniteInstanceName("ignite0"));
> IgniteCache cache =
> ignite0.getOrCreateCache(DEFAULT_CACHE_NAME);
> IgniteDataStreamer streamer =
> ignite0.dataStreamer(DEFAULT_CACHE_NAME);
> for (int i = 0; i < 100_000; i++)
> streamer.addData(i, i);
> streamer.flush();
> IgniteEx ignite1 = startGrid(new
> IgniteConfiguration().setIgniteInstanceName("ignite1")
>
> .setIncludeEventTypes(EventType.EVT_CACHE_REBALANCE_OBJECT_LOADED));
> ignite1.events().localListen(e -> {
> throw new Error();
> }, EventType.EVT_CACHE_REBALANCE_OBJECT_LOADED);
> awaitPartitionMapExchange();
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12927) The CacheGroupsMetricsRebalanceTest.testRebalancingLastCancelledTime is flacky
[
https://issues.apache.org/jira/browse/IGNITE-12927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17089477#comment-17089477
]
Nikolai Kulagin commented on IGNITE-12927:
--
LGTM
> The CacheGroupsMetricsRebalanceTest.testRebalancingLastCancelledTime is flacky
> --
>
> Key: IGNITE-12927
> URL: https://issues.apache.org/jira/browse/IGNITE-12927
> Project: Ignite
> Issue Type: Bug
>Reporter: Amelchev Nikita
>Assignee: Amelchev Nikita
>Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The {{CacheGroupsMetricsRebalanceTest.testRebalancingLastCancelledTime}} is
> flacky.
> [TC
> history.|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-448222889376376497=%3Cdefault%3E=testDetails]
> {noformat}
> java.lang.IllegalStateException: Duplicate key 1472820775 (attempted merging
> values 1472820775 and 1472820775)
> at
> java.base/java.util.stream.Collectors.duplicateKeyException(Collectors.java:133)
> at
> java.base/java.util.stream.Collectors.lambda$uniqKeysMapAccumulator$1(Collectors.java:180)
> at
> java.base/java.util.stream.ReduceOps$3ReducingSink.accept(ReduceOps.java:169)
> at
> java.base/java.util.stream.IntPipeline$1$1.accept(IntPipeline.java:180)
> at
> java.base/java.util.Random$RandomIntsSpliterator.forEachRemaining(Random.java:1044)
> at
> java.base/java.util.Spliterator$OfInt.forEachRemaining(Spliterator.java:699)
> at
> java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484)
> at
> java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474)
> at
> java.base/java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:913)
> at
> java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
> at
> java.base/java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:578)
> at
> org.apache.ignite.internal.processors.cache.CacheGroupsMetricsRebalanceTest.testRebalancingLastCancelledTime(CacheGroupsMetricsRebalanceTest.java:315)
> {noformat}
> The reason is that randomly generated keys can be duplicated and cant be
> collected from stream .
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-12823) .NET: Service method with user type array parameter can't be found
[
https://issues.apache.org/jira/browse/IGNITE-12823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolai Kulagin reassigned IGNITE-12823:
Assignee: Nikolai Kulagin (was: Pavel Tupitsyn)
> .NET: Service method with user type array parameter can't be found
> --
>
> Key: IGNITE-12823
> URL: https://issues.apache.org/jira/browse/IGNITE-12823
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Reporter: Alexey Kukushkin
>Assignee: Nikolai Kulagin
>Priority: Major
> Labels: .NET, sbcf
> Attachments: ignite-12823-vs-2.8.patch
>
>
> *+Setup+*
> * Ignite Java service with a method having an array of user types as a
> parameters, for example, caclulate(Parameter[] params)
> *+Actions+*
> * .NET client calls the Ignite Java service, for example,
> ignite.GetServices().GetServiceProxy().calculate(new[] \{new
> Parameter()});
> *+Expected+*
> * The service method is called
> *+Actual+*
> * Exception "Could not find proxy method 'calculate' in class ICalculator"
> *+Workaround+*
> * Replace array of user types with array of objects in the service methods
> signatures, for example, caclulate(Object[] params)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-10075) .NET: Avoid binary configurations of Ignite Java service params and result when calling it from Ignite.NET
[ https://issues.apache.org/jira/browse/IGNITE-10075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17084934#comment-17084934 ] Nikolai Kulagin commented on IGNITE-10075: -- [~kukushal], I checked this version. I created Java service with complex type and created complex type on .NET with an equal namespace. And this solution worked without a patch. If java package and .NET namespace were different, I got the error. > .NET: Avoid binary configurations of Ignite Java service params and result > when calling it from Ignite.NET > -- > > Key: IGNITE-10075 > URL: https://issues.apache.org/jira/browse/IGNITE-10075 > Project: Ignite > Issue Type: Improvement > Components: platforms >Affects Versions: 2.6 >Reporter: Alexey Kukushkin >Assignee: Pavel Tupitsyn >Priority: Major > Labels: .NET, sbcf > Attachments: MyTest.cs, ignite-10075-vs-2.8.patch > > > Presently if there is an Ignite Java service taking parameters of complex > (composite) types and returning a result of complex type then all the complex > types must be explicitly specified in the binary configuration. > We need to enhance Ignite not to require binary configuration assuming that > we use the same type, package/namespace and field/property names on both the > .NET and Java sides (or provide a custom name mapper for relaxed naming > conventions). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-10075) .NET: Avoid binary configurations of Ignite Java service params and result when calling it from Ignite.NET
[ https://issues.apache.org/jira/browse/IGNITE-10075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17073645#comment-17073645 ] Nikolai Kulagin commented on IGNITE-10075: -- [~kukushal], [~ptupitsyn], I tried to write a producer but did not see a problem [^MyTest.cs] > .NET: Avoid binary configurations of Ignite Java service params and result > when calling it from Ignite.NET > -- > > Key: IGNITE-10075 > URL: https://issues.apache.org/jira/browse/IGNITE-10075 > Project: Ignite > Issue Type: Improvement > Components: platforms >Affects Versions: 2.6 >Reporter: Alexey Kukushkin >Assignee: Pavel Tupitsyn >Priority: Major > Labels: .NET, sbcf > Attachments: MyTest.cs, ignite-10075-vs-2.8.patch > > > Presently if there is an Ignite Java service taking parameters of complex > (composite) types and returning a result of complex type then all the complex > types must be explicitly specified in the binary configuration. > We need to enhance Ignite not to require binary configuration assuming that > we use the same type, package/namespace and field/property names on both the > .NET and Java sides (or provide a custom name mapper for relaxed naming > conventions). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-10075) .NET: Avoid binary configurations of Ignite Java service params and result when calling it from Ignite.NET
[ https://issues.apache.org/jira/browse/IGNITE-10075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolai Kulagin updated IGNITE-10075: - Attachment: MyTest.cs > .NET: Avoid binary configurations of Ignite Java service params and result > when calling it from Ignite.NET > -- > > Key: IGNITE-10075 > URL: https://issues.apache.org/jira/browse/IGNITE-10075 > Project: Ignite > Issue Type: Improvement > Components: platforms >Affects Versions: 2.6 >Reporter: Alexey Kukushkin >Assignee: Pavel Tupitsyn >Priority: Major > Labels: .NET, sbcf > Attachments: MyTest.cs, ignite-10075-vs-2.8.patch > > > Presently if there is an Ignite Java service taking parameters of complex > (composite) types and returning a result of complex type then all the complex > types must be explicitly specified in the binary configuration. > We need to enhance Ignite not to require binary configuration assuming that > we use the same type, package/namespace and field/property names on both the > .NET and Java sides (or provide a custom name mapper for relaxed naming > conventions). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-10075) .NET: Avoid binary configurations of Ignite Java service params and result when calling it from Ignite.NET
[ https://issues.apache.org/jira/browse/IGNITE-10075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolai Kulagin updated IGNITE-10075: - Attachment: (was: MyTest.cs) > .NET: Avoid binary configurations of Ignite Java service params and result > when calling it from Ignite.NET > -- > > Key: IGNITE-10075 > URL: https://issues.apache.org/jira/browse/IGNITE-10075 > Project: Ignite > Issue Type: Improvement > Components: platforms >Affects Versions: 2.6 >Reporter: Alexey Kukushkin >Assignee: Pavel Tupitsyn >Priority: Major > Labels: .NET, sbcf > Attachments: MyTest.cs, ignite-10075-vs-2.8.patch > > > Presently if there is an Ignite Java service taking parameters of complex > (composite) types and returning a result of complex type then all the complex > types must be explicitly specified in the binary configuration. > We need to enhance Ignite not to require binary configuration assuming that > we use the same type, package/namespace and field/property names on both the > .NET and Java sides (or provide a custom name mapper for relaxed naming > conventions). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-10075) .NET: Avoid binary configurations of Ignite Java service params and result when calling it from Ignite.NET
[ https://issues.apache.org/jira/browse/IGNITE-10075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolai Kulagin updated IGNITE-10075: - Attachment: MyTest.cs > .NET: Avoid binary configurations of Ignite Java service params and result > when calling it from Ignite.NET > -- > > Key: IGNITE-10075 > URL: https://issues.apache.org/jira/browse/IGNITE-10075 > Project: Ignite > Issue Type: Improvement > Components: platforms >Affects Versions: 2.6 >Reporter: Alexey Kukushkin >Assignee: Pavel Tupitsyn >Priority: Major > Labels: .NET, sbcf > Attachments: MyTest.cs, ignite-10075-vs-2.8.patch > > > Presently if there is an Ignite Java service taking parameters of complex > (composite) types and returning a result of complex type then all the complex > types must be explicitly specified in the binary configuration. > We need to enhance Ignite not to require binary configuration assuming that > we use the same type, package/namespace and field/property names on both the > .NET and Java sides (or provide a custom name mapper for relaxed naming > conventions). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12826) Poor JDBC Cache Store performance due to default fetch size
[ https://issues.apache.org/jira/browse/IGNITE-12826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17068338#comment-17068338 ] Nikolai Kulagin commented on IGNITE-12826: -- [~nizhikov], Looks good to me > Poor JDBC Cache Store performance due to default fetch size > --- > > Key: IGNITE-12826 > URL: https://issues.apache.org/jira/browse/IGNITE-12826 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.8 >Reporter: Alexey Kukushkin >Assignee: Nikolay Izhikov >Priority: Major > Labels: sbcf > Fix For: 2.9 > > Attachments: ignite-12826-vs-2.8.patch > > Time Spent: 10m > Remaining Estimate: 0h > > JDBC "fetchSize" parameter specifies the number of rows to be fetched from > the database when additional rows are needed. For most drivers it is 10 by > default. Larger fetchSize can significantly improve performance due to less > network roundtrips (at expense of greater memory consumption). > For some reason out-of-box JDBC POJO Cache Store uses default fetchSize in > the loadCache method implementation. > We have very poor loadCache performance when loading large amount of data > from Oracle with the default fetchSize of 10. We tried setting fetchSize to > 20K and that improved performance 40 times. > We need to use JdbcDialect#fetchSize in the loadCache implementation so that > users could implement a custom JdbcDialect to configure fetchSIze. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-12757) ignitevisorcmd does not connect to the cluster
[ https://issues.apache.org/jira/browse/IGNITE-12757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolai Kulagin reassigned IGNITE-12757: Assignee: Nikolai Kulagin > ignitevisorcmd does not connect to the cluster > -- > > Key: IGNITE-12757 > URL: https://issues.apache.org/jira/browse/IGNITE-12757 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.8 >Reporter: Nikolai Kulagin >Assignee: Nikolai Kulagin >Priority: Blocker > Fix For: 2.8.1 > > > ignitevisorcmd does not connect to the cluster (on default configs). The log > does not contain any errors. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12757) ignitevisorcmd does not connect to the cluster
[ https://issues.apache.org/jira/browse/IGNITE-12757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolai Kulagin updated IGNITE-12757: - Description: ignitevisorcmd does not connect to the cluster (on default configs). The log does not contain any errors. (was: ignitevisorcmd does not connect to the cluster. The log does not contain any errors.) > ignitevisorcmd does not connect to the cluster > -- > > Key: IGNITE-12757 > URL: https://issues.apache.org/jira/browse/IGNITE-12757 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.8 >Reporter: Nikolai Kulagin >Priority: Major > > ignitevisorcmd does not connect to the cluster (on default configs). The log > does not contain any errors. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12757) ignitevisorcmd does not connect to the cluster
Nikolai Kulagin created IGNITE-12757: Summary: ignitevisorcmd does not connect to the cluster Key: IGNITE-12757 URL: https://issues.apache.org/jira/browse/IGNITE-12757 Project: Ignite Issue Type: Bug Affects Versions: 2.8 Reporter: Nikolai Kulagin ignitevisorcmd does not connect to the cluster. The log does not contain any errors. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12737) Incorrect annotation on TxDeadlockCauseTest
Nikolai Kulagin created IGNITE-12737:
Summary: Incorrect annotation on TxDeadlockCauseTest
Key: IGNITE-12737
URL: https://issues.apache.org/jira/browse/IGNITE-12737
Project: Ignite
Issue Type: Bug
Reporter: Nikolai Kulagin
Method TxDeadlockCauseTest#testCauseObject() have annotation
{color:#ffab00}@Test{color}, but it is not a test case. As a result, JUnit can
run no one test in this class and printed error.
{code:java}
java.lang.Exception: Method testCauseObject should have no parameters.{code}
Most likely TxDeadlockCauseTest.class was commented on in the suite
TxDeadlockDetectionTestSuite because of this.
I suggest:
1. Delete the annotation {color:#ffab00}@Test{color};
2. Fix the tests in TxDeadlockCauseTest (3 tests look good, 1 test fails);
3. Uncomment the TxDeadlockCauseTest in the suite.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-11591) Add info about lock candidates that are ahead in queue to transaction timeout error message
[
https://issues.apache.org/jira/browse/IGNITE-11591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolai Kulagin reassigned IGNITE-11591:
Assignee: Nikolai Kulagin
> Add info about lock candidates that are ahead in queue to transaction timeout
> error message
> ---
>
> Key: IGNITE-11591
> URL: https://issues.apache.org/jira/browse/IGNITE-11591
> Project: Ignite
> Issue Type: Improvement
>Reporter: Ivan Rakov
>Assignee: Nikolai Kulagin
>Priority: Major
> Fix For: 2.9
>
>
> If transaction is timed out due to lock acquisition failure, corresponding
> error will show up in server log on DHT (primary) node:
> {code:java}
> [2019-03-20
> 21:13:10,831][ERROR][grid-timeout-worker-#23%transactions.TxRollbackOnTimeoutTest0%][GridDhtColocatedCache]
> Failed to acquire lock for request: GridNearLockRequest
> [topVer=AffinityTopologyVersion [topVer=4, minorTopVer=0], miniId=1,
> dhtVers=GridCacheVersion[] [null],
> subjId=651a30e1-45ac-4b35-86d2-028d1f81d8dc, taskNameHash=0, createTtl=-1,
> accessTtl=-1, flags=6, txLbl=null, filter=null,
> super=GridDistributedLockRequest
> [nodeId=651a30e1-45ac-4b35-86d2-028d1f81d8dc, nearXidVer=GridCacheVersion
> [topVer=164585585, order=1553105588524, nodeOrder=4], threadId=262,
> futId=5967e4c9961-d32ea2a6-1789-47d7-bdbf-aa66e6d8c35b, timeout=890,
> isInTx=true, isInvalidate=false, isRead=false, isolation=REPEATABLE_READ,
> retVals=[false], txSize=2, flags=0, keysCnt=1,
> super=GridDistributedBaseMessage [ver=GridCacheVersion [topVer=164585585,
> order=1553105588524, nodeOrder=4], committedVers=null, rolledbackVers=null,
> cnt=0, super=GridCacheIdMessage [cacheId=3556498
> class
> org.apache.ignite.internal.transactions.IgniteTxTimeoutCheckedException:
> Failed to acquire lock within provided timeout for transaction [timeout=890,
> tx=GridDhtTxLocal[xid=f219e4c9961--09cf-6071--0001,
> xidVersion=GridCacheVersion [topVer=164585585, order=1553105588527,
> nodeOrder=1], concurrency=PESSIMISTIC, isolation=REPEATABLE_READ,
> state=MARKED_ROLLBACK, invalidate=false, rollbackOnly=true,
> nodeId=c7dccddb-dee1-4499-94b1-03896350, timeout=890, duration=891]]
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxLocalAdapter$PostLockClosure1.apply(IgniteTxLocalAdapter.java:1766)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxLocalAdapter$PostLockClosure1.apply(IgniteTxLocalAdapter.java:1714)
> at
> org.apache.ignite.internal.util.future.GridEmbeddedFuture$2.applyx(GridEmbeddedFuture.java:86)
> at
> org.apache.ignite.internal.util.future.GridEmbeddedFuture$AsyncListener1.apply(GridEmbeddedFuture.java:292)
> at
> org.apache.ignite.internal.util.future.GridEmbeddedFuture$AsyncListener1.apply(GridEmbeddedFuture.java:285)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:399)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblock(GridFutureAdapter.java:347)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblockAll(GridFutureAdapter.java:335)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:511)
> at
> org.apache.ignite.internal.processors.cache.GridCacheCompoundIdentityFuture.onDone(GridCacheCompoundIdentityFuture.java:56)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:490)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLockFuture.onComplete(GridDhtLockFuture.java:793)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLockFuture.access$900(GridDhtLockFuture.java:89)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLockFuture$LockTimeoutObject.onTimeout(GridDhtLockFuture.java:1189)
> at
> org.apache.ignite.internal.processors.timeout.GridTimeoutProcessor$TimeoutWorker.body(GridTimeoutProcessor.java:234)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at java.lang.Thread.run(Thread.j
> {code}
> It would be much more useful if this message also contained information about
> transaction that actually owns corresponding lock (or information about all
> transactions that are ahead in queue if there are several).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-11591) Add info about lock candidates that are ahead in queue to transaction timeout error message
[
https://issues.apache.org/jira/browse/IGNITE-11591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17039061#comment-17039061
]
Nikolai Kulagin edited comment on IGNITE-11591 at 2/18/20 1:11 PM:
---
[~ivan.glukos], if I understand correctly, then
# Include information about pending locks in the error message;
# Print a dump from IGNITE-11059 no more than "n" times per minute (for
transactions with timeout less than a minute); {color:#505f79}Something similar
to GridLogThrottle?{color}
# Make "n" configurable.
"n" is the messages rate.
was (Author: zzzadruga):
[~ivan.glukos], if I understand correctly, then
# Include information about pending locks in the error message;
# Print a dump from IGNITE-11059 no more than "n" times per minute (for
transactions with timeout less than a minute);
# Make "n" configurable.
"n" is the messages rate.
> Add info about lock candidates that are ahead in queue to transaction timeout
> error message
> ---
>
> Key: IGNITE-11591
> URL: https://issues.apache.org/jira/browse/IGNITE-11591
> Project: Ignite
> Issue Type: Improvement
>Reporter: Ivan Rakov
>Priority: Major
> Fix For: 2.9
>
>
> If transaction is timed out due to lock acquisition failure, corresponding
> error will show up in server log on DHT (primary) node:
> {code:java}
> [2019-03-20
> 21:13:10,831][ERROR][grid-timeout-worker-#23%transactions.TxRollbackOnTimeoutTest0%][GridDhtColocatedCache]
> Failed to acquire lock for request: GridNearLockRequest
> [topVer=AffinityTopologyVersion [topVer=4, minorTopVer=0], miniId=1,
> dhtVers=GridCacheVersion[] [null],
> subjId=651a30e1-45ac-4b35-86d2-028d1f81d8dc, taskNameHash=0, createTtl=-1,
> accessTtl=-1, flags=6, txLbl=null, filter=null,
> super=GridDistributedLockRequest
> [nodeId=651a30e1-45ac-4b35-86d2-028d1f81d8dc, nearXidVer=GridCacheVersion
> [topVer=164585585, order=1553105588524, nodeOrder=4], threadId=262,
> futId=5967e4c9961-d32ea2a6-1789-47d7-bdbf-aa66e6d8c35b, timeout=890,
> isInTx=true, isInvalidate=false, isRead=false, isolation=REPEATABLE_READ,
> retVals=[false], txSize=2, flags=0, keysCnt=1,
> super=GridDistributedBaseMessage [ver=GridCacheVersion [topVer=164585585,
> order=1553105588524, nodeOrder=4], committedVers=null, rolledbackVers=null,
> cnt=0, super=GridCacheIdMessage [cacheId=3556498
> class
> org.apache.ignite.internal.transactions.IgniteTxTimeoutCheckedException:
> Failed to acquire lock within provided timeout for transaction [timeout=890,
> tx=GridDhtTxLocal[xid=f219e4c9961--09cf-6071--0001,
> xidVersion=GridCacheVersion [topVer=164585585, order=1553105588527,
> nodeOrder=1], concurrency=PESSIMISTIC, isolation=REPEATABLE_READ,
> state=MARKED_ROLLBACK, invalidate=false, rollbackOnly=true,
> nodeId=c7dccddb-dee1-4499-94b1-03896350, timeout=890, duration=891]]
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxLocalAdapter$PostLockClosure1.apply(IgniteTxLocalAdapter.java:1766)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxLocalAdapter$PostLockClosure1.apply(IgniteTxLocalAdapter.java:1714)
> at
> org.apache.ignite.internal.util.future.GridEmbeddedFuture$2.applyx(GridEmbeddedFuture.java:86)
> at
> org.apache.ignite.internal.util.future.GridEmbeddedFuture$AsyncListener1.apply(GridEmbeddedFuture.java:292)
> at
> org.apache.ignite.internal.util.future.GridEmbeddedFuture$AsyncListener1.apply(GridEmbeddedFuture.java:285)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:399)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblock(GridFutureAdapter.java:347)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblockAll(GridFutureAdapter.java:335)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:511)
> at
> org.apache.ignite.internal.processors.cache.GridCacheCompoundIdentityFuture.onDone(GridCacheCompoundIdentityFuture.java:56)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:490)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLockFuture.onComplete(GridDhtLockFuture.java:793)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLockFuture.access$900(GridDhtLockFuture.java:89)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLockFuture$LockTimeoutObject.onTimeout(GridDhtLockFuture.java:1189)
> at
> org.apache.ignite.internal.processors.timeout.GridTimeoutProcessor$TimeoutWorker.body(GridTimeoutProcessor.java:234)
> at
>
[jira] [Commented] (IGNITE-11591) Add info about lock candidates that are ahead in queue to transaction timeout error message
[
https://issues.apache.org/jira/browse/IGNITE-11591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17039061#comment-17039061
]
Nikolai Kulagin commented on IGNITE-11591:
--
[~ivan.glukos], if I understand correctly, then
# Include information about pending locks in the error message;
# Print a dump from IGNITE-11059 no more than "n" times per minute (for
transactions with timeout less than a minute);
# Make "n" configurable.
"n" is the messages rate.
> Add info about lock candidates that are ahead in queue to transaction timeout
> error message
> ---
>
> Key: IGNITE-11591
> URL: https://issues.apache.org/jira/browse/IGNITE-11591
> Project: Ignite
> Issue Type: Improvement
>Reporter: Ivan Rakov
>Priority: Major
> Fix For: 2.9
>
>
> If transaction is timed out due to lock acquisition failure, corresponding
> error will show up in server log on DHT (primary) node:
> {code:java}
> [2019-03-20
> 21:13:10,831][ERROR][grid-timeout-worker-#23%transactions.TxRollbackOnTimeoutTest0%][GridDhtColocatedCache]
> Failed to acquire lock for request: GridNearLockRequest
> [topVer=AffinityTopologyVersion [topVer=4, minorTopVer=0], miniId=1,
> dhtVers=GridCacheVersion[] [null],
> subjId=651a30e1-45ac-4b35-86d2-028d1f81d8dc, taskNameHash=0, createTtl=-1,
> accessTtl=-1, flags=6, txLbl=null, filter=null,
> super=GridDistributedLockRequest
> [nodeId=651a30e1-45ac-4b35-86d2-028d1f81d8dc, nearXidVer=GridCacheVersion
> [topVer=164585585, order=1553105588524, nodeOrder=4], threadId=262,
> futId=5967e4c9961-d32ea2a6-1789-47d7-bdbf-aa66e6d8c35b, timeout=890,
> isInTx=true, isInvalidate=false, isRead=false, isolation=REPEATABLE_READ,
> retVals=[false], txSize=2, flags=0, keysCnt=1,
> super=GridDistributedBaseMessage [ver=GridCacheVersion [topVer=164585585,
> order=1553105588524, nodeOrder=4], committedVers=null, rolledbackVers=null,
> cnt=0, super=GridCacheIdMessage [cacheId=3556498
> class
> org.apache.ignite.internal.transactions.IgniteTxTimeoutCheckedException:
> Failed to acquire lock within provided timeout for transaction [timeout=890,
> tx=GridDhtTxLocal[xid=f219e4c9961--09cf-6071--0001,
> xidVersion=GridCacheVersion [topVer=164585585, order=1553105588527,
> nodeOrder=1], concurrency=PESSIMISTIC, isolation=REPEATABLE_READ,
> state=MARKED_ROLLBACK, invalidate=false, rollbackOnly=true,
> nodeId=c7dccddb-dee1-4499-94b1-03896350, timeout=890, duration=891]]
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxLocalAdapter$PostLockClosure1.apply(IgniteTxLocalAdapter.java:1766)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxLocalAdapter$PostLockClosure1.apply(IgniteTxLocalAdapter.java:1714)
> at
> org.apache.ignite.internal.util.future.GridEmbeddedFuture$2.applyx(GridEmbeddedFuture.java:86)
> at
> org.apache.ignite.internal.util.future.GridEmbeddedFuture$AsyncListener1.apply(GridEmbeddedFuture.java:292)
> at
> org.apache.ignite.internal.util.future.GridEmbeddedFuture$AsyncListener1.apply(GridEmbeddedFuture.java:285)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:399)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblock(GridFutureAdapter.java:347)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblockAll(GridFutureAdapter.java:335)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:511)
> at
> org.apache.ignite.internal.processors.cache.GridCacheCompoundIdentityFuture.onDone(GridCacheCompoundIdentityFuture.java:56)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:490)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLockFuture.onComplete(GridDhtLockFuture.java:793)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLockFuture.access$900(GridDhtLockFuture.java:89)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLockFuture$LockTimeoutObject.onTimeout(GridDhtLockFuture.java:1189)
> at
> org.apache.ignite.internal.processors.timeout.GridTimeoutProcessor$TimeoutWorker.body(GridTimeoutProcessor.java:234)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at java.lang.Thread.run(Thread.j
> {code}
> It would be much more useful if this message also contained information about
> transaction that actually owns corresponding lock (or information about all
> transactions that are ahead in queue if there are several).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12693) Incorrect operation of the eviction policy internal counter
Nikolai Kulagin created IGNITE-12693:
Summary: Incorrect operation of the eviction policy internal
counter
Key: IGNITE-12693
URL: https://issues.apache.org/jira/browse/IGNITE-12693
Project: Ignite
Issue Type: Bug
Components: cache
Reporter: Nikolai Kulagin
Attachments: EvictionPoliciesReproducer.java
When an entry is added to the cache, its size is added to the internal policy
counter. When the size of the internal counter exceeds the max, entries begin
to evict until the internal size is less than the maximum.
When deleting, the size of the entry is subtracted from the internal counter,
but since when deleting an element, only its key is most often indicated, only
the key size is subtracted. This way you can get the moment when the cache is
empty, but the size of the internal counter is not.
{code:java}
@Override public void onEntryAccessed(boolean rmv, EvictableEntry
entry) {
if (!rmv) {
...
else {
Object node = entry.removeMeta();
if (node != null) {
removeMeta(node);
memSize.add(-entry.size());
}
}
}
{code}
In the worst case, a situation is possible when an object added to an empty
cache is evicted, although it is much smaller than the maximum size.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12193) [Phase-1] Rebalancing cache group keys metric counters
[ https://issues.apache.org/jira/browse/IGNITE-12193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16998907#comment-16998907 ] Nikolai Kulagin commented on IGNITE-12193: -- [~mmuzaf], please, review my change. I fixed your remarks. > [Phase-1] Rebalancing cache group keys metric counters > -- > > Key: IGNITE-12193 > URL: https://issues.apache.org/jira/browse/IGNITE-12193 > Project: Ignite > Issue Type: Sub-task >Reporter: Maxim Muzafarov >Assignee: Nikolai Kulagin >Priority: Critical > Labels: IEP-35 > Fix For: 2.8 > > Time Spent: 2h > Remaining Estimate: 0h > > Implement metrics counters related to the cache group: > * rebalancingPartitionsLeft long metric > * rebalancingReceivedKeys long metric > * rebalancingReceivedBytes long metric > * rebalancingStartTime long metric > * rebalancingFinishTime long metric -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-12194) [Phase-2] Calculate expected rebalancing cache group keys
[ https://issues.apache.org/jira/browse/IGNITE-12194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolai Kulagin reassigned IGNITE-12194: Assignee: Nikolai Kulagin > [Phase-2] Calculate expected rebalancing cache group keys > - > > Key: IGNITE-12194 > URL: https://issues.apache.org/jira/browse/IGNITE-12194 > Project: Ignite > Issue Type: Sub-task >Reporter: Maxim Muzafarov >Assignee: Nikolai Kulagin >Priority: Critical > Labels: IEP-35 > Fix For: 2.8 > > > We need to implement expected to be rebalanced cache group keys and total > bytes. Currently, 'estimatedKeysCount' cache metric returns '-1' for some of > the cases (see comments IGNITE-11330). > * rebalancingExpectedKeys long metric > * rebalancingExpectedBytes long metric > * rebalancingEvictedPartitionsLeft long metric -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12193) [Phase-1] Rebalancing cache group keys metric counters
[ https://issues.apache.org/jira/browse/IGNITE-12193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16983546#comment-16983546 ] Nikolai Kulagin commented on IGNITE-12193: -- [~NSAmelchev], I think that we can determine the duration by the start and end time. But from the duration we cannot find the start or end time. > [Phase-1] Rebalancing cache group keys metric counters > -- > > Key: IGNITE-12193 > URL: https://issues.apache.org/jira/browse/IGNITE-12193 > Project: Ignite > Issue Type: Sub-task >Reporter: Maxim Muzafarov >Assignee: Nikolai Kulagin >Priority: Major > Labels: IEP-35 > Fix For: 2.8 > > Time Spent: 20m > Remaining Estimate: 0h > > Implement metrics counters related to the cache group: > * rebalancingPartitionsLeft long metric > * rebalancingReceivedKeys long metric > * rebalancingReceivedBytes long metric > * rebalancingStartTime long metric > * rebalancingFinishTime long metric -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-9005) Eviction policy MBeans change failed LifecycleAwareTest on cache name injectoin
[
https://issues.apache.org/jira/browse/IGNITE-9005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolai Kulagin reassigned IGNITE-9005:
---
Assignee: Nikolai Kulagin (was: Stanislav Lukyanov)
> Eviction policy MBeans change failed LifecycleAwareTest on cache name
> injectoin
> ---
>
> Key: IGNITE-9005
> URL: https://issues.apache.org/jira/browse/IGNITE-9005
> Project: Ignite
> Issue Type: Bug
>Reporter: Dmitry Pavlov
>Assignee: Nikolai Kulagin
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.9
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> http://apache-ignite-developers.2346864.n4.nabble.com/MTCGA-new-failures-in-builds-1485687-needs-to-be-handled-td32531.html
> New test failure detected
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=7246907407546697403=%3Cdefault%3E=testDetails
> after merging
> IGNITE-8776 Eviction policy MBeans are never registered if
> evictionPolicyFactory is used
> Revert of commit makes test passing.
> Locally test also failed. Failed with message
> {noformat}
> Unexpected cache name for
> org.apache.ignite.internal.processors.cache.GridCacheLifecycleAwareSelfTest$TestEvictionPolicy@322714f4
> expected: but was:
> {noformat}
> Message of failure seems to be related to TestEvictionPolicy instance from
> test class.
> Seems that returing call to cctx.kernalContext (). resource ().
> injectCacheName (rsrc, cfg.getName ()); should fix issue.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12317) Add EvictionFilter factory support in IgniteConfiguration.
[ https://issues.apache.org/jira/browse/IGNITE-12317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16957916#comment-16957916 ] Nikolai Kulagin commented on IGNITE-12317: -- Waiting for ticket IGNITE-9005 to continue working > Add EvictionFilter factory support in IgniteConfiguration. > -- > > Key: IGNITE-12317 > URL: https://issues.apache.org/jira/browse/IGNITE-12317 > Project: Ignite > Issue Type: Sub-task > Components: cache >Reporter: Nikolai Kulagin >Assignee: Nikolai Kulagin >Priority: Major > Fix For: 2.9 > > Time Spent: 10m > Remaining Estimate: 0h > > Some entities on cache configuration are configured via factories, while > others are set directly, for example, eviction policy and eviction filter. > Need to add new configuration properties for eviction filter factory and > deprecate old ones (do not remove for compatibility). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12317) Add EvictionFilter factory support in IgniteConfiguration.
Nikolai Kulagin created IGNITE-12317: Summary: Add EvictionFilter factory support in IgniteConfiguration. Key: IGNITE-12317 URL: https://issues.apache.org/jira/browse/IGNITE-12317 Project: Ignite Issue Type: Sub-task Components: cache Reporter: Nikolai Kulagin Assignee: Nikolai Kulagin Fix For: 2.9 Some entities on cache configuration are configured via factories, while others are set directly, for example, eviction policy and eviction filter. Need to add new configuration properties for eviction filter factory and deprecate old ones (do not remove for compatibility). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-9005) Eviction policy MBeans change failed LifecycleAwareTest on cache name injectoin
[
https://issues.apache.org/jira/browse/IGNITE-9005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16956367#comment-16956367
]
Nikolai Kulagin commented on IGNITE-9005:
-
[~slukyanov], hello. I copied your fix to my branch and fixed the errors
([PR|https://github.com/apache/ignite/pull/6970]). Can this speed up the task?
Or maybe I can take on the task?
> Eviction policy MBeans change failed LifecycleAwareTest on cache name
> injectoin
> ---
>
> Key: IGNITE-9005
> URL: https://issues.apache.org/jira/browse/IGNITE-9005
> Project: Ignite
> Issue Type: Bug
>Reporter: Dmitry Pavlov
>Assignee: Stanislav Lukyanov
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.9
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> http://apache-ignite-developers.2346864.n4.nabble.com/MTCGA-new-failures-in-builds-1485687-needs-to-be-handled-td32531.html
> New test failure detected
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=7246907407546697403=%3Cdefault%3E=testDetails
> after merging
> IGNITE-8776 Eviction policy MBeans are never registered if
> evictionPolicyFactory is used
> Revert of commit makes test passing.
> Locally test also failed. Failed with message
> {noformat}
> Unexpected cache name for
> org.apache.ignite.internal.processors.cache.GridCacheLifecycleAwareSelfTest$TestEvictionPolicy@322714f4
> expected: but was:
> {noformat}
> Message of failure seems to be related to TestEvictionPolicy instance from
> test class.
> Seems that returing call to cctx.kernalContext (). resource ().
> injectCacheName (rsrc, cfg.getName ()); should fix issue.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-11087) GridJobCheckpointCleanupSelfTest.testCheckpointCleanup is flaky
[
https://issues.apache.org/jira/browse/IGNITE-11087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16954567#comment-16954567
]
Nikolai Kulagin commented on IGNITE-11087:
--
[~mmuzaf], please, review my change.
> GridJobCheckpointCleanupSelfTest.testCheckpointCleanup is flaky
> ---
>
> Key: IGNITE-11087
> URL: https://issues.apache.org/jira/browse/IGNITE-11087
> Project: Ignite
> Issue Type: Bug
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Minor
> Labels: MakeTeamcityGreenAgain
> Attachments: #removeCheckpoint is called once more.txt,
> #removeCheckpoint isn't called.txt
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The method of remove a checkpoint is sometimes not called or is called once
> more. Test has a very low fail rate, 1 per 366 runs on
> [TeamCity|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-7655052229521669617=testDetails_IgniteTests24Java8=%3Cdefault%3E]
> and 1 per 412 on TC Bot. On local machine approximately 1 failure per 100
> runs. Logs in the attachment.
> Test is flaky for a long time. Before replacing IP Finder in IGNITE-10555,
> test was slower, which made fail rate even less.
>
> {code:java}
> [2019-01-25 14:49:03,050][ERROR][main][root] Test failed.
> junit.framework.AssertionFailedError: expected:<1> but was:<0>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:234)
> at junit.framework.Assert.assertEquals(Assert.java:241)
> at
> org.apache.ignite.internal.GridJobCheckpointCleanupSelfTest.testCheckpointCleanup(GridJobCheckpointCleanupSelfTest.java:88)
> at sun.reflect.GeneratedMethodAccessor22.invoke(Unknown Source)
> 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.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:2088)
> at java.lang.Thread.run(Thread.java:748){code}
>
> [^#removeCheckpoint isn't called.txt]
> ^_^
>
> {code:java}
> [2019-01-25 14:50:03,282][ERROR][main][root] Test failed.
> junit.framework.AssertionFailedError: expected:<-1> but was:<0>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:234)
> at junit.framework.Assert.assertEquals(Assert.java:241)
> at
> org.apache.ignite.internal.GridJobCheckpointCleanupSelfTest.testCheckpointCleanup(GridJobCheckpointCleanupSelfTest.java:88)
> at sun.reflect.GeneratedMethodAccessor22.invoke(Unknown Source)
> 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.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:2088)
> at java.lang.Thread.run(Thread.java:748){code}
> [^#removeCheckpoint is called once more.txt]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-11087) GridJobCheckpointCleanupSelfTest.testCheckpointCleanup is flaky
[
https://issues.apache.org/jira/browse/IGNITE-11087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16954060#comment-16954060
]
Nikolai Kulagin commented on IGNITE-11087:
--
Because the test task is very short, CheckpointRequestListener catches a
message about saving a checkpoint, and the #onSessionEnd method after the task
is finished, work simultaneously. In one moment task node add sessionId in
closedSess map, and the listener finds sessionId in map. Task node removes the
key from keymap for this session and removes checkpoint for this key.
{code:java}
closedSess.add(ses.getId());
// If on task node.
if (ses.getJobId() == null) {
Set keys = keyMap.remove(ses.getId());
if (keys != null) {
for (String key : keys)
getSpi(ses.getCheckpointSpi()).removeCheckpoint(key);
}
}{code}
Listener removes the key from keymap and removes checkpoint too (even if the
key was not in the map).
{code:java}
if (closedSess.contains(sesId)) {
keyMap.remove(sesId, keys);
getSpi(req.getCheckpointSpi()).removeCheckpoint(req.getKey());
}{code}
For bugfix need add listener's check for contains key in keymap before removing
key. And delete the checkpoint only if the key is found.
{code:java}
if (closedSess.contains(sesId)) {
if (keyMap.remove(sesId, keys))
getSpi(req.getCheckpointSpi()).removeCheckpoint(req.getKey());
}
{code}
After fixing a new bug appears.
Between create new keySet and add checkpoint key in the listener,
{code:java}
Set old = keyMap.putIfAbsent(sesId, (CheckpointSet)(keys = new
CheckpointSet(ses)));
if (old != null)
keys = old;
}
<-- here
keys.add(req.getKey());
{code}
task node adds a session in closedSess map, remove empty keySet for session,
but not found no one key (because the listener has not added key yet), and
don't remove checkpoint.
{code:java}
Set keys = keyMap.remove(ses.getId());
if (keys != null) {
for (String key : keys){code}
Listener after added key did not find this key in keyMap, and did not remove
checkpoint.
{code:java}
if (closedSess.contains(sesId)) {
if (keyMap.remove(sesId, keys)){code}
> GridJobCheckpointCleanupSelfTest.testCheckpointCleanup is flaky
> ---
>
> Key: IGNITE-11087
> URL: https://issues.apache.org/jira/browse/IGNITE-11087
> Project: Ignite
> Issue Type: Bug
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Minor
> Labels: MakeTeamcityGreenAgain
> Attachments: #removeCheckpoint is called once more.txt,
> #removeCheckpoint isn't called.txt
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The method of remove a checkpoint is sometimes not called or is called once
> more. Test has a very low fail rate, 1 per 366 runs on
> [TeamCity|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-7655052229521669617=testDetails_IgniteTests24Java8=%3Cdefault%3E]
> and 1 per 412 on TC Bot. On local machine approximately 1 failure per 100
> runs. Logs in the attachment.
> Test is flaky for a long time. Before replacing IP Finder in IGNITE-10555,
> test was slower, which made fail rate even less.
>
> {code:java}
> [2019-01-25 14:49:03,050][ERROR][main][root] Test failed.
> junit.framework.AssertionFailedError: expected:<1> but was:<0>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:234)
> at junit.framework.Assert.assertEquals(Assert.java:241)
> at
> org.apache.ignite.internal.GridJobCheckpointCleanupSelfTest.testCheckpointCleanup(GridJobCheckpointCleanupSelfTest.java:88)
> at sun.reflect.GeneratedMethodAccessor22.invoke(Unknown Source)
> 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.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:2088)
> at java.lang.Thread.run(Thread.java:748){code}
>
> [^#removeCheckpoint isn't called.txt]
> ^_^
>
> {code:java}
> [2019-01-25 14:50:03,282][ERROR][main][root] Test failed.
> junit.framework.AssertionFailedError: expected:<-1> but was:<0>
> at junit.framework.Assert.fail(Assert.java:57)
> at
[jira] [Commented] (IGNITE-12252) Unchecked exceptions during rebalancing should be handled
[
https://issues.apache.org/jira/browse/IGNITE-12252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16951844#comment-16951844
]
Nikolai Kulagin commented on IGNITE-12252:
--
[~avinogradov],
I believe that other thread pools are not critical, it is worth handling
exceptions the only if it is OOM. Rebalance is a critical operation, and all
exceptions must be handled by failure handler.
> Unchecked exceptions during rebalancing should be handled
> -
>
> Key: IGNITE-12252
> URL: https://issues.apache.org/jira/browse/IGNITE-12252
> Project: Ignite
> Issue Type: Bug
>Reporter: Aleksey Plekhanov
>Assignee: Nikolai Kulagin
>Priority: Critical
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Rebalancing should handle unchecked exceptions by failure handler. In current
> implementation unchecked exceptions just ignored. They were handled by IO
> worker before IGNITE-3195.
> Reproducer:
> {code:java}
> @Test
> public void testRebalanceUncheckedError() throws Exception {
> IgniteEx ignite0 = startGrid(new
> IgniteConfiguration().setIgniteInstanceName("ignite0"));
> IgniteCache cache =
> ignite0.getOrCreateCache(DEFAULT_CACHE_NAME);
> IgniteDataStreamer streamer =
> ignite0.dataStreamer(DEFAULT_CACHE_NAME);
> for (int i = 0; i < 100_000; i++)
> streamer.addData(i, i);
> streamer.flush();
> IgniteEx ignite1 = startGrid(new
> IgniteConfiguration().setIgniteInstanceName("ignite1")
>
> .setIncludeEventTypes(EventType.EVT_CACHE_REBALANCE_OBJECT_LOADED));
> ignite1.events().localListen(e -> {
> throw new Error();
> }, EventType.EVT_CACHE_REBALANCE_OBJECT_LOADED);
> awaitPartitionMapExchange();
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12193) [Phase-1] Rebalancing cache group keys metric counters
[ https://issues.apache.org/jira/browse/IGNITE-12193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16950911#comment-16950911 ] Nikolai Kulagin commented on IGNITE-12193: -- [~mmuzaf], please, review my change. > [Phase-1] Rebalancing cache group keys metric counters > -- > > Key: IGNITE-12193 > URL: https://issues.apache.org/jira/browse/IGNITE-12193 > Project: Ignite > Issue Type: Sub-task >Reporter: Maxim Muzafarov >Assignee: Nikolai Kulagin >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > Implement metrics counters related to the cache group: > * rebalancingPartitionsLeft long metric > * rebalancingReceivedKeys long metric > * rebalancingReceivedBytes long metric > * rebalancingStartTime long metric > * rebalancingFinishTime long metric -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12252) Unchecked exceptions during rebalancing should be handled
[
https://issues.apache.org/jira/browse/IGNITE-12252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16950874#comment-16950874
]
Nikolai Kulagin commented on IGNITE-12252:
--
[~avinogradov], please, review my change.
> Unchecked exceptions during rebalancing should be handled
> -
>
> Key: IGNITE-12252
> URL: https://issues.apache.org/jira/browse/IGNITE-12252
> Project: Ignite
> Issue Type: Bug
>Reporter: Aleksey Plekhanov
>Assignee: Nikolai Kulagin
>Priority: Critical
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Rebalancing should handle unchecked exceptions by failure handler. In current
> implementation unchecked exceptions just ignored. They were handled by IO
> worker before IGNITE-3195.
> Reproducer:
> {code:java}
> @Test
> public void testRebalanceUncheckedError() throws Exception {
> IgniteEx ignite0 = startGrid(new
> IgniteConfiguration().setIgniteInstanceName("ignite0"));
> IgniteCache cache =
> ignite0.getOrCreateCache(DEFAULT_CACHE_NAME);
> IgniteDataStreamer streamer =
> ignite0.dataStreamer(DEFAULT_CACHE_NAME);
> for (int i = 0; i < 100_000; i++)
> streamer.addData(i, i);
> streamer.flush();
> IgniteEx ignite1 = startGrid(new
> IgniteConfiguration().setIgniteInstanceName("ignite1")
>
> .setIncludeEventTypes(EventType.EVT_CACHE_REBALANCE_OBJECT_LOADED));
> ignite1.events().localListen(e -> {
> throw new Error();
> }, EventType.EVT_CACHE_REBALANCE_OBJECT_LOADED);
> awaitPartitionMapExchange();
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-9160) FindBugs: NPE and CCE on equals() methods
[
https://issues.apache.org/jira/browse/IGNITE-9160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16949530#comment-16949530
]
Nikolai Kulagin edited comment on IGNITE-9160 at 10/11/19 3:07 PM:
---
[~mmuzaf], I created new pull request
[#6967|https://github.com/apache/ignite/pull/6967], added [^reproduce.txt] with
a test method for reproducing bugs in equals methods, and added [^check.txt]
with a test method for checking fixes.
was (Author: zzzadruga):
[~mmuzaf], I created new pull request
[#6967|[https://github.com/apache/ignite/pull/6967]], added [^reproduce.txt]
with a test method for reproducing bugs in equals methods, and added
[^check.txt] with a test method for checking fixes.
> FindBugs: NPE and CCE on equals() methods
> -
>
> Key: IGNITE-9160
> URL: https://issues.apache.org/jira/browse/IGNITE-9160
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.6
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Minor
> Labels: newbie
> Fix For: 2.9
>
> Attachments: check.txt, reproduce.txt
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Some classes have Incorrect equals() method:
> {code:java}
> // GridDhtPartitionMap.java
> @Override public boolean equals(Object o) {
> if (this == o)
> return true;
> GridDhtPartitionMap other = (GridDhtPartitionMap)o;
> return other.nodeId.equals(nodeId) && other.updateSeq == updateSeq;
> }{code}
> In this case, we can get CCE
> {code:java}
> GridDhtPartitionMap gridDhtPartMap = new GridDhtPartitionMap();
> gridDhtPartMap.equals(new Object());
> --
> Exception in thread "main" java.lang.ClassCastException: java.lang.Object
> cannot be cast to
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionMap
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionMap.equals(GridDhtPartitionMap.java:319)
> at ru.zzzadruga.Ignite.main(Ignite.java:9){code}
> Or NPE
> {code:java}
> GridDhtPartitionMap gridDhtPartMap = new GridDhtPartitionMap();
> gridDhtPartMap.equals(null);
> --
> Exception in thread "main" java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionMap.equals(GridDhtPartitionMap.java:321)
> at ru.zzzadruga.Ignite.main(Ignite.java:9){code}
> The following code will prevent this
> {code:java}
> if (o == null || getClass() != o.getClass())
> return false;{code}
> + List of classes with similar problems: +
> * *GridTopic$T1-T8* - NPE
> * *GridCachePreloadLifecycleAbstractTest -* NPE
> * *GridDhtPartitionFullMap -* NPE and CCE
> * *GridDhtPartitionMap -* NPE and CCE
> * *OptimizedMarshallerSelfTest -* NPE and CCE
> * *GatewayProtectedCacheProxy -* NPE and CCE
> * *GridNearOptimisticTxPrepareFuture -* NPE and CCE
> * *GridCacheDistributedQueryManager -* NPE and CCE
> * *GridServiceMethodReflectKey -* NPE and CCE
> * *GridListSetSelfTest -* NPE and CCE
> * *GridTestKey -* NPE and CCE
> * *GridCacheMvccCandidate -* CCE
> * *GridDhtPartitionExchangeId -* CCE
> * *GridTuple6 -* CCE
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-9160) FindBugs: NPE and CCE on equals() methods
[
https://issues.apache.org/jira/browse/IGNITE-9160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16949530#comment-16949530
]
Nikolai Kulagin commented on IGNITE-9160:
-
[~mmuzaf], I created new pull request #6967, added [^reproduce.txt] with a test
method for reproducing bugs in equals methods, and added [^check.txt] with a
test method for checking fixes.
> FindBugs: NPE and CCE on equals() methods
> -
>
> Key: IGNITE-9160
> URL: https://issues.apache.org/jira/browse/IGNITE-9160
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.6
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Minor
> Labels: newbie
> Fix For: 2.9
>
> Attachments: check.txt, reproduce.txt
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Some classes have Incorrect equals() method:
> {code:java}
> // GridDhtPartitionMap.java
> @Override public boolean equals(Object o) {
> if (this == o)
> return true;
> GridDhtPartitionMap other = (GridDhtPartitionMap)o;
> return other.nodeId.equals(nodeId) && other.updateSeq == updateSeq;
> }{code}
> In this case, we can get CCE
> {code:java}
> GridDhtPartitionMap gridDhtPartMap = new GridDhtPartitionMap();
> gridDhtPartMap.equals(new Object());
> --
> Exception in thread "main" java.lang.ClassCastException: java.lang.Object
> cannot be cast to
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionMap
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionMap.equals(GridDhtPartitionMap.java:319)
> at ru.zzzadruga.Ignite.main(Ignite.java:9){code}
> Or NPE
> {code:java}
> GridDhtPartitionMap gridDhtPartMap = new GridDhtPartitionMap();
> gridDhtPartMap.equals(null);
> --
> Exception in thread "main" java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionMap.equals(GridDhtPartitionMap.java:321)
> at ru.zzzadruga.Ignite.main(Ignite.java:9){code}
> The following code will prevent this
> {code:java}
> if (o == null || getClass() != o.getClass())
> return false;{code}
> + List of classes with similar problems: +
> * *GridTopic$T1-T8* - NPE
> * *GridCachePreloadLifecycleAbstractTest -* NPE
> * *GridDhtPartitionFullMap -* NPE and CCE
> * *GridDhtPartitionMap -* NPE and CCE
> * *OptimizedMarshallerSelfTest -* NPE and CCE
> * *GatewayProtectedCacheProxy -* NPE and CCE
> * *GridNearOptimisticTxPrepareFuture -* NPE and CCE
> * *GridCacheDistributedQueryManager -* NPE and CCE
> * *GridServiceMethodReflectKey -* NPE and CCE
> * *GridListSetSelfTest -* NPE and CCE
> * *GridTestKey -* NPE and CCE
> * *GridCacheMvccCandidate -* CCE
> * *GridDhtPartitionExchangeId -* CCE
> * *GridTuple6 -* CCE
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-9160) FindBugs: NPE and CCE on equals() methods
[
https://issues.apache.org/jira/browse/IGNITE-9160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16949530#comment-16949530
]
Nikolai Kulagin edited comment on IGNITE-9160 at 10/11/19 3:06 PM:
---
[~mmuzaf], I created new pull request
[#6967|[https://github.com/apache/ignite/pull/6967]], added [^reproduce.txt]
with a test method for reproducing bugs in equals methods, and added
[^check.txt] with a test method for checking fixes.
was (Author: zzzadruga):
[~mmuzaf], I created new pull request #6967, added [^reproduce.txt] with a test
method for reproducing bugs in equals methods, and added [^check.txt] with a
test method for checking fixes.
> FindBugs: NPE and CCE on equals() methods
> -
>
> Key: IGNITE-9160
> URL: https://issues.apache.org/jira/browse/IGNITE-9160
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.6
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Minor
> Labels: newbie
> Fix For: 2.9
>
> Attachments: check.txt, reproduce.txt
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Some classes have Incorrect equals() method:
> {code:java}
> // GridDhtPartitionMap.java
> @Override public boolean equals(Object o) {
> if (this == o)
> return true;
> GridDhtPartitionMap other = (GridDhtPartitionMap)o;
> return other.nodeId.equals(nodeId) && other.updateSeq == updateSeq;
> }{code}
> In this case, we can get CCE
> {code:java}
> GridDhtPartitionMap gridDhtPartMap = new GridDhtPartitionMap();
> gridDhtPartMap.equals(new Object());
> --
> Exception in thread "main" java.lang.ClassCastException: java.lang.Object
> cannot be cast to
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionMap
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionMap.equals(GridDhtPartitionMap.java:319)
> at ru.zzzadruga.Ignite.main(Ignite.java:9){code}
> Or NPE
> {code:java}
> GridDhtPartitionMap gridDhtPartMap = new GridDhtPartitionMap();
> gridDhtPartMap.equals(null);
> --
> Exception in thread "main" java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionMap.equals(GridDhtPartitionMap.java:321)
> at ru.zzzadruga.Ignite.main(Ignite.java:9){code}
> The following code will prevent this
> {code:java}
> if (o == null || getClass() != o.getClass())
> return false;{code}
> + List of classes with similar problems: +
> * *GridTopic$T1-T8* - NPE
> * *GridCachePreloadLifecycleAbstractTest -* NPE
> * *GridDhtPartitionFullMap -* NPE and CCE
> * *GridDhtPartitionMap -* NPE and CCE
> * *OptimizedMarshallerSelfTest -* NPE and CCE
> * *GatewayProtectedCacheProxy -* NPE and CCE
> * *GridNearOptimisticTxPrepareFuture -* NPE and CCE
> * *GridCacheDistributedQueryManager -* NPE and CCE
> * *GridServiceMethodReflectKey -* NPE and CCE
> * *GridListSetSelfTest -* NPE and CCE
> * *GridTestKey -* NPE and CCE
> * *GridCacheMvccCandidate -* CCE
> * *GridDhtPartitionExchangeId -* CCE
> * *GridTuple6 -* CCE
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-9160) FindBugs: NPE and CCE on equals() methods
[
https://issues.apache.org/jira/browse/IGNITE-9160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolai Kulagin updated IGNITE-9160:
Attachment: reproduce.txt
check.txt
> FindBugs: NPE and CCE on equals() methods
> -
>
> Key: IGNITE-9160
> URL: https://issues.apache.org/jira/browse/IGNITE-9160
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.6
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Minor
> Labels: newbie
> Fix For: 2.9
>
> Attachments: check.txt, reproduce.txt
>
>
> Some classes have Incorrect equals() method:
> {code:java}
> // GridDhtPartitionMap.java
> @Override public boolean equals(Object o) {
> if (this == o)
> return true;
> GridDhtPartitionMap other = (GridDhtPartitionMap)o;
> return other.nodeId.equals(nodeId) && other.updateSeq == updateSeq;
> }{code}
> In this case, we can get CCE
> {code:java}
> GridDhtPartitionMap gridDhtPartMap = new GridDhtPartitionMap();
> gridDhtPartMap.equals(new Object());
> --
> Exception in thread "main" java.lang.ClassCastException: java.lang.Object
> cannot be cast to
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionMap
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionMap.equals(GridDhtPartitionMap.java:319)
> at ru.zzzadruga.Ignite.main(Ignite.java:9){code}
> Or NPE
> {code:java}
> GridDhtPartitionMap gridDhtPartMap = new GridDhtPartitionMap();
> gridDhtPartMap.equals(null);
> --
> Exception in thread "main" java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionMap.equals(GridDhtPartitionMap.java:321)
> at ru.zzzadruga.Ignite.main(Ignite.java:9){code}
> The following code will prevent this
> {code:java}
> if (o == null || getClass() != o.getClass())
> return false;{code}
> + List of classes with similar problems: +
> * *GridTopic$T1-T8* - NPE
> * *GridCachePreloadLifecycleAbstractTest -* NPE
> * *GridDhtPartitionFullMap -* NPE and CCE
> * *GridDhtPartitionMap -* NPE and CCE
> * *OptimizedMarshallerSelfTest -* NPE and CCE
> * *GatewayProtectedCacheProxy -* NPE and CCE
> * *GridNearOptimisticTxPrepareFuture -* NPE and CCE
> * *GridCacheDistributedQueryManager -* NPE and CCE
> * *GridServiceMethodReflectKey -* NPE and CCE
> * *GridListSetSelfTest -* NPE and CCE
> * *GridTestKey -* NPE and CCE
> * *GridCacheMvccCandidate -* CCE
> * *GridDhtPartitionExchangeId -* CCE
> * *GridTuple6 -* CCE
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-12252) Unchecked exceptions during rebalancing should be handled
[
https://issues.apache.org/jira/browse/IGNITE-12252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolai Kulagin reassigned IGNITE-12252:
Assignee: Nikolai Kulagin (was: Anton Vinogradov)
> Unchecked exceptions during rebalancing should be handled
> -
>
> Key: IGNITE-12252
> URL: https://issues.apache.org/jira/browse/IGNITE-12252
> Project: Ignite
> Issue Type: Bug
>Reporter: Aleksey Plekhanov
>Assignee: Nikolai Kulagin
>Priority: Critical
> Fix For: 2.8
>
>
> Rebalancing should handle unchecked exceptions by failure handler. In current
> implementation unchecked exceptions just ignored. They were handled by IO
> worker before IGNITE-3195.
> Reproducer:
> {code:java}
> @Test
> public void testRebalanceUncheckedError() throws Exception {
> IgniteEx ignite0 = startGrid(new
> IgniteConfiguration().setIgniteInstanceName("ignite0"));
> IgniteCache cache =
> ignite0.getOrCreateCache(DEFAULT_CACHE_NAME);
> IgniteDataStreamer streamer =
> ignite0.dataStreamer(DEFAULT_CACHE_NAME);
> for (int i = 0; i < 100_000; i++)
> streamer.addData(i, i);
> streamer.flush();
> IgniteEx ignite1 = startGrid(new
> IgniteConfiguration().setIgniteInstanceName("ignite1")
>
> .setIncludeEventTypes(EventType.EVT_CACHE_REBALANCE_OBJECT_LOADED));
> ignite1.events().localListen(e -> {
> throw new Error();
> }, EventType.EVT_CACHE_REBALANCE_OBJECT_LOADED);
> awaitPartitionMapExchange();
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-896) Configuration inconsistency
[ https://issues.apache.org/jira/browse/IGNITE-896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16946718#comment-16946718 ] Nikolai Kulagin commented on IGNITE-896: [~mmuzaf], I'm waiting for ticket IGNITE-9005 to continue working. I suppose we can move it to the next release. > Configuration inconsistency > --- > > Key: IGNITE-896 > URL: https://issues.apache.org/jira/browse/IGNITE-896 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: sprint-5 >Reporter: Valentin Kulichenko >Assignee: Nikolai Kulagin >Priority: Minor > Labels: Usability > Fix For: 2.8 > > > I noticed that some entities on cache configuration are configured via > factories, while others are set directly. For example, we use factory for > ExpiryPolicy, but not for EvictionPolicy, which looks inconsistent. Since > factory-based approach comes from JCache, I think we should use it wherever > possible. > Here is the list of settings that need to be fixed: > * Affinity > * AffinityMapper > * EvictionFilter > * EvictionPolicy > * CacheInterceptor > * TopologyValidator > Need to add new configuration properties that use factories and deprecate old > ones (do not remove for compatibility). > Also need to check other configuration beans (list above is for cache config > only). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-12193) [Phase-1] Rebalancing cache group keys metric counters
[ https://issues.apache.org/jira/browse/IGNITE-12193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolai Kulagin reassigned IGNITE-12193: Assignee: Nikolai Kulagin (was: Surkov Aleksandr) > [Phase-1] Rebalancing cache group keys metric counters > -- > > Key: IGNITE-12193 > URL: https://issues.apache.org/jira/browse/IGNITE-12193 > Project: Ignite > Issue Type: Sub-task >Reporter: Maxim Muzafarov >Assignee: Nikolai Kulagin >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Implement metrics counters related to the cache group: > * rebalancingPartitionsLeft long metric > * rebalancingReceivedKeys long metric > * rebalancingReceivedBytes long metric > * rebalancingStartTime long metric > * rebalancingFinishTime long metric -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Issue Comment Deleted] (IGNITE-9160) FindBugs: NPE and CCE on equals() methods
[
https://issues.apache.org/jira/browse/IGNITE-9160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolai Kulagin updated IGNITE-9160:
Comment: was deleted
(was: {panel:title=~[Excluded] - Run :: IntelliJ IDEA Inspections: No
blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *~[Excluded] - Run :: IntelliJ IDEA Inspections*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3873890buildTypeId=IgniteTests24Java8_RunIntelliJIdeaInspections])
> FindBugs: NPE and CCE on equals() methods
> -
>
> Key: IGNITE-9160
> URL: https://issues.apache.org/jira/browse/IGNITE-9160
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.6
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Minor
> Labels: newbie
> Fix For: 2.8
>
>
> Some classes have Incorrect equals() method:
> {code:java}
> // GridDhtPartitionMap.java
> @Override public boolean equals(Object o) {
> if (this == o)
> return true;
> GridDhtPartitionMap other = (GridDhtPartitionMap)o;
> return other.nodeId.equals(nodeId) && other.updateSeq == updateSeq;
> }{code}
> In this case, we can get CCE
> {code:java}
> GridDhtPartitionMap gridDhtPartMap = new GridDhtPartitionMap();
> gridDhtPartMap.equals(new Object());
> --
> Exception in thread "main" java.lang.ClassCastException: java.lang.Object
> cannot be cast to
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionMap
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionMap.equals(GridDhtPartitionMap.java:319)
> at ru.zzzadruga.Ignite.main(Ignite.java:9){code}
> Or NPE
> {code:java}
> GridDhtPartitionMap gridDhtPartMap = new GridDhtPartitionMap();
> gridDhtPartMap.equals(null);
> --
> Exception in thread "main" java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionMap.equals(GridDhtPartitionMap.java:321)
> at ru.zzzadruga.Ignite.main(Ignite.java:9){code}
> The following code will prevent this
> {code:java}
> if (o == null || getClass() != o.getClass())
> return false;{code}
> + List of classes with similar problems: +
> * *GridTopic$T1-T8* - NPE
> * *GridCachePreloadLifecycleAbstractTest -* NPE
> * *GridDhtPartitionFullMap -* NPE and CCE
> * *GridDhtPartitionMap -* NPE and CCE
> * *OptimizedMarshallerSelfTest -* NPE and CCE
> * *GatewayProtectedCacheProxy -* NPE and CCE
> * *GridNearOptimisticTxPrepareFuture -* NPE and CCE
> * *GridCacheDistributedQueryManager -* NPE and CCE
> * *GridServiceMethodReflectKey -* NPE and CCE
> * *GridListSetSelfTest -* NPE and CCE
> * *GridTestKey -* NPE and CCE
> * *GridCacheMvccCandidate -* CCE
> * *GridDhtPartitionExchangeId -* CCE
> * *GridTuple6 -* CCE
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9160) FindBugs: NPE and CCE on equals() methods
[
https://issues.apache.org/jira/browse/IGNITE-9160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16843186#comment-16843186
]
Nikolai Kulagin commented on IGNITE-9160:
-
{panel:title=~[Excluded] - Run :: IntelliJ IDEA Inspections: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *~[Excluded] - Run :: IntelliJ IDEA Inspections*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3873890buildTypeId=IgniteTests24Java8_RunIntelliJIdeaInspections]
> FindBugs: NPE and CCE on equals() methods
> -
>
> Key: IGNITE-9160
> URL: https://issues.apache.org/jira/browse/IGNITE-9160
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.6
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Minor
> Labels: newbie
> Fix For: 2.8
>
>
> Some classes have Incorrect equals() method:
> {code:java}
> // GridDhtPartitionMap.java
> @Override public boolean equals(Object o) {
> if (this == o)
> return true;
> GridDhtPartitionMap other = (GridDhtPartitionMap)o;
> return other.nodeId.equals(nodeId) && other.updateSeq == updateSeq;
> }{code}
> In this case, we can get CCE
> {code:java}
> GridDhtPartitionMap gridDhtPartMap = new GridDhtPartitionMap();
> gridDhtPartMap.equals(new Object());
> --
> Exception in thread "main" java.lang.ClassCastException: java.lang.Object
> cannot be cast to
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionMap
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionMap.equals(GridDhtPartitionMap.java:319)
> at ru.zzzadruga.Ignite.main(Ignite.java:9){code}
> Or NPE
> {code:java}
> GridDhtPartitionMap gridDhtPartMap = new GridDhtPartitionMap();
> gridDhtPartMap.equals(null);
> --
> Exception in thread "main" java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionMap.equals(GridDhtPartitionMap.java:321)
> at ru.zzzadruga.Ignite.main(Ignite.java:9){code}
> The following code will prevent this
> {code:java}
> if (o == null || getClass() != o.getClass())
> return false;{code}
> + List of classes with similar problems: +
> * *GridTopic$T1-T8* - NPE
> * *GridCachePreloadLifecycleAbstractTest -* NPE
> * *GridDhtPartitionFullMap -* NPE and CCE
> * *GridDhtPartitionMap -* NPE and CCE
> * *OptimizedMarshallerSelfTest -* NPE and CCE
> * *GatewayProtectedCacheProxy -* NPE and CCE
> * *GridNearOptimisticTxPrepareFuture -* NPE and CCE
> * *GridCacheDistributedQueryManager -* NPE and CCE
> * *GridServiceMethodReflectKey -* NPE and CCE
> * *GridListSetSelfTest -* NPE and CCE
> * *GridTestKey -* NPE and CCE
> * *GridCacheMvccCandidate -* CCE
> * *GridDhtPartitionExchangeId -* CCE
> * *GridTuple6 -* CCE
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-9160) FindBugs: NPE and CCE on equals() methods
[
https://issues.apache.org/jira/browse/IGNITE-9160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16820009#comment-16820009
]
Nikolai Kulagin edited comment on IGNITE-9160 at 4/17/19 11:59 AM:
---
[~dpavlov], I changed instanceofs to getClass
was (Author: zzzadruga):
[~dpavlov], Dmitriy, I changed instanceofs to getClass
> FindBugs: NPE and CCE on equals() methods
> -
>
> Key: IGNITE-9160
> URL: https://issues.apache.org/jira/browse/IGNITE-9160
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.6
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Minor
> Labels: newbie
> Fix For: 2.8
>
>
> Some classes have Incorrect equals() method:
> {code:java}
> // GridDhtPartitionMap.java
> @Override public boolean equals(Object o) {
> if (this == o)
> return true;
> GridDhtPartitionMap other = (GridDhtPartitionMap)o;
> return other.nodeId.equals(nodeId) && other.updateSeq == updateSeq;
> }{code}
> In this case, we can get CCE
> {code:java}
> GridDhtPartitionMap gridDhtPartMap = new GridDhtPartitionMap();
> gridDhtPartMap.equals(new Object());
> --
> Exception in thread "main" java.lang.ClassCastException: java.lang.Object
> cannot be cast to
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionMap
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionMap.equals(GridDhtPartitionMap.java:319)
> at ru.zzzadruga.Ignite.main(Ignite.java:9){code}
> Or NPE
> {code:java}
> GridDhtPartitionMap gridDhtPartMap = new GridDhtPartitionMap();
> gridDhtPartMap.equals(null);
> --
> Exception in thread "main" java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionMap.equals(GridDhtPartitionMap.java:321)
> at ru.zzzadruga.Ignite.main(Ignite.java:9){code}
> The following code will prevent this
> {code:java}
> if (o == null || getClass() != o.getClass())
> return false;{code}
> + List of classes with similar problems: +
> * *GridTopic$T1-T8* - NPE
> * *GridCachePreloadLifecycleAbstractTest -* NPE
> * *GridDhtPartitionFullMap -* NPE and CCE
> * *GridDhtPartitionMap -* NPE and CCE
> * *OptimizedMarshallerSelfTest -* NPE and CCE
> * *GatewayProtectedCacheProxy -* NPE and CCE
> * *GridNearOptimisticTxPrepareFuture -* NPE and CCE
> * *GridCacheDistributedQueryManager -* NPE and CCE
> * *GridServiceMethodReflectKey -* NPE and CCE
> * *GridListSetSelfTest -* NPE and CCE
> * *GridTestKey -* NPE and CCE
> * *GridCacheMvccCandidate -* CCE
> * *GridDhtPartitionExchangeId -* CCE
> * *GridTuple6 -* CCE
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9160) FindBugs: NPE and CCE on equals() methods
[
https://issues.apache.org/jira/browse/IGNITE-9160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16820009#comment-16820009
]
Nikolai Kulagin commented on IGNITE-9160:
-
[~dpavlov], Dmitriy, I changed instanceofs to getClass
> FindBugs: NPE and CCE on equals() methods
> -
>
> Key: IGNITE-9160
> URL: https://issues.apache.org/jira/browse/IGNITE-9160
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.6
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Minor
> Labels: newbie
> Fix For: 2.8
>
>
> Some classes have Incorrect equals() method:
> {code:java}
> // GridDhtPartitionMap.java
> @Override public boolean equals(Object o) {
> if (this == o)
> return true;
> GridDhtPartitionMap other = (GridDhtPartitionMap)o;
> return other.nodeId.equals(nodeId) && other.updateSeq == updateSeq;
> }{code}
> In this case, we can get CCE
> {code:java}
> GridDhtPartitionMap gridDhtPartMap = new GridDhtPartitionMap();
> gridDhtPartMap.equals(new Object());
> --
> Exception in thread "main" java.lang.ClassCastException: java.lang.Object
> cannot be cast to
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionMap
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionMap.equals(GridDhtPartitionMap.java:319)
> at ru.zzzadruga.Ignite.main(Ignite.java:9){code}
> Or NPE
> {code:java}
> GridDhtPartitionMap gridDhtPartMap = new GridDhtPartitionMap();
> gridDhtPartMap.equals(null);
> --
> Exception in thread "main" java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionMap.equals(GridDhtPartitionMap.java:321)
> at ru.zzzadruga.Ignite.main(Ignite.java:9){code}
> The following code will prevent this
> {code:java}
> if (o == null || getClass() != o.getClass())
> return false;{code}
> + List of classes with similar problems: +
> * *GridTopic$T1-T8* - NPE
> * *GridCachePreloadLifecycleAbstractTest -* NPE
> * *GridDhtPartitionFullMap -* NPE and CCE
> * *GridDhtPartitionMap -* NPE and CCE
> * *OptimizedMarshallerSelfTest -* NPE and CCE
> * *GatewayProtectedCacheProxy -* NPE and CCE
> * *GridNearOptimisticTxPrepareFuture -* NPE and CCE
> * *GridCacheDistributedQueryManager -* NPE and CCE
> * *GridServiceMethodReflectKey -* NPE and CCE
> * *GridListSetSelfTest -* NPE and CCE
> * *GridTestKey -* NPE and CCE
> * *GridCacheMvccCandidate -* CCE
> * *GridDhtPartitionExchangeId -* CCE
> * *GridTuple6 -* CCE
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9160) FindBugs: NPE and CCE on equals() methods
[
https://issues.apache.org/jira/browse/IGNITE-9160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16814623#comment-16814623
]
Nikolai Kulagin commented on IGNITE-9160:
-
[~dpavlov], I agree with your comment and fix it soon.
> FindBugs: NPE and CCE on equals() methods
> -
>
> Key: IGNITE-9160
> URL: https://issues.apache.org/jira/browse/IGNITE-9160
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.6
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Minor
> Labels: newbie
> Fix For: 2.8
>
>
> Some classes have Incorrect equals() method:
> {code:java}
> // GridDhtPartitionMap.java
> @Override public boolean equals(Object o) {
> if (this == o)
> return true;
> GridDhtPartitionMap other = (GridDhtPartitionMap)o;
> return other.nodeId.equals(nodeId) && other.updateSeq == updateSeq;
> }{code}
> In this case, we can get CCE
> {code:java}
> GridDhtPartitionMap gridDhtPartMap = new GridDhtPartitionMap();
> gridDhtPartMap.equals(new Object());
> --
> Exception in thread "main" java.lang.ClassCastException: java.lang.Object
> cannot be cast to
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionMap
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionMap.equals(GridDhtPartitionMap.java:319)
> at ru.zzzadruga.Ignite.main(Ignite.java:9){code}
> Or NPE
> {code:java}
> GridDhtPartitionMap gridDhtPartMap = new GridDhtPartitionMap();
> gridDhtPartMap.equals(null);
> --
> Exception in thread "main" java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionMap.equals(GridDhtPartitionMap.java:321)
> at ru.zzzadruga.Ignite.main(Ignite.java:9){code}
> The following code will prevent this
> {code:java}
> if (o == null || getClass() != o.getClass())
> return false;{code}
> + List of classes with similar problems: +
> * *GridTopic$T1-T8* - NPE
> * *GridCachePreloadLifecycleAbstractTest -* NPE
> * *GridDhtPartitionFullMap -* NPE and CCE
> * *GridDhtPartitionMap -* NPE and CCE
> * *OptimizedMarshallerSelfTest -* NPE and CCE
> * *GatewayProtectedCacheProxy -* NPE and CCE
> * *GridNearOptimisticTxPrepareFuture -* NPE and CCE
> * *GridCacheDistributedQueryManager -* NPE and CCE
> * *GridServiceMethodReflectKey -* NPE and CCE
> * *GridListSetSelfTest -* NPE and CCE
> * *GridTestKey -* NPE and CCE
> * *GridCacheMvccCandidate -* CCE
> * *GridDhtPartitionExchangeId -* CCE
> * *GridTuple6 -* CCE
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11087) GridJobCheckpointCleanupSelfTest.testCheckpointCleanup is flaky
[
https://issues.apache.org/jira/browse/IGNITE-11087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolai Kulagin updated IGNITE-11087:
-
Description:
The method of remove a checkpoint is sometimes not called or is called once
more. Test has a very low fail rate, 1 per 366 runs on
[TeamCity|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-7655052229521669617=testDetails_IgniteTests24Java8=%3Cdefault%3E]
and 1 per 412 on TC Bot. On local machine approximately 1 failure per 100
runs. Logs in the attachment.
Test is flaky for a long time. Before replacing IP Finder in IGNITE-10555, test
was slower, which made fail rate even less.
{code:java}
[2019-01-25 14:49:03,050][ERROR][main][root] Test failed.
junit.framework.AssertionFailedError: expected:<1> but was:<0>
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.Assert.failNotEquals(Assert.java:329)
at junit.framework.Assert.assertEquals(Assert.java:78)
at junit.framework.Assert.assertEquals(Assert.java:234)
at junit.framework.Assert.assertEquals(Assert.java:241)
at
org.apache.ignite.internal.GridJobCheckpointCleanupSelfTest.testCheckpointCleanup(GridJobCheckpointCleanupSelfTest.java:88)
at sun.reflect.GeneratedMethodAccessor22.invoke(Unknown Source)
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.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:2088)
at java.lang.Thread.run(Thread.java:748){code}
[^#removeCheckpoint isn't called.txt]
^_^
{code:java}
[2019-01-25 14:50:03,282][ERROR][main][root] Test failed.
junit.framework.AssertionFailedError: expected:<-1> but was:<0>
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.Assert.failNotEquals(Assert.java:329)
at junit.framework.Assert.assertEquals(Assert.java:78)
at junit.framework.Assert.assertEquals(Assert.java:234)
at junit.framework.Assert.assertEquals(Assert.java:241)
at
org.apache.ignite.internal.GridJobCheckpointCleanupSelfTest.testCheckpointCleanup(GridJobCheckpointCleanupSelfTest.java:88)
at sun.reflect.GeneratedMethodAccessor22.invoke(Unknown Source)
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.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:2088)
at java.lang.Thread.run(Thread.java:748){code}
[^#removeCheckpoint is called once more.txt]
was:
The method of remove a checkpoint is sometimes not called or is called once
more. Test has a very low fail rate, 0 per 360 runs on TC and 1 per 412 on TC
Bot. On local machine approximately 1 failure per 100 runs. Logs in the
attachment.
Test is flaky for a long time. Before replacing IP Finder in IGNITE-10555, test
was slower, which made fail rate even less.
{code:java}
[2019-01-25 14:49:03,050][ERROR][main][root] Test failed.
junit.framework.AssertionFailedError: expected:<1> but was:<0>
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.Assert.failNotEquals(Assert.java:329)
at junit.framework.Assert.assertEquals(Assert.java:78)
at junit.framework.Assert.assertEquals(Assert.java:234)
at junit.framework.Assert.assertEquals(Assert.java:241)
at
org.apache.ignite.internal.GridJobCheckpointCleanupSelfTest.testCheckpointCleanup(GridJobCheckpointCleanupSelfTest.java:88)
at sun.reflect.GeneratedMethodAccessor22.invoke(Unknown Source)
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.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:2088)
at java.lang.Thread.run(Thread.java:748){code}
[jira] [Updated] (IGNITE-11087) GridJobCheckpointCleanupSelfTest.testCheckpointCleanup is flaky
[
https://issues.apache.org/jira/browse/IGNITE-11087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolai Kulagin updated IGNITE-11087:
-
Attachment: (was: #removeCheckpointis called once more.txt)
> GridJobCheckpointCleanupSelfTest.testCheckpointCleanup is flaky
> ---
>
> Key: IGNITE-11087
> URL: https://issues.apache.org/jira/browse/IGNITE-11087
> Project: Ignite
> Issue Type: Bug
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Minor
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
> Attachments: #removeCheckpoint is called once more.txt,
> #removeCheckpoint isn't called.txt
>
>
> The method of remove a checkpoint is sometimes not called or is called once
> more. Test has a very low fail rate, 0 per 360 runs on TC and 1 per 412 on TC
> Bot. On local machine approximately 1 failure per 100 runs. Logs in the
> attachment.
> Test is flaky for a long time. Before replacing IP Finder in IGNITE-10555,
> test was slower, which made fail rate even less.
>
> {code:java}
> [2019-01-25 14:49:03,050][ERROR][main][root] Test failed.
> junit.framework.AssertionFailedError: expected:<1> but was:<0>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:234)
> at junit.framework.Assert.assertEquals(Assert.java:241)
> at
> org.apache.ignite.internal.GridJobCheckpointCleanupSelfTest.testCheckpointCleanup(GridJobCheckpointCleanupSelfTest.java:88)
> at sun.reflect.GeneratedMethodAccessor22.invoke(Unknown Source)
> 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.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:2088)
> at java.lang.Thread.run(Thread.java:748){code}
>
> [^#removeCheckpoint isn't called.txt]
> ^_^
>
> {code:java}
> [2019-01-25 14:50:03,282][ERROR][main][root] Test failed.
> junit.framework.AssertionFailedError: expected:<-1> but was:<0>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:234)
> at junit.framework.Assert.assertEquals(Assert.java:241)
> at
> org.apache.ignite.internal.GridJobCheckpointCleanupSelfTest.testCheckpointCleanup(GridJobCheckpointCleanupSelfTest.java:88)
> at sun.reflect.GeneratedMethodAccessor22.invoke(Unknown Source)
> 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.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:2088)
> at java.lang.Thread.run(Thread.java:748){code}
> [^#removeCheckpointis called once more.txt]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11087) GridJobCheckpointCleanupSelfTest.testCheckpointCleanup is flaky
[
https://issues.apache.org/jira/browse/IGNITE-11087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolai Kulagin updated IGNITE-11087:
-
Attachment: #removeCheckpoint is called once more.txt
> GridJobCheckpointCleanupSelfTest.testCheckpointCleanup is flaky
> ---
>
> Key: IGNITE-11087
> URL: https://issues.apache.org/jira/browse/IGNITE-11087
> Project: Ignite
> Issue Type: Bug
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Minor
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
> Attachments: #removeCheckpoint is called once more.txt,
> #removeCheckpoint isn't called.txt
>
>
> The method of remove a checkpoint is sometimes not called or is called once
> more. Test has a very low fail rate, 0 per 360 runs on TC and 1 per 412 on TC
> Bot. On local machine approximately 1 failure per 100 runs. Logs in the
> attachment.
> Test is flaky for a long time. Before replacing IP Finder in IGNITE-10555,
> test was slower, which made fail rate even less.
>
> {code:java}
> [2019-01-25 14:49:03,050][ERROR][main][root] Test failed.
> junit.framework.AssertionFailedError: expected:<1> but was:<0>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:234)
> at junit.framework.Assert.assertEquals(Assert.java:241)
> at
> org.apache.ignite.internal.GridJobCheckpointCleanupSelfTest.testCheckpointCleanup(GridJobCheckpointCleanupSelfTest.java:88)
> at sun.reflect.GeneratedMethodAccessor22.invoke(Unknown Source)
> 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.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:2088)
> at java.lang.Thread.run(Thread.java:748){code}
>
> [^#removeCheckpoint isn't called.txt]
> ^_^
>
> {code:java}
> [2019-01-25 14:50:03,282][ERROR][main][root] Test failed.
> junit.framework.AssertionFailedError: expected:<-1> but was:<0>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:234)
> at junit.framework.Assert.assertEquals(Assert.java:241)
> at
> org.apache.ignite.internal.GridJobCheckpointCleanupSelfTest.testCheckpointCleanup(GridJobCheckpointCleanupSelfTest.java:88)
> at sun.reflect.GeneratedMethodAccessor22.invoke(Unknown Source)
> 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.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:2088)
> at java.lang.Thread.run(Thread.java:748){code}
> [^#removeCheckpointis called once more.txt]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11087) GridJobCheckpointCleanupSelfTest.testCheckpointCleanup is flaky
[
https://issues.apache.org/jira/browse/IGNITE-11087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolai Kulagin updated IGNITE-11087:
-
Description:
The method of remove a checkpoint is sometimes not called or is called once
more. Test has a very low fail rate, 0 per 360 runs on TC and 1 per 412 on TC
Bot. On local machine approximately 1 failure per 100 runs. Logs in the
attachment.
Test is flaky for a long time. Before replacing IP Finder in IGNITE-10555, test
was slower, which made fail rate even less.
{code:java}
[2019-01-25 14:49:03,050][ERROR][main][root] Test failed.
junit.framework.AssertionFailedError: expected:<1> but was:<0>
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.Assert.failNotEquals(Assert.java:329)
at junit.framework.Assert.assertEquals(Assert.java:78)
at junit.framework.Assert.assertEquals(Assert.java:234)
at junit.framework.Assert.assertEquals(Assert.java:241)
at
org.apache.ignite.internal.GridJobCheckpointCleanupSelfTest.testCheckpointCleanup(GridJobCheckpointCleanupSelfTest.java:88)
at sun.reflect.GeneratedMethodAccessor22.invoke(Unknown Source)
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.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:2088)
at java.lang.Thread.run(Thread.java:748){code}
[^#removeCheckpoint isn't called.txt]
^_^
{code:java}
[2019-01-25 14:50:03,282][ERROR][main][root] Test failed.
junit.framework.AssertionFailedError: expected:<-1> but was:<0>
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.Assert.failNotEquals(Assert.java:329)
at junit.framework.Assert.assertEquals(Assert.java:78)
at junit.framework.Assert.assertEquals(Assert.java:234)
at junit.framework.Assert.assertEquals(Assert.java:241)
at
org.apache.ignite.internal.GridJobCheckpointCleanupSelfTest.testCheckpointCleanup(GridJobCheckpointCleanupSelfTest.java:88)
at sun.reflect.GeneratedMethodAccessor22.invoke(Unknown Source)
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.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:2088)
at java.lang.Thread.run(Thread.java:748){code}
[^#removeCheckpoint is called once more.txt]
was:
The method of remove a checkpoint is sometimes not called or is called once
more. Test has a very low fail rate, 0 per 360 runs on TC and 1 per 412 on TC
Bot. On local machine approximately 1 failure per 100 runs. Logs in the
attachment.
Test is flaky for a long time. Before replacing IP Finder in IGNITE-10555, test
was slower, which made fail rate even less.
{code:java}
[2019-01-25 14:49:03,050][ERROR][main][root] Test failed.
junit.framework.AssertionFailedError: expected:<1> but was:<0>
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.Assert.failNotEquals(Assert.java:329)
at junit.framework.Assert.assertEquals(Assert.java:78)
at junit.framework.Assert.assertEquals(Assert.java:234)
at junit.framework.Assert.assertEquals(Assert.java:241)
at
org.apache.ignite.internal.GridJobCheckpointCleanupSelfTest.testCheckpointCleanup(GridJobCheckpointCleanupSelfTest.java:88)
at sun.reflect.GeneratedMethodAccessor22.invoke(Unknown Source)
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.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:2088)
at java.lang.Thread.run(Thread.java:748){code}
[^#removeCheckpoint isn't called.txt]
^_^
{code:java}
[2019-01-25
[jira] [Created] (IGNITE-11087) GridJobCheckpointCleanupSelfTest.testCheckpointCleanup is flaky
Nikolai Kulagin created IGNITE-11087:
Summary: GridJobCheckpointCleanupSelfTest.testCheckpointCleanup is
flaky
Key: IGNITE-11087
URL: https://issues.apache.org/jira/browse/IGNITE-11087
Project: Ignite
Issue Type: Bug
Reporter: Nikolai Kulagin
Assignee: Nikolai Kulagin
Fix For: 2.8
Attachments: #removeCheckpoint isn't called.txt, #removeCheckpointis
called once more.txt
The method of remove a checkpoint is sometimes not called or is called once
more. Test has a very low fail rate, 0 per 360 runs on TC and 1 per 412 on TC
Bot. On local machine approximately 1 failure per 100 runs. Logs in the
attachment.
Test is flaky for a long time. Before replacing IP Finder in IGNITE-10555, test
was slower, which made fail rate even less.
{code:java}
[2019-01-25 14:49:03,050][ERROR][main][root] Test failed.
junit.framework.AssertionFailedError: expected:<1> but was:<0>
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.Assert.failNotEquals(Assert.java:329)
at junit.framework.Assert.assertEquals(Assert.java:78)
at junit.framework.Assert.assertEquals(Assert.java:234)
at junit.framework.Assert.assertEquals(Assert.java:241)
at
org.apache.ignite.internal.GridJobCheckpointCleanupSelfTest.testCheckpointCleanup(GridJobCheckpointCleanupSelfTest.java:88)
at sun.reflect.GeneratedMethodAccessor22.invoke(Unknown Source)
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.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:2088)
at java.lang.Thread.run(Thread.java:748){code}
[^#removeCheckpoint isn't called.txt]
^_^
{code:java}
[2019-01-25 14:50:03,282][ERROR][main][root] Test failed.
junit.framework.AssertionFailedError: expected:<-1> but was:<0>
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.Assert.failNotEquals(Assert.java:329)
at junit.framework.Assert.assertEquals(Assert.java:78)
at junit.framework.Assert.assertEquals(Assert.java:234)
at junit.framework.Assert.assertEquals(Assert.java:241)
at
org.apache.ignite.internal.GridJobCheckpointCleanupSelfTest.testCheckpointCleanup(GridJobCheckpointCleanupSelfTest.java:88)
at sun.reflect.GeneratedMethodAccessor22.invoke(Unknown Source)
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.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:2088)
at java.lang.Thread.run(Thread.java:748){code}
[^#removeCheckpointis called once more.txt]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10779) PagesWriteThrottleSmokeTest.testThrottle is flaky
[
https://issues.apache.org/jira/browse/IGNITE-10779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16728277#comment-16728277
]
Nikolai Kulagin commented on IGNITE-10779:
--
[~dpavlov], this counter use for right calc target dirty ratio, what affects
the calculation park time. This counter was removed in IGNITE-10028, and
thereafter test became flaky
> PagesWriteThrottleSmokeTest.testThrottle is flaky
> -
>
> Key: IGNITE-10779
> URL: https://issues.apache.org/jira/browse/IGNITE-10779
> Project: Ignite
> Issue Type: Task
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Minor
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
>
> Sometimes, at poor checkpoint write speed, put rate degrated to zero for at
> least 10 seconds with write throttling enabled. Success rate on TC = 87%.
> [Test
> details|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=2808794487465215609=testDetails]
> {code:java}
> junit.framework.AssertionFailedError: Put rate degraded to zero for at least
> 10 seconds
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.TestCase.fail(TestCase.java:227)
> at
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PagesWriteThrottleSmokeTest.testThrottle(PagesWriteThrottleSmokeTest.java:217)
> 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:2209)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:144)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:2124)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> Test became flaky after IGNITE-10028.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10779) PagesWriteThrottleSmokeTest.testThrottle is flaky
Nikolai Kulagin created IGNITE-10779:
Summary: PagesWriteThrottleSmokeTest.testThrottle is flaky
Key: IGNITE-10779
URL: https://issues.apache.org/jira/browse/IGNITE-10779
Project: Ignite
Issue Type: Task
Reporter: Nikolai Kulagin
Assignee: Nikolai Kulagin
Fix For: 2.8
Sometimes, at poor checkpoint write speed, put rate degrated to zero for at
least 10 seconds with write throttling enabled. Success rate on TC = 87%. [Test
details|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=2808794487465215609=testDetails]
{code:java}
junit.framework.AssertionFailedError: Put rate degraded to zero for at least 10
seconds
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.TestCase.fail(TestCase.java:227)
at
org.apache.ignite.internal.processors.cache.persistence.pagemem.PagesWriteThrottleSmokeTest.testThrottle(PagesWriteThrottleSmokeTest.java:217)
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:2209)
at
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:144)
at
org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:2124)
at java.lang.Thread.run(Thread.java:748)
{code}
Test became flaky after IGNITE-10028.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10628) Add support for nightly RunAll
Nikolai Kulagin created IGNITE-10628: Summary: Add support for nightly RunAll Key: IGNITE-10628 URL: https://issues.apache.org/jira/browse/IGNITE-10628 Project: Ignite Issue Type: Sub-task Reporter: Nikolai Kulagin Assignee: Nikolai Kulagin Add support for nightly RunAll, fix divisions on the y-axis of duration chart -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9165) FindBugs: Methods may fail to close stream in core module
[
https://issues.apache.org/jira/browse/IGNITE-9165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16711685#comment-16711685
]
Nikolai Kulagin commented on IGNITE-9165:
-
{panel:title=-- Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform .NET (Long Running){color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=2317263]]
* exe: CacheQueriesTest.TestSqlFieldsQueryTimeout - 0,0% fails in last 16
master runs.
* exe: CacheQueriesTest.TestSqlQueryTimeout - 0,0% fails in last 16 master runs.
* exe: CacheQueriesTest.TestSqlFieldsQueryTimeout - 0,0% fails in last 16
master runs.
* exe: CacheQueriesTest.TestSqlQueryTimeout - 0,0% fails in last 16 master runs.
{color:#d04437}Hadoop{color} [[tests
5|https://ci.ignite.apache.org/viewLog.html?buildId=2255238]]
* IgniteHadoopTestSuite: HadoopSplitWrapperSelfTest.testSerialization - 0,0%
fails in last 15 master runs.
* IgniteHadoopTestSuite: HadoopTasksV1Test.testReduceTask - 0,0% fails in last
15 master runs.
* IgniteHadoopTestSuite: HadoopTaskExecutionSelfTest.testJobKill - 0,0% fails
in last 15 master runs.
* IgniteHadoopTestSuite: HadoopV2JobSelfTest.testCustomSerializationApplying -
0,0% fails in last 15 master runs.
* IgniteHadoopTestSuite:
HadoopSerializationWrapperSelfTest.testIntJavaSerialization - 0,0% fails in
last 15 master runs.
{color:#d04437}Platform .NET (Core Linux){color} [[tests
5|https://ci.ignite.apache.org/viewLog.html?buildId=2262951]]
* dll: IgniteConfigurationTest.TestMulticastIpFinder - 0,0% fails in last 15
master runs.
* dll: CacheQueriesTestSimpleName.TestSqlQueryTimeout - 0,0% fails in last 15
master runs.
* dll: CacheQueriesTest.TestSqlFieldsQueryTimeout - 0,0% fails in last 15
master runs.
* dll: CacheQueriesTestSimpleName.TestSqlFieldsQueryTimeout - 0,0% fails in
last 15 master runs.
* dll: CacheQueriesTest.TestSqlQueryTimeout - 0,0% fails in last 15 master runs.
{color:#d04437}SPI{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=2317266]]
* IgniteSpiTestSuite:
TcpDiscoverySelfTest.testNodeShutdownOnRingMessageWorkerStartNotFinished - 0,0%
fails in last 16 master runs.
* IgniteSpiTestSuite:
TcpDiscoverySslTrustedSelfTest.testNodeShutdownOnRingMessageWorkerStartNotFinished
- 0,0% fails in last 16 master runs.
{color:#d04437}PDS 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2253771]]
* IgnitePdsTestSuite:
BPlusTreeReuseListPageMemoryImplTest.testMassiveRemove2_false - 0,0% fails in
last 17 master runs.
{color:#d04437}PDS 2{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2253772]]
* IgnitePdsTestSuite2:
WalCompactionTest.testCompressorToleratesEmptyWalSegmentsLogOnly - 0,0% fails
in last 14 master runs.
{color:#d04437}Platform C++ (Windows x64){color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=2317272]]
* IgniteOdbcTest: QueriesTestSuite: TestManyCursorsTwoSelects2 - 0,0% fails in
last 20 master runs.
* IgniteOdbcTest: QueriesTestSuite: TestManyCursorsSelectMerge2 - 0,0% fails in
last 20 master runs.
{color:#d04437}Platform C++ (Linux){color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=2317276]]
* IgniteOdbcTest: QueriesTestSuite: TestManyCursorsTwoSelects2 - 0,0% fails in
last 20 master runs.
* IgniteOdbcTest: QueriesTestSuite: TestManyCursorsSelectMerge2 - 0,0% fails in
last 20 master runs.
{color:#d04437}Cache 2{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2253751]]
* IgniteCacheTestSuite2:
IgniteCacheClientNodeChangingTopologyTest.testLockAllMultinode - 0,0% fails in
last 17 master runs.
{color:#d04437}Platform C++ (Linux Clang){color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=2317274]]
* IgniteOdbcTest: QueriesTestSuite: TestManyCursorsTwoSelects2 - 0,0% fails in
last 20 master runs.
* IgniteOdbcTest: QueriesTestSuite: TestManyCursorsSelectMerge2 - 0,0% fails in
last 20 master runs.
{color:#d04437}Inspections: Core{color} [[tests 0 BuildFailureOnMetric
|https://ci.ignite.apache.org/viewLog.html?buildId=2317264]]
{color:#d04437}Thin client: Python{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2317278]]
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2253787buildTypeId=IgniteTests24Java8_RunAll]
> FindBugs: Methods may fail to close stream in core module
> -
>
> Key: IGNITE-9165
> URL: https://issues.apache.org/jira/browse/IGNITE-9165
> Project: Ignite
> Issue Type: Bug
> Components: binary
>Affects Versions: 2.6
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Minor
> Labels: newbie
> Fix For: 2.8
>
> Attachments:
>
[jira] [Issue Comment Deleted] (IGNITE-9165) FindBugs: Methods may fail to close stream in core module
[
https://issues.apache.org/jira/browse/IGNITE-9165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolai Kulagin updated IGNITE-9165:
Comment: was deleted
(was: {panel:title=-- Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform .NET (Long Running){color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=2317263]]
* exe: CacheQueriesTest.TestSqlFieldsQueryTimeout - 0,0% fails in last 16
master runs.
* exe: CacheQueriesTest.TestSqlQueryTimeout - 0,0% fails in last 16 master runs.
* exe: CacheQueriesTest.TestSqlFieldsQueryTimeout - 0,0% fails in last 16
master runs.
* exe: CacheQueriesTest.TestSqlQueryTimeout - 0,0% fails in last 16 master runs.
{color:#d04437}Hadoop{color} [[tests
5|https://ci.ignite.apache.org/viewLog.html?buildId=2255238]]
* IgniteHadoopTestSuite: HadoopSplitWrapperSelfTest.testSerialization - 0,0%
fails in last 15 master runs.
* IgniteHadoopTestSuite: HadoopTasksV1Test.testReduceTask - 0,0% fails in last
15 master runs.
* IgniteHadoopTestSuite: HadoopTaskExecutionSelfTest.testJobKill - 0,0% fails
in last 15 master runs.
* IgniteHadoopTestSuite: HadoopV2JobSelfTest.testCustomSerializationApplying -
0,0% fails in last 15 master runs.
* IgniteHadoopTestSuite:
HadoopSerializationWrapperSelfTest.testIntJavaSerialization - 0,0% fails in
last 15 master runs.
{color:#d04437}Platform .NET (Core Linux){color} [[tests
5|https://ci.ignite.apache.org/viewLog.html?buildId=2262951]]
* dll: IgniteConfigurationTest.TestMulticastIpFinder - 0,0% fails in last 15
master runs.
* dll: CacheQueriesTestSimpleName.TestSqlQueryTimeout - 0,0% fails in last 15
master runs.
* dll: CacheQueriesTest.TestSqlFieldsQueryTimeout - 0,0% fails in last 15
master runs.
* dll: CacheQueriesTestSimpleName.TestSqlFieldsQueryTimeout - 0,0% fails in
last 15 master runs.
* dll: CacheQueriesTest.TestSqlQueryTimeout - 0,0% fails in last 15 master runs.
{color:#d04437}SPI{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=2317266]]
* IgniteSpiTestSuite:
TcpDiscoverySelfTest.testNodeShutdownOnRingMessageWorkerStartNotFinished - 0,0%
fails in last 16 master runs.
* IgniteSpiTestSuite:
TcpDiscoverySslTrustedSelfTest.testNodeShutdownOnRingMessageWorkerStartNotFinished
- 0,0% fails in last 16 master runs.
{color:#d04437}PDS 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2253771]]
* IgnitePdsTestSuite:
BPlusTreeReuseListPageMemoryImplTest.testMassiveRemove2_false - 0,0% fails in
last 17 master runs.
{color:#d04437}PDS 2{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2253772]]
* IgnitePdsTestSuite2:
WalCompactionTest.testCompressorToleratesEmptyWalSegmentsLogOnly - 0,0% fails
in last 14 master runs.
{color:#d04437}Platform C++ (Windows x64){color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=2317272]]
* IgniteOdbcTest: QueriesTestSuite: TestManyCursorsTwoSelects2 - 0,0% fails in
last 20 master runs.
* IgniteOdbcTest: QueriesTestSuite: TestManyCursorsSelectMerge2 - 0,0% fails in
last 20 master runs.
{color:#d04437}Platform C++ (Linux){color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=2317276]]
* IgniteOdbcTest: QueriesTestSuite: TestManyCursorsTwoSelects2 - 0,0% fails in
last 20 master runs.
* IgniteOdbcTest: QueriesTestSuite: TestManyCursorsSelectMerge2 - 0,0% fails in
last 20 master runs.
{color:#d04437}Cache 2{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2253751]]
* IgniteCacheTestSuite2:
IgniteCacheClientNodeChangingTopologyTest.testLockAllMultinode - 0,0% fails in
last 17 master runs.
{color:#d04437}Platform C++ (Linux Clang){color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=2317274]]
* IgniteOdbcTest: QueriesTestSuite: TestManyCursorsTwoSelects2 - 0,0% fails in
last 20 master runs.
* IgniteOdbcTest: QueriesTestSuite: TestManyCursorsSelectMerge2 - 0,0% fails in
last 20 master runs.
{color:#d04437}Inspections: Core{color} [[tests 0 BuildFailureOnMetric
|https://ci.ignite.apache.org/viewLog.html?buildId=2317264]]
{color:#d04437}Thin client: Python{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2317278]]
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2253787buildTypeId=IgniteTests24Java8_RunAll])
> FindBugs: Methods may fail to close stream in core module
> -
>
> Key: IGNITE-9165
> URL: https://issues.apache.org/jira/browse/IGNITE-9165
> Project: Ignite
> Issue Type: Bug
> Components: binary
>Affects Versions: 2.6
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Minor
> Labels: newbie
> Fix For: 2.8
>
> Attachments:
>
[jira] [Issue Comment Deleted] (IGNITE-10243) [TC Bot] Support partially cancelled suites in RunAll
[
https://issues.apache.org/jira/browse/IGNITE-10243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolai Kulagin updated IGNITE-10243:
-
Comment: was deleted
(was: {panel:title=-- Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 5{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=2312122]]
{color:#d04437}IGFS (Linux and MacOS){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2316383]]
* IgniteIgfsLinuxAndMacOSTestSuite:
IgniteHadoopFileSystemShmemExternalToClientPrimarySelfTest.testDeleteSuccessfulIfPathIsOpenedToRead
- 0,0% fails in last 13 master runs.
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2312157buildTypeId=IgniteTests24Java8_RunAll])
> [TC Bot] Support partially cancelled suites in RunAll
> -
>
> Key: IGNITE-10243
> URL: https://issues.apache.org/jira/browse/IGNITE-10243
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
>
> For case, there is no TC run (RunAll) for the branch with normal status we
> can check if there are any with canceled status.
> If canceled status (unknown) appeared on the latest build in suite's rebuilds
> sequence, we can use the latest build successful.
> If there is only one build in rebuilds sequence and it was canceled => use
> this one as a possible blocker for PR report.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (IGNITE-10243) [TC Bot] Support partially cancelled suites in RunAll
[
https://issues.apache.org/jira/browse/IGNITE-10243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolai Kulagin updated IGNITE-10243:
-
Comment: was deleted
(was: {panel:title=-- Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 5{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=2312122]]
{color:#d04437}IGFS (Linux and MacOS){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2316383]]
* IgniteIgfsLinuxAndMacOSTestSuite:
IgniteHadoopFileSystemShmemExternalToClientPrimarySelfTest.testDeleteSuccessfulIfPathIsOpenedToRead
- 0,0% fails in last 13 master runs.
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2312157buildTypeId=IgniteTests24Java8_RunAll])
> [TC Bot] Support partially cancelled suites in RunAll
> -
>
> Key: IGNITE-10243
> URL: https://issues.apache.org/jira/browse/IGNITE-10243
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
>
> For case, there is no TC run (RunAll) for the branch with normal status we
> can check if there are any with canceled status.
> If canceled status (unknown) appeared on the latest build in suite's rebuilds
> sequence, we can use the latest build successful.
> If there is only one build in rebuilds sequence and it was canceled => use
> this one as a possible blocker for PR report.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10243) [TC Bot] Support partially cancelled suites in RunAll
[
https://issues.apache.org/jira/browse/IGNITE-10243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16710290#comment-16710290
]
Nikolai Kulagin commented on IGNITE-10243:
--
{panel:title=-- Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 5{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=2312122]]
{color:#d04437}IGFS (Linux and MacOS){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2316383]]
* IgniteIgfsLinuxAndMacOSTestSuite:
IgniteHadoopFileSystemShmemExternalToClientPrimarySelfTest.testDeleteSuccessfulIfPathIsOpenedToRead
- 0,0% fails in last 13 master runs.
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2312157buildTypeId=IgniteTests24Java8_RunAll]
> [TC Bot] Support partially cancelled suites in RunAll
> -
>
> Key: IGNITE-10243
> URL: https://issues.apache.org/jira/browse/IGNITE-10243
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
>
> For case, there is no TC run (RunAll) for the branch with normal status we
> can check if there are any with canceled status.
> If canceled status (unknown) appeared on the latest build in suite's rebuilds
> sequence, we can use the latest build successful.
> If there is only one build in rebuilds sequence and it was canceled => use
> this one as a possible blocker for PR report.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10243) [TC Bot] Support partially cancelled suites in RunAll
[
https://issues.apache.org/jira/browse/IGNITE-10243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16710293#comment-16710293
]
Nikolai Kulagin commented on IGNITE-10243:
--
{panel:title=-- Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 5{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=2312122]]
{color:#d04437}IGFS (Linux and MacOS){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2316383]]
* IgniteIgfsLinuxAndMacOSTestSuite:
IgniteHadoopFileSystemShmemExternalToClientPrimarySelfTest.testDeleteSuccessfulIfPathIsOpenedToRead
- 0,0% fails in last 13 master runs.
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2312157buildTypeId=IgniteTests24Java8_RunAll]
> [TC Bot] Support partially cancelled suites in RunAll
> -
>
> Key: IGNITE-10243
> URL: https://issues.apache.org/jira/browse/IGNITE-10243
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
>
> For case, there is no TC run (RunAll) for the branch with normal status we
> can check if there are any with canceled status.
> If canceled status (unknown) appeared on the latest build in suite's rebuilds
> sequence, we can use the latest build successful.
> If there is only one build in rebuilds sequence and it was canceled => use
> this one as a possible blocker for PR report.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10243) [TC Bot] Support partially cancelled suites in RunAll
[
https://issues.apache.org/jira/browse/IGNITE-10243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16710099#comment-16710099
]
Nikolai Kulagin commented on IGNITE-10243:
--
{panel:title=-- Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 5{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=2312122]]
{color:#d04437}IGFS (Linux and MacOS){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2316383]]
* IgniteIgfsLinuxAndMacOSTestSuite:
IgniteHadoopFileSystemShmemExternalToClientPrimarySelfTest.testDeleteSuccessfulIfPathIsOpenedToRead
- 0,0% fails in last 13 master runs.
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2312157buildTypeId=IgniteTests24Java8_RunAll]
> [TC Bot] Support partially cancelled suites in RunAll
> -
>
> Key: IGNITE-10243
> URL: https://issues.apache.org/jira/browse/IGNITE-10243
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
>
> For case, there is no TC run (RunAll) for the branch with normal status we
> can check if there are any with canceled status.
> If canceled status (unknown) appeared on the latest build in suite's rebuilds
> sequence, we can use the latest build successful.
> If there is only one build in rebuilds sequence and it was canceled => use
> this one as a possible blocker for PR report.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (IGNITE-10243) [TC Bot] Support partially cancelled suites in RunAll
[
https://issues.apache.org/jira/browse/IGNITE-10243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolai Kulagin updated IGNITE-10243:
-
Comment: was deleted
(was: {panel:title=-- Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 5{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=2312122]]
{color:#d04437}IGFS (Linux and MacOS){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2316383]]
* IgniteIgfsLinuxAndMacOSTestSuite:
IgniteHadoopFileSystemShmemExternalToClientPrimarySelfTest.testDeleteSuccessfulIfPathIsOpenedToRead
- 0,0% fails in last 13 master runs.
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2312157buildTypeId=IgniteTests24Java8_RunAll])
> [TC Bot] Support partially cancelled suites in RunAll
> -
>
> Key: IGNITE-10243
> URL: https://issues.apache.org/jira/browse/IGNITE-10243
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
>
> For case, there is no TC run (RunAll) for the branch with normal status we
> can check if there are any with canceled status.
> If canceled status (unknown) appeared on the latest build in suite's rebuilds
> sequence, we can use the latest build successful.
> If there is only one build in rebuilds sequence and it was canceled => use
> this one as a possible blocker for PR report.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10540) [TC Bot] "Compare builds" page with Internal Server Error [500]
Nikolai Kulagin created IGNITE-10540:
Summary: [TC Bot] "Compare builds" page with Internal Server Error
[500]
Key: IGNITE-10540
URL: https://issues.apache.org/jira/browse/IGNITE-10540
Project: Ignite
Issue Type: Bug
Reporter: Nikolai Kulagin
Assignee: Nikolai Kulagin
"Compare builds" page with Internal Server Error [500].
{code:java}
com.google.inject.ConfigurationException: Guice configuration errors:
1) No implementation for org.apache.ignite.ci.user.ICredentialsProv was bound.
while locating org.apache.ignite.ci.user.ICredentialsProv
for field at
org.apache.ignite.ci.tcbot.builds.CompareBuildsService.prov(CompareBuildsService.java:38)
while locating org.apache.ignite.ci.tcbot.builds.CompareBuildsService
1 error
at
com.google.inject.internal.InjectorImpl.getProvider(InjectorImpl.java:1075)
at
com.google.inject.internal.InjectorImpl.getProvider(InjectorImpl.java:1034)
at
com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1086)
at
org.apache.ignite.ci.web.rest.build.CompareBuilds.tests(CompareBuilds.java:120)
at
org.apache.ignite.ci.web.rest.build.CompareBuilds.sortedTests(CompareBuilds.java:79)
at
org.apache.ignite.ci.web.rest.build.CompareBuilds.getTestFailsComparision(CompareBuilds.java:95)
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.glassfish.jersey.server.model.internal.ResourceMethodInvocationHandlerFactory$1.invoke(ResourceMethodInvocationHandlerFactory.java:81)
at
org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher$1.run(AbstractJavaResourceMethodDispatcher.java:144)
at
org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.invoke(AbstractJavaResourceMethodDispatcher.java:161)
at
org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$TypeOutInvoker.doDispatch(JavaResourceMethodDispatcherProvider.java:205)
at
org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.dispatch(AbstractJavaResourceMethodDispatcher.java:99)
at
org.glassfish.jersey.server.model.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:389)
at
org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:347)
at
org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:102)
at
org.glassfish.jersey.server.ServerRuntime$2.run(ServerRuntime.java:326)
at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271)
at org.glassfish.jersey.internal.Errors$1.call(Errors.java:267)
at org.glassfish.jersey.internal.Errors.process(Errors.java:315)
at org.glassfish.jersey.internal.Errors.process(Errors.java:297)
at org.glassfish.jersey.internal.Errors.process(Errors.java:267)
at
org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:317)
at
org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:305)
at
org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:1154)
at
org.glassfish.jersey.servlet.WebComponent.serviceImpl(WebComponent.java:473)
at
org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:427)
at
org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:388)
at
org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:341)
at
org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:228)
at
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:857)
at
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:535)
at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:146)
at
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)
at
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)
at
org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:257)
at
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1595)
at
org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255)
at
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1340)
at
org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:203)
at
[jira] [Resolved] (IGNITE-9332) [TC Bot] Add statistic page
[ https://issues.apache.org/jira/browse/IGNITE-9332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolai Kulagin resolved IGNITE-9332. - Resolution: Fixed > [TC Bot] Add statistic page > --- > > Key: IGNITE-9332 > URL: https://issues.apache.org/jira/browse/IGNITE-9332 > Project: Ignite > Issue Type: Task >Reporter: Eduard Shangareev >Assignee: Nikolai Kulagin >Priority: Major > > So, we are starting work on adding statistic information to our TC Helper. > It should make easier to get an insight into what to do next or what needs to > be fixed right now. > Also, it should show how we are progressing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9332) [TC Bot] Add statistic page
[ https://issues.apache.org/jira/browse/IGNITE-9332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolai Kulagin reassigned IGNITE-9332: --- Assignee: Nikolai Kulagin > [TC Bot] Add statistic page > --- > > Key: IGNITE-9332 > URL: https://issues.apache.org/jira/browse/IGNITE-9332 > Project: Ignite > Issue Type: Task >Reporter: Eduard Shangareev >Assignee: Nikolai Kulagin >Priority: Major > > So, we are starting work on adding statistic information to our TC Helper. > It should make easier to get an insight into what to do next or what needs to > be fixed right now. > Also, it should show how we are progressing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10243) [TC Bot] Support partially cancelled suites in RunAll
[
https://issues.apache.org/jira/browse/IGNITE-10243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16698816#comment-16698816
]
Nikolai Kulagin commented on IGNITE-10243:
--
{panel:title=- Run :: IntelliJ IDEA Inspections: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity - Run :: IntelliJ IDEA Inspections
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2312154buildTypeId=IgniteTests24Java8_RunIntelliJIdeaInspections]
> [TC Bot] Support partially cancelled suites in RunAll
> -
>
> Key: IGNITE-10243
> URL: https://issues.apache.org/jira/browse/IGNITE-10243
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
>
> For case, there is no TC run (RunAll) for the branch with normal status we
> can check if there are any with canceled status.
> If canceled status (unknown) appeared on the latest build in suite's rebuilds
> sequence, we can use the latest build successful.
> If there is only one build in rebuilds sequence and it was canceled => use
> this one as a possible blocker for PR report.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-10243) [TC Bot] Support partially cancelled suites in RunAll
[
https://issues.apache.org/jira/browse/IGNITE-10243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16698816#comment-16698816
]
Nikolai Kulagin edited comment on IGNITE-10243 at 11/26/18 11:33 AM:
-
{panel:title=- Run :: IntelliJ IDEA Inspections: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *- Run :: IntelliJ IDEA Inspections*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2312154buildTypeId=IgniteTests24Java8_RunIntelliJIdeaInspections]
was (Author: zzzadruga):
{panel:title=- Run :: IntelliJ IDEA Inspections: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity - Run :: IntelliJ IDEA Inspections
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2312154buildTypeId=IgniteTests24Java8_RunIntelliJIdeaInspections]
> [TC Bot] Support partially cancelled suites in RunAll
> -
>
> Key: IGNITE-10243
> URL: https://issues.apache.org/jira/browse/IGNITE-10243
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
>
> For case, there is no TC run (RunAll) for the branch with normal status we
> can check if there are any with canceled status.
> If canceled status (unknown) appeared on the latest build in suite's rebuilds
> sequence, we can use the latest build successful.
> If there is only one build in rebuilds sequence and it was canceled => use
> this one as a possible blocker for PR report.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (IGNITE-10243) [TC Bot] Support partially cancelled suites in RunAll
[
https://issues.apache.org/jira/browse/IGNITE-10243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolai Kulagin updated IGNITE-10243:
-
Comment: was deleted
(was: {panel:title=- Run :: IntelliJ IDEA Inspections: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity _- Run :: IntelliJ IDEA Inspections_
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2312154buildTypeId=IgniteTests24Java8_RunIntelliJIdeaInspections])
> [TC Bot] Support partially cancelled suites in RunAll
> -
>
> Key: IGNITE-10243
> URL: https://issues.apache.org/jira/browse/IGNITE-10243
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
>
> For case, there is no TC run (RunAll) for the branch with normal status we
> can check if there are any with canceled status.
> If canceled status (unknown) appeared on the latest build in suite's rebuilds
> sequence, we can use the latest build successful.
> If there is only one build in rebuilds sequence and it was canceled => use
> this one as a possible blocker for PR report.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10243) [TC Bot] Support partially cancelled suites in RunAll
[
https://issues.apache.org/jira/browse/IGNITE-10243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16698818#comment-16698818
]
Nikolai Kulagin commented on IGNITE-10243:
--
{panel:title=- Run :: IntelliJ IDEA Inspections: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity _- Run :: IntelliJ IDEA Inspections_
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2312154buildTypeId=IgniteTests24Java8_RunIntelliJIdeaInspections]
> [TC Bot] Support partially cancelled suites in RunAll
> -
>
> Key: IGNITE-10243
> URL: https://issues.apache.org/jira/browse/IGNITE-10243
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
>
> For case, there is no TC run (RunAll) for the branch with normal status we
> can check if there are any with canceled status.
> If canceled status (unknown) appeared on the latest build in suite's rebuilds
> sequence, we can use the latest build successful.
> If there is only one build in rebuilds sequence and it was canceled => use
> this one as a possible blocker for PR report.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (IGNITE-10243) [TC Bot] Support partially cancelled suites in RunAll
[
https://issues.apache.org/jira/browse/IGNITE-10243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolai Kulagin updated IGNITE-10243:
-
Comment: was deleted
(was: {panel:title=-- Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Queries 2{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2316250]]
* IgniteBinaryCacheQueryTestSuite2:
DisappearedCacheWasNotFoundMessageSelfTest.testDisappearedCacheWasNotFoundMessage
- 0,0% fails in last 100 master runs.
{color:#d04437}ZooKeeper (Discovery) 4{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2316260]]
* ZookeeperDiscoverySpiTestSuite4:
IgniteCacheReplicatedQuerySelfTest.testNodeLeft
{color:#d04437}Queries (Binary Objects Simple Mapper){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2332247]]
* IgniteBinarySimpleNameMapperCacheQueryTestSuite:
IgniteErrorOnRebalanceTest.testErrorOnRebalance
{color:#d04437}MVCC Queries{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=2316246]]
* IgniteCacheMvccSqlTestSuite:
CacheMvccPartitionedSqlCoordinatorFailoverTest.testPutAllGetAll_ClientServer_Backups1_Restart_Scan
* IgniteCacheMvccSqlTestSuite:
IgniteCacheMvccSqlTestSuite$MvccColocatedTxPessimisticOriginatingNodeFailureRecoveryTest.testPrimaryNodeFailureCommit
{color:#d04437}Start Nodes{color} [[tests
16|https://ci.ignite.apache.org/viewLog.html?buildId=2316299]]
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testStopNodesByIds - 3,2% fails in
last 100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testStopNodesFiltered - 3,2% fails in
last 100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testStartThreeNodesAndDoEmptyCall -
3,2% fails in last 100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testStartOneNode - 3,2% fails in last
100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testRestartNodes - 3,2% fails in last
100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testRestartNodesByIds - 3,2% fails in
last 100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testCustomScript - 3,2% fails in last
100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testStartFiveWithTwoSpecs - 3,2% fails
in last 100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testRestartNodesFiltered - 3,2% fails
in last 100 master runs.
{color:#d04437}IGFS (Linux and MacOS){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2316383]]
* IgniteIgfsLinuxAndMacOSTestSuite:
IgniteHadoopFileSystemShmemExternalToClientPrimarySelfTest.testDeleteSuccessfulIfPathIsOpenedToRead
- 0,0% fails in last 100 master runs.
{color:#d04437}Cache 5{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=2312122]]
{panel}
[TeamCity -- Run :: All
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2312157buildTypeId=IgniteTests24Java8_RunAll])
> [TC Bot] Support partially cancelled suites in RunAll
> -
>
> Key: IGNITE-10243
> URL: https://issues.apache.org/jira/browse/IGNITE-10243
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
>
> For case, there is no TC run (RunAll) for the branch with normal status we
> can check if there are any with canceled status.
> If canceled status (unknown) appeared on the latest build in suite's rebuilds
> sequence, we can use the latest build successful.
> If there is only one build in rebuilds sequence and it was canceled => use
> this one as a possible blocker for PR report.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10243) [TC Bot] Support partially cancelled suites in RunAll
[
https://issues.apache.org/jira/browse/IGNITE-10243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16698815#comment-16698815
]
Nikolai Kulagin commented on IGNITE-10243:
--
{panel:title=-- Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Queries 2{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2316250]]
* IgniteBinaryCacheQueryTestSuite2:
DisappearedCacheWasNotFoundMessageSelfTest.testDisappearedCacheWasNotFoundMessage
- 0,0% fails in last 100 master runs.
{color:#d04437}ZooKeeper (Discovery) 4{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2316260]]
* ZookeeperDiscoverySpiTestSuite4:
IgniteCacheReplicatedQuerySelfTest.testNodeLeft
{color:#d04437}Queries (Binary Objects Simple Mapper){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2332247]]
* IgniteBinarySimpleNameMapperCacheQueryTestSuite:
IgniteErrorOnRebalanceTest.testErrorOnRebalance
{color:#d04437}MVCC Queries{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=2316246]]
* IgniteCacheMvccSqlTestSuite:
CacheMvccPartitionedSqlCoordinatorFailoverTest.testPutAllGetAll_ClientServer_Backups1_Restart_Scan
* IgniteCacheMvccSqlTestSuite:
IgniteCacheMvccSqlTestSuite$MvccColocatedTxPessimisticOriginatingNodeFailureRecoveryTest.testPrimaryNodeFailureCommit
{color:#d04437}Start Nodes{color} [[tests
16|https://ci.ignite.apache.org/viewLog.html?buildId=2316299]]
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testStopNodesByIds - 3,2% fails in
last 100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testStopNodesFiltered - 3,2% fails in
last 100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testStartThreeNodesAndDoEmptyCall -
3,2% fails in last 100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testStartOneNode - 3,2% fails in last
100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testRestartNodes - 3,2% fails in last
100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testRestartNodesByIds - 3,2% fails in
last 100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testCustomScript - 3,2% fails in last
100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testStartFiveWithTwoSpecs - 3,2% fails
in last 100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testRestartNodesFiltered - 3,2% fails
in last 100 master runs.
{color:#d04437}IGFS (Linux and MacOS){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2316383]]
* IgniteIgfsLinuxAndMacOSTestSuite:
IgniteHadoopFileSystemShmemExternalToClientPrimarySelfTest.testDeleteSuccessfulIfPathIsOpenedToRead
- 0,0% fails in last 100 master runs.
{color:#d04437}Cache 5{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=2312122]]
{panel}
[TeamCity -- Run :: All
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2312157buildTypeId=IgniteTests24Java8_RunAll]
> [TC Bot] Support partially cancelled suites in RunAll
> -
>
> Key: IGNITE-10243
> URL: https://issues.apache.org/jira/browse/IGNITE-10243
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
>
> For case, there is no TC run (RunAll) for the branch with normal status we
> can check if there are any with canceled status.
> If canceled status (unknown) appeared on the latest build in suite's rebuilds
> sequence, we can use the latest build successful.
> If there is only one build in rebuilds sequence and it was canceled => use
> this one as a possible blocker for PR report.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10243) [TC Bot] Support partially cancelled suites in RunAll
[
https://issues.apache.org/jira/browse/IGNITE-10243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16698750#comment-16698750
]
Nikolai Kulagin commented on IGNITE-10243:
--
{panel:title=- Run :: IntelliJ IDEA Inspections: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity RunIntelliJIdeaInspections
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2312154buildTypeId=IgniteTests24Java8_RunIntelliJIdeaInspections]
> [TC Bot] Support partially cancelled suites in RunAll
> -
>
> Key: IGNITE-10243
> URL: https://issues.apache.org/jira/browse/IGNITE-10243
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
>
> For case, there is no TC run (RunAll) for the branch with normal status we
> can check if there are any with canceled status.
> If canceled status (unknown) appeared on the latest build in suite's rebuilds
> sequence, we can use the latest build successful.
> If there is only one build in rebuilds sequence and it was canceled => use
> this one as a possible blocker for PR report.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (IGNITE-10243) [TC Bot] Support partially cancelled suites in RunAll
[
https://issues.apache.org/jira/browse/IGNITE-10243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolai Kulagin updated IGNITE-10243:
-
Comment: was deleted
(was: {panel:title=RunAll: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Queries 2{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2316250]]
* IgniteBinaryCacheQueryTestSuite2:
DisappearedCacheWasNotFoundMessageSelfTest.testDisappearedCacheWasNotFoundMessage
- 0,0% fails in last 100 master runs.
{color:#d04437}ZooKeeper (Discovery) 4{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2316260]]
* ZookeeperDiscoverySpiTestSuite4:
IgniteCacheReplicatedQuerySelfTest.testNodeLeft
{color:#d04437}Queries (Binary Objects Simple Mapper){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2332247]]
* IgniteBinarySimpleNameMapperCacheQueryTestSuite:
IgniteErrorOnRebalanceTest.testErrorOnRebalance
{color:#d04437}MVCC Queries{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=2316246]]
* IgniteCacheMvccSqlTestSuite:
CacheMvccPartitionedSqlCoordinatorFailoverTest.testPutAllGetAll_ClientServer_Backups1_Restart_Scan
* IgniteCacheMvccSqlTestSuite:
IgniteCacheMvccSqlTestSuite$MvccColocatedTxPessimisticOriginatingNodeFailureRecoveryTest.testPrimaryNodeFailureCommit
{color:#d04437}Start Nodes{color} [[tests
16|https://ci.ignite.apache.org/viewLog.html?buildId=2316299]]
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testStopNodesByIds - 3,2% fails in
last 100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testStopNodesFiltered - 3,2% fails in
last 100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testStartThreeNodesAndDoEmptyCall -
3,2% fails in last 100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testStartOneNode - 3,2% fails in last
100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testRestartNodes - 3,2% fails in last
100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testRestartNodesByIds - 3,2% fails in
last 100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testCustomScript - 3,2% fails in last
100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testStartFiveWithTwoSpecs - 3,2% fails
in last 100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testRestartNodesFiltered - 3,2% fails
in last 100 master runs.
{color:#d04437}IGFS (Linux and MacOS){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2316383]]
* IgniteIgfsLinuxAndMacOSTestSuite:
IgniteHadoopFileSystemShmemExternalToClientPrimarySelfTest.testDeleteSuccessfulIfPathIsOpenedToRead
- 0,0% fails in last 100 master runs.
{color:#d04437}Cache 5{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=2312122]]
{panel}
[TeamCity RunAll
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2312157buildTypeId=IgniteTests24Java8_RunAll])
> [TC Bot] Support partially cancelled suites in RunAll
> -
>
> Key: IGNITE-10243
> URL: https://issues.apache.org/jira/browse/IGNITE-10243
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
>
> For case, there is no TC run (RunAll) for the branch with normal status we
> can check if there are any with canceled status.
> If canceled status (unknown) appeared on the latest build in suite's rebuilds
> sequence, we can use the latest build successful.
> If there is only one build in rebuilds sequence and it was canceled => use
> this one as a possible blocker for PR report.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10243) [TC Bot] Support partially cancelled suites in RunAll
[
https://issues.apache.org/jira/browse/IGNITE-10243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16698774#comment-16698774
]
Nikolai Kulagin commented on IGNITE-10243:
--
{panel:title=RunAll: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Queries 2{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2316250]]
* IgniteBinaryCacheQueryTestSuite2:
DisappearedCacheWasNotFoundMessageSelfTest.testDisappearedCacheWasNotFoundMessage
- 0,0% fails in last 100 master runs.
{color:#d04437}ZooKeeper (Discovery) 4{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2316260]]
* ZookeeperDiscoverySpiTestSuite4:
IgniteCacheReplicatedQuerySelfTest.testNodeLeft
{color:#d04437}Queries (Binary Objects Simple Mapper){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2332247]]
* IgniteBinarySimpleNameMapperCacheQueryTestSuite:
IgniteErrorOnRebalanceTest.testErrorOnRebalance
{color:#d04437}MVCC Queries{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=2316246]]
* IgniteCacheMvccSqlTestSuite:
CacheMvccPartitionedSqlCoordinatorFailoverTest.testPutAllGetAll_ClientServer_Backups1_Restart_Scan
* IgniteCacheMvccSqlTestSuite:
IgniteCacheMvccSqlTestSuite$MvccColocatedTxPessimisticOriginatingNodeFailureRecoveryTest.testPrimaryNodeFailureCommit
{color:#d04437}Start Nodes{color} [[tests
16|https://ci.ignite.apache.org/viewLog.html?buildId=2316299]]
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testStopNodesByIds - 3,2% fails in
last 100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testStopNodesFiltered - 3,2% fails in
last 100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testStartThreeNodesAndDoEmptyCall -
3,2% fails in last 100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testStartOneNode - 3,2% fails in last
100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testRestartNodes - 3,2% fails in last
100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testRestartNodesByIds - 3,2% fails in
last 100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testCustomScript - 3,2% fails in last
100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testStartFiveWithTwoSpecs - 3,2% fails
in last 100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testRestartNodesFiltered - 3,2% fails
in last 100 master runs.
{color:#d04437}IGFS (Linux and MacOS){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2316383]]
* IgniteIgfsLinuxAndMacOSTestSuite:
IgniteHadoopFileSystemShmemExternalToClientPrimarySelfTest.testDeleteSuccessfulIfPathIsOpenedToRead
- 0,0% fails in last 100 master runs.
{color:#d04437}Cache 5{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=2312122]]
{panel}
[TeamCity RunAll
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2312157buildTypeId=IgniteTests24Java8_RunAll]
> [TC Bot] Support partially cancelled suites in RunAll
> -
>
> Key: IGNITE-10243
> URL: https://issues.apache.org/jira/browse/IGNITE-10243
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
>
> For case, there is no TC run (RunAll) for the branch with normal status we
> can check if there are any with canceled status.
> If canceled status (unknown) appeared on the latest build in suite's rebuilds
> sequence, we can use the latest build successful.
> If there is only one build in rebuilds sequence and it was canceled => use
> this one as a possible blocker for PR report.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10243) [TC Bot] Support partially cancelled suites in RunAll
[
https://issues.apache.org/jira/browse/IGNITE-10243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16698775#comment-16698775
]
Nikolai Kulagin commented on IGNITE-10243:
--
{panel:title=RunIntelliJIdeaInspections: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity RunIntelliJIdeaInspections
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2312154buildTypeId=IgniteTests24Java8_RunIntelliJIdeaInspections]
> [TC Bot] Support partially cancelled suites in RunAll
> -
>
> Key: IGNITE-10243
> URL: https://issues.apache.org/jira/browse/IGNITE-10243
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
>
> For case, there is no TC run (RunAll) for the branch with normal status we
> can check if there are any with canceled status.
> If canceled status (unknown) appeared on the latest build in suite's rebuilds
> sequence, we can use the latest build successful.
> If there is only one build in rebuilds sequence and it was canceled => use
> this one as a possible blocker for PR report.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10243) [TC Bot] Support partially cancelled suites in RunAll
[
https://issues.apache.org/jira/browse/IGNITE-10243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16698730#comment-16698730
]
Nikolai Kulagin commented on IGNITE-10243:
--
{panel:title=- Run :: IntelliJ IDEA Inspections: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity IgniteTests24Java8_RunIntelliJIdeaInspections
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2312154buildTypeId=IgniteTests24Java8_RunIntelliJIdeaInspections]
> [TC Bot] Support partially cancelled suites in RunAll
> -
>
> Key: IGNITE-10243
> URL: https://issues.apache.org/jira/browse/IGNITE-10243
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
>
> For case, there is no TC run (RunAll) for the branch with normal status we
> can check if there are any with canceled status.
> If canceled status (unknown) appeared on the latest build in suite's rebuilds
> sequence, we can use the latest build successful.
> If there is only one build in rebuilds sequence and it was canceled => use
> this one as a possible blocker for PR report.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10243) [TC Bot] Support partially cancelled suites in RunAll
[
https://issues.apache.org/jira/browse/IGNITE-10243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16698725#comment-16698725
]
Nikolai Kulagin commented on IGNITE-10243:
--
{panel:title=- Run :: IntelliJ IDEA Inspections: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity - Run :: IntelliJ IDEA Inspections
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2312154buildTypeId=IgniteTests24Java8_RunIntelliJIdeaInspections]
> [TC Bot] Support partially cancelled suites in RunAll
> -
>
> Key: IGNITE-10243
> URL: https://issues.apache.org/jira/browse/IGNITE-10243
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
>
> For case, there is no TC run (RunAll) for the branch with normal status we
> can check if there are any with canceled status.
> If canceled status (unknown) appeared on the latest build in suite's rebuilds
> sequence, we can use the latest build successful.
> If there is only one build in rebuilds sequence and it was canceled => use
> this one as a possible blocker for PR report.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10243) [TC Bot] Support partially cancelled suites in RunAll
[
https://issues.apache.org/jira/browse/IGNITE-10243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16698652#comment-16698652
]
Nikolai Kulagin commented on IGNITE-10243:
--
{panel:title=IgniteTests24Java8_RunIntelliJIdeaInspections: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity IgniteTests24Java8_RunIntelliJIdeaInspections
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2312154buildTypeId=IgniteTests24Java8_RunIntelliJIdeaInspections]
> [TC Bot] Support partially cancelled suites in RunAll
> -
>
> Key: IGNITE-10243
> URL: https://issues.apache.org/jira/browse/IGNITE-10243
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
>
> For case, there is no TC run (RunAll) for the branch with normal status we
> can check if there are any with canceled status.
> If canceled status (unknown) appeared on the latest build in suite's rebuilds
> sequence, we can use the latest build successful.
> If there is only one build in rebuilds sequence and it was canceled => use
> this one as a possible blocker for PR report.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10243) [TC Bot] Support partially cancelled suites in RunAll
[
https://issues.apache.org/jira/browse/IGNITE-10243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16698651#comment-16698651
]
Nikolai Kulagin commented on IGNITE-10243:
--
{panel:title=IgniteTests24Java8_RunAll: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Queries 2{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2316250]]
* IgniteBinaryCacheQueryTestSuite2:
DisappearedCacheWasNotFoundMessageSelfTest.testDisappearedCacheWasNotFoundMessage
- 0,0% fails in last 100 master runs.
{color:#d04437}ZooKeeper (Discovery) 4{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2316260]]
* ZookeeperDiscoverySpiTestSuite4:
IgniteCacheReplicatedQuerySelfTest.testNodeLeft
{color:#d04437}Queries (Binary Objects Simple Mapper){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2332247]]
* IgniteBinarySimpleNameMapperCacheQueryTestSuite:
IgniteErrorOnRebalanceTest.testErrorOnRebalance
{color:#d04437}MVCC Queries{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=2316246]]
* IgniteCacheMvccSqlTestSuite:
CacheMvccPartitionedSqlCoordinatorFailoverTest.testPutAllGetAll_ClientServer_Backups1_Restart_Scan
* IgniteCacheMvccSqlTestSuite:
IgniteCacheMvccSqlTestSuite$MvccColocatedTxPessimisticOriginatingNodeFailureRecoveryTest.testPrimaryNodeFailureCommit
{color:#d04437}Start Nodes{color} [[tests
16|https://ci.ignite.apache.org/viewLog.html?buildId=2316299]]
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testStopNodesByIds - 3,2% fails in
last 100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testStopNodesFiltered - 3,2% fails in
last 100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testStartThreeNodesAndDoEmptyCall -
3,2% fails in last 100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testStartOneNode - 3,2% fails in last
100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testRestartNodes - 3,2% fails in last
100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testRestartNodesByIds - 3,2% fails in
last 100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testCustomScript - 3,2% fails in last
100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testStartFiveWithTwoSpecs - 3,2% fails
in last 100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testRestartNodesFiltered - 3,2% fails
in last 100 master runs.
{color:#d04437}IGFS (Linux and MacOS){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2316383]]
* IgniteIgfsLinuxAndMacOSTestSuite:
IgniteHadoopFileSystemShmemExternalToClientPrimarySelfTest.testDeleteSuccessfulIfPathIsOpenedToRead
- 0,0% fails in last 100 master runs.
{color:#d04437}Cache 5{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=2312122]]
{panel}
[TeamCity IgniteTests24Java8_RunAll
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2312157buildTypeId=IgniteTests24Java8_RunAll]
> [TC Bot] Support partially cancelled suites in RunAll
> -
>
> Key: IGNITE-10243
> URL: https://issues.apache.org/jira/browse/IGNITE-10243
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
>
> For case, there is no TC run (RunAll) for the branch with normal status we
> can check if there are any with canceled status.
> If canceled status (unknown) appeared on the latest build in suite's rebuilds
> sequence, we can use the latest build successful.
> If there is only one build in rebuilds sequence and it was canceled => use
> this one as a possible blocker for PR report.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (IGNITE-10243) [TC Bot] Support partially cancelled suites in RunAll
[
https://issues.apache.org/jira/browse/IGNITE-10243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolai Kulagin updated IGNITE-10243:
-
Comment: was deleted
(was: {panel:title=IgniteTests24Java8_RunIntelliJIdeaInspections: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity IgniteTests24Java8_RunIntelliJIdeaInspections
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2312154buildTypeId=IgniteTests24Java8_RunIntelliJIdeaInspections])
> [TC Bot] Support partially cancelled suites in RunAll
> -
>
> Key: IGNITE-10243
> URL: https://issues.apache.org/jira/browse/IGNITE-10243
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
>
> For case, there is no TC run (RunAll) for the branch with normal status we
> can check if there are any with canceled status.
> If canceled status (unknown) appeared on the latest build in suite's rebuilds
> sequence, we can use the latest build successful.
> If there is only one build in rebuilds sequence and it was canceled => use
> this one as a possible blocker for PR report.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10243) [TC Bot] Support partially cancelled suites in RunAll
[
https://issues.apache.org/jira/browse/IGNITE-10243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16698640#comment-16698640
]
Nikolai Kulagin commented on IGNITE-10243:
--
{panel:title=IgniteTests24Java8_RunIntelliJIdeaInspections: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity IgniteTests24Java8_RunIntelliJIdeaInspections
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2312154buildTypeId=IgniteTests24Java8_RunIntelliJIdeaInspections]
> [TC Bot] Support partially cancelled suites in RunAll
> -
>
> Key: IGNITE-10243
> URL: https://issues.apache.org/jira/browse/IGNITE-10243
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
>
> For case, there is no TC run (RunAll) for the branch with normal status we
> can check if there are any with canceled status.
> If canceled status (unknown) appeared on the latest build in suite's rebuilds
> sequence, we can use the latest build successful.
> If there is only one build in rebuilds sequence and it was canceled => use
> this one as a possible blocker for PR report.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10243) [TC Bot] Support partially cancelled suites in RunAll
[
https://issues.apache.org/jira/browse/IGNITE-10243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16698628#comment-16698628
]
Nikolai Kulagin commented on IGNITE-10243:
--
{panel:title=IgniteTests24Java8_RunIntelliJIdeaInspections: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity IgniteTests24Java8_RunIntelliJIdeaInspections
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2312154buildTypeId=IgniteTests24Java8_RunIntelliJIdeaInspections]
> [TC Bot] Support partially cancelled suites in RunAll
> -
>
> Key: IGNITE-10243
> URL: https://issues.apache.org/jira/browse/IGNITE-10243
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
>
> For case, there is no TC run (RunAll) for the branch with normal status we
> can check if there are any with canceled status.
> If canceled status (unknown) appeared on the latest build in suite's rebuilds
> sequence, we can use the latest build successful.
> If there is only one build in rebuilds sequence and it was canceled => use
> this one as a possible blocker for PR report.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (IGNITE-9165) FindBugs: Methods may fail to close stream in core module
[
https://issues.apache.org/jira/browse/IGNITE-9165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolai Kulagin updated IGNITE-9165:
Comment: was deleted
(was: {panel:title=IgniteTests24Java8_RunCache: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity IgniteTests24Java8_RunCache
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2067903buildTypeId=IgniteTests24Java8_RunCache])
> FindBugs: Methods may fail to close stream in core module
> -
>
> Key: IGNITE-9165
> URL: https://issues.apache.org/jira/browse/IGNITE-9165
> Project: Ignite
> Issue Type: Bug
> Components: binary
>Affects Versions: 2.6
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Minor
> Labels: newbie
> Fix For: 2.8
>
> Attachments:
> findbugs-result-apache-ignite[ignite-core]_2018_08_02_12_38_02.html
>
>
> The method creates an IO stream object, does not assign it to any fields,
> pass it to other methods that might close it, or return it, and does not
> appear to close the stream on all paths out of the method. This may result
> in a file descriptor leak.
> Example:
>
> {code:java}
> // GridCacheAbstractLoadTest#GridCacheAbstractLoadTest()
> try {
> props.load(new FileReader(GridTestUtils.resolveIgnitePath(
> "modules/tests/config/cache-load.properties")));
> }
> catch (IOException e) {
> throw new RuntimeException(e);
> }{code}
>
> One of possible solutions:
> {code:java}
> try (Reader reader = new FileReader(GridTestUtils.resolveIgnitePath(
> "modules/tests/config/cache-load.properties"))) {
> props.load(reader);
> }
> catch (IOException e) {
> throw new RuntimeException(e);
> }{code}
> List of classes in "core" module:
>
> +org.apache.ignite.internal:+
> * *BinaryContext*#classesInPackage(String)
> * *GridClientJdkMarshaller*#marshal(Object, int)
> *
> *IgniteExplicitImplicitDeploymentSelfTest*$GridDeploymentResourceTestJob#execute()
> * *OptimizedObjectStreamSelfTest*#testReadLine()
> * *PageIdDistributionTest*#_testRealHistory()
> * *HttpIgniteUpdatesChecker*#getUpdates(boolean)
> * *IpcSharedMemoryNativeLoaderSelfTest*#readStreams(Process)
> +org.apache.ignite:+
> * *GridCacheAbstractLoadTest*#GridCacheAbstractLoadTest()
> * *GridTestUtils*.sslContext()
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9165) FindBugs: Methods may fail to close stream in core module
[
https://issues.apache.org/jira/browse/IGNITE-9165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16698584#comment-16698584
]
Nikolai Kulagin commented on IGNITE-9165:
-
{panel:title=IgniteTests24Java8_RunCache: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity IgniteTests24Java8_RunCache
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2067903buildTypeId=IgniteTests24Java8_RunCache]
> FindBugs: Methods may fail to close stream in core module
> -
>
> Key: IGNITE-9165
> URL: https://issues.apache.org/jira/browse/IGNITE-9165
> Project: Ignite
> Issue Type: Bug
> Components: binary
>Affects Versions: 2.6
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Minor
> Labels: newbie
> Fix For: 2.8
>
> Attachments:
> findbugs-result-apache-ignite[ignite-core]_2018_08_02_12_38_02.html
>
>
> The method creates an IO stream object, does not assign it to any fields,
> pass it to other methods that might close it, or return it, and does not
> appear to close the stream on all paths out of the method. This may result
> in a file descriptor leak.
> Example:
>
> {code:java}
> // GridCacheAbstractLoadTest#GridCacheAbstractLoadTest()
> try {
> props.load(new FileReader(GridTestUtils.resolveIgnitePath(
> "modules/tests/config/cache-load.properties")));
> }
> catch (IOException e) {
> throw new RuntimeException(e);
> }{code}
>
> One of possible solutions:
> {code:java}
> try (Reader reader = new FileReader(GridTestUtils.resolveIgnitePath(
> "modules/tests/config/cache-load.properties"))) {
> props.load(reader);
> }
> catch (IOException e) {
> throw new RuntimeException(e);
> }{code}
> List of classes in "core" module:
>
> +org.apache.ignite.internal:+
> * *BinaryContext*#classesInPackage(String)
> * *GridClientJdkMarshaller*#marshal(Object, int)
> *
> *IgniteExplicitImplicitDeploymentSelfTest*$GridDeploymentResourceTestJob#execute()
> * *OptimizedObjectStreamSelfTest*#testReadLine()
> * *PageIdDistributionTest*#_testRealHistory()
> * *HttpIgniteUpdatesChecker*#getUpdates(boolean)
> * *IpcSharedMemoryNativeLoaderSelfTest*#readStreams(Process)
> +org.apache.ignite:+
> * *GridCacheAbstractLoadTest*#GridCacheAbstractLoadTest()
> * *GridTestUtils*.sslContext()
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10375) Fix inspection failures
[
https://issues.apache.org/jira/browse/IGNITE-10375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697178#comment-16697178
]
Nikolai Kulagin commented on IGNITE-10375:
--
{panel:title=No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity IgniteTests24Java8_RunIntelliJIdeaInspections
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2377131buildTypeId=IgniteTests24Java8_RunIntelliJIdeaInspections]
> Fix inspection failures
> ---
>
> Key: IGNITE-10375
> URL: https://issues.apache.org/jira/browse/IGNITE-10375
> Project: Ignite
> Issue Type: Bug
>Reporter: Ryabov Dmitrii
>Assignee: Ryabov Dmitrii
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
>
> 4 failures in the master
> https://ci.ignite.apache.org/viewLog.html?buildId=2376109=IgniteTests24Java8_InspectionsCore=Inspection
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10372) [TC Bot] Optimize master trends page
[ https://issues.apache.org/jira/browse/IGNITE-10372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697066#comment-16697066 ] Nikolai Kulagin commented on IGNITE-10372: -- [~dpavlov], looks good to me > [TC Bot] Optimize master trends page > > > Key: IGNITE-10372 > URL: https://issues.apache.org/jira/browse/IGNITE-10372 > Project: Ignite > Issue Type: Task >Reporter: Dmitriy Pavlov >Assignee: Dmitriy Pavlov >Priority: Major > > Now loading of the page may take up to several minutes. > It may be optimized > - by avoiding tests list obtaining from composites (instead we may load chain > of sub-builds) > - by creating a cache of loaded builds in memory (e.g. guava soft values for > the main method) > - by excluding of usage of deprecated REST caching API approach -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (IGNITE-9165) FindBugs: Methods may fail to close stream in core module
[
https://issues.apache.org/jira/browse/IGNITE-9165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolai Kulagin updated IGNITE-9165:
Comment: was deleted
(was: {panel:title=No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity IgniteTests24Java8_RunCache
Results|http://ci.ignite.apache.org/viewLog.html?buildId=2067903buildTypeId=IgniteTests24Java8_RunCache])
> FindBugs: Methods may fail to close stream in core module
> -
>
> Key: IGNITE-9165
> URL: https://issues.apache.org/jira/browse/IGNITE-9165
> Project: Ignite
> Issue Type: Bug
> Components: binary
>Affects Versions: 2.6
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Minor
> Labels: newbie
> Fix For: 2.8
>
> Attachments:
> findbugs-result-apache-ignite[ignite-core]_2018_08_02_12_38_02.html
>
>
> The method creates an IO stream object, does not assign it to any fields,
> pass it to other methods that might close it, or return it, and does not
> appear to close the stream on all paths out of the method. This may result
> in a file descriptor leak.
> Example:
>
> {code:java}
> // GridCacheAbstractLoadTest#GridCacheAbstractLoadTest()
> try {
> props.load(new FileReader(GridTestUtils.resolveIgnitePath(
> "modules/tests/config/cache-load.properties")));
> }
> catch (IOException e) {
> throw new RuntimeException(e);
> }{code}
>
> One of possible solutions:
> {code:java}
> try (Reader reader = new FileReader(GridTestUtils.resolveIgnitePath(
> "modules/tests/config/cache-load.properties"))) {
> props.load(reader);
> }
> catch (IOException e) {
> throw new RuntimeException(e);
> }{code}
> List of classes in "core" module:
>
> +org.apache.ignite.internal:+
> * *BinaryContext*#classesInPackage(String)
> * *GridClientJdkMarshaller*#marshal(Object, int)
> *
> *IgniteExplicitImplicitDeploymentSelfTest*$GridDeploymentResourceTestJob#execute()
> * *OptimizedObjectStreamSelfTest*#testReadLine()
> * *PageIdDistributionTest*#_testRealHistory()
> * *HttpIgniteUpdatesChecker*#getUpdates(boolean)
> * *IpcSharedMemoryNativeLoaderSelfTest*#readStreams(Process)
> +org.apache.ignite:+
> * *GridCacheAbstractLoadTest*#GridCacheAbstractLoadTest()
> * *GridTestUtils*.sslContext()
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9165) FindBugs: Methods may fail to close stream in core module
[
https://issues.apache.org/jira/browse/IGNITE-9165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16684270#comment-16684270
]
Nikolai Kulagin commented on IGNITE-9165:
-
{panel:title=No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity IgniteTests24Java8_RunCache
Results|http://ci.ignite.apache.org/viewLog.html?buildId=2067903buildTypeId=IgniteTests24Java8_RunCache]
> FindBugs: Methods may fail to close stream in core module
> -
>
> Key: IGNITE-9165
> URL: https://issues.apache.org/jira/browse/IGNITE-9165
> Project: Ignite
> Issue Type: Bug
> Components: binary
>Affects Versions: 2.6
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Minor
> Labels: newbie
> Fix For: 2.8
>
> Attachments:
> findbugs-result-apache-ignite[ignite-core]_2018_08_02_12_38_02.html
>
>
> The method creates an IO stream object, does not assign it to any fields,
> pass it to other methods that might close it, or return it, and does not
> appear to close the stream on all paths out of the method. This may result
> in a file descriptor leak.
> Example:
>
> {code:java}
> // GridCacheAbstractLoadTest#GridCacheAbstractLoadTest()
> try {
> props.load(new FileReader(GridTestUtils.resolveIgnitePath(
> "modules/tests/config/cache-load.properties")));
> }
> catch (IOException e) {
> throw new RuntimeException(e);
> }{code}
>
> One of possible solutions:
> {code:java}
> try (Reader reader = new FileReader(GridTestUtils.resolveIgnitePath(
> "modules/tests/config/cache-load.properties"))) {
> props.load(reader);
> }
> catch (IOException e) {
> throw new RuntimeException(e);
> }{code}
> List of classes in "core" module:
>
> +org.apache.ignite.internal:+
> * *BinaryContext*#classesInPackage(String)
> * *GridClientJdkMarshaller*#marshal(Object, int)
> *
> *IgniteExplicitImplicitDeploymentSelfTest*$GridDeploymentResourceTestJob#execute()
> * *OptimizedObjectStreamSelfTest*#testReadLine()
> * *PageIdDistributionTest*#_testRealHistory()
> * *HttpIgniteUpdatesChecker*#getUpdates(boolean)
> * *IpcSharedMemoryNativeLoaderSelfTest*#readStreams(Process)
> +org.apache.ignite:+
> * *GridCacheAbstractLoadTest*#GridCacheAbstractLoadTest()
> * *GridTestUtils*.sslContext()
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10203) [TC Bot] Support for alternative configurations for PR testing
Nikolai Kulagin created IGNITE-10203: Summary: [TC Bot] Support for alternative configurations for PR testing Key: IGNITE-10203 URL: https://issues.apache.org/jira/browse/IGNITE-10203 Project: Ignite Issue Type: Task Reporter: Nikolai Kulagin Assignee: Nikolai Kulagin Support for alternative configurations for PR testing (for example, IgniteTests24Java8_RunMl) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10169) Show tests and problems values on graphs
Nikolai Kulagin created IGNITE-10169: Summary: Show tests and problems values on graphs Key: IGNITE-10169 URL: https://issues.apache.org/jira/browse/IGNITE-10169 Project: Ignite Issue Type: Sub-task Reporter: Nikolai Kulagin Assignee: Nikolai Kulagin Show tests and problems values on graphs (currently shows build's start time). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9160) FindBugs: NPE and CCE on equals() methods
[
https://issues.apache.org/jira/browse/IGNITE-9160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16678030#comment-16678030
]
Nikolai Kulagin commented on IGNITE-9160:
-
[~NIzhikov], tests added, visa received
> FindBugs: NPE and CCE on equals() methods
> -
>
> Key: IGNITE-9160
> URL: https://issues.apache.org/jira/browse/IGNITE-9160
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.6
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Minor
> Labels: newbie
> Fix For: 2.8
>
>
> Some classes have Incorrect equals() method:
> {code:java}
> // GridDhtPartitionMap.java
> @Override public boolean equals(Object o) {
> if (this == o)
> return true;
> GridDhtPartitionMap other = (GridDhtPartitionMap)o;
> return other.nodeId.equals(nodeId) && other.updateSeq == updateSeq;
> }{code}
> In this case, we can get CCE
> {code:java}
> GridDhtPartitionMap gridDhtPartMap = new GridDhtPartitionMap();
> gridDhtPartMap.equals(new Object());
> --
> Exception in thread "main" java.lang.ClassCastException: java.lang.Object
> cannot be cast to
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionMap
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionMap.equals(GridDhtPartitionMap.java:319)
> at ru.zzzadruga.Ignite.main(Ignite.java:9){code}
> Or NPE
> {code:java}
> GridDhtPartitionMap gridDhtPartMap = new GridDhtPartitionMap();
> gridDhtPartMap.equals(null);
> --
> Exception in thread "main" java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionMap.equals(GridDhtPartitionMap.java:321)
> at ru.zzzadruga.Ignite.main(Ignite.java:9){code}
> The following code will prevent this
> {code:java}
> if (o == null || getClass() != o.getClass())
> return false;{code}
> + List of classes with similar problems: +
> * *GridTopic$T1-T8* - NPE
> * *GridCachePreloadLifecycleAbstractTest -* NPE
> * *GridDhtPartitionFullMap -* NPE and CCE
> * *GridDhtPartitionMap -* NPE and CCE
> * *OptimizedMarshallerSelfTest -* NPE and CCE
> * *GatewayProtectedCacheProxy -* NPE and CCE
> * *GridNearOptimisticTxPrepareFuture -* NPE and CCE
> * *GridCacheDistributedQueryManager -* NPE and CCE
> * *GridServiceMethodReflectKey -* NPE and CCE
> * *GridListSetSelfTest -* NPE and CCE
> * *GridTestKey -* NPE and CCE
> * *GridCacheMvccCandidate -* CCE
> * *GridDhtPartitionExchangeId -* CCE
> * *GridTuple6 -* CCE
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9005) Eviction policy MBeans change failed LifecycleAwareTest on cache name injectoin
[
https://issues.apache.org/jira/browse/IGNITE-9005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16677887#comment-16677887
]
Nikolai Kulagin commented on IGNITE-9005:
-
[~slukyanov], this fix is necessary for IGNITE-896. But I think, it is not
urgent
> Eviction policy MBeans change failed LifecycleAwareTest on cache name
> injectoin
> ---
>
> Key: IGNITE-9005
> URL: https://issues.apache.org/jira/browse/IGNITE-9005
> Project: Ignite
> Issue Type: Test
>Reporter: Dmitriy Pavlov
>Assignee: Stanislav Lukyanov
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
>
> http://apache-ignite-developers.2346864.n4.nabble.com/MTCGA-new-failures-in-builds-1485687-needs-to-be-handled-td32531.html
> New test failure detected
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=7246907407546697403=%3Cdefault%3E=testDetails
> after merging
> IGNITE-8776 Eviction policy MBeans are never registered if
> evictionPolicyFactory is used
> Revert of commit makes test passing.
> Locally test also failed. Failed with message
> {noformat}
> Unexpected cache name for
> org.apache.ignite.internal.processors.cache.GridCacheLifecycleAwareSelfTest$TestEvictionPolicy@322714f4
> expected: but was:
> {noformat}
> Message of failure seems to be related to TestEvictionPolicy instance from
> test class.
> Seems that returing call to cctx.kernalContext (). resource ().
> injectCacheName (rsrc, cfg.getName ()); should fix issue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10137) [TC Bot] Add button 'Expand all' on 'PR failures' page
Nikolai Kulagin created IGNITE-10137: Summary: [TC Bot] Add button 'Expand all' on 'PR failures' page Key: IGNITE-10137 URL: https://issues.apache.org/jira/browse/IGNITE-10137 Project: Ignite Issue Type: Sub-task Reporter: Nikolai Kulagin Assignee: Nikolai Kulagin Add button 'Expand all' on '[PR failures|http://localhost:8080/prs.html]' page. The button should show additional information for all available lines. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10125) [TC Bot] Uniform style for buttons
[ https://issues.apache.org/jira/browse/IGNITE-10125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolai Kulagin updated IGNITE-10125: - Attachment: image-2018-11-02-12-06-59-734.png Description: Uniform style for buttons: "Inspect" from [PR selection|https://mtcga.gridgain.com/prs.html], "Show graph" from [Master Trends|https://mtcga.gridgain.com/comparison.html], "More >>" from [PR Failures|https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAll=pull/5200/head=Latest] !image-2018-11-02-12-06-59-734.png! was:Uniform style for buttons: "Inspect" from [PR selection|https://mtcga.gridgain.com/prs.html], "Show graph" from [Master Trends|https://mtcga.gridgain.com/comparison.html], "More >>" from [PR Failures|https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAll=pull/5200/head=Latest] > [TC Bot] Uniform style for buttons > -- > > Key: IGNITE-10125 > URL: https://issues.apache.org/jira/browse/IGNITE-10125 > Project: Ignite > Issue Type: Sub-task >Reporter: Nikolai Kulagin >Assignee: Nikolai Kulagin >Priority: Minor > Attachments: image-2018-11-02-12-06-59-734.png > > > Uniform style for buttons: "Inspect" from [PR > selection|https://mtcga.gridgain.com/prs.html], "Show graph" from [Master > Trends|https://mtcga.gridgain.com/comparison.html], "More >>" from [PR > Failures|https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAll=pull/5200/head=Latest] > > !image-2018-11-02-12-06-59-734.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10125) [TC Bot] Uniform style for buttons
[ https://issues.apache.org/jira/browse/IGNITE-10125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolai Kulagin updated IGNITE-10125: - Description: Uniform style for buttons: "Inspect" from [PR selection|https://mtcga.gridgain.com/prs.html], "Show graph" from [Master Trends|https://mtcga.gridgain.com/comparison.html], "More >>" from [PR Failures|https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAll=pull/5200/head=Latest] (was: Uniform style for buttons: "Inspect" from [PR selection|mtcga.gridgain.com/prs.html], "Show graph" from [Master Trends|https://mtcga.gridgain.com/comparison.html], "More >>" from [PR Failures|https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAll=pull/5200/head=Latest]) > [TC Bot] Uniform style for buttons > -- > > Key: IGNITE-10125 > URL: https://issues.apache.org/jira/browse/IGNITE-10125 > Project: Ignite > Issue Type: Sub-task >Reporter: Nikolai Kulagin >Assignee: Nikolai Kulagin >Priority: Minor > > Uniform style for buttons: "Inspect" from [PR > selection|https://mtcga.gridgain.com/prs.html], "Show graph" from [Master > Trends|https://mtcga.gridgain.com/comparison.html], "More >>" from [PR > Failures|https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAll=pull/5200/head=Latest] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
