[jira] [Created] (IGNITE-13107) ODBC: Memory leak in the tests
Igor Sapego created IGNITE-13107: Summary: ODBC: Memory leak in the tests Key: IGNITE-13107 URL: https://issues.apache.org/jira/browse/IGNITE-13107 Project: Ignite Issue Type: Improvement Components: odbc Reporter: Igor Sapego Fix For: 2.9 The memory leak, which is reproducible on TC Windows debug configuration, have place in case of odce-test unit tests executing. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-13107) ODBC: Memory leak in the tests
[ https://issues.apache.org/jira/browse/IGNITE-13107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego reassigned IGNITE-13107: Assignee: Igor Sapego > ODBC: Memory leak in the tests > -- > > Key: IGNITE-13107 > URL: https://issues.apache.org/jira/browse/IGNITE-13107 > Project: Ignite > Issue Type: Improvement > Components: odbc >Reporter: Igor Sapego >Assignee: Igor Sapego >Priority: Major > Fix For: 2.9 > > > The memory leak, which is reproducible on TC Windows debug configuration, > have place in case of odce-test unit tests executing. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13095) .NET: Thin Client Compute does not cancel task on server when cancelled on client
[ https://issues.apache.org/jira/browse/IGNITE-13095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17124344#comment-17124344 ] Igor Sapego commented on IGNITE-13095: -- [~ptupitsyn] Looks good to me. Ship it. > .NET: Thin Client Compute does not cancel task on server when cancelled on > client > - > > Key: IGNITE-13095 > URL: https://issues.apache.org/jira/browse/IGNITE-13095 > Project: Ignite > Issue Type: New Feature > Components: platforms, thin client >Affects Versions: 2.9 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: .NET > Fix For: 2.9 > > Original Estimate: 3h > Time Spent: 10m > Remaining Estimate: 2h 50m > > Client should call OP_RESOURCE_CLOSE to cancel the task on server side. > Test this by reading server logs, "Job was cancelled" should be there. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-4029) Local ContinuousQueries on PARTITIONED caches may await for previously rejected events
[
https://issues.apache.org/jira/browse/IGNITE-4029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov reassigned IGNITE-4029:
---
Assignee: Maxim Muzafarov (was: Nikolay Tikhonov)
> Local ContinuousQueries on PARTITIONED caches may await for previously
> rejected events
> --
>
> Key: IGNITE-4029
> URL: https://issues.apache.org/jira/browse/IGNITE-4029
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 1.7, 1.8
>Reporter: David Bidorff
>Assignee: Maxim Muzafarov
>Priority: Major
> Attachments: Ignite4029Test.java
>
>
> {{CacheContinuousQueryHandler.PartitionRecovery.collectEntries()}} stores and
> updates the identifier of the next expected event. However, some events may
> be rejected before even reaching the query handler, preventing this counter
> to be incremented and leading the next events to be queued until
> {{MAX_BUFF_SIZE}} is reached.
> This happens after data was rebalanced: some events may be handled as
> happening on a backup node, leading the test {{primary || skipPrimaryCheck}}
> (on line 410 of {{CacheContinuousQueryHandler.onEntryUpdate()}}) to be false
> and preventing the previously mentioned counter to be increased.
> I'm not sure if the main problem is about those events being considered has
> happening on a backup node or if it is about the counter not being
> incremented, but either way, this can be problematic on caches with very few
> 'update events' where the {{MAX_BUFF_SIZE}} is not reached quickly.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13094) java.lang.ClassNotFoundException: ch.qos.logback for distributed compute
[
https://issues.apache.org/jira/browse/IGNITE-13094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17124222#comment-17124222
]
Ivan Pavlukhin commented on IGNITE-13094:
-
[~ilyak], the patch definitely makes things better and consequently can be
merged.
Still I suspect one potential problem (which existed before). From the code I
see that a case when a received class name does not ends with ".class" is legal
as well. And if we have a class named "org.example.classic.Foo" (not ending
with ".class") then it will be trimmed to "org.example". Perhaps a following
check could be more universal:
{code:java}
String className = ...;
if (className.endsWith(".class")) {
className = className.substring(0, className.length() - ".class".length());
}
{code}
> java.lang.ClassNotFoundException: ch.qos.logback for distributed compute
>
>
> Key: IGNITE-13094
> URL: https://issues.apache.org/jira/browse/IGNITE-13094
> Project: Ignite
> Issue Type: Bug
> Components: compute
>Affects Versions: 2.8.1
> Environment: Ignite 2.8.0
> Spring Boot 2.1.0.RELEASE
> Java 1.8
>Reporter: AK47Sonic
>Assignee: Ilya Kasnacheev
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I try to use spring boot (2.1.0.RELEASE) to run ignite.compute. As spring
> boot + lombok use logback as default, the following codes always throw
> exceptions (2020-05-28 07:00:48.979 WARN 8460 --- [ p2p-#49]
> o.a.i.i.m.d.GridDeploymentCommunication : Failed to resolve class:
> ch.qos.logback). The result (28) could be returned. Seems we see log4j and
> log4j2 on official website. I try to use log4j2 to replace logback. And it
> works fine. Does ignite support logback for distributed compute? Or It is
> just a bug?
> {panel:title=pom.xml}
>
>
> org.springframework.boot
> spring-boot-starter-web
>
>
> org.springframework.boot
> spring-boot-starter-log4j
>
>
>
>
> org.apache.ignite
> ignite-core
> 2.8.0
>
>
> org.apache.ignite
> ignite-spring
> 2.8.0
>
>
> org.projectlombok
> lombok
> 1.18.12
> provided
>
>
> {panel}
> {panel:title=config.xml}
>
> http://www.springframework.org/schema/beans";
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>xmlns:util="http://www.springframework.org/schema/util";
>xsi:schemaLocation="
> http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans.xsd
> http://www.springframework.org/schema/util
> http://www.springframework.org/schema/util/spring-util.xsd";>
> class="org.apache.ignite.configuration.IgniteConfiguration">
>
>
>
>
>
>
>
> class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">
>
>
> 127.0.0.1:48500..48520
>
>
>
>
>
>
>
> class="org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi">
>
>
>
>
>
> {panel}
> {code:java}
> @Configuration
> @ImportResource(locations={"classpath:default-config.xml"})
> public class IgniteConfig {
> @Bean
> public Ignite ignite(IgniteConfiguration igniteConfiguration) {
> Ignite ignite = Ignition.start(igniteConfiguration);
> Ignition.setClientMode(true);
> return ignite;
> }
> }
> @Slf4j
> @RestController
> public class WebController {
> @Autowired
> private Ignite ignite;
> @GetMapping("/compute")
> public void compute() {
> Collection> calls = new ArrayList<>();
> // Iterate through all the words in the sentence and create Callable
> jobs.
> for (final String word : "Count characters using callable".split(" "))
> calls.add(word::length);
> // Execute collection of Callables on the grid.
> Collection res = ignite.compute().call(calls);
> // Add up all the results.
> int sum = res.stream().mapToInt(Integer::intValue).sum();
> log.info("Total number of characters is '" + sum + "'.");
> }
> }
> {code}
> {panel:title=Exception}
> 2020-05-28 07:00:48.786 INFO 8460 --- [nio-8080-exec-1]
> o.a.i.i.m.d.GridDeploymentLocalStore : Cla
[jira] [Commented] (IGNITE-13094) java.lang.ClassNotFoundException: ch.qos.logback for distributed compute
[
https://issues.apache.org/jira/browse/IGNITE-13094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17124177#comment-17124177
]
Ignite TC Bot commented on IGNITE-13094:
{panel:title=Branch: [pull/7887/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5358104&buildTypeId=IgniteTests24Java8_RunAll]
> java.lang.ClassNotFoundException: ch.qos.logback for distributed compute
>
>
> Key: IGNITE-13094
> URL: https://issues.apache.org/jira/browse/IGNITE-13094
> Project: Ignite
> Issue Type: Bug
> Components: compute
>Affects Versions: 2.8.1
> Environment: Ignite 2.8.0
> Spring Boot 2.1.0.RELEASE
> Java 1.8
>Reporter: AK47Sonic
>Assignee: Ilya Kasnacheev
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I try to use spring boot (2.1.0.RELEASE) to run ignite.compute. As spring
> boot + lombok use logback as default, the following codes always throw
> exceptions (2020-05-28 07:00:48.979 WARN 8460 --- [ p2p-#49]
> o.a.i.i.m.d.GridDeploymentCommunication : Failed to resolve class:
> ch.qos.logback). The result (28) could be returned. Seems we see log4j and
> log4j2 on official website. I try to use log4j2 to replace logback. And it
> works fine. Does ignite support logback for distributed compute? Or It is
> just a bug?
> {panel:title=pom.xml}
>
>
> org.springframework.boot
> spring-boot-starter-web
>
>
> org.springframework.boot
> spring-boot-starter-log4j
>
>
>
>
> org.apache.ignite
> ignite-core
> 2.8.0
>
>
> org.apache.ignite
> ignite-spring
> 2.8.0
>
>
> org.projectlombok
> lombok
> 1.18.12
> provided
>
>
> {panel}
> {panel:title=config.xml}
>
> http://www.springframework.org/schema/beans";
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>xmlns:util="http://www.springframework.org/schema/util";
>xsi:schemaLocation="
> http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans.xsd
> http://www.springframework.org/schema/util
> http://www.springframework.org/schema/util/spring-util.xsd";>
> class="org.apache.ignite.configuration.IgniteConfiguration">
>
>
>
>
>
>
>
> class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">
>
>
> 127.0.0.1:48500..48520
>
>
>
>
>
>
>
> class="org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi">
>
>
>
>
>
> {panel}
> {code:java}
> @Configuration
> @ImportResource(locations={"classpath:default-config.xml"})
> public class IgniteConfig {
> @Bean
> public Ignite ignite(IgniteConfiguration igniteConfiguration) {
> Ignite ignite = Ignition.start(igniteConfiguration);
> Ignition.setClientMode(true);
> return ignite;
> }
> }
> @Slf4j
> @RestController
> public class WebController {
> @Autowired
> private Ignite ignite;
> @GetMapping("/compute")
> public void compute() {
> Collection> calls = new ArrayList<>();
> // Iterate through all the words in the sentence and create Callable
> jobs.
> for (final String word : "Count characters using callable".split(" "))
> calls.add(word::length);
> // Execute collection of Callables on the grid.
> Collection res = ignite.compute().call(calls);
> // Add up all the results.
> int sum = res.stream().mapToInt(Integer::intValue).sum();
> log.info("Total number of characters is '" + sum + "'.");
> }
> }
> {code}
> {panel:title=Exception}
> 2020-05-28 07:00:48.786 INFO 8460 --- [nio-8080-exec-1]
> o.a.i.i.m.d.GridDeploymentLocalStore : Class locally deployed: class
> com.sonic.sample.springboot.controller.WebController
> 2020-05-28 07:00:48.890 WARN 8460 --- [p2p-#49]
> o.a.i.i.m.d.GridDeploymentCommunication : Failed to resolve class:
> ch.qos.logback
> java.lang.ClassNotFoundException: ch.qos.logback
> at java.net.URLClassLoader.find
[jira] [Commented] (IGNITE-13094) java.lang.ClassNotFoundException: ch.qos.logback for distributed compute
[
https://issues.apache.org/jira/browse/IGNITE-13094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17124179#comment-17124179
]
Ilya Kasnacheev commented on IGNITE-13094:
--
[~Pavlukhin] please review proposed fix.
> java.lang.ClassNotFoundException: ch.qos.logback for distributed compute
>
>
> Key: IGNITE-13094
> URL: https://issues.apache.org/jira/browse/IGNITE-13094
> Project: Ignite
> Issue Type: Bug
> Components: compute
>Affects Versions: 2.8.1
> Environment: Ignite 2.8.0
> Spring Boot 2.1.0.RELEASE
> Java 1.8
>Reporter: AK47Sonic
>Assignee: Ilya Kasnacheev
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I try to use spring boot (2.1.0.RELEASE) to run ignite.compute. As spring
> boot + lombok use logback as default, the following codes always throw
> exceptions (2020-05-28 07:00:48.979 WARN 8460 --- [ p2p-#49]
> o.a.i.i.m.d.GridDeploymentCommunication : Failed to resolve class:
> ch.qos.logback). The result (28) could be returned. Seems we see log4j and
> log4j2 on official website. I try to use log4j2 to replace logback. And it
> works fine. Does ignite support logback for distributed compute? Or It is
> just a bug?
> {panel:title=pom.xml}
>
>
> org.springframework.boot
> spring-boot-starter-web
>
>
> org.springframework.boot
> spring-boot-starter-log4j
>
>
>
>
> org.apache.ignite
> ignite-core
> 2.8.0
>
>
> org.apache.ignite
> ignite-spring
> 2.8.0
>
>
> org.projectlombok
> lombok
> 1.18.12
> provided
>
>
> {panel}
> {panel:title=config.xml}
>
> http://www.springframework.org/schema/beans";
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>xmlns:util="http://www.springframework.org/schema/util";
>xsi:schemaLocation="
> http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans.xsd
> http://www.springframework.org/schema/util
> http://www.springframework.org/schema/util/spring-util.xsd";>
> class="org.apache.ignite.configuration.IgniteConfiguration">
>
>
>
>
>
>
>
> class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">
>
>
> 127.0.0.1:48500..48520
>
>
>
>
>
>
>
> class="org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi">
>
>
>
>
>
> {panel}
> {code:java}
> @Configuration
> @ImportResource(locations={"classpath:default-config.xml"})
> public class IgniteConfig {
> @Bean
> public Ignite ignite(IgniteConfiguration igniteConfiguration) {
> Ignite ignite = Ignition.start(igniteConfiguration);
> Ignition.setClientMode(true);
> return ignite;
> }
> }
> @Slf4j
> @RestController
> public class WebController {
> @Autowired
> private Ignite ignite;
> @GetMapping("/compute")
> public void compute() {
> Collection> calls = new ArrayList<>();
> // Iterate through all the words in the sentence and create Callable
> jobs.
> for (final String word : "Count characters using callable".split(" "))
> calls.add(word::length);
> // Execute collection of Callables on the grid.
> Collection res = ignite.compute().call(calls);
> // Add up all the results.
> int sum = res.stream().mapToInt(Integer::intValue).sum();
> log.info("Total number of characters is '" + sum + "'.");
> }
> }
> {code}
> {panel:title=Exception}
> 2020-05-28 07:00:48.786 INFO 8460 --- [nio-8080-exec-1]
> o.a.i.i.m.d.GridDeploymentLocalStore : Class locally deployed: class
> com.sonic.sample.springboot.controller.WebController
> 2020-05-28 07:00:48.890 WARN 8460 --- [p2p-#49]
> o.a.i.i.m.d.GridDeploymentCommunication : Failed to resolve class:
> ch.qos.logback
> java.lang.ClassNotFoundException: ch.qos.logback
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> ~[na:1.8.0_121]
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424) ~[na:1.8.0_121]
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> ~[na:1.8.0_121]
> at
[jira] [Updated] (IGNITE-13100) ClassCastException in cache group metrics on client nodes
[
https://issues.apache.org/jira/browse/IGNITE-13100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-13100:
--
Labels: metrics (was: )
> ClassCastException in cache group metrics on client nodes
> -
>
> Key: IGNITE-13100
> URL: https://issues.apache.org/jira/browse/IGNITE-13100
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
>Priority: Major
> Labels: metrics
> Fix For: 2.9
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> The following exception can be observed when reading cache group metrics on
> client nodes with persistence-enabled config:
> {code}
> java.lang.ClassCastException:
> org.apache.ignite.internal.processors.cache.persistence.IgniteCacheDatabaseSharedManager
> cannot be cast to
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager
> at
> org.apache.ignite.internal.processors.cache.CacheGroupMetricsImpl.database(CacheGroupMetricsImpl.java:506)
> at
> org.apache.ignite.internal.processors.cache.CacheGroupMetricsImpl.lambda$new$0(CacheGroupMetricsImpl.java:103)
> at
> org.apache.ignite.internal.util.lang.GridFunc.lambda$nonThrowableSupplier$3(GridFunc.java:3341)
> at
> org.apache.ignite.internal.processors.metric.impl.LongGauge.value(LongGauge.java:45)
> at
> org.apache.ignite.spi.metric.LongMetric.getAsString(LongMetric.java:29)
> {code}
> The reason is an incomplete check for persistence enabled in
> {{CacheGroupMetricsImpl}}: we should also check for client nodes.
> Suggested solution: include the check for client node mode for database
> metrics readings
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-13100) ClassCastException in cache group metrics on client nodes
[
https://issues.apache.org/jira/browse/IGNITE-13100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-13100:
--
Labels: (was: metrics)
> ClassCastException in cache group metrics on client nodes
> -
>
> Key: IGNITE-13100
> URL: https://issues.apache.org/jira/browse/IGNITE-13100
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
>Priority: Major
> Fix For: 2.9
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> The following exception can be observed when reading cache group metrics on
> client nodes with persistence-enabled config:
> {code}
> java.lang.ClassCastException:
> org.apache.ignite.internal.processors.cache.persistence.IgniteCacheDatabaseSharedManager
> cannot be cast to
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager
> at
> org.apache.ignite.internal.processors.cache.CacheGroupMetricsImpl.database(CacheGroupMetricsImpl.java:506)
> at
> org.apache.ignite.internal.processors.cache.CacheGroupMetricsImpl.lambda$new$0(CacheGroupMetricsImpl.java:103)
> at
> org.apache.ignite.internal.util.lang.GridFunc.lambda$nonThrowableSupplier$3(GridFunc.java:3341)
> at
> org.apache.ignite.internal.processors.metric.impl.LongGauge.value(LongGauge.java:45)
> at
> org.apache.ignite.spi.metric.LongMetric.getAsString(LongMetric.java:29)
> {code}
> The reason is an incomplete check for persistence enabled in
> {{CacheGroupMetricsImpl}}: we should also check for client nodes.
> Suggested solution: include the check for client node mode for database
> metrics readings
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-13100) ClassCastException in cache group metrics on client nodes
[
https://issues.apache.org/jira/browse/IGNITE-13100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Ivanov updated IGNITE-13100:
--
Description:
The following exception can be observed when reading cache group metrics on
client nodes with persistence-enabled config:
{code}
java.lang.ClassCastException:
org.apache.ignite.internal.processors.cache.persistence.IgniteCacheDatabaseSharedManager
cannot be cast to
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager
at
org.apache.ignite.internal.processors.cache.CacheGroupMetricsImpl.database(CacheGroupMetricsImpl.java:506)
at
org.apache.ignite.internal.processors.cache.CacheGroupMetricsImpl.lambda$new$0(CacheGroupMetricsImpl.java:103)
at
org.apache.ignite.internal.util.lang.GridFunc.lambda$nonThrowableSupplier$3(GridFunc.java:3341)
at
org.apache.ignite.internal.processors.metric.impl.LongGauge.value(LongGauge.java:45)
at
org.apache.ignite.spi.metric.LongMetric.getAsString(LongMetric.java:29)
{code}
The reason is an incomplete check for persistence enabled in
{{CacheGroupMetricsImpl}}: we should also check for client nodes.
Suggested solution: include the check for client node mode for database metrics
readings
was:
The following exception can be observed when reading cache group metrics on
client nodes with persistence-enabled config:
{code}
java.lang.ClassCastException:
org.apache.ignite.internal.processors.cache.persistence.IgniteCacheDatabaseSharedManager
cannot be cast to
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager
at
org.apache.ignite.internal.processors.cache.CacheGroupMetricsImpl.database(CacheGroupMetricsImpl.java:506)
at
org.apache.ignite.internal.processors.cache.CacheGroupMetricsImpl.lambda$new$0(CacheGroupMetricsImpl.java:103)
at
org.apache.ignite.internal.util.lang.GridFunc.lambda$nonThrowableSupplier$3(GridFunc.java:3341)
at
org.apache.ignite.internal.processors.metric.impl.LongGauge.value(LongGauge.java:45)
at
org.apache.ignite.spi.metric.LongMetric.getAsString(LongMetric.java:29)
{code}
The reason is an incomplete check for persistence enabled in
{{CacheGroupMetricsImpl}}: we should also check for client nodes.
Suggested solution: include the check for client node mode for database metrics
readings
> ClassCastException in cache group metrics on client nodes
> -
>
> Key: IGNITE-13100
> URL: https://issues.apache.org/jira/browse/IGNITE-13100
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
>Priority: Major
> Fix For: 2.9
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> The following exception can be observed when reading cache group metrics on
> client nodes with persistence-enabled config:
> {code}
> java.lang.ClassCastException:
> org.apache.ignite.internal.processors.cache.persistence.IgniteCacheDatabaseSharedManager
> cannot be cast to
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager
> at
> org.apache.ignite.internal.processors.cache.CacheGroupMetricsImpl.database(CacheGroupMetricsImpl.java:506)
> at
> org.apache.ignite.internal.processors.cache.CacheGroupMetricsImpl.lambda$new$0(CacheGroupMetricsImpl.java:103)
> at
> org.apache.ignite.internal.util.lang.GridFunc.lambda$nonThrowableSupplier$3(GridFunc.java:3341)
> at
> org.apache.ignite.internal.processors.metric.impl.LongGauge.value(LongGauge.java:45)
> at
> org.apache.ignite.spi.metric.LongMetric.getAsString(LongMetric.java:29)
> {code}
> The reason is an incomplete check for persistence enabled in
> {{CacheGroupMetricsImpl}}: we should also check for client nodes.
> Suggested solution: include the check for client node mode for database
> metrics readings
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-13100) ClassCastException in cache group metrics on client nodes
[
https://issues.apache.org/jira/browse/IGNITE-13100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Ivanov updated IGNITE-13100:
--
Description:
The following exception can be observed when reading cache group metrics on
client nodes with persistence-enabled config:
{code}
java.lang.ClassCastException:
org.apache.ignite.internal.processors.cache.persistence.IgniteCacheDatabaseSharedManager
cannot be cast to
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager
at
org.apache.ignite.internal.processors.cache.CacheGroupMetricsImpl.database(CacheGroupMetricsImpl.java:506)
at
org.apache.ignite.internal.processors.cache.CacheGroupMetricsImpl.lambda$new$0(CacheGroupMetricsImpl.java:103)
at
org.apache.ignite.internal.util.lang.GridFunc.lambda$nonThrowableSupplier$3(GridFunc.java:3341)
at
org.apache.ignite.internal.processors.metric.impl.LongGauge.value(LongGauge.java:45)
at
org.apache.ignite.spi.metric.LongMetric.getAsString(LongMetric.java:29)
{code}
The reason is an incomplete check for persistence enabled in
{{CacheGroupMetricsImpl}}: we should also check for client nodes.
Suggested solution: include the check for client node mode for database metrics
readings
was:
The following exception can be observed when reading cache group metrics on
client nodes with persistence-enabled config:
{code}
java.lang.ClassCastException:
org.apache.ignite.internal.processors.cache.persistence.IgniteCacheDatabaseSharedManager
cannot be cast to
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager
at
org.apache.ignite.internal.processors.cache.CacheGroupMetricsImpl.database(CacheGroupMetricsImpl.java:506)
at
org.apache.ignite.internal.processors.cache.CacheGroupMetricsImpl.lambda$new$0(CacheGroupMetricsImpl.java:103)
at
org.apache.ignite.internal.util.lang.GridFunc.lambda$nonThrowableSupplier$3(GridFunc.java:3341)
at
org.apache.ignite.internal.processors.metric.impl.LongGauge.value(LongGauge.java:45)
at
org.apache.ignite.spi.metric.LongMetric.getAsString(LongMetric.java:29)
{code}
The reason is an incomplete check for persistence enabled in
{{CacheGroupMetricsImpl}}: we should also check for client nodes.
Suggested solution: include the check for client node mode for database metrics
readings
> ClassCastException in cache group metrics on client nodes
> -
>
> Key: IGNITE-13100
> URL: https://issues.apache.org/jira/browse/IGNITE-13100
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
>Priority: Major
> Fix For: 2.9
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> The following exception can be observed when reading cache group metrics on
> client nodes with persistence-enabled config:
> {code}
> java.lang.ClassCastException:
> org.apache.ignite.internal.processors.cache.persistence.IgniteCacheDatabaseSharedManager
> cannot be cast to
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager
> at
> org.apache.ignite.internal.processors.cache.CacheGroupMetricsImpl.database(CacheGroupMetricsImpl.java:506)
> at
> org.apache.ignite.internal.processors.cache.CacheGroupMetricsImpl.lambda$new$0(CacheGroupMetricsImpl.java:103)
> at
> org.apache.ignite.internal.util.lang.GridFunc.lambda$nonThrowableSupplier$3(GridFunc.java:3341)
> at
> org.apache.ignite.internal.processors.metric.impl.LongGauge.value(LongGauge.java:45)
> at
> org.apache.ignite.spi.metric.LongMetric.getAsString(LongMetric.java:29)
> {code}
> The reason is an incomplete check for persistence enabled in
> {{CacheGroupMetricsImpl}}: we should also check for client nodes.
> Suggested solution: include the check for client node mode for database
> metrics readings
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13095) .NET: Thin Client Compute does not cancel task on server when cancelled on client
[
https://issues.apache.org/jira/browse/IGNITE-13095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17124126#comment-17124126
]
Ignite TC Bot commented on IGNITE-13095:
{panel:title=Branch: [pull/7883/head] Base: [master] : Possible Blockers
(7)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 6{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5357135]]
{color:#d04437}Cache 7{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5357136]]
{color:#d04437}PDS 3{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5357149]]
* IgnitePdsTestSuite3:
IgnitePdsContinuousRestartTest.testRebalancingDuringLoad_8000_8000_1_1 - Test
has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Platform .NET{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5357214]]
* exe: ComputeClientTests.TestExecuteJavaTaskAsyncCancellation - Test has low
fail rate in base branch 0,0% and is not flaky
{color:#d04437}Platform .NET (Core Linux){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5358147]]
* dll: ComputeClientTests.TestExecuteJavaTaskAsyncCancellation - Test has low
fail rate in base branch 0,0% and is not flaky
{color:#d04437}Streamers{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5357095]]
* IgniteMqttStreamerTestSuite:
IgniteMqttStreamerTest.testSingleTopic_NoQoS_ConnectOptions_Durable - Test has
low fail rate in base branch 0,0% and is not flaky
{color:#d04437}~Build Apache Ignite~{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5358520]]
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5358636&buildTypeId=IgniteTests24Java8_RunAll]
> .NET: Thin Client Compute does not cancel task on server when cancelled on
> client
> -
>
> Key: IGNITE-13095
> URL: https://issues.apache.org/jira/browse/IGNITE-13095
> Project: Ignite
> Issue Type: New Feature
> Components: platforms, thin client
>Affects Versions: 2.9
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: .NET
> Fix For: 2.9
>
> Original Estimate: 3h
> Time Spent: 10m
> Remaining Estimate: 2h 50m
>
> Client should call OP_RESOURCE_CLOSE to cancel the task on server side.
> Test this by reading server logs, "Job was cancelled" should be there.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13095) .NET: Thin Client Compute does not cancel task on server when cancelled on client
[ https://issues.apache.org/jira/browse/IGNITE-13095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17124089#comment-17124089 ] Pavel Tupitsyn commented on IGNITE-13095: - [~isapego] [~ashapkin] PR ready, please have a look. Sorry for some whitespace-only changes. > .NET: Thin Client Compute does not cancel task on server when cancelled on > client > - > > Key: IGNITE-13095 > URL: https://issues.apache.org/jira/browse/IGNITE-13095 > Project: Ignite > Issue Type: New Feature > Components: platforms, thin client >Affects Versions: 2.9 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: .NET > Fix For: 2.9 > > Original Estimate: 3h > Time Spent: 10m > Remaining Estimate: 2h 50m > > Client should call OP_RESOURCE_CLOSE to cancel the task on server side. > Test this by reading server logs, "Job was cancelled" should be there. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-7105) .NET: IIgnite.ReentrantLock
[
https://issues.apache.org/jira/browse/IGNITE-7105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn reassigned IGNITE-7105:
--
Assignee: Pavel Tupitsyn
> .NET: IIgnite.ReentrantLock
> ---
>
> Key: IGNITE-7105
> URL: https://issues.apache.org/jira/browse/IGNITE-7105
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Minor
> Labels: .NET, newbie
>
> Propagate {{Ignite.reentrantLock}} to .NET.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-13105) Spring data 2.0 IgniteRepositoryQuery#transformQueryCursor contains cursor leak
[
https://issues.apache.org/jira/browse/IGNITE-13105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Kuznetsov updated IGNITE-13105:
--
Ignite Flags: Release Notes Required (was: Docs Required,Release Notes
Required)
> Spring data 2.0 IgniteRepositoryQuery#transformQueryCursor contains cursor
> leak
> ---
>
> Key: IGNITE-13105
> URL: https://issues.apache.org/jira/browse/IGNITE-13105
> Project: Ignite
> Issue Type: Improvement
> Components: springdata
>Affects Versions: 2.8.1
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
>Priority: Critical
> Fix For: 2.9
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> This code produce cursor leak in RunningQueryManager:
> If result set contains one ore more rows.
> {code}
> case ONE_VALUE:
> Iterator iter = qryIter.iterator();
> if (iter.hasNext())
> return iter.next().get(0);
> return null;
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13086) Improve current page replacement mechanism.
[ https://issues.apache.org/jira/browse/IGNITE-13086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17124004#comment-17124004 ] Stanilovsky Evgeny commented on IGNITE-13086: - [~alex_pl] could you take a look ? > Improve current page replacement mechanism. > --- > > Key: IGNITE-13086 > URL: https://issues.apache.org/jira/browse/IGNITE-13086 > Project: Ignite > Issue Type: Improvement > Components: persistence >Affects Versions: 2.8.1 >Reporter: Stanilovsky Evgeny >Assignee: Stanilovsky Evgeny >Priority: Major > Attachments: 8.7-fix-replacement400_rand_512val_5touch_oldts.log, > 8.7-replacement400_rand_512val_5touch_oldts.log, > IgnitePdsPageReplacementTestToYard.java, replacement_64_new.jfr.zip, > replacement_64_old.jfr.zip, screenshot-1.png > > Time Spent: 10m > Remaining Estimate: 0h > > Experimentally proven that current page replacement functionality has > problems with replace candidate computation. Current implementation obtain 5 > random pages and make further decisions basing this pages last touch > timestamp and some inner flags, however still possible cases when this pages > set can be simply nullified due to inner logic. All improvements need to be > proven, for example, by simple scenario: > 1. put some data until event EVT_PAGE_REPLACEMENT_STARTED is triggered > 2. put 2 times more data than been loaded in p1. > 3. execute fullscan (through ScanQuery) for old\cold data processing > emulation. > 4. start processing only pages which can fit into current mem region. > 5. measure "replacedPages" metric. > (i attach code mention above) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13078) С++: Add CMake build support
[
https://issues.apache.org/jira/browse/IGNITE-13078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17123993#comment-17123993
]
Ivan Daschinskiy commented on IGNITE-13078:
---
Yes, I agree with you. I'd suggest to write something like ${IGNITE_CPP_DIR}.
And, even better, rewrite doc in markdown
> С++: Add CMake build support
>
>
> Key: IGNITE-13078
> URL: https://issues.apache.org/jira/browse/IGNITE-13078
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Reporter: Ivan Daschinskiy
>Assignee: Ivan Daschinskiy
>Priority: Major
> Fix For: 2.9
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, it is hard to build Ignite.C++. Different build process for
> windows and linux, lack of building support on Mac OS X (quite popular OS
> among developers), absolutely not IDE support, except windows and only Visual
> Studio is supported.
> I’d suggest to migrate to CMake build system. It is very popular among open
> source projects, and in Apache Software Foundation too. Notable user: Apache
> Mesos, Apache Zookeeper (C client offers CMake as an alternative to autoconf
> and only option on windows), Apache Kafka (librdkafka - C/C++ client), Apache
> Thrift. Popular column-oriented database ClickHouse also uses CMake.
> CMake is widely supported in many IDE’s on various platforms, notably Visual
> Studio, CLion, Xcode, QtCreator, KDevelop.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13078) С++: Add CMake build support
[ https://issues.apache.org/jira/browse/IGNITE-13078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17123981#comment-17123981 ] Ilya Kasnacheev commented on IGNITE-13078: -- [~ivandasch] Please see above. It was not completely obvious that path is needed. > С++: Add CMake build support > > > Key: IGNITE-13078 > URL: https://issues.apache.org/jira/browse/IGNITE-13078 > Project: Ignite > Issue Type: Improvement > Components: platforms >Reporter: Ivan Daschinskiy >Assignee: Ivan Daschinskiy >Priority: Major > Fix For: 2.9 > > Time Spent: 10m > Remaining Estimate: 0h > > Currently, it is hard to build Ignite.C++. Different build process for > windows and linux, lack of building support on Mac OS X (quite popular OS > among developers), absolutely not IDE support, except windows and only Visual > Studio is supported. > I’d suggest to migrate to CMake build system. It is very popular among open > source projects, and in Apache Software Foundation too. Notable user: Apache > Mesos, Apache Zookeeper (C client offers CMake as an alternative to autoconf > and only option on windows), Apache Kafka (librdkafka - C/C++ client), Apache > Thrift. Popular column-oriented database ClickHouse also uses CMake. > CMake is widely supported in many IDE’s on various platforms, notably Visual > Studio, CLion, Xcode, QtCreator, KDevelop. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13078) С++: Add CMake build support
[ https://issues.apache.org/jira/browse/IGNITE-13078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17123979#comment-17123979 ] Ivan Daschinskiy commented on IGNITE-13078: --- You can in fact add full path at the end > С++: Add CMake build support > > > Key: IGNITE-13078 > URL: https://issues.apache.org/jira/browse/IGNITE-13078 > Project: Ignite > Issue Type: Improvement > Components: platforms >Reporter: Ivan Daschinskiy >Assignee: Ivan Daschinskiy >Priority: Major > Fix For: 2.9 > > Time Spent: 10m > Remaining Estimate: 0h > > Currently, it is hard to build Ignite.C++. Different build process for > windows and linux, lack of building support on Mac OS X (quite popular OS > among developers), absolutely not IDE support, except windows and only Visual > Studio is supported. > I’d suggest to migrate to CMake build system. It is very popular among open > source projects, and in Apache Software Foundation too. Notable user: Apache > Mesos, Apache Zookeeper (C client offers CMake as an alternative to autoconf > and only option on windows), Apache Kafka (librdkafka - C/C++ client), Apache > Thrift. Popular column-oriented database ClickHouse also uses CMake. > CMake is widely supported in many IDE’s on various platforms, notably Visual > Studio, CLion, Xcode, QtCreator, KDevelop. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-13078) С++: Add CMake build support
[
https://issues.apache.org/jira/browse/IGNITE-13078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17123977#comment-17123977
]
Ilya Kasnacheev edited comment on IGNITE-13078 at 6/2/20, 4:09 PM:
---
Okay, okay, I get it, I have missed `..' at the end. After I do that, it works
OK.
Can we update the following line:
{code}
* cmake -DCMAKE_BUILD_TYPE=[Release|Debug]
[-DCMAKE_INSTALL_PREFIX=] ..
{code}
to
{code}
* cmake .. -DCMAKE_BUILD_TYPE={Release|Debug}
[-DCMAKE_INSTALL_PREFIX=]
{code}
to make it more apparent?
was (Author: ilyak):
Okay, okay, I get it, I have missed `..' at the end. After I do that, it works
OK.
Can we update the following line:
{code}
* cmake -DCMAKE_BUILD_TYPE=[Release|Debug]
[-DCMAKE_INSTALL_PREFIX=] ..
{code}
to
{code}
* cmake .. -DCMAKE_BUILD_TYPE=[Release|Debug]
[-DCMAKE_INSTALL_PREFIX=]
{code}
to make it more apparent?
> С++: Add CMake build support
>
>
> Key: IGNITE-13078
> URL: https://issues.apache.org/jira/browse/IGNITE-13078
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Reporter: Ivan Daschinskiy
>Assignee: Ivan Daschinskiy
>Priority: Major
> Fix For: 2.9
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, it is hard to build Ignite.C++. Different build process for
> windows and linux, lack of building support on Mac OS X (quite popular OS
> among developers), absolutely not IDE support, except windows and only Visual
> Studio is supported.
> I’d suggest to migrate to CMake build system. It is very popular among open
> source projects, and in Apache Software Foundation too. Notable user: Apache
> Mesos, Apache Zookeeper (C client offers CMake as an alternative to autoconf
> and only option on windows), Apache Kafka (librdkafka - C/C++ client), Apache
> Thrift. Popular column-oriented database ClickHouse also uses CMake.
> CMake is widely supported in many IDE’s on various platforms, notably Visual
> Studio, CLion, Xcode, QtCreator, KDevelop.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13078) С++: Add CMake build support
[
https://issues.apache.org/jira/browse/IGNITE-13078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17123977#comment-17123977
]
Ilya Kasnacheev commented on IGNITE-13078:
--
Okay, okay, I get it, I have missed `..' at the end. After I do that, it works
OK.
Can we update the following line:
{code}
* cmake -DCMAKE_BUILD_TYPE=[Release|Debug]
[-DCMAKE_INSTALL_PREFIX=] ..
{code}
to
{code}
* cmake .. -DCMAKE_BUILD_TYPE=[Release|Debug]
[-DCMAKE_INSTALL_PREFIX=]
{code}
to make it more apparent?
> С++: Add CMake build support
>
>
> Key: IGNITE-13078
> URL: https://issues.apache.org/jira/browse/IGNITE-13078
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Reporter: Ivan Daschinskiy
>Assignee: Ivan Daschinskiy
>Priority: Major
> Fix For: 2.9
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, it is hard to build Ignite.C++. Different build process for
> windows and linux, lack of building support on Mac OS X (quite popular OS
> among developers), absolutely not IDE support, except windows and only Visual
> Studio is supported.
> I’d suggest to migrate to CMake build system. It is very popular among open
> source projects, and in Apache Software Foundation too. Notable user: Apache
> Mesos, Apache Zookeeper (C client offers CMake as an alternative to autoconf
> and only option on windows), Apache Kafka (librdkafka - C/C++ client), Apache
> Thrift. Popular column-oriented database ClickHouse also uses CMake.
> CMake is widely supported in many IDE’s on various platforms, notably Visual
> Studio, CLion, Xcode, QtCreator, KDevelop.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13078) С++: Add CMake build support
[ https://issues.apache.org/jira/browse/IGNITE-13078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17123973#comment-17123973 ] Ivan Daschinskiy commented on IGNITE-13078: --- @ilyak you forgot two dots at the end > С++: Add CMake build support > > > Key: IGNITE-13078 > URL: https://issues.apache.org/jira/browse/IGNITE-13078 > Project: Ignite > Issue Type: Improvement > Components: platforms >Reporter: Ivan Daschinskiy >Assignee: Ivan Daschinskiy >Priority: Major > Fix For: 2.9 > > Time Spent: 10m > Remaining Estimate: 0h > > Currently, it is hard to build Ignite.C++. Different build process for > windows and linux, lack of building support on Mac OS X (quite popular OS > among developers), absolutely not IDE support, except windows and only Visual > Studio is supported. > I’d suggest to migrate to CMake build system. It is very popular among open > source projects, and in Apache Software Foundation too. Notable user: Apache > Mesos, Apache Zookeeper (C client offers CMake as an alternative to autoconf > and only option on windows), Apache Kafka (librdkafka - C/C++ client), Apache > Thrift. Popular column-oriented database ClickHouse also uses CMake. > CMake is widely supported in many IDE’s on various platforms, notably Visual > Studio, CLion, Xcode, QtCreator, KDevelop. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13078) С++: Add CMake build support
[
https://issues.apache.org/jira/browse/IGNITE-13078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17123969#comment-17123969
]
Ilya Kasnacheev commented on IGNITE-13078:
--
[~ivandasch] I think this means that DEVNOTES is not correct:
{code}
Building and installing the Apache Ignite C++ components:
* Navigate to the directory $IGNITE_HOME/platforms/cpp
* Execute the following commands one by one to build the project:
* mkdir cmake-build-[release|debug]
* cd ./cmake-build-[release|debug]
* cmake -DCMAKE_BUILD_TYPE=[Release|Debug]
[-DCMAKE_INSTALL_PREFIX=] ..
{code}
but
{code}
~/w/incubator-ignite/modules/platforms/cpp% mkdir cmake-build-release
~/w/incubator-ignite/modules/platforms/cpp% cd cmake-build-release
~/w/incubator-ignite/modules/platforms/cpp/cmake-build-release% cmake
-DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=~ -DWITH_ODBC=ON
-DWITH_THIN_CLIENT=ON
CMake Error: The source directory
"/home/gridgain/w/incubator-ignite/modules/platforms/cpp/cmake-build-release"
does not appear to contain CMakeLists.txt.
Specify --help for usage, or press the help button on the CMake GUI.
{code}
What's wrong? From the cpp/ directory it builds.
> С++: Add CMake build support
>
>
> Key: IGNITE-13078
> URL: https://issues.apache.org/jira/browse/IGNITE-13078
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Reporter: Ivan Daschinskiy
>Assignee: Ivan Daschinskiy
>Priority: Major
> Fix For: 2.9
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, it is hard to build Ignite.C++. Different build process for
> windows and linux, lack of building support on Mac OS X (quite popular OS
> among developers), absolutely not IDE support, except windows and only Visual
> Studio is supported.
> I’d suggest to migrate to CMake build system. It is very popular among open
> source projects, and in Apache Software Foundation too. Notable user: Apache
> Mesos, Apache Zookeeper (C client offers CMake as an alternative to autoconf
> and only option on windows), Apache Kafka (librdkafka - C/C++ client), Apache
> Thrift. Popular column-oriented database ClickHouse also uses CMake.
> CMake is widely supported in many IDE’s on various platforms, notably Visual
> Studio, CLion, Xcode, QtCreator, KDevelop.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-5214) ConcurrentModificationException with enable DEBUG log level
[
https://issues.apache.org/jira/browse/IGNITE-5214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17123887#comment-17123887
]
Alexander Korenshteyn commented on IGNITE-5214:
---
[~ilyak] Fix looks good!
> ConcurrentModificationException with enable DEBUG log level
> ---
>
> Key: IGNITE-5214
> URL: https://issues.apache.org/jira/browse/IGNITE-5214
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Nikolay Tikhonov
>Assignee: Ilya Kasnacheev
>Priority: Major
> Attachments: IGNITE_5214.patch
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> ConcurrentModificationException with
> org.apache.ignite.continuous.query=DEBUG
> {noformat}
> Unexpected exception during cache update
> java.util.ConcurrentModificationException: null
> at java.util.TreeMap$PrivateEntryIterator.nextEntry(TreeMap.java:1211)
> at java.util.TreeMap$EntryIterator.next(TreeMap.java:1247)
> at java.util.TreeMap$EntryIterator.next(TreeMap.java:1242)
> at java.util.AbstractMap.toString(AbstractMap.java:554)
> at java.lang.String.valueOf(String.java:2994)
> at java.lang.StringBuilder.append(StringBuilder.java:131)
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler$PartitionRecovery.collectEntries(CacheContinuousQueryHandler.java:1132)
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.handleEvent(CacheContinuousQueryHandler.java:739)
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.onEntryUpdate(CacheContinuousQueryHandler.java:792)
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.access$800(CacheContinuousQueryHandler.java:91)
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler$1.onEntryUpdated(CacheContinuousQueryHandler.java:419)
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryManager.onEntryUpdated(CacheContinuousQueryManager.java:347)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.innerUpdate(GridCacheMapEntry.java:2669)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateSingle(GridDhtAtomicCache.java:2390)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1792)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1632)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.mapSingle(GridNearAtomicAbstractUpdateFuture.java:263)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.map(GridNearAtomicSingleUpdateFuture.java:494)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.mapOnTopology(GridNearAtomicSingleUpdateFuture.java:436)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.map(GridNearAtomicAbstractUpdateFuture.java:208)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$23.apply(GridDhtAtomicCache.java:1152)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$23.apply(GridDhtAtomicCache.java:1150)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.asyncOp(GridDhtAtomicCache.java:847)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAsync0(GridDhtAtomicCache.java:1150)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.putAsync0(GridDhtAtomicCache.java:619)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.putAsync(GridCacheAdapter.java:2574)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.putIfAbsentAsync(GridDhtAtomicCache.java:664)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.putIfAbsent(GridDhtAtomicCache.java:657)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.putIfAbsent(IgniteCacheProxy.java:1451)
> at
> com.workday.fabric.ignite.management.IgniteManagementService.doExecute(IgniteManagementService.java:174)
> at
> com.workday.fabric.ignite.service.AbstractIgniteService.execu
[jira] [Updated] (IGNITE-13100) ClassCastException in cache group metrics on client nodes
[
https://issues.apache.org/jira/browse/IGNITE-13100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-13100:
--
Labels: metrics (was: )
> ClassCastException in cache group metrics on client nodes
> -
>
> Key: IGNITE-13100
> URL: https://issues.apache.org/jira/browse/IGNITE-13100
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
>Priority: Major
> Labels: metrics
> Fix For: 2.9
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> The following exception can be observed when reading cache group metrics on
> client nodes with persistence-enabled config:
> {code}
> java.lang.ClassCastException:
> org.apache.ignite.internal.processors.cache.persistence.IgniteCacheDatabaseSharedManager
> cannot be cast to
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager
> at
> org.apache.ignite.internal.processors.cache.CacheGroupMetricsImpl.database(CacheGroupMetricsImpl.java:506)
> at
> org.apache.ignite.internal.processors.cache.CacheGroupMetricsImpl.lambda$new$0(CacheGroupMetricsImpl.java:103)
> at
> org.apache.ignite.internal.util.lang.GridFunc.lambda$nonThrowableSupplier$3(GridFunc.java:3341)
> at
> org.apache.ignite.internal.processors.metric.impl.LongGauge.value(LongGauge.java:45)
> at
> org.apache.ignite.spi.metric.LongMetric.getAsString(LongMetric.java:29)
> {code}
> The reason is an incomplete check for persistence enabled in
> {{CacheGroupMetricsImpl}}: we should also check for client nodes.
> Suggested solution: include the check for client node mode for database
> metrics readings
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-13100) ClassCastException in cache group metrics on client nodes
[
https://issues.apache.org/jira/browse/IGNITE-13100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-13100:
--
Labels: (was: metrics)
> ClassCastException in cache group metrics on client nodes
> -
>
> Key: IGNITE-13100
> URL: https://issues.apache.org/jira/browse/IGNITE-13100
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
>Priority: Major
> Fix For: 2.9
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> The following exception can be observed when reading cache group metrics on
> client nodes with persistence-enabled config:
> {code}
> java.lang.ClassCastException:
> org.apache.ignite.internal.processors.cache.persistence.IgniteCacheDatabaseSharedManager
> cannot be cast to
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager
> at
> org.apache.ignite.internal.processors.cache.CacheGroupMetricsImpl.database(CacheGroupMetricsImpl.java:506)
> at
> org.apache.ignite.internal.processors.cache.CacheGroupMetricsImpl.lambda$new$0(CacheGroupMetricsImpl.java:103)
> at
> org.apache.ignite.internal.util.lang.GridFunc.lambda$nonThrowableSupplier$3(GridFunc.java:3341)
> at
> org.apache.ignite.internal.processors.metric.impl.LongGauge.value(LongGauge.java:45)
> at
> org.apache.ignite.spi.metric.LongMetric.getAsString(LongMetric.java:29)
> {code}
> The reason is an incomplete check for persistence enabled in
> {{CacheGroupMetricsImpl}}: we should also check for client nodes.
> Suggested solution: include the check for client node mode for database
> metrics readings
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13103) Investigate marshalling errors when changing fields of lambda's capturingClass
[
https://issues.apache.org/jira/browse/IGNITE-13103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17123792#comment-17123792
]
Ilya Kasnacheev commented on IGNITE-13103:
--
Please review proposed Class fields marshalling change.
[~agoncharuk] [~dmekhanikov]
> Investigate marshalling errors when changing fields of lambda's capturingClass
> --
>
> Key: IGNITE-13103
> URL: https://issues.apache.org/jira/browse/IGNITE-13103
> Project: Ignite
> Issue Type: Bug
> Components: binary, compute
>Affects Versions: 2.8.1
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Major
> Attachments: deployer.zip
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Trying to execute static lambda whose outer type's fields changed leads to
> the following error:
> {code}
> Exception in thread "main" class org.apache.ignite.IgniteException: Remote
> job threw user exception (override or implement ComputeTask.result(..) method
> if you would like to have automatic failover for this exception): Failed to
> serialize object
> [typeName=org.apache.ignite.internal.processors.closure.GridClosureProcessor$C4]
> at
> org.apache.ignite.compute.ComputeTaskAdapter.result(ComputeTaskAdapter.java:102)
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker$5.apply(GridTaskWorker.java:1062)
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker$5.apply(GridTaskWorker.java:1055)
> at
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:7037)
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.result(GridTaskWorker.java:1055)
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.onResponse(GridTaskWorker.java:862)
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.processDelayedResponses(GridTaskWorker.java:711)
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.body(GridTaskWorker.java:542)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at
> org.apache.ignite.internal.processors.task.GridTaskProcessor.startTask(GridTaskProcessor.java:829)
> at
> org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:497)
> at
> org.apache.ignite.internal.processors.closure.GridClosureProcessor.runAsync(GridClosureProcessor.java:244)
> at
> org.apache.ignite.internal.processors.closure.GridClosureProcessor.runAsync(GridClosureProcessor.java:216)
> at
> org.apache.ignite.internal.IgniteComputeImpl.runAsync0(IgniteComputeImpl.java:702)
> at
> org.apache.ignite.internal.IgniteComputeImpl.run(IgniteComputeImpl.java:678)
> at
> com.gridgain.deployer.c.ComputeCallerStarter.start(ComputeCallerStarter.java:19)
> at
> com.gridgain.deployer.c.ComputeCallerStarter.main(ComputeCallerStarter.java:13)
> Caused by: class org.apache.ignite.binary.BinaryObjectException: Failed to
> serialize object
> [typeName=org.apache.ignite.internal.processors.closure.GridClosureProcessor$C4]
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:853)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:232)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:165)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:152)
> at
> org.apache.ignite.internal.binary.GridBinaryMarshaller.marshal(GridBinaryMarshaller.java:251)
> at
> org.apache.ignite.internal.binary.BinaryMarshaller.marshal0(BinaryMarshaller.java:84)
> at
> org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.marshal(AbstractNodeNameAwareMarshaller.java:57)
> at
> org.apache.ignite.internal.util.IgniteUtils.marshal(IgniteUtils.java:10386)
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.sendRequest(GridTaskWorker.java:1397)
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.processMappedJobs(GridTaskWorker.java:664)
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.body(GridTaskWorker.java:536)
> ... 9 more
> Caused by: class org.apache.ignite.binary.BinaryObjectException: Failed to
> serialize object [typeName=java.lang.invoke.SerializedLambda]
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:853)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:232)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:1
[jira] [Commented] (IGNITE-13100) ClassCastException in cache group metrics on client nodes
[
https://issues.apache.org/jira/browse/IGNITE-13100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17123790#comment-17123790
]
Ignite TC Bot commented on IGNITE-13100:
{panel:title=Branch: [pull/7875/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5356821&buildTypeId=IgniteTests24Java8_RunAll]
> ClassCastException in cache group metrics on client nodes
> -
>
> Key: IGNITE-13100
> URL: https://issues.apache.org/jira/browse/IGNITE-13100
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
>Priority: Major
> Fix For: 2.9
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The following exception can be observed when reading cache group metrics on
> client nodes with persistence-enabled config:
> {code}
> java.lang.ClassCastException:
> org.apache.ignite.internal.processors.cache.persistence.IgniteCacheDatabaseSharedManager
> cannot be cast to
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager
> at
> org.apache.ignite.internal.processors.cache.CacheGroupMetricsImpl.database(CacheGroupMetricsImpl.java:506)
> at
> org.apache.ignite.internal.processors.cache.CacheGroupMetricsImpl.lambda$new$0(CacheGroupMetricsImpl.java:103)
> at
> org.apache.ignite.internal.util.lang.GridFunc.lambda$nonThrowableSupplier$3(GridFunc.java:3341)
> at
> org.apache.ignite.internal.processors.metric.impl.LongGauge.value(LongGauge.java:45)
> at
> org.apache.ignite.spi.metric.LongMetric.getAsString(LongMetric.java:29)
> {code}
> The reason is an incomplete check for persistence enabled in
> {{CacheGroupMetricsImpl}}: we should also check for client nodes.
> Suggested solution: include the check for client node mode for database
> metrics readings
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13103) Investigate marshalling errors when changing fields of lambda's capturingClass
[
https://issues.apache.org/jira/browse/IGNITE-13103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17123791#comment-17123791
]
Ignite TC Bot commented on IGNITE-13103:
{panel:title=Branch: [pull/7880/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5355031&buildTypeId=IgniteTests24Java8_RunAll]
> Investigate marshalling errors when changing fields of lambda's capturingClass
> --
>
> Key: IGNITE-13103
> URL: https://issues.apache.org/jira/browse/IGNITE-13103
> Project: Ignite
> Issue Type: Bug
> Components: binary, compute
>Affects Versions: 2.8.1
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Major
> Attachments: deployer.zip
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Trying to execute static lambda whose outer type's fields changed leads to
> the following error:
> {code}
> Exception in thread "main" class org.apache.ignite.IgniteException: Remote
> job threw user exception (override or implement ComputeTask.result(..) method
> if you would like to have automatic failover for this exception): Failed to
> serialize object
> [typeName=org.apache.ignite.internal.processors.closure.GridClosureProcessor$C4]
> at
> org.apache.ignite.compute.ComputeTaskAdapter.result(ComputeTaskAdapter.java:102)
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker$5.apply(GridTaskWorker.java:1062)
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker$5.apply(GridTaskWorker.java:1055)
> at
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:7037)
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.result(GridTaskWorker.java:1055)
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.onResponse(GridTaskWorker.java:862)
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.processDelayedResponses(GridTaskWorker.java:711)
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.body(GridTaskWorker.java:542)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at
> org.apache.ignite.internal.processors.task.GridTaskProcessor.startTask(GridTaskProcessor.java:829)
> at
> org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:497)
> at
> org.apache.ignite.internal.processors.closure.GridClosureProcessor.runAsync(GridClosureProcessor.java:244)
> at
> org.apache.ignite.internal.processors.closure.GridClosureProcessor.runAsync(GridClosureProcessor.java:216)
> at
> org.apache.ignite.internal.IgniteComputeImpl.runAsync0(IgniteComputeImpl.java:702)
> at
> org.apache.ignite.internal.IgniteComputeImpl.run(IgniteComputeImpl.java:678)
> at
> com.gridgain.deployer.c.ComputeCallerStarter.start(ComputeCallerStarter.java:19)
> at
> com.gridgain.deployer.c.ComputeCallerStarter.main(ComputeCallerStarter.java:13)
> Caused by: class org.apache.ignite.binary.BinaryObjectException: Failed to
> serialize object
> [typeName=org.apache.ignite.internal.processors.closure.GridClosureProcessor$C4]
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:853)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:232)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:165)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:152)
> at
> org.apache.ignite.internal.binary.GridBinaryMarshaller.marshal(GridBinaryMarshaller.java:251)
> at
> org.apache.ignite.internal.binary.BinaryMarshaller.marshal0(BinaryMarshaller.java:84)
> at
> org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.marshal(AbstractNodeNameAwareMarshaller.java:57)
> at
> org.apache.ignite.internal.util.IgniteUtils.marshal(IgniteUtils.java:10386)
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.sendRequest(GridTaskWorker.java:1397)
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.processMappedJobs(GridTaskWorker.java:664)
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.body(GridTaskWorker.java:536)
> ... 9 more
> Caused by: class org.apache.ignite.binary.BinaryObjectException: Failed to
> serialize object [typeName=java.lang.invoke.SerializedLambda]
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:853)
> at
> org.apa
[jira] [Commented] (IGNITE-13106) Java thin client: Race between response and notification for compute tasks
[
https://issues.apache.org/jira/browse/IGNITE-13106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17123788#comment-17123788
]
Ignite TC Bot commented on IGNITE-13106:
{panel:title=Branch: [pull/7885/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: Basic Tests*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5357718&buildTypeId=IgniteTests24Java8_RunBasicTests]
> Java thin client: Race between response and notification for compute tasks
> ---
>
> Key: IGNITE-13106
> URL: https://issues.apache.org/jira/browse/IGNITE-13106
> Project: Ignite
> Issue Type: Bug
> Components: thin client
>Affects Versions: 2.9
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Java thin client {{ClientCompute.execute()}} method can hang due to race
> between processing of COMPUTE_TASK_EXECUTE response and COMPUTE_TASK_FINISHED
> notification.
> These messages are strongly ordered on the server-side. But on the
> client-side response and notification are processed by different threads. If
> notification will be processed before response, task future will never be
> completed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-13104) Spring data 2.0 IgniteRepositoryImpl#deleteAllById contains wrong code
[
https://issues.apache.org/jira/browse/IGNITE-13104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Kuznetsov updated IGNITE-13104:
--
Release Note: Fixed incorrect processing of non-comparable keys in
spring-data for repository methods: findAllById(ids) and deleteAllById(ids).
> Spring data 2.0 IgniteRepositoryImpl#deleteAllById contains wrong code
> --
>
> Key: IGNITE-13104
> URL: https://issues.apache.org/jira/browse/IGNITE-13104
> Project: Ignite
> Issue Type: Improvement
> Components: springdata
>Affects Versions: 2.8.1
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
>Priority: Major
> Fix For: 2.9
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {code}
> /** {@inheritDoc} */
> @Override public void deleteAllById(Iterable ids) {
> if (ids instanceof Set)
> cache.removeAll((Set)ids);
> if (ids instanceof Collection)
> cache.removeAll(new HashSet<>((Collection)ids));
> TreeSet keys = new TreeSet<>();
> for (ID id : ids)
> keys.add(id);
> cache.removeAll(keys);
> }
> {code}
> As you can see cache.removeAll may be executed THREE times in some situations.
> Also this method can throw ClassCast exception if ids collection contains
> objects that are not implement Comparable interface.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-13104) Spring data 2.0 IgniteRepositoryImpl#deleteAllById contains wrong code
[
https://issues.apache.org/jira/browse/IGNITE-13104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Kuznetsov updated IGNITE-13104:
--
Ignite Flags: Release Notes Required (was: Docs Required,Release Notes
Required)
> Spring data 2.0 IgniteRepositoryImpl#deleteAllById contains wrong code
> --
>
> Key: IGNITE-13104
> URL: https://issues.apache.org/jira/browse/IGNITE-13104
> Project: Ignite
> Issue Type: Improvement
> Components: springdata
>Affects Versions: 2.8.1
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
>Priority: Major
> Fix For: 2.9
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {code}
> /** {@inheritDoc} */
> @Override public void deleteAllById(Iterable ids) {
> if (ids instanceof Set)
> cache.removeAll((Set)ids);
> if (ids instanceof Collection)
> cache.removeAll(new HashSet<>((Collection)ids));
> TreeSet keys = new TreeSet<>();
> for (ID id : ids)
> keys.add(id);
> cache.removeAll(keys);
> }
> {code}
> As you can see cache.removeAll may be executed THREE times in some situations.
> Also this method can throw ClassCast exception if ids collection contains
> objects that are not implement Comparable interface.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (IGNITE-5617) Web Console: Rework backend from MongoDB+NodeJS to Java + Ignite + Persistent storage
[ https://issues.apache.org/jira/browse/IGNITE-5617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov resolved IGNITE-5617. -- Resolution: Won't Fix Web Console was discontinued. > Web Console: Rework backend from MongoDB+NodeJS to Java + Ignite + Persistent > storage > - > > Key: IGNITE-5617 > URL: https://issues.apache.org/jira/browse/IGNITE-5617 > Project: Ignite > Issue Type: Task > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov >Priority: Major > Time Spent: 2.25h > Remaining Estimate: 0h > > As of new persistent storage donated to Ignite it make sense to > migrate from MongoDB+NodeJS to use some Java-based Web Server + Ignite+PS. > This will give fault tolerance Out Of The Box and minimize third-party > dependencies. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-5617) Web Console: Rework backend from MongoDB+NodeJS to Java + Ignite + Persistent storage
[ https://issues.apache.org/jira/browse/IGNITE-5617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-5617. > Web Console: Rework backend from MongoDB+NodeJS to Java + Ignite + Persistent > storage > - > > Key: IGNITE-5617 > URL: https://issues.apache.org/jira/browse/IGNITE-5617 > Project: Ignite > Issue Type: Task > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov >Priority: Major > Time Spent: 2.25h > Remaining Estimate: 0h > > As of new persistent storage donated to Ignite it make sense to > migrate from MongoDB+NodeJS to use some Java-based Web Server + Ignite+PS. > This will give fault tolerance Out Of The Box and minimize third-party > dependencies. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13094) java.lang.ClassNotFoundException: ch.qos.logback for distributed compute
[
https://issues.apache.org/jira/browse/IGNITE-13094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17123723#comment-17123723
]
AK47Sonic commented on IGNITE-13094:
Hi Ilya,
Also thanks for your help. :)
> java.lang.ClassNotFoundException: ch.qos.logback for distributed compute
>
>
> Key: IGNITE-13094
> URL: https://issues.apache.org/jira/browse/IGNITE-13094
> Project: Ignite
> Issue Type: Bug
> Components: compute
>Affects Versions: 2.8.1
> Environment: Ignite 2.8.0
> Spring Boot 2.1.0.RELEASE
> Java 1.8
>Reporter: AK47Sonic
>Assignee: Ilya Kasnacheev
>Priority: Major
>
> I try to use spring boot (2.1.0.RELEASE) to run ignite.compute. As spring
> boot + lombok use logback as default, the following codes always throw
> exceptions (2020-05-28 07:00:48.979 WARN 8460 --- [ p2p-#49]
> o.a.i.i.m.d.GridDeploymentCommunication : Failed to resolve class:
> ch.qos.logback). The result (28) could be returned. Seems we see log4j and
> log4j2 on official website. I try to use log4j2 to replace logback. And it
> works fine. Does ignite support logback for distributed compute? Or It is
> just a bug?
> {panel:title=pom.xml}
>
>
> org.springframework.boot
> spring-boot-starter-web
>
>
> org.springframework.boot
> spring-boot-starter-log4j
>
>
>
>
> org.apache.ignite
> ignite-core
> 2.8.0
>
>
> org.apache.ignite
> ignite-spring
> 2.8.0
>
>
> org.projectlombok
> lombok
> 1.18.12
> provided
>
>
> {panel}
> {panel:title=config.xml}
>
> http://www.springframework.org/schema/beans";
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>xmlns:util="http://www.springframework.org/schema/util";
>xsi:schemaLocation="
> http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans.xsd
> http://www.springframework.org/schema/util
> http://www.springframework.org/schema/util/spring-util.xsd";>
> class="org.apache.ignite.configuration.IgniteConfiguration">
>
>
>
>
>
>
>
> class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">
>
>
> 127.0.0.1:48500..48520
>
>
>
>
>
>
>
> class="org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi">
>
>
>
>
>
> {panel}
> {code:java}
> @Configuration
> @ImportResource(locations={"classpath:default-config.xml"})
> public class IgniteConfig {
> @Bean
> public Ignite ignite(IgniteConfiguration igniteConfiguration) {
> Ignite ignite = Ignition.start(igniteConfiguration);
> Ignition.setClientMode(true);
> return ignite;
> }
> }
> @Slf4j
> @RestController
> public class WebController {
> @Autowired
> private Ignite ignite;
> @GetMapping("/compute")
> public void compute() {
> Collection> calls = new ArrayList<>();
> // Iterate through all the words in the sentence and create Callable
> jobs.
> for (final String word : "Count characters using callable".split(" "))
> calls.add(word::length);
> // Execute collection of Callables on the grid.
> Collection res = ignite.compute().call(calls);
> // Add up all the results.
> int sum = res.stream().mapToInt(Integer::intValue).sum();
> log.info("Total number of characters is '" + sum + "'.");
> }
> }
> {code}
> {panel:title=Exception}
> 2020-05-28 07:00:48.786 INFO 8460 --- [nio-8080-exec-1]
> o.a.i.i.m.d.GridDeploymentLocalStore : Class locally deployed: class
> com.sonic.sample.springboot.controller.WebController
> 2020-05-28 07:00:48.890 WARN 8460 --- [p2p-#49]
> o.a.i.i.m.d.GridDeploymentCommunication : Failed to resolve class:
> ch.qos.logback
> java.lang.ClassNotFoundException: ch.qos.logback
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> ~[na:1.8.0_121]
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424) ~[na:1.8.0_121]
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> ~[na:1.8.0_121]
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ~[na:1.8.0_12
[jira] [Commented] (IGNITE-13094) java.lang.ClassNotFoundException: ch.qos.logback for distributed compute
[
https://issues.apache.org/jira/browse/IGNITE-13094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17123722#comment-17123722
]
AK47Sonic commented on IGNITE-13094:
Since logback and log4j2 are commonly used, I think both logback and log4j2
will work fine for ignite server(binary distribution). Anyway, thanks so much
for your help. :)
> java.lang.ClassNotFoundException: ch.qos.logback for distributed compute
>
>
> Key: IGNITE-13094
> URL: https://issues.apache.org/jira/browse/IGNITE-13094
> Project: Ignite
> Issue Type: Bug
> Components: compute
>Affects Versions: 2.8.1
> Environment: Ignite 2.8.0
> Spring Boot 2.1.0.RELEASE
> Java 1.8
>Reporter: AK47Sonic
>Assignee: Ilya Kasnacheev
>Priority: Major
>
> I try to use spring boot (2.1.0.RELEASE) to run ignite.compute. As spring
> boot + lombok use logback as default, the following codes always throw
> exceptions (2020-05-28 07:00:48.979 WARN 8460 --- [ p2p-#49]
> o.a.i.i.m.d.GridDeploymentCommunication : Failed to resolve class:
> ch.qos.logback). The result (28) could be returned. Seems we see log4j and
> log4j2 on official website. I try to use log4j2 to replace logback. And it
> works fine. Does ignite support logback for distributed compute? Or It is
> just a bug?
> {panel:title=pom.xml}
>
>
> org.springframework.boot
> spring-boot-starter-web
>
>
> org.springframework.boot
> spring-boot-starter-log4j
>
>
>
>
> org.apache.ignite
> ignite-core
> 2.8.0
>
>
> org.apache.ignite
> ignite-spring
> 2.8.0
>
>
> org.projectlombok
> lombok
> 1.18.12
> provided
>
>
> {panel}
> {panel:title=config.xml}
>
> http://www.springframework.org/schema/beans";
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>xmlns:util="http://www.springframework.org/schema/util";
>xsi:schemaLocation="
> http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans.xsd
> http://www.springframework.org/schema/util
> http://www.springframework.org/schema/util/spring-util.xsd";>
> class="org.apache.ignite.configuration.IgniteConfiguration">
>
>
>
>
>
>
>
> class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">
>
>
> 127.0.0.1:48500..48520
>
>
>
>
>
>
>
> class="org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi">
>
>
>
>
>
> {panel}
> {code:java}
> @Configuration
> @ImportResource(locations={"classpath:default-config.xml"})
> public class IgniteConfig {
> @Bean
> public Ignite ignite(IgniteConfiguration igniteConfiguration) {
> Ignite ignite = Ignition.start(igniteConfiguration);
> Ignition.setClientMode(true);
> return ignite;
> }
> }
> @Slf4j
> @RestController
> public class WebController {
> @Autowired
> private Ignite ignite;
> @GetMapping("/compute")
> public void compute() {
> Collection> calls = new ArrayList<>();
> // Iterate through all the words in the sentence and create Callable
> jobs.
> for (final String word : "Count characters using callable".split(" "))
> calls.add(word::length);
> // Execute collection of Callables on the grid.
> Collection res = ignite.compute().call(calls);
> // Add up all the results.
> int sum = res.stream().mapToInt(Integer::intValue).sum();
> log.info("Total number of characters is '" + sum + "'.");
> }
> }
> {code}
> {panel:title=Exception}
> 2020-05-28 07:00:48.786 INFO 8460 --- [nio-8080-exec-1]
> o.a.i.i.m.d.GridDeploymentLocalStore : Class locally deployed: class
> com.sonic.sample.springboot.controller.WebController
> 2020-05-28 07:00:48.890 WARN 8460 --- [p2p-#49]
> o.a.i.i.m.d.GridDeploymentCommunication : Failed to resolve class:
> ch.qos.logback
> java.lang.ClassNotFoundException: ch.qos.logback
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> ~[na:1.8.0_121]
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424) ~[na:1.8.0_121]
> at sun.misc.Launcher$Ap
[jira] [Commented] (IGNITE-13096) Java thin client: Binary type schema is not registered for nested objects when CompactFooter is enabled
[
https://issues.apache.org/jira/browse/IGNITE-13096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17123720#comment-17123720
]
Aleksey Plekhanov commented on IGNITE-13096:
[~dmekhanikov] can you please review the patch? There is only one line of
production code changed in method {{BinaryClassDescriptor#metadata}}, according
to {{git annotate}} this method was introduced by you.
> Java thin client: Binary type schema is not registered for nested objects
> when CompactFooter is enabled
> ---
>
> Key: IGNITE-13096
> URL: https://issues.apache.org/jira/browse/IGNITE-13096
> Project: Ignite
> Issue Type: Bug
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When we first time marshal object, a binary type registration request is sent
> to the server. This request contains schemas for deserialization
> (deserialization without schema is not possible when CompactFooter is
> enabled). If the object contains references to objects of other types these
> types also sent to the server, but without schemas.
> Reproducer:
> {code:java}
> try (Ignite ignite = Ignition.start(Config.getServerConfiguration())) {
> try (IgniteClient client = Ignition.startClient(new
> ClientConfiguration().setAddresses(Config.SERVER)
> .setBinaryConfiguration(new
> BinaryConfiguration().setCompactFooter(true)))
> ) {
> IgniteCache igniteCache =
> ignite.getOrCreateCache(Config.DEFAULT_CACHE_NAME);
> ClientCache clientCache =
> client.getOrCreateCache(Config.DEFAULT_CACHE_NAME);
> Person[] val = new Person[] {new Person(1, "Joe")};
> clientCache.put(1, val);
> assertArrayEquals(val, igniteCache.get(1));
> }
> }
> {code}
> Fails with exception:
> {noformat}
> Caused by: class org.apache.ignite.binary.BinaryObjectException: Cannot find
> schema for object with compact footer
> [typeName=org.apache.ignite.client.Person, typeId=1468224522,
> missingSchemaId=970781171, existingSchemaIds=[]]
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.getOrCreateSchema(BinaryReaderExImpl.java:2028)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:287)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:186)
> at
> org.apache.ignite.internal.binary.BinaryObjectImpl.reader(BinaryObjectImpl.java:830)
> at
> org.apache.ignite.internal.binary.BinaryObjectImpl.deserializeValue(BinaryObjectImpl.java:793){noformat}
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13094) java.lang.ClassNotFoundException: ch.qos.logback for distributed compute
[
https://issues.apache.org/jira/browse/IGNITE-13094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17123715#comment-17123715
]
AK47Sonic commented on IGNITE-13094:
Hi Pavlukhin,
Thanks for your advice. I added the log, just want to print the result. I was
not aware that logback causes the exception potentially because log4j2 works
fine. If it not supported for remote invocation, I could remember that and
remove it. :)
> java.lang.ClassNotFoundException: ch.qos.logback for distributed compute
>
>
> Key: IGNITE-13094
> URL: https://issues.apache.org/jira/browse/IGNITE-13094
> Project: Ignite
> Issue Type: Bug
> Components: compute
>Affects Versions: 2.8.1
> Environment: Ignite 2.8.0
> Spring Boot 2.1.0.RELEASE
> Java 1.8
>Reporter: AK47Sonic
>Assignee: Ilya Kasnacheev
>Priority: Major
>
> I try to use spring boot (2.1.0.RELEASE) to run ignite.compute. As spring
> boot + lombok use logback as default, the following codes always throw
> exceptions (2020-05-28 07:00:48.979 WARN 8460 --- [ p2p-#49]
> o.a.i.i.m.d.GridDeploymentCommunication : Failed to resolve class:
> ch.qos.logback). The result (28) could be returned. Seems we see log4j and
> log4j2 on official website. I try to use log4j2 to replace logback. And it
> works fine. Does ignite support logback for distributed compute? Or It is
> just a bug?
> {panel:title=pom.xml}
>
>
> org.springframework.boot
> spring-boot-starter-web
>
>
> org.springframework.boot
> spring-boot-starter-log4j
>
>
>
>
> org.apache.ignite
> ignite-core
> 2.8.0
>
>
> org.apache.ignite
> ignite-spring
> 2.8.0
>
>
> org.projectlombok
> lombok
> 1.18.12
> provided
>
>
> {panel}
> {panel:title=config.xml}
>
> http://www.springframework.org/schema/beans";
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>xmlns:util="http://www.springframework.org/schema/util";
>xsi:schemaLocation="
> http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans.xsd
> http://www.springframework.org/schema/util
> http://www.springframework.org/schema/util/spring-util.xsd";>
> class="org.apache.ignite.configuration.IgniteConfiguration">
>
>
>
>
>
>
>
> class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">
>
>
> 127.0.0.1:48500..48520
>
>
>
>
>
>
>
> class="org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi">
>
>
>
>
>
> {panel}
> {code:java}
> @Configuration
> @ImportResource(locations={"classpath:default-config.xml"})
> public class IgniteConfig {
> @Bean
> public Ignite ignite(IgniteConfiguration igniteConfiguration) {
> Ignite ignite = Ignition.start(igniteConfiguration);
> Ignition.setClientMode(true);
> return ignite;
> }
> }
> @Slf4j
> @RestController
> public class WebController {
> @Autowired
> private Ignite ignite;
> @GetMapping("/compute")
> public void compute() {
> Collection> calls = new ArrayList<>();
> // Iterate through all the words in the sentence and create Callable
> jobs.
> for (final String word : "Count characters using callable".split(" "))
> calls.add(word::length);
> // Execute collection of Callables on the grid.
> Collection res = ignite.compute().call(calls);
> // Add up all the results.
> int sum = res.stream().mapToInt(Integer::intValue).sum();
> log.info("Total number of characters is '" + sum + "'.");
> }
> }
> {code}
> {panel:title=Exception}
> 2020-05-28 07:00:48.786 INFO 8460 --- [nio-8080-exec-1]
> o.a.i.i.m.d.GridDeploymentLocalStore : Class locally deployed: class
> com.sonic.sample.springboot.controller.WebController
> 2020-05-28 07:00:48.890 WARN 8460 --- [p2p-#49]
> o.a.i.i.m.d.GridDeploymentCommunication : Failed to resolve class:
> ch.qos.logback
> java.lang.ClassNotFoundException: ch.qos.logback
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> ~[na:1.8.0_121]
> at java.lang.Cla
[jira] [Commented] (IGNITE-13096) Java thin client: Binary type schema is not registered for nested objects when CompactFooter is enabled
[
https://issues.apache.org/jira/browse/IGNITE-13096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17123711#comment-17123711
]
Ignite TC Bot commented on IGNITE-13096:
{panel:title=Branch: [pull/7878/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5354775&buildTypeId=IgniteTests24Java8_RunAll]
> Java thin client: Binary type schema is not registered for nested objects
> when CompactFooter is enabled
> ---
>
> Key: IGNITE-13096
> URL: https://issues.apache.org/jira/browse/IGNITE-13096
> Project: Ignite
> Issue Type: Bug
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When we first time marshal object, a binary type registration request is sent
> to the server. This request contains schemas for deserialization
> (deserialization without schema is not possible when CompactFooter is
> enabled). If the object contains references to objects of other types these
> types also sent to the server, but without schemas.
> Reproducer:
> {code:java}
> try (Ignite ignite = Ignition.start(Config.getServerConfiguration())) {
> try (IgniteClient client = Ignition.startClient(new
> ClientConfiguration().setAddresses(Config.SERVER)
> .setBinaryConfiguration(new
> BinaryConfiguration().setCompactFooter(true)))
> ) {
> IgniteCache igniteCache =
> ignite.getOrCreateCache(Config.DEFAULT_CACHE_NAME);
> ClientCache clientCache =
> client.getOrCreateCache(Config.DEFAULT_CACHE_NAME);
> Person[] val = new Person[] {new Person(1, "Joe")};
> clientCache.put(1, val);
> assertArrayEquals(val, igniteCache.get(1));
> }
> }
> {code}
> Fails with exception:
> {noformat}
> Caused by: class org.apache.ignite.binary.BinaryObjectException: Cannot find
> schema for object with compact footer
> [typeName=org.apache.ignite.client.Person, typeId=1468224522,
> missingSchemaId=970781171, existingSchemaIds=[]]
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.getOrCreateSchema(BinaryReaderExImpl.java:2028)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:287)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:186)
> at
> org.apache.ignite.internal.binary.BinaryObjectImpl.reader(BinaryObjectImpl.java:830)
> at
> org.apache.ignite.internal.binary.BinaryObjectImpl.deserializeValue(BinaryObjectImpl.java:793){noformat}
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13100) ClassCastException in cache group metrics on client nodes
[
https://issues.apache.org/jira/browse/IGNITE-13100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17123709#comment-17123709
]
Alexey Goncharuk commented on IGNITE-13100:
---
Fixed the comment, the visa is pending.
> ClassCastException in cache group metrics on client nodes
> -
>
> Key: IGNITE-13100
> URL: https://issues.apache.org/jira/browse/IGNITE-13100
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
>Priority: Major
> Fix For: 2.9
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The following exception can be observed when reading cache group metrics on
> client nodes with persistence-enabled config:
> {code}
> java.lang.ClassCastException:
> org.apache.ignite.internal.processors.cache.persistence.IgniteCacheDatabaseSharedManager
> cannot be cast to
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager
> at
> org.apache.ignite.internal.processors.cache.CacheGroupMetricsImpl.database(CacheGroupMetricsImpl.java:506)
> at
> org.apache.ignite.internal.processors.cache.CacheGroupMetricsImpl.lambda$new$0(CacheGroupMetricsImpl.java:103)
> at
> org.apache.ignite.internal.util.lang.GridFunc.lambda$nonThrowableSupplier$3(GridFunc.java:3341)
> at
> org.apache.ignite.internal.processors.metric.impl.LongGauge.value(LongGauge.java:45)
> at
> org.apache.ignite.spi.metric.LongMetric.getAsString(LongMetric.java:29)
> {code}
> The reason is an incomplete check for persistence enabled in
> {{CacheGroupMetricsImpl}}: we should also check for client nodes.
> Suggested solution: include the check for client node mode for database
> metrics readings
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-13078) С++: Add CMake build support
[
https://issues.apache.org/jira/browse/IGNITE-13078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17123641#comment-17123641
]
Ivan Daschinskiy edited comment on IGNITE-13078 at 6/2/20, 11:02 AM:
-
[~ilyak] Ilya, I've added {{cmake-build-release}} and {{cmake-build-debug}} to
\{{ .gitignore }}, it should works. I've emphasized in README this fact. As a
build step, you should create specific directory, change one of these directory
as current, and run {{cmake ..}} in it. It is common to create
special subdirectory with these namings (actually, build directory can be
everywhere and with arbitrary name), many projects use this convention, CLion
automatically creates these directories.
was (Author: ivandasch):
[~ilyak] Ilya, I've added {{cmake-build-release}} and {{cmake-build-debug}} to
{{.gitignore}}, it should works. I've emphasized in README this fact. As a
build step, you should create specific directory, change one of these directory
as current, and run {{ cmake .. }} in it. It is common to create
special subdirectory with these namings (actually, build directory can be
everywhere and with arbitrary name), many projects use this convention, CLion
automatically creates these directories.
> С++: Add CMake build support
>
>
> Key: IGNITE-13078
> URL: https://issues.apache.org/jira/browse/IGNITE-13078
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Reporter: Ivan Daschinskiy
>Assignee: Ivan Daschinskiy
>Priority: Major
> Fix For: 2.9
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, it is hard to build Ignite.C++. Different build process for
> windows and linux, lack of building support on Mac OS X (quite popular OS
> among developers), absolutely not IDE support, except windows and only Visual
> Studio is supported.
> I’d suggest to migrate to CMake build system. It is very popular among open
> source projects, and in Apache Software Foundation too. Notable user: Apache
> Mesos, Apache Zookeeper (C client offers CMake as an alternative to autoconf
> and only option on windows), Apache Kafka (librdkafka - C/C++ client), Apache
> Thrift. Popular column-oriented database ClickHouse also uses CMake.
> CMake is widely supported in many IDE’s on various platforms, notably Visual
> Studio, CLion, Xcode, QtCreator, KDevelop.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-13078) С++: Add CMake build support
[
https://issues.apache.org/jira/browse/IGNITE-13078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17123641#comment-17123641
]
Ivan Daschinskiy edited comment on IGNITE-13078 at 6/2/20, 11:02 AM:
-
[~ilyak] Ilya, I've added {{cmake-build-release}} and {{cmake-build-debug}} to
{{.gitignore}} , it should works. I've emphasized in README this fact. As a
build step, you should create specific directory, change one of these directory
as current, and run {{cmake ..}} in it. It is common to create
special subdirectory with these namings (actually, build directory can be
everywhere and with arbitrary name), many projects use this convention, CLion
automatically creates these directories.
was (Author: ivandasch):
[~ilyak] Ilya, I've added {{cmake-build-release}} and {{cmake-build-debug}} to
\{{ .gitignore }}, it should works. I've emphasized in README this fact. As a
build step, you should create specific directory, change one of these directory
as current, and run {{cmake ..}} in it. It is common to create
special subdirectory with these namings (actually, build directory can be
everywhere and with arbitrary name), many projects use this convention, CLion
automatically creates these directories.
> С++: Add CMake build support
>
>
> Key: IGNITE-13078
> URL: https://issues.apache.org/jira/browse/IGNITE-13078
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Reporter: Ivan Daschinskiy
>Assignee: Ivan Daschinskiy
>Priority: Major
> Fix For: 2.9
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, it is hard to build Ignite.C++. Different build process for
> windows and linux, lack of building support on Mac OS X (quite popular OS
> among developers), absolutely not IDE support, except windows and only Visual
> Studio is supported.
> I’d suggest to migrate to CMake build system. It is very popular among open
> source projects, and in Apache Software Foundation too. Notable user: Apache
> Mesos, Apache Zookeeper (C client offers CMake as an alternative to autoconf
> and only option on windows), Apache Kafka (librdkafka - C/C++ client), Apache
> Thrift. Popular column-oriented database ClickHouse also uses CMake.
> CMake is widely supported in many IDE’s on various platforms, notably Visual
> Studio, CLion, Xcode, QtCreator, KDevelop.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-13078) С++: Add CMake build support
[
https://issues.apache.org/jira/browse/IGNITE-13078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17123641#comment-17123641
]
Ivan Daschinskiy edited comment on IGNITE-13078 at 6/2/20, 11:01 AM:
-
[~ilyak] Ilya, I've added {{cmake-build-release}} and {{cmake-build-debug}} to
{{.gitignore}}, it should works. I've emphasized in README this fact. As a
build step, you should create specific directory, change one of these directory
as current, and run {{cmake .. }} in it. It is common to create
special subdirectory with these namings (actually, build directory can be
everywhere and with arbitrary name), many projects use this convention, CLion
automatically creates these directories.
was (Author: ivandasch):
[~ilyak] Ilya, I've added cmake-build-release and cmake-build-debug to
.gitignore, it should works. I've emphasized in README this fact. As a build
step, you should create specific directory, change one of these directory as
current, and run cmake .. in it. It is common to create special
subdirectory withthese namings (actually, build directory can be everywhere and
with arbitrary name), many projects use this convention, CLion automatically
creates these directories.
> С++: Add CMake build support
>
>
> Key: IGNITE-13078
> URL: https://issues.apache.org/jira/browse/IGNITE-13078
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Reporter: Ivan Daschinskiy
>Assignee: Ivan Daschinskiy
>Priority: Major
> Fix For: 2.9
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, it is hard to build Ignite.C++. Different build process for
> windows and linux, lack of building support on Mac OS X (quite popular OS
> among developers), absolutely not IDE support, except windows and only Visual
> Studio is supported.
> I’d suggest to migrate to CMake build system. It is very popular among open
> source projects, and in Apache Software Foundation too. Notable user: Apache
> Mesos, Apache Zookeeper (C client offers CMake as an alternative to autoconf
> and only option on windows), Apache Kafka (librdkafka - C/C++ client), Apache
> Thrift. Popular column-oriented database ClickHouse also uses CMake.
> CMake is widely supported in many IDE’s on various platforms, notably Visual
> Studio, CLion, Xcode, QtCreator, KDevelop.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13078) С++: Add CMake build support
[ https://issues.apache.org/jira/browse/IGNITE-13078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17123641#comment-17123641 ] Ivan Daschinskiy commented on IGNITE-13078: --- [~ilyak] Ilya, I've added cmake-build-release and cmake-build-debug to .gitignore, it should works. I've emphasized in README this fact. As a build step, you should create specific directory, change one of these directory as current, and run cmake .. in it. It is common to create special subdirectory withthese namings (actually, build directory can be everywhere and with arbitrary name), many projects use this convention, CLion automatically creates these directories. > С++: Add CMake build support > > > Key: IGNITE-13078 > URL: https://issues.apache.org/jira/browse/IGNITE-13078 > Project: Ignite > Issue Type: Improvement > Components: platforms >Reporter: Ivan Daschinskiy >Assignee: Ivan Daschinskiy >Priority: Major > Fix For: 2.9 > > Time Spent: 10m > Remaining Estimate: 0h > > Currently, it is hard to build Ignite.C++. Different build process for > windows and linux, lack of building support on Mac OS X (quite popular OS > among developers), absolutely not IDE support, except windows and only Visual > Studio is supported. > I’d suggest to migrate to CMake build system. It is very popular among open > source projects, and in Apache Software Foundation too. Notable user: Apache > Mesos, Apache Zookeeper (C client offers CMake as an alternative to autoconf > and only option on windows), Apache Kafka (librdkafka - C/C++ client), Apache > Thrift. Popular column-oriented database ClickHouse also uses CMake. > CMake is widely supported in many IDE’s on various platforms, notably Visual > Studio, CLion, Xcode, QtCreator, KDevelop. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-13078) С++: Add CMake build support
[
https://issues.apache.org/jira/browse/IGNITE-13078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17123641#comment-17123641
]
Ivan Daschinskiy edited comment on IGNITE-13078 at 6/2/20, 11:01 AM:
-
[~ilyak] Ilya, I've added {{cmake-build-release}} and {{cmake-build-debug}} to
{{.gitignore}}, it should works. I've emphasized in README this fact. As a
build step, you should create specific directory, change one of these directory
as current, and run {{ cmake .. }} in it. It is common to create
special subdirectory with these namings (actually, build directory can be
everywhere and with arbitrary name), many projects use this convention, CLion
automatically creates these directories.
was (Author: ivandasch):
[~ilyak] Ilya, I've added {{cmake-build-release}} and {{cmake-build-debug}} to
{{.gitignore}}, it should works. I've emphasized in README this fact. As a
build step, you should create specific directory, change one of these directory
as current, and run {{cmake .. }} in it. It is common to create
special subdirectory with these namings (actually, build directory can be
everywhere and with arbitrary name), many projects use this convention, CLion
automatically creates these directories.
> С++: Add CMake build support
>
>
> Key: IGNITE-13078
> URL: https://issues.apache.org/jira/browse/IGNITE-13078
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Reporter: Ivan Daschinskiy
>Assignee: Ivan Daschinskiy
>Priority: Major
> Fix For: 2.9
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, it is hard to build Ignite.C++. Different build process for
> windows and linux, lack of building support on Mac OS X (quite popular OS
> among developers), absolutely not IDE support, except windows and only Visual
> Studio is supported.
> I’d suggest to migrate to CMake build system. It is very popular among open
> source projects, and in Apache Software Foundation too. Notable user: Apache
> Mesos, Apache Zookeeper (C client offers CMake as an alternative to autoconf
> and only option on windows), Apache Kafka (librdkafka - C/C++ client), Apache
> Thrift. Popular column-oriented database ClickHouse also uses CMake.
> CMake is widely supported in many IDE’s on various platforms, notably Visual
> Studio, CLion, Xcode, QtCreator, KDevelop.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13078) С++: Add CMake build support
[
https://issues.apache.org/jira/browse/IGNITE-13078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17123624#comment-17123624
]
Ilya Kasnacheev commented on IGNITE-13078:
--
[~ivandasch] I have noticed that after successful builds, git has a lot of
untracked files:
{code}
modules/platforms/cpp/CMakeCache.txt
modules/platforms/cpp/CMakeFiles/
modules/platforms/cpp/binary/CMakeFiles/
modules/platforms/cpp/binary/cmake_install.cmake
modules/platforms/cpp/binary/libignite-binary.so
modules/platforms/cpp/binary/libignite-binary.so.2.9.0.42453
modules/platforms/cpp/cmake_install.cmake
modules/platforms/cpp/common/CMakeFiles/
modules/platforms/cpp/common/cmake_install.cmake
modules/platforms/cpp/common/libignite-common.so
modules/platforms/cpp/common/libignite-common.so.2.9.0.42453
modules/platforms/cpp/core/CMakeFiles/
modules/platforms/cpp/core/cmake_install.cmake
modules/platforms/cpp/core/libignite.so
modules/platforms/cpp/core/libignite.so.2.9.0.42453
modules/platforms/cpp/ignite/CMakeFiles/
modules/platforms/cpp/ignite/cmake_install.cmake
modules/platforms/cpp/install_manifest.txt
modules/platforms/cpp/jni/CMakeFiles/
modules/platforms/cpp/jni/cmake_install.cmake
modules/platforms/cpp/jni/libignite-jni.so
modules/platforms/cpp/jni/libignite-jni.so.2.9.0.42453
modules/platforms/cpp/network/CMakeFiles/
modules/platforms/cpp/network/cmake_install.cmake
modules/platforms/cpp/network/libignite-network.so
modules/platforms/cpp/network/libignite-network.so.2.9.0.42453
modules/platforms/cpp/odbc/CMakeFiles/
modules/platforms/cpp/odbc/cmake_install.cmake
modules/platforms/cpp/odbc/libignite-odbc.so
modules/platforms/cpp/odbc/libignite-odbc.so.2.9.0.42453
modules/platforms/cpp/thin-client/CMakeFiles/
modules/platforms/cpp/thin-client/cmake_install.cmake
modules/platforms/cpp/thin-client/libignite-thin-client.so
modules/platforms/cpp/thin-client/libignite-thin-client.so.2.9.0.42453
{code}
We should match them with patterns, add to .gitignore
It's weird that they're not in .gitignore, we should match them with patterns
and ignore. Possibly some changes to cmake process is needed.
> С++: Add CMake build support
>
>
> Key: IGNITE-13078
> URL: https://issues.apache.org/jira/browse/IGNITE-13078
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Reporter: Ivan Daschinskiy
>Assignee: Ivan Daschinskiy
>Priority: Major
> Fix For: 2.9
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, it is hard to build Ignite.C++. Different build process for
> windows and linux, lack of building support on Mac OS X (quite popular OS
> among developers), absolutely not IDE support, except windows and only Visual
> Studio is supported.
> I’d suggest to migrate to CMake build system. It is very popular among open
> source projects, and in Apache Software Foundation too. Notable user: Apache
> Mesos, Apache Zookeeper (C client offers CMake as an alternative to autoconf
> and only option on windows), Apache Kafka (librdkafka - C/C++ client), Apache
> Thrift. Popular column-oriented database ClickHouse also uses CMake.
> CMake is widely supported in many IDE’s on various platforms, notably Visual
> Studio, CLion, Xcode, QtCreator, KDevelop.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-13012) Make node connection checking rely on the configuration. Simplify node ping routine.
[
https://issues.apache.org/jira/browse/IGNITE-13012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Steshin updated IGNITE-13012:
--
Description:
Node-to-next-node connection checking has several drawbacks which go together.
These drawback hindered understanding and catching problems in IGNITE-13016.
We should fix the following :
1. Failure detection timeout should take in account last sent message.
Connection check interval should also rely on this time. If we set timeout on
current message only, we have no guarantee that connection failure is detected
with failure detection timeout.
Current ping is bound to own time:
{code:java}ServerImpl. RingMessageWorker.lastTimeConnCheckMsgSent{code}
This is weird because any discovery message check connection. And
TpcDiscoveryConnectionCheckMessage is just an addition when message queue is
empty for a long time.
2. Make connection check interval depend on failure detection timeout (FTD).
Current value is a constant:
{code:java}static int ServerImpls.CON_CHECK_INTERVAL = 500{code}
Let's set it FDT/4 to get enough timeout time since last sent message.
3. Remove additional, quickened connection checking. Once we do fix 1, this
will become even more useless.
Despite TCP discovery has a period of connection checking, it may send ping
before this period exhausts. This premature node ping relies on the time of any
sent or even any received message. Imagine: if node 2 receives no message from
node 1 within some time, it decides to do extra ping node 3 not waiting for
regular ping. Such behavior makes confusion and gives no considerable benefits.
See {code:java}ServerImpl.RingMessageWorker.failureThresholdReached{code}
4. Do not worry user with “Node disconnected” when everything is OK. Once we do
fix 1 and 3, this will become even more useless.
Node may log on INFO: “Local node seems to be disconnected from topology …”
whereas it is not actually disconnected at all.
was:
Node-to-next-node connection checking has several drawbacks which go together.
These drawback hindered understanding and catching problems in IGNITE-13016.
We should fix the following :
1. Make connection check interval depend on failure detection timeout (FTD).
Current value is a constant:
{code:java}static int ServerImpls.CON_CHECK_INTERVAL = 500{code}
Let's set it FDT/2. Another half of FDT - timeout on ping message exchange.
2. Make connection check interval rely on common time of any last sent message.
Current ping is bound to own time:
{code:java}ServerImpl. RingMessageWorker.lastTimeConnCheckMsgSent{code}
This is weird because any discovery message check connection. And
TpcDiscoveryConnectionCheckMessage is just an addition when message queue is
empty for a long time.
3. Remove additional, quickened connection checking. Once we do fix 1, this
will become even more useless.
Despite TCP discovery has a period of connection checking, it may send ping
before this period exhausts. This premature node ping relies on the time of any
sent or even any received message. Imagine: if node 2 receives no message from
node 1 within some time, it decides to do extra ping node 3 not waiting for
regular ping. Such behavior makes confusion and gives no considerable benefits.
See {code:java}ServerImpl.RingMessageWorker.failureThresholdReached{code}
4. Do not worry user with “Node disconnected” when everything is OK. Once we do
fix 1 and 3, this will become even more useless.
Node may log on INFO: “Local node seems to be disconnected from topology …”
whereas it is not actually disconnected at all.
> Make node connection checking rely on the configuration. Simplify node ping
> routine.
>
>
> Key: IGNITE-13012
> URL: https://issues.apache.org/jira/browse/IGNITE-13012
> Project: Ignite
> Issue Type: Improvement
>Reporter: Vladimir Steshin
>Assignee: Vladimir Steshin
>Priority: Major
> Labels: iep-45
> Time Spent: 2h
> Remaining Estimate: 0h
>
> Node-to-next-node connection checking has several drawbacks which go
> together. These drawback hindered understanding and catching problems in
> IGNITE-13016. We should fix the following :
> 1. Failure detection timeout should take in account last sent message.
> Connection check interval should also rely on this time. If we set timeout on
> current message only, we have no guarantee that connection failure is
> detected with failure detection timeout.
> Current ping is bound to own time:
> {code:java}ServerImpl. RingMessageWorker.lastTimeConnCheckMsgSent{code}
> This is weird because any discovery message check connection. And
> TpcDiscoveryConnectionCheckMessage is just an addition when message queue is
> empty for a long time.
> 2. Make connect
[jira] [Commented] (IGNITE-13095) .NET: Thin Client Compute does not cancel task on server when cancelled on client
[
https://issues.apache.org/jira/browse/IGNITE-13095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17123599#comment-17123599
]
Ignite TC Bot commented on IGNITE-13095:
{panel:title=Branch: [pull/7883/head] Base: [master] : Possible Blockers
(6)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 6{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5357135]]
{color:#d04437}Cache 7{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5357136]]
{color:#d04437}PDS 3{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5357149]]
* IgnitePdsTestSuite3:
IgnitePdsContinuousRestartTest.testRebalancingDuringLoad_8000_8000_1_1 - Test
has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Platform .NET{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5357214]]
* exe: ComputeClientTests.TestExecuteJavaTaskAsyncCancellation - Test has low
fail rate in base branch 0,0% and is not flaky
{color:#d04437}Platform .NET (Core Linux){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5357186]]
* dll: ComputeClientTests.TestExecuteJavaTaskAsyncCancellation - Test has low
fail rate in base branch 0,0% and is not flaky
{color:#d04437}Streamers{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5357095]]
* IgniteMqttStreamerTestSuite:
IgniteMqttStreamerTest.testSingleTopic_NoQoS_ConnectOptions_Durable - Test has
low fail rate in base branch 0,0% and is not flaky
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5357182&buildTypeId=IgniteTests24Java8_RunAll]
> .NET: Thin Client Compute does not cancel task on server when cancelled on
> client
> -
>
> Key: IGNITE-13095
> URL: https://issues.apache.org/jira/browse/IGNITE-13095
> Project: Ignite
> Issue Type: New Feature
> Components: platforms, thin client
>Affects Versions: 2.9
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: .NET
> Fix For: 2.9
>
> Original Estimate: 3h
> Time Spent: 10m
> Remaining Estimate: 2h 50m
>
> Client should call OP_RESOURCE_CLOSE to cancel the task on server side.
> Test this by reading server logs, "Job was cancelled" should be there.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13094) java.lang.ClassNotFoundException: ch.qos.logback for distributed compute
[
https://issues.apache.org/jira/browse/IGNITE-13094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17123530#comment-17123530
]
Ivan Pavlukhin commented on IGNITE-13094:
-
Hi [~AK47Sonic],
I guess that server startup procedure matters here (binary distribution in your
case and Java code in my). And it turns out that Ilya caught the cause. But why
log classes need to be loaded remotely in the described case is not clear for
me (it still might be a technical detail I do not understand).
> java.lang.ClassNotFoundException: ch.qos.logback for distributed compute
>
>
> Key: IGNITE-13094
> URL: https://issues.apache.org/jira/browse/IGNITE-13094
> Project: Ignite
> Issue Type: Bug
> Components: compute
>Affects Versions: 2.8.1
> Environment: Ignite 2.8.0
> Spring Boot 2.1.0.RELEASE
> Java 1.8
>Reporter: AK47Sonic
>Assignee: Ilya Kasnacheev
>Priority: Major
>
> I try to use spring boot (2.1.0.RELEASE) to run ignite.compute. As spring
> boot + lombok use logback as default, the following codes always throw
> exceptions (2020-05-28 07:00:48.979 WARN 8460 --- [ p2p-#49]
> o.a.i.i.m.d.GridDeploymentCommunication : Failed to resolve class:
> ch.qos.logback). The result (28) could be returned. Seems we see log4j and
> log4j2 on official website. I try to use log4j2 to replace logback. And it
> works fine. Does ignite support logback for distributed compute? Or It is
> just a bug?
> {panel:title=pom.xml}
>
>
> org.springframework.boot
> spring-boot-starter-web
>
>
> org.springframework.boot
> spring-boot-starter-log4j
>
>
>
>
> org.apache.ignite
> ignite-core
> 2.8.0
>
>
> org.apache.ignite
> ignite-spring
> 2.8.0
>
>
> org.projectlombok
> lombok
> 1.18.12
> provided
>
>
> {panel}
> {panel:title=config.xml}
>
> http://www.springframework.org/schema/beans";
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>xmlns:util="http://www.springframework.org/schema/util";
>xsi:schemaLocation="
> http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans.xsd
> http://www.springframework.org/schema/util
> http://www.springframework.org/schema/util/spring-util.xsd";>
> class="org.apache.ignite.configuration.IgniteConfiguration">
>
>
>
>
>
>
>
> class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">
>
>
> 127.0.0.1:48500..48520
>
>
>
>
>
>
>
> class="org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi">
>
>
>
>
>
> {panel}
> {code:java}
> @Configuration
> @ImportResource(locations={"classpath:default-config.xml"})
> public class IgniteConfig {
> @Bean
> public Ignite ignite(IgniteConfiguration igniteConfiguration) {
> Ignite ignite = Ignition.start(igniteConfiguration);
> Ignition.setClientMode(true);
> return ignite;
> }
> }
> @Slf4j
> @RestController
> public class WebController {
> @Autowired
> private Ignite ignite;
> @GetMapping("/compute")
> public void compute() {
> Collection> calls = new ArrayList<>();
> // Iterate through all the words in the sentence and create Callable
> jobs.
> for (final String word : "Count characters using callable".split(" "))
> calls.add(word::length);
> // Execute collection of Callables on the grid.
> Collection res = ignite.compute().call(calls);
> // Add up all the results.
> int sum = res.stream().mapToInt(Integer::intValue).sum();
> log.info("Total number of characters is '" + sum + "'.");
> }
> }
> {code}
> {panel:title=Exception}
> 2020-05-28 07:00:48.786 INFO 8460 --- [nio-8080-exec-1]
> o.a.i.i.m.d.GridDeploymentLocalStore : Class locally deployed: class
> com.sonic.sample.springboot.controller.WebController
> 2020-05-28 07:00:48.890 WARN 8460 --- [p2p-#49]
> o.a.i.i.m.d.GridDeploymentCommunication : Failed to resolve class:
> ch.qos.logback
> java.lang.ClassNotFoundException: ch.qos.logback
> at java.net.URLClassLoader.findCl
[jira] [Updated] (IGNITE-13101) Metastore may leave uncompleted write futures during node stop
[
https://issues.apache.org/jira/browse/IGNITE-13101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-13101:
--
Fix Version/s: 2.9
> Metastore may leave uncompleted write futures during node stop
> --
>
> Key: IGNITE-13101
> URL: https://issues.apache.org/jira/browse/IGNITE-13101
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexey Goncharuk
>Priority: Major
> Fix For: 2.9
>
>
> I've got the following thread-dump (only relevant parts are retained) during
> one of the teamcity runs:
> {code}
> "sys-#103862%baseline.IgniteStableBaselineBinObjFieldsQuerySelfTest0%"
> #107048 prio=5 os_prio=0 tid=0x7fa2d8009800 nid=0x480d waiting on
> condition [0x7fa1d1cdc000]
>java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:304)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:178)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:141)
> at
> org.apache.ignite.internal.processors.metric.GridMetricManager.remove(GridMetricManager.java:411)
> at
> org.apache.ignite.internal.processors.cache.CacheGroupMetricsImpl.remove(CacheGroupMetricsImpl.java:497)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.cleanup(GridCacheProcessor.java:512)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.stopCacheGroup(GridCacheProcessor.java:2901)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.stopCacheGroup(GridCacheProcessor.java:2889)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.processCacheStopRequestOnExchangeDone(GridCacheProcessor.java:2781)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onExchangeDone(GridCacheProcessor.java:2878)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onDone(GridDhtPartitionsExchangeFuture.java:2431)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.finishExchangeOnCoordinator(GridDhtPartitionsExchangeFuture.java:3832)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onAllReceived(GridDhtPartitionsExchangeFuture.java:3608)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.processSingleMessage(GridDhtPartitionsExchangeFuture.java:3207)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.access$200(GridDhtPartitionsExchangeFuture.java:154)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2.apply(GridDhtPartitionsExchangeFuture.java:2994)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2.apply(GridDhtPartitionsExchangeFuture.java:2982)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:399)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:354)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onReceiveSingleMessage(GridDhtPartitionsExchangeFuture.java:2982)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.processSinglePartitionUpdate(GridCachePartitionExchangeManager.java:1989)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.preprocessSingleMessage(GridCachePartitionExchangeManager.java:524)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.access$1100(GridCachePartitionExchangeManager.java:182)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$2.onMessage(GridCachePartitionExchangeManager.java:407)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$2.onMessage(GridCachePartitionExchangeManager.java:389)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$MessageHandler.apply(GridCachePartitionExchangeManager.java:3715)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$MessageHandler.apply(GridCachePartitionExchangeManager.java:3694)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1142)
> at
> org
