[jira] [Created] (IGNITE-13650) Remove FileWriteAheadLogManager#updateCurrentHandle from under assert
Kirill Tkalenko created IGNITE-13650:
Summary: Remove FileWriteAheadLogManager#updateCurrentHandle from
under assert
Key: IGNITE-13650
URL: https://issues.apache.org/jira/browse/IGNITE-13650
Project: Ignite
Issue Type: Bug
Components: persistence
Reporter: Kirill Tkalenko
Assignee: Kirill Tkalenko
Fix For: 2.10
It is necessary to remove FileWriteAheadLogManager#updateCurrentHandle out of
assert:
{code:java}
assert updateCurrentHandle(next, hnd) : "Concurrent updates on rollover are not
allowed";
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-13649) Local cache causes system thread pool overflow
Pavel Vinokurov created IGNITE-13649: Summary: Local cache causes system thread pool overflow Key: IGNITE-13649 URL: https://issues.apache.org/jira/browse/IGNITE-13649 Project: Ignite Issue Type: Bug Components: cache Affects Versions: 2.8.1 Reporter: Pavel Vinokurov Attachments: LocalCacheAndStoreReproducerClient.java, LocalCacheAndStoreReproducerServer.java Calling get operations for a LOCAL cache with read-through within a long running job causes system thread pool overflow. Scenario: 1. Start 2 server nodes using LocalCacheAndStoreReproducerServer 2. Start 1 client node using LocalCacheAndStoreReproducerClient 3. Forcible stop the client node. Result: The system thread pool is consistently increasing until OOM. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: Compiling Apache Ignite 2.8.1 on JAVA 11
Hello, You can run current Ignite binaries on JDK11, no need to compile it on JDK11. If you still want to compile it by yourself on JDK11, try the command line that I provided. You can also try Ignite 2.9, this issue is fixed in the 2.9 release. вс, 1 нояб. 2020 г. в 23:12, shm : > Hi Ilya Kasnacheev and Alexey Plekhanov > > Thanks for your replies... > we want to run Ignite on jdk11 so compiling on jdk11 > > Currently the compilation failing for ignite-spark-2.4 (not sure if it > fails for visor modules also) > > [INFO] ignite-spark ... SUCCESS [ > 13.694 > s] > [INFO] ignite-spark-2.4 ... FAILURE [ > 7.545 > s] > [INFO] ignite-visor-console_2.10 .. SKIPPED > [INFO] ignite-visor-console ... SKIPPED > [INFO] ignite-visor-plugins ... SKIPPED > [INFO] apache-ignite .. SKIPPED > [INFO] > > [INFO] BUILD FAILURE > > The error Iam getting is > [INFO] > > [ERROR] Failed to execute goal > net.alchim31.maven:scala-maven-plugin:3.3.2:compile (scala-compile-first) > on > project ignite-spark-2.4: wrap: org.apache.commons.exec.ExecuteException: > Process exited with an error: 1 (Exit value: 1) -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal net.alchim31.maven:scala-maven-plugin:3.3.2:compile > (scala-compile-first) on project ignite-spark-2.4: wrap: > org.apache.commons.exec.ExecuteException: Process exited with an error: 1 > (Exit value: 1) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:215) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:156) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:148) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:117) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:81) > at > > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build > (SingleThreadedBuilder.java:56) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute > (LifecycleStarter.java:128) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) > at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) > at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) > at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288) > at org.apache.maven.cli.MavenCli.main (MavenCli.java:192) > at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native > Method) > at jdk.internal.reflect.NativeMethodAccessorImpl.invoke > (NativeMethodAccessorImpl.java:62) > at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke > (DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke (Method.java:566) > at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced > (Launcher.java:289) > at org.codehaus.plexus.classworlds.launcher.Launcher.launch > (Launcher.java:229) > at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode > (Launcher.java:415) > at org.codehaus.plexus.classworlds.launcher.Launcher.main > (Launcher.java:356) > Caused by: org.apache.maven.plugin.MojoExecutionException: wrap: > org.apache.commons.exec.ExecuteException: Process exited with an error: 1 > (Exit value: 1) > > > Is there any known issue on this compilation ? Is it not supported on > java11 > at all ? could you please help me in this > > > > -- > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/ >
[jira] [Created] (IGNITE-13648) Tests failing for extensions modules
Saikat Maitra created IGNITE-13648:
--
Summary: Tests failing for extensions modules
Key: IGNITE-13648
URL: https://issues.apache.org/jira/browse/IGNITE-13648
Project: Ignite
Issue Type: Sub-task
Components: streaming
Reporter: Saikat Maitra
Tests failing for extensions modules
{code}
org.apache.ignite.IgniteException: Failed to start manager: GridManagerAdapter
[enabled=true,
name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
at
org.apache.ignite.stream.kafka.connect.IgniteSinkConnectorTest.beforeTestsStarted(IgniteSinkConnectorTest.java:136)
Caused by: org.apache.ignite.IgniteCheckedException: Failed to start manager:
GridManagerAdapter [enabled=true,
name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
at
org.apache.ignite.stream.kafka.connect.IgniteSinkConnectorTest.beforeTestsStarted(IgniteSinkConnectorTest.java:136)
Caused by: org.apache.ignite.IgniteCheckedException: Remote node has peer class
loading enabled flag different from local [locId8=dfc9ddaf,
locPeerClassLoading=true, rmtId8=fee013c8, rmtPeerClassLoading=false,
rmtAddrs=[9dc3d9f4b167/127.0.0.1, /172.17.0.6], rmtNode=ClusterNode
[id=fee013c8-d398-4cdc-92f5-c368c5fc663a, order=1, addr=[127.0.0.1,
172.17.0.6], daemon=false]]
at
org.apache.ignite.stream.kafka.connect.IgniteSinkConnectorTest.beforeTestsStarted(IgniteSinkConnectorTest.java:136)
{code}
{code}
org.apache.ignite.IgniteException: Failed to start manager: GridManagerAdapter
[enabled=true,
name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
at
org.apache.ignite.stream.kafka.connect.IgniteSourceConnectorTest.beforeTestsStarted(IgniteSourceConnectorTest.java:96)
Caused by: org.apache.ignite.IgniteCheckedException: Failed to start manager:
GridManagerAdapter [enabled=true,
name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
at
org.apache.ignite.stream.kafka.connect.IgniteSourceConnectorTest.beforeTestsStarted(IgniteSourceConnectorTest.java:96)
Caused by: org.apache.ignite.IgniteCheckedException: Remote node has peer class
loading enabled flag different from local [locId8=bbb64dda,
locPeerClassLoading=true, rmtId8=fee013c8, rmtPeerClassLoading=false,
rmtAddrs=[9dc3d9f4b167/127.0.0.1, /172.17.0.6], rmtNode=ClusterNode
[id=fee013c8-d398-4cdc-92f5-c368c5fc663a, order=1, addr=[127.0.0.1,
172.17.0.6], daemon=false]]
at
org.apache.ignite.stream.kafka.connect.IgniteSourceConnectorTest.beforeTestsStarted(IgniteSourceConnectorTest.java:96)
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-13647) Spring Data: Avoid creation of cache object through reflection when _VAL field is present in query.
Mikhail Petrov created IGNITE-13647: --- Summary: Spring Data: Avoid creation of cache object through reflection when _VAL field is present in query. Key: IGNITE-13647 URL: https://issues.apache.org/jira/browse/IGNITE-13647 Project: Ignite Issue Type: Improvement Reporter: Mikhail Petrov It's needed to avoid creation of cache object through reflection in case VAL field is present in query and corresponding repository method returns objects of cache value type. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: Compiling Apache Ignite 2.8.1 on JAVA 11
Hi Ilya Kasnacheev and Alexey Plekhanov Thanks for your replies... we want to run Ignite on jdk11 so compiling on jdk11 Currently the compilation failing for ignite-spark-2.4 (not sure if it fails for visor modules also) [INFO] ignite-spark ... SUCCESS [ 13.694 s] [INFO] ignite-spark-2.4 ... FAILURE [ 7.545 s] [INFO] ignite-visor-console_2.10 .. SKIPPED [INFO] ignite-visor-console ... SKIPPED [INFO] ignite-visor-plugins ... SKIPPED [INFO] apache-ignite .. SKIPPED [INFO] [INFO] BUILD FAILURE The error Iam getting is [INFO] [ERROR] Failed to execute goal net.alchim31.maven:scala-maven-plugin:3.3.2:compile (scala-compile-first) on project ignite-spark-2.4: wrap: org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1) -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal net.alchim31.maven:scala-maven-plugin:3.3.2:compile (scala-compile-first) on project ignite-spark-2.4: wrap: org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:215) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288) at org.apache.maven.cli.MavenCli.main (MavenCli.java:192) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62) at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke (Method.java:566) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:356) Caused by: org.apache.maven.plugin.MojoExecutionException: wrap: org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1) Is there any known issue on this compilation ? Is it not supported on java11 at all ? could you please help me in this -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Re: [Micronaut] pubsub support
Hi Denis,
Ignite Messaging apis are considered for depreciation due to mainly being
unused integration. Please find a related presentation that Val presented
to the community.
https://youtu.be/zPuLJgUfLaM?t=1580
Please feel free to start a separate [DISCUSS] thread for IgniteMessaging
api in the dev channel.
Also please find the related thread for Apache Ignite 3.0 release.
http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-3-0-td48671.html
Regards,
Saikat
On Sun, Nov 1, 2020 at 11:32 AM Saikat Maitra
wrote:
> Hi Michael,
>
> My thoughts are that in the intercept method of
> PubSubClientIntroductionAdvice we can publish messages similar to Mqtt.
>
>
> https://github.com/micronaut-projects/micronaut-mqtt/blob/230a6564344ceea21bcf244681d10b79763b2b19/mqtt-core/src/main/java/io/micronaut/mqtt/intercept/AbstractMqttIntroductionAdvice.java#L75
>
> https://github.com/micronaut-projects/micronaut-mqtt/blob/230a6564344ceea21bcf244681d10b79763b2b19/mqttv3/src/main/java/io/micronaut/mqtt/v3/intercept/MqttIntroductionAdvice.java#L48
>
> The publish method will call stmr.addData.
>
> Regards,
> Saikat
>
>
>
> On Sun, Nov 1, 2020 at 3:14 AM Denis Garus wrote:
>
>> Hello, Saikat!
>>
>> I know that IgniteMessagin is used in the production environment and
>> I don't see any bugs in Jira with this feature.
>> I wrote some tests for IgniteMessaging in the security suite, and only
>> one confusing thing was noticed [1].
>>
>> Why did we decide to deprecate IgniyeMessaging API in Ignite 3.0?
>>
>> 1.
>> http://apache-ignite-developers.2346864.n4.nabble.com/Inconsistent-behavior-of-IgniteMessaging-td47481.html
>>
>> вс, 1 нояб. 2020 г. в 04:43, Michael Pollind :
>>
>>> I'm looking at this data stream api and I'm having a hard time working
>>> out
>>> how this scheme fits into the pub sub model that micronaut uses. Here is
>>> what I've kind of come up with and wonder if this would work.
>>>
>>> @PubSubClientpublic interface MultipleMessage {
>>>
>>> @Topic("animals")
>>> public void send(@key() String key, Animal o);
>>>
>>> @Topic("my_topic")
>>> public void send2(@key() Long key, Object o);
>>> }
>>>
>>>
>>> @PubSubListener
>>>
>>> public class SimpleSub {
>>>
>>> @Subscription("animals")
>>>
>>> public class Listener(@key() String key, Animal o) {
>>>
>>> }
>>>
>>> }
>>>
>>>
>>> On Tue, Oct 27, 2020 at 7:15 PM Saikat Maitra
>>> wrote:
>>>
>>> > Hi Michael, Denis
>>> >
>>> > I did an initial review of the PR and wanted to share my thoughts. I
>>> > observed that currently the implementation is using Ignite messaging
>>> apis
>>> > and I am thinking if we should change the implementation to use Ignite
>>> data
>>> > streaming apis. The reason for change is to ensure that it will be
>>> better
>>> > aligned to Ignite 3.0 release as we are planning to deprecate Ignite
>>> > Messaging apis in Ignite 3.0 [1]
>>> >
>>> > My recommendation to use Ignite data streaming apis is also due to the
>>> > fact that we have multiple integration like Google Pub/Sub[2] and Kafka
>>> > Streamer[3] that uses Data streaming apis for integration and it will
>>> keep
>>> > micronaut implementation consistent with other extensions.
>>> >
>>> > Here is an example[4] of how Kafka Streamer can be used to stream data
>>> > into Ignite nodes.
>>> >
>>> >
>>> > [1]
>>> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+3.0
>>> > [2]
>>> >
>>> https://github.com/apache/ignite-extensions/blob/master/modules/pub-sub-ext/src/main/java/org/apache/ignite/stream/pubsub/PubSubStreamer.java
>>> > [3]
>>> >
>>> https://github.com/apache/ignite-extensions/blob/master/modules/kafka-ext/src/main/java/org/apache/ignite/stream/kafka/KafkaStreamer.java
>>> > [4]
>>> >
>>> https://github.com/samaitra/streamersk-extensions/blob/main/src/main/kotlin/com/example/streamerskextensions/kafka/KafkaStreamer.kt
>>> >
>>> > Please let me know your feedback.
>>> >
>>> > Regards,
>>> > Saikat
>>> >
>>> > On Tue, Oct 27, 2020 at 12:48 PM Denis Magda
>>> wrote:
>>> >
>>> >> Michael, glad to see you back!
>>> >>
>>> >> Could you please explain in a few words what this integration does and
>>> >> what
>>> >> it enables for Ignite and Micronaout? So that we are as a community
>>> are on
>>> >> the same page.
>>> >>
>>> >> -
>>> >> Denis
>>> >>
>>> >>
>>> >> On Sun, Oct 25, 2020 at 3:05 PM Michael Pollind
>>> >> wrote:
>>> >>
>>> >> > I've started to work on adding some basic pubsub support for
>>> >> > Micronaut-ignite. I only have a draft PR in progress. There are a
>>> couple
>>> >> > modules that already implement pub-sub so those modules would be a
>>> good
>>> >> > start for reference:
>>> >> > https://github.com/micronaut-projects/micronaut-gcp
>>> >> > https://github.com/micronaut-projects/micronaut-kafka
>>> >> > https://github.com/micronaut-projects/micronaut-mqtt
>>> >> >
>>> >> > https://github.com/micronaut-projects/micronaut-ignite/pull/62
>>> >> >
>>> >> >
>>> >> >
>>> >>
>>> >
>>>
>>
Re: [Micronaut] pubsub support
Hi Michael,
My thoughts are that in the intercept method of
PubSubClientIntroductionAdvice we can publish messages similar to Mqtt.
https://github.com/micronaut-projects/micronaut-mqtt/blob/230a6564344ceea21bcf244681d10b79763b2b19/mqtt-core/src/main/java/io/micronaut/mqtt/intercept/AbstractMqttIntroductionAdvice.java#L75
https://github.com/micronaut-projects/micronaut-mqtt/blob/230a6564344ceea21bcf244681d10b79763b2b19/mqttv3/src/main/java/io/micronaut/mqtt/v3/intercept/MqttIntroductionAdvice.java#L48
The publish method will call stmr.addData.
Regards,
Saikat
On Sun, Nov 1, 2020 at 3:14 AM Denis Garus wrote:
> Hello, Saikat!
>
> I know that IgniteMessagin is used in the production environment and
> I don't see any bugs in Jira with this feature.
> I wrote some tests for IgniteMessaging in the security suite, and only one
> confusing thing was noticed [1].
>
> Why did we decide to deprecate IgniyeMessaging API in Ignite 3.0?
>
> 1.
> http://apache-ignite-developers.2346864.n4.nabble.com/Inconsistent-behavior-of-IgniteMessaging-td47481.html
>
> вс, 1 нояб. 2020 г. в 04:43, Michael Pollind :
>
>> I'm looking at this data stream api and I'm having a hard time working out
>> how this scheme fits into the pub sub model that micronaut uses. Here is
>> what I've kind of come up with and wonder if this would work.
>>
>> @PubSubClientpublic interface MultipleMessage {
>>
>> @Topic("animals")
>> public void send(@key() String key, Animal o);
>>
>> @Topic("my_topic")
>> public void send2(@key() Long key, Object o);
>> }
>>
>>
>> @PubSubListener
>>
>> public class SimpleSub {
>>
>> @Subscription("animals")
>>
>> public class Listener(@key() String key, Animal o) {
>>
>> }
>>
>> }
>>
>>
>> On Tue, Oct 27, 2020 at 7:15 PM Saikat Maitra
>> wrote:
>>
>> > Hi Michael, Denis
>> >
>> > I did an initial review of the PR and wanted to share my thoughts. I
>> > observed that currently the implementation is using Ignite messaging
>> apis
>> > and I am thinking if we should change the implementation to use Ignite
>> data
>> > streaming apis. The reason for change is to ensure that it will be
>> better
>> > aligned to Ignite 3.0 release as we are planning to deprecate Ignite
>> > Messaging apis in Ignite 3.0 [1]
>> >
>> > My recommendation to use Ignite data streaming apis is also due to the
>> > fact that we have multiple integration like Google Pub/Sub[2] and Kafka
>> > Streamer[3] that uses Data streaming apis for integration and it will
>> keep
>> > micronaut implementation consistent with other extensions.
>> >
>> > Here is an example[4] of how Kafka Streamer can be used to stream data
>> > into Ignite nodes.
>> >
>> >
>> > [1]
>> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+3.0
>> > [2]
>> >
>> https://github.com/apache/ignite-extensions/blob/master/modules/pub-sub-ext/src/main/java/org/apache/ignite/stream/pubsub/PubSubStreamer.java
>> > [3]
>> >
>> https://github.com/apache/ignite-extensions/blob/master/modules/kafka-ext/src/main/java/org/apache/ignite/stream/kafka/KafkaStreamer.java
>> > [4]
>> >
>> https://github.com/samaitra/streamersk-extensions/blob/main/src/main/kotlin/com/example/streamerskextensions/kafka/KafkaStreamer.kt
>> >
>> > Please let me know your feedback.
>> >
>> > Regards,
>> > Saikat
>> >
>> > On Tue, Oct 27, 2020 at 12:48 PM Denis Magda wrote:
>> >
>> >> Michael, glad to see you back!
>> >>
>> >> Could you please explain in a few words what this integration does and
>> >> what
>> >> it enables for Ignite and Micronaout? So that we are as a community
>> are on
>> >> the same page.
>> >>
>> >> -
>> >> Denis
>> >>
>> >>
>> >> On Sun, Oct 25, 2020 at 3:05 PM Michael Pollind
>> >> wrote:
>> >>
>> >> > I've started to work on adding some basic pubsub support for
>> >> > Micronaut-ignite. I only have a draft PR in progress. There are a
>> couple
>> >> > modules that already implement pub-sub so those modules would be a
>> good
>> >> > start for reference:
>> >> > https://github.com/micronaut-projects/micronaut-gcp
>> >> > https://github.com/micronaut-projects/micronaut-kafka
>> >> > https://github.com/micronaut-projects/micronaut-mqtt
>> >> >
>> >> > https://github.com/micronaut-projects/micronaut-ignite/pull/62
>> >> >
>> >> >
>> >> >
>> >>
>> >
>>
>
[MTCGA]: new failures in builds [5707409] needs to be handled
Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. *New Critical Failure in master-nightly Disk Page Compressions https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_DiskPageCompressions?branch=%3Cdefault%3E No changes in the build - Here's a reminder of what contributors were agreed to do https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute - Should you have any questions please contact dev@ignite.apache.org Best Regards, Apache Ignite TeamCity Bot https://github.com/apache/ignite-teamcity-bot Notification generated at 18:31:21 01-11-2020
[MTCGA]: new failures in builds [5707207, 5705209] needs to be handled
Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
*New Critical Failure in master Cache (Restarts) 1
https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_CacheRestarts1?branch=%3Cdefault%3E
No changes in the build
*Test with high flaky rate in master
PlatformCacheTopologyChangeTest.TestContinuousTopologyChangeMaintainsCorrectPlatformCacheData(2)
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-289285092905892256=%3Cdefault%3E=testDetails
*Test with high flaky rate in master
PartitionAwarenessTest.CacheGet_NewNodeEnteredTopology_RequestIsRoutedToNewNode
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=4293363389832349350=%3Cdefault%3E=testDetails
*Test with high flaky rate in master
PlatformCacheTopologyChangeTest.TestContinuousTopologyChangeMaintainsCorrectPlatformCacheData(1)
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=1020567278715453005=%3Cdefault%3E=testDetails
*Test with high flaky rate in master
PlatformCacheTopologyChangeTest.TestContinuousTopologyChangeMaintainsCorrectPlatformCacheData(0)
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-5107102370162796808=%3Cdefault%3E=testDetails
*Test with high flaky rate in master
PlatformCacheTopologyChangeTest.TestPrimaryNodeChangeClearsPlatformCacheDataOnServer
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=7538483029086413080=%3Cdefault%3E=testDetails
*Test with high flaky rate in master
PartitionAwarenessTest.CachePut_GuidKey_RequestIsRoutedToPrimaryNode("2611e3d2-618d-43b9-a318-2f5039f82568",1)
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-4792247141060534383=%3Cdefault%3E=testDetails
*Test with high flaky rate in master
PlatformCacheTopologyChangeTest.TestPrimaryNodeChangeClearsPlatformCacheDataOnClient(TryPeek)
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=4558562257001335970=%3Cdefault%3E=testDetails
*Test with high flaky rate in master
PartitionAwarenessTest.AllKeyBasedOperations_PrimitiveKeyType_RequestIsRoutedToPrimaryNode(6,2)
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=8844940099918945717=%3Cdefault%3E=testDetails
*Test with high flaky rate in master
PartitionAwarenessTest.CacheGetAsync_PrimitiveKeyType_RequestIsRoutedToPrimaryNode(6,2)
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-8578563276325766615=%3Cdefault%3E=testDetails
*Test with high flaky rate in master
PlatformCacheTopologyChangeTest.TestPrimaryNodeChangeClearsPlatformCacheDataOnClient(Peek)
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-358472204911208093=%3Cdefault%3E=testDetails
*Test with high flaky rate in master ClientConnectionTest.TestFailover
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=5141024434072758432=%3Cdefault%3E=testDetails
*Test with high flaky rate in master
PartitionAwarenessTest.CacheGet_UserDefinedKeyType_RequestIsRoutedToPrimaryNode(1,0)
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=5484854050439054884=%3Cdefault%3E=testDetails
*Test with high flaky rate in master
PlatformCacheTopologyChangeTest.TestPrimaryNodeChangeClearsPlatformCacheDataOnClient(Entries)
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-8202434451519838096=%3Cdefault%3E=testDetails
*Test with high flaky rate in master
PartitionAwarenessTest.CacheGet_PrimitiveKeyType_RequestIsRoutedToPrimaryNode(6,2)
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-4495360811669101527=%3Cdefault%3E=testDetails
*Test with high flaky rate in master
PlatformCacheTopologyChangeTest.TestServerNodeJoinDoesNotAffectNonPrimaryKeysInPlatformCache
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-7952350858345737670=%3Cdefault%3E=testDetails
*Test with high flaky rate in master
PartitionAwarenessTest.CacheGet_UserDefinedKeyType_RequestIsRoutedToPrimaryNode(5,2)
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=1220686906234430281=%3Cdefault%3E=testDetails
*Test with high flaky rate in master
PartitionAwarenessTest.CacheGet_UserDefinedKeyType_RequestIsRoutedToPrimaryNode(6,1)
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-4998885337602260478=%3Cdefault%3E=testDetails
*Test with high flaky rate in master
PartitionAwarenessTest.CachePut_GuidKey_RequestIsRoutedToPrimaryNode("----",0)
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=1810471672936016577=%3Cdefault%3E=testDetails
*Test with high flaky rate in master
PlatformCacheTopologyChangeTest.TestPrimaryNodeLeaveClearsPlatformCache
Re: [Micronaut] pubsub support
Hello, Saikat!
I know that IgniteMessagin is used in the production environment and
I don't see any bugs in Jira with this feature.
I wrote some tests for IgniteMessaging in the security suite, and only one
confusing thing was noticed [1].
Why did we decide to deprecate IgniyeMessaging API in Ignite 3.0?
1.
http://apache-ignite-developers.2346864.n4.nabble.com/Inconsistent-behavior-of-IgniteMessaging-td47481.html
вс, 1 нояб. 2020 г. в 04:43, Michael Pollind :
> I'm looking at this data stream api and I'm having a hard time working out
> how this scheme fits into the pub sub model that micronaut uses. Here is
> what I've kind of come up with and wonder if this would work.
>
> @PubSubClientpublic interface MultipleMessage {
>
> @Topic("animals")
> public void send(@key() String key, Animal o);
>
> @Topic("my_topic")
> public void send2(@key() Long key, Object o);
> }
>
>
> @PubSubListener
>
> public class SimpleSub {
>
> @Subscription("animals")
>
> public class Listener(@key() String key, Animal o) {
>
> }
>
> }
>
>
> On Tue, Oct 27, 2020 at 7:15 PM Saikat Maitra
> wrote:
>
> > Hi Michael, Denis
> >
> > I did an initial review of the PR and wanted to share my thoughts. I
> > observed that currently the implementation is using Ignite messaging apis
> > and I am thinking if we should change the implementation to use Ignite
> data
> > streaming apis. The reason for change is to ensure that it will be better
> > aligned to Ignite 3.0 release as we are planning to deprecate Ignite
> > Messaging apis in Ignite 3.0 [1]
> >
> > My recommendation to use Ignite data streaming apis is also due to the
> > fact that we have multiple integration like Google Pub/Sub[2] and Kafka
> > Streamer[3] that uses Data streaming apis for integration and it will
> keep
> > micronaut implementation consistent with other extensions.
> >
> > Here is an example[4] of how Kafka Streamer can be used to stream data
> > into Ignite nodes.
> >
> >
> > [1] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+3.0
> > [2]
> >
> https://github.com/apache/ignite-extensions/blob/master/modules/pub-sub-ext/src/main/java/org/apache/ignite/stream/pubsub/PubSubStreamer.java
> > [3]
> >
> https://github.com/apache/ignite-extensions/blob/master/modules/kafka-ext/src/main/java/org/apache/ignite/stream/kafka/KafkaStreamer.java
> > [4]
> >
> https://github.com/samaitra/streamersk-extensions/blob/main/src/main/kotlin/com/example/streamerskextensions/kafka/KafkaStreamer.kt
> >
> > Please let me know your feedback.
> >
> > Regards,
> > Saikat
> >
> > On Tue, Oct 27, 2020 at 12:48 PM Denis Magda wrote:
> >
> >> Michael, glad to see you back!
> >>
> >> Could you please explain in a few words what this integration does and
> >> what
> >> it enables for Ignite and Micronaout? So that we are as a community are
> on
> >> the same page.
> >>
> >> -
> >> Denis
> >>
> >>
> >> On Sun, Oct 25, 2020 at 3:05 PM Michael Pollind
> >> wrote:
> >>
> >> > I've started to work on adding some basic pubsub support for
> >> > Micronaut-ignite. I only have a draft PR in progress. There are a
> couple
> >> > modules that already implement pub-sub so those modules would be a
> good
> >> > start for reference:
> >> > https://github.com/micronaut-projects/micronaut-gcp
> >> > https://github.com/micronaut-projects/micronaut-kafka
> >> > https://github.com/micronaut-projects/micronaut-mqtt
> >> >
> >> > https://github.com/micronaut-projects/micronaut-ignite/pull/62
> >> >
> >> >
> >> >
> >>
> >
>
