NullPointerException when destroying caches

[Garaude, Benjamin]

Hello,

If I destroy a cache when a service is deployed, there is an error message with 
a NullPointerException that is logged by ignite.
This does not seems harmful to me, since the cache destroying terminates 
successfully. Can you confirm that?
Its also annoying because it pollutes the logs a lot.

This happens in 2.8.1 and 2.8.0, but not in 2.7.x or lower.

You can find attached an example to reproduce this.

The error message and stack trace are the following:
Sep 02, 2020 8:50:29 AM org.apache.ignite.logger.java.JavaLogger error
SEVERE: Failed to notify direct custom event listener: DynamicCacheChangeBatch 
[id=553849d4471-5ac52f5c-11b5-454f-965e-3c6e7bcb7a5a, reqs=ArrayList 
[DynamicCacheChangeRequest [cacheName=foo, hasCfg=false, 
nodeId=2e57fb89-5665-48fb-a0e9-fbd880e8d4b3, clientStartOnly=false, stop=true, 
destroy=false, disabledAfterStartfalse]], exchangeActions=ExchangeActions 
[startCaches=null, stopCaches=[foo], startGrps=[], stopGrps=[foo, 
destroy=true], resetParts=null, stateChangeRequest=null], startCaches=false]
java.lang.NullPointerException
   at 
org.apache.ignite.internal.processors.service.IgniteServiceProcessor.lambda$processDynamicCacheChangeRequest$6(IgniteServiceProcessor.java:1694)
   at java.util.Collection.removeIf(Collection.java:414)
   at 
org.apache.ignite.internal.processors.service.IgniteServiceProcessor.processDynamicCacheChangeRequest(IgniteServiceProcessor.java:1691)
   at 
org.apache.ignite.internal.processors.service.IgniteServiceProcessor.access$200(IgniteServiceProcessor.java:108)
   at 
org.apache.ignite.internal.processors.service.IgniteServiceProcessor$3.onCustomEvent(IgniteServiceProcessor.java:232)
   at 
org.apache.ignite.internal.processors.service.IgniteServiceProcessor$3.onCustomEvent(IgniteServiceProcessor.java:229)
   at 
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:665)
   at 
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.lambda$onDiscovery$0(GridDiscoveryManager.java:528)
   at 
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body0(GridDiscoveryManager.java:2608)
   at 
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body(GridDiscoveryManager.java:2646)
   at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
   at java.lang.Thread.run(Thread.java:748)



Regards,


Benjamin


Main.java
Description: Main.java

partition loss policy exception??

[kay]

Hello, I have a question about PartitionLossPolicy..

I configure partitionLossPolicy for 'READ_ONLY_SAFE' specific cache and If
some reason that I don't know occur a partition loss.

Then, when I access to loss partition for read using java thin client, What
happend?

Is it throw a exception? If throw a Exception, What is a Exception Name??


I'll waiting for reply.

Thank you so much.








--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

How to persist data only on selected nodes but not all nodes in cluster

[xingjl6280]

Hi team,

My cluster is running in Replicated cache mode, to ensure no data loss if
any node is down.

Now I'm going to to enable persistence, but I don't want each node to to
hold a full backup. 
Is it possible to make some of nodes persist, while the rest are running in
pure memory mode to read and write same set of data?

I'm quite confused with Baseline topology.
I saw this in documentation:

*Moreover, the cluster can have cluster nodes that are not a part of the
baseline topology such as:
Server nodes that either store data in memory or persist it to a 3rd party
database like RDBMS or NoSQL.*



But I also find this statement seems conflict to above

*The new node cannot hold data of caches/tables who persist data in Ignite
persistence.*


please kindly advise.
thank you

Regards



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Lag before records are visible after transaction commit

[Evgenii Zhuravlev]

Hi,

Checked this reproducer. Continuous Query itself is not transactional and
it looks like it can't be used for this at the moment. So, it gets
notification before other entries were committed.

Best Regards,
Evgenii

вт, 1 сент. 2020 г. в 00:34, ssansoy :

> Hi is anyone able to help look into/reproduce this with the example code
> given? thanks!
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Possible to change cache config without destroying and recreating cache?

[bhlewka]

Hi All, 

I have an ignite cache that is getting an affinity backup filter function
added
(https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/cache/affinity/rendezvous/ClusterNodeAttributeAffinityBackupFilter.html)
to it, and I'm noticing that it isn't working unless it is a newly created
cache. 

Is it possible to change/add this filter function to caches that are already
created and contain data, or do they have to be destroyed and recreated?

Thanks!



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

NullPointerException when destroying cache

[Benjamin]

Hello,

If I destroy a cache when a node singleton service is deployed, a
NullPointerException is logged.
The cache destroying process still terminates successfully though.
So it does not seems harmful, but it pollutes the logs and I wonder if it's
really harmless.

This happens in 2.8.0 and 2.8.1, but not in 2.7.5.


You can find attached a simple example reproducing this.  Main.java
  

The error message is the following:
Sep 01, 2020 10:46:35 AM org.apache.ignite.logger.java.JavaLogger error
SEVERE: Failed to notify direct custom event listener:
DynamicCacheChangeBatch
[id=33788d84471-920edd0a-25b5-4d6d-9684-33f0524e9e0d, reqs=ArrayList
[DynamicCacheChangeRequest [cacheName=foo, hasCfg=false,
nodeId=d9234a21-9fa5-48b3-904b-d84a9cee9d25, clientStartOnly=false,
stop=true, destroy=false, disabledAfterStartfalse]],
exchangeActions=ExchangeActions [startCaches=null, stopCaches=[foo],
startGrps=[], stopGrps=[foo, destroy=true], resetParts=null,
stateChangeRequest=null], startCaches=false]
java.lang.NullPointerException
at
org.apache.ignite.internal.processors.service.IgniteServiceProcessor.lambda$processDynamicCacheChangeRequest$6(IgniteServiceProcessor.java:1694)
at java.util.Collection.removeIf(Collection.java:414)
at
org.apache.ignite.internal.processors.service.IgniteServiceProcessor.processDynamicCacheChangeRequest(IgniteServiceProcessor.java:1691)
at
org.apache.ignite.internal.processors.service.IgniteServiceProcessor.access$200(IgniteServiceProcessor.java:108)
at
org.apache.ignite.internal.processors.service.IgniteServiceProcessor$3.onCustomEvent(IgniteServiceProcessor.java:232)
at
org.apache.ignite.internal.processors.service.IgniteServiceProcessor$3.onCustomEvent(IgniteServiceProcessor.java:229)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:665)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.lambda$onDiscovery$0(GridDiscoveryManager.java:528)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body0(GridDiscoveryManager.java:2625)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body(GridDiscoveryManager.java:2663)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at java.lang.Thread.run(Thread.java:748)




--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: [WARN] Failed to read magic header log

[Vladislav Pyatkov]

Hi,

Can you provide a log from another node, that started on 42.1.188.128?
My thought that node configured differently, may be SSL configured.

On Tue, Sep 1, 2020 at 10:27 AM kay  wrote:

> Hello, I'm waiting for reply..
>
> rmtAddr port is always change..
>
> Is it normal or I don't have to care log msg??
> these log shows every 3~5 seconds.
>
> Thank u so much.
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>


-- 
Vladislav Pyatkov

Re: Lag before records are visible after transaction commit

[ssansoy]

Hi is anyone able to help look into/reproduce this with the example code
given? thanks!



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: [WARN] Failed to read magic header log

[kay]

Hello, I'm waiting for reply..

rmtAddr port is always change..

Is it normal or I don't have to care log msg??
these log shows every 3~5 seconds.

Thank u so much.



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/