Re: Confusion/inaccurate visor stats

[Alex Plehanov]

Hello, Eugene!

> 2) How come Non-heap memory usage is minimal?
"Non-heap memory" here it's JVM managed memory regions other then heap used
for internal JVM purposes (JIT compiler, method area, etc.), it's not a
memory used by Ignite to store data (information about this memory can be
obtained by data region metrics).

> 3) How can I tell how much memory the table is consuming?
AFAIK there is no such functionality in visor now. There is JMX metric
CacheGroupMetricsMXBean#getTotalAllocatedSize, which can help you, but
unfortunately there is the bug in current implementation of this metric
with persistent store enabled (ticket [1], already fixed, fix will be
available in Ignite 2.7) and there still no implementation of this metric
with persistence disabled (ticket [2]).

[1]: https://issues.apache.org/jira/browse/IGNITE-8515
[2]: https://issues.apache.org/jira/browse/IGNITE-8517


2018-08-17 18:37 GMT+03:00 Alexey Kuznetsov :

> Hi!
>
> > 1) In Data region metrics, why is everything 0?
> Did you enable metrics?
>
> See:
>   DataRegionConfiguration dataRegionCfg = new DataRegionConfiguration();
>   dataRegionCfg.setMetricsEnabled(true);
>
> > 4) Total busy time is 15s, the upload took longer than that.
> This is actually time spend in compute engine see:
> org.apache.ignite.cluster.ClusterMetrics
> /**
>  * Gets total time this node spent executing jobs.
>  * @return Total time this node spent executing jobs.
>  */
> public long getTotalBusyTime();
>
> I hope 2) & 3) will answer some one who knows about it.
>
> --
> Alexey Kuznetsov
>
>

Re: Source code of latest benchmarks

[akurbanov]

Hi,

Sounds fantastic! 
There is no separate repository for benchmarks, the latest version you can
find is in master branch here:
https://github.com/apache/ignite/tree/master/modules/yardstick.

Discussions and contributions are always welcome, if you have some insights
on what could be improved/added, devlist would be a great place to start
sharing your thoughts with Ignite dev community:
http://apache-ignite-developers.2346864.n4.nabble.com





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

Re: SQl Fields Query Using Java date

[siva]

Yes,I came the reason ,i have changed already existing object field
type(string to date ) which  ignite don't support ,that is the reason its
trowed  serialization exception .


Thanks *akurbanov *for your support.



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

Re: Possible issue with Web Console

[Alexey Kuznetsov]

Vishwas,

You may clone Ignite repo and cherry-pick a commit.
And build from sources.

Will this work for you?

On Fri, Aug 17, 2018 at 5:27 PM vbm  wrote:

> Hi,
>
> Can this fix be backported to 2.5 or 2.6 version ?
>
> Regards,
> Vishwas
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
> --
> Alexey Kuznetsov
> 
>

Re: Confusion/inaccurate visor stats

[Alexey Kuznetsov]

Hi!

> 1) In Data region metrics, why is everything 0?
Did you enable metrics?

See:
  DataRegionConfiguration dataRegionCfg = new DataRegionConfiguration();
  dataRegionCfg.setMetricsEnabled(true);

> 4) Total busy time is 15s, the upload took longer than that.
This is actually time spend in compute engine see:
org.apache.ignite.cluster.ClusterMetrics
/**
 * Gets total time this node spent executing jobs.
 * @return Total time this node spent executing jobs.
 */
public long getTotalBusyTime();

I hope 2) & 3) will answer some one who knows about it.

-- 
Alexey Kuznetsov

Confusion/inaccurate visor stats

[eugene miretsky]

Hello,

I am running a single Ignite node on a r4.8xlarge EC2 node. I am using the
default settings with 132G allocated for the default memory region. So far
I have uploaded 1 large table 60M rows using Spark

The output of node and cache commands is pasted bellow.

A few questions
1) In Data region metrics, why is everything 0?
2) How come Non-heap memory usage is minimal?
3) How can I tell how much memory the table is consuming?
4) Total busy time is 15s, the upload took longer than that.

Cheers,
Eugene


*Visor output*

Time of the snapshot: 2018-08-17 15:06:37

+---+

| ID  | b19229cd-c6c2-4cfe-ba82-3fb0ac0946b9
|

| ID8 | B19229CD
|

| Node Type   | Server
|

| Order   | 1
|

| Address (0) | 172.17.0.1
|

| Address (1) | 172.21.85.213
|

| Address (2) | 127.0.0.1
|

| Address (3) | 0:0:0:0:0:0:0:1%lo
|

| OS info | Linux amd64 4.4.0-1062-aws
|

| OS user | root
|

| Deployment mode | SHARED
|

| Language runtime| Java Platform API Specification ver. 1.8
|

| Ignite version  | 2.5.0
|

| Ignite instance name| 
|

| JRE information | HotSpot 64-Bit Tiered Compilers
|

| JVM start time  | 2018-08-17 13:52:05
|

| Node start time | 2018-08-17 13:52:07
|

| Up time | 01:02:17.619
|

| CPUs| 32
|

| Last metric update  | 2018-08-17 14:54:23
|

| Non-loopback IPs| 172.17.0.1, 172.21.85.213,
fe80:0:0:0:59:71ff:fe32:36e%ens3 |

| Enabled MACs| 0242652B992A, 02597132036E
|

| Maximum active jobs | 1
|

| Current active jobs | 0
|

| Average active jobs | 0.00
|

| Maximum waiting jobs| 0
|

| Current waiting jobs| 0
|

| Average waiting jobs| 0.00
|

| Maximum rejected jobs   | 0
|

| Current rejected jobs   | 0
|

| Average rejected jobs   | 0.00
|

| Maximum cancelled jobs  | 0
|

| Current cancelled jobs  | 0
|

| Average cancelled jobs  | 0.00
|

| Total rejected jobs | 0
|

| Total executed jobs | 9
|

| Total cancelled jobs| 0
|

| Maximum job wait time   | 0ms
|

| Current job wait time   | 0ms
|

| Average job wait time   | 0.00ms
|

| Maximum job execute time| 0ms
|

| Current job execute time| 0ms
|

| Average job execute time| 0.00ms
|

| Total busy time | 15724ms
|

| Busy time % | 0.42%
|

| Current CPU load %  | 0.03%
|

| Average CPU load %  | 5.03%
|

| Heap memory initialized | 32gb
|

| Heap memory used| 57gb
|

| Heap memory committed   | 113gb
|

| Heap memory maximum | 178gb
|

| Non-heap memory initialized | 2mb
|

| Non-heap memory used| 75mb
|

| Non-heap memory committed   | 76mb
|

| Non-heap memory maximum | 496mb
|

| Current thread count| 230
|

| Maximum thread count| 233
|

| Total started thread count  | 391
|

| Current daemon thread count | 13
|

+---+


Data region metrics:

++

|  Name  | Page size |   Pages|  Memory   |  Rates
| Checkpoint buffer | Large entries |

++

| Default_Region | 0 | Total:  0  | Total:  0 | Allocation:
0.00 | Pages: 0  | 0.00% |

||   | Dirty:  0  | In RAM: 0 |
Eviction:   0.00
| Size:  0  |   |

||   | Memory: 0  |   |
Replace:

Re:

[Ilya Kasnacheev]

Hello!

Please try notifying Ignite about your types so that you can use them
immediately (without putting to cache first):

ignite.GetBinary().GetBinaryType(typeof(TestEntityKey));
ignite.GetBinary().GetBinaryType(typeof(TestEntity));

that before your Console.WriteLine() line.

Regards,

-- 
Ilya Kasnacheev

2018-08-17 16:28 GMT+03:00 Som Som <2av10...@gmail.com>:

> I’v got an ignite java server node and  a client node which is c#
> application
>
> public partial class TestEntityKey
>
> {
>
> public string s1 { get; set; }
>
> public string s2 { get; set; }
>
> }
>
>
>
> public partial class TestEntity
>
> {
>
> public string v1 { get; set; }
>
> public string v2 { get; set; }
>
> }
>
>
>
> static void Main(string[] args)
>
> {
>
> var ignite = Ignition.StartFromApplicationConfiguration();
>
>
>
> var qe = new QueryEntity
>
> {
>
> KeyType = typeof(TestEntityKey),
>
> ValueType = typeof(TestEntity),
>
> Fields = new[]
>
> {
>
> new QueryField {Name = "s1", FieldType =
> typeof(string) IsKeyField = true},
>
> new QueryField {Name = "s2", FieldType =
> typeof(string) IsKeyField = true },
>
> new QueryField {Name = "v1", FieldType =
> typeof(string) },
>
> new QueryField {Name = "v2", FieldType =
> typeof(string) },
>
> }
>
> };
>
>
>
> var testCache = ignite.GetOrCreateCache TestEntity>
>
> (
>
> new CacheConfiguration
>
> {
>
> Name = "TestEntity",
>
> QueryEntities = new[]
>
> {
>
> qe
>
> },
>
> SqlSchema = "PUBLIC"
>
> }
>
> );
>
> Console.WriteLine("Press any key...");
>
> Console.ReadKey();
>
>
>
> ignite.Dispose();
>
> }
>
> I started client application then added one row into TestEntity table via
> DBeaver, there was no problem on that point. Than I added one line of code
> into my client application
>
> *Console**.WriteLine(**$"\n**{ToString(testCache.FirstOrDefault())}**\n"*
> *);”*
>
> and got an error: “Requesting mapping from grid failed for [platformId=1,
> typeId=-232515692]” after that I added one more line just before the first
> one
>
> testCache.Put(new TestEntityKey(), newTestEntity());
>
> and after that I saw two rows of my TestEntity table without anybproblems.
>
> Isn’t it an error?
>

[no subject]

[Som Som]

I’v got an ignite java server node and  a client node which is c#
application

public partial class TestEntityKey

{

public string s1 { get; set; }

public string s2 { get; set; }

}



public partial class TestEntity

{

public string v1 { get; set; }

public string v2 { get; set; }

}



static void Main(string[] args)

{

var ignite = Ignition.StartFromApplicationConfiguration();



var qe = new QueryEntity

{

KeyType = typeof(TestEntityKey),

ValueType = typeof(TestEntity),

Fields = new[]

{

new QueryField {Name = "s1", FieldType =
typeof(string) IsKeyField = true},

new QueryField {Name = "s2", FieldType =
typeof(string) IsKeyField = true },

new QueryField {Name = "v1", FieldType =
typeof(string) },

new QueryField {Name = "v2", FieldType =
typeof(string) },

}

};



var testCache = ignite.GetOrCreateCache

(

new CacheConfiguration

{

Name = "TestEntity",

QueryEntities = new[]

{

qe

},

SqlSchema = "PUBLIC"

}

);

Console.WriteLine("Press any key...");

Console.ReadKey();



ignite.Dispose();

}

I started client application then added one row into TestEntity table via
DBeaver, there was no problem on that point. Than I added one line of code
into my client application

*Console**.WriteLine(**$"\n**{ToString(testCache.FirstOrDefault())}**\n"*
*);”*

and got an error: “Requesting mapping from grid failed for [platformId=1,
typeId=-232515692]” after that I added one more line just before the first
one

testCache.Put(new TestEntityKey(), newTestEntity());

and after that I saw two rows of my TestEntity table without anybproblems.

Isn’t it an error?

Re: Ignite SQL Queries not getting all data back in ignite 2.4 and 2.6

[yfernando]

The above error appears to be an issue in
org.apache.ignite.internal.processors.cache.CacheMetricsSnapshot in a
mismatch between the readExternal() and writeExternal() methods.

I've made a change locally and it fixed the error and also the testing so
far seems to show that the queries return the correct results (so it's
likely that the cause may have been
https://issues.apache.org/jira/browse/IGNITE-8900)

If you would like me to contribute the fix back to the ignite codebase
please let me know and i'll be happy to do it



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

Re: Ignite memory leak

[Igor Tanackovic]

Thx... will yry the fix.


Regards,
Igor

On Fri, Aug 17, 2018 at 11:24 Denis Mekhanikov 
wrote:

> Igor,
>
> The fix for this issue is merged to master. It will be included into
> Ignite 2.7.
> Until then you can use one of the nightly builds, available at
> https://ci.ignite.apache.org/viewLog.html?buildId=lastSuccessful=Releases_NightlyRelease_RunApacheIgniteNightlyRelease=artifacts=1
>
> Denis
>
> пн, 6 авг. 2018 г. в 15:01, Denis Mekhanikov :
>
>> Igor,
>>
>> There really is a memory leak in this place.
>> Thank you for the analysis! This is very cool!
>>
>> I filed a JIRA ticket for it:
>> https://issues.apache.org/jira/browse/IGNITE-9196
>> Feel free to assign it to yourself and fix it, since you already debugged
>> through it.
>> If not, then I think, it will be fixed in Ignite 2.7 anyway.
>>
>> Denis
>>
>> сб, 4 авг. 2018 г. в 19:11, igor.tanackovic :
>>
>>> Hi,
>>>
>>> I want to discuss about potential memory leak in Ignite (I imply
>>> potential
>>> mem leak as I'm not 100% sure I do something wrong ;))
>>>
>>> However, believe I found a corner case which triggers memory leak even
>>> with
>>> the lates stable version. In my case, MapQueryResults fills
>>> MapNodeResults
>>> map without being removed which leads to out of memory exception or huge
>>> gc
>>> major collections. I'm pretty sure the issue is in *fetchNextPage*
>>> method of
>>> MapQueryResult class as this method never returns *true* if you have
>>> result
>>> set with pageSize*n records.
>>>
>>> Actually, we had a major issue with memory in our production cluster and
>>> the
>>> only workaround was to limit all queries bellow page size (currently
>>> 1024).
>>>
>>>
>>> Regards,
>>> Igor
>>>
>>>
>>>
>>>
>>> --
>>> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>>>
>>

Re: Ignite benchamrking issue

[debashissinha]

Hi ,
The issue is 
failed to set up benchmark drivers java.lang.nullpointerexception



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

Re: Possible issue with Web Console

[vbm]

Hi,

Can this fix be backported to 2.5 or 2.6 version ?

Regards,
Vishwas



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

Re: Ignite memory leak

[Denis Mekhanikov]

Igor,

The fix for this issue is merged to master. It will be included into Ignite
2.7.
Until then you can use one of the nightly builds, available at
https://ci.ignite.apache.org/viewLog.html?buildId=lastSuccessful=Releases_NightlyRelease_RunApacheIgniteNightlyRelease=artifacts=1

Denis

пн, 6 авг. 2018 г. в 15:01, Denis Mekhanikov :

> Igor,
>
> There really is a memory leak in this place.
> Thank you for the analysis! This is very cool!
>
> I filed a JIRA ticket for it:
> https://issues.apache.org/jira/browse/IGNITE-9196
> Feel free to assign it to yourself and fix it, since you already debugged
> through it.
> If not, then I think, it will be fixed in Ignite 2.7 anyway.
>
> Denis
>
> сб, 4 авг. 2018 г. в 19:11, igor.tanackovic :
>
>> Hi,
>>
>> I want to discuss about potential memory leak in Ignite (I imply potential
>> mem leak as I'm not 100% sure I do something wrong ;))
>>
>> However, believe I found a corner case which triggers memory leak even
>> with
>> the lates stable version. In my case, MapQueryResults fills MapNodeResults
>> map without being removed which leads to out of memory exception or huge
>> gc
>> major collections. I'm pretty sure the issue is in *fetchNextPage* method
>> of
>> MapQueryResult class as this method never returns *true* if you have
>> result
>> set with pageSize*n records.
>>
>> Actually, we had a major issue with memory in our production cluster and
>> the
>> only workaround was to limit all queries bellow page size (currently
>> 1024).
>>
>>
>> Regards,
>> Igor
>>
>>
>>
>>
>> --
>> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>>
>

Re: While enabling JCache, JCacheMetrics is throwing NullPointerException in getCacheManager with spring boot

[Вячеслав Коптилин]

  Hello,

As I mentioned above, this exception indicates that the cache with the
given name already exists in the cluster.

Thanks,
S.

пт, 17 авг. 2018 г., 10:52 daya airody :

> Hi Slava,
>
> other reply is about issues in caching Spring proxied objects.
>
> I am also seeing "Cache already exists" issue. Could you please throw some
> light on this?
>
> Thanks in advance,
> --daya--
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

答复: why my ignite cluster went to compatibility mode

[Huang Meilong]

Thank you Alex, but why one of my ignite nodes went down abnormally?


发件人: Alex Plehanov 
发送时间: 2018年8月17日 15:58:07
收件人: user@ignite.apache.org
主题: Re: why my ignite cluster went to compatibility mode

Hi, Huang,

Already was discussed here [1]. You probably run visor (daemon node) to join 
cluster, which switch cluster to compatibility mode. You can restart to switch 
it to normal state again. Fix (ticket IGNITE-8774) will be available in Ignite 
2.7

[1]: 
http://apache-ignite-users.70518.x6.nabble.com/Node-with-BaselineTopology-cannot-join-mixed-cluster-running-in-compatibility-mode-td22200.html

2018-08-17 10:36 GMT+03:00 Huang Meilong 
mailto:ims...@outlook.com>>:

Hi all,


I'm new to ignite, I started a ignite cluster with three nodes yesterday(with 
command: ./ignite.sh -v -np 
/root/apache-ignite-fabric-2.6.0-bin/examples/config/persistentstore/examples-persistent-store.xml),
 I found one node is down without any log today, and when I try to restart the 
lost node, it say that cluster is in compatibility mode and can not join new 
node. How can I restart the new node?


"""

[15:19:14,299][INFO][tcp-disco-sock-reader-#5][TcpDiscoverySpi] Started serving 
remote node connection 
[rmtAddr=/172.16.157.129:34695, rmtPort=34695]
[15:19:14,414][SEVERE][tcp-disco-msg-worker-#3][TcpDiscoverySpi] 
TcpDiscoverSpi's message worker thread failed abnormally. Stopping the node in 
order to prevent cluster wide instability.
class org.apache.ignite.IgniteException: Node with BaselineTopology cannot join 
mixed cluster running in compatibility mode
at 
org.apache.ignite.internal.processors.cluster.GridClusterStateProcessor.onGridDataReceived(GridClusterStateProcessor.java:714)
at 
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$5.onExchange(GridDiscoveryManager.java:883)
at 
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.onExchange(TcpDiscoverySpi.java:1939)
at 
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processNodeAddedMessage(ServerImpl.java:4354)
at 
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2744)
at 
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2536)
at 
org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerAdapter.body(ServerImpl.java:6775)
at 
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.body(ServerImpl.java:2621)
at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
[15:19:14,423][SEVERE][tcp-disco-msg-worker-#3][] Critical system error 
detected. Will be handled accordingly to configured handler [hnd=class 
o.a.i.failure.StopNodeOrHaltFailureHandler, failureCtx=FailureContext 
[type=SYSTEM_WORKER_TERMINATION, err=class o.a.i.IgniteException: Node with 
BaselineTopology cannot join mixed cluster running in compatibility mode]]
class org.apache.ignite.IgniteException: Node with BaselineTopology cannot join 
mixed cluster running in compatibility mode
at 
org.apache.ignite.internal.processors.cluster.GridClusterStateProcessor.onGridDataReceived(GridClusterStateProcessor.java:714)
at 
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$5.onExchange(GridDiscoveryManager.java:883)
at 
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.onExchange(TcpDiscoverySpi.java:1939)
at 
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processNodeAddedMessage(ServerImpl.java:4354)
at 
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2744)
at 
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2536)
at 
org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerAdapter.body(ServerImpl.java:6775)
at 
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.body(ServerImpl.java:2621)
at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
[15:19:14,424][SEVERE][tcp-disco-msg-worker-#3][] JVM will be halted 
immediately due to the failure: [failureCtx=FailureContext 
[type=SYSTEM_WORKER_TERMINATION, err=class o.a.i.IgniteException: Node with 
BaselineTopology cannot join mixed cluster running in compatibility mode]]


"""


Thanks,

Huang

Re: Possible issue with Web Console

[Vasiliy Sisko]

Hello @sv
Problem is fixed and will be available in Ignite 2.7.
As a workaround you can download a valid configuration immediately after
configuration page refresh.



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

Re: why my ignite cluster went to compatibility mode

[Alex Plehanov]

Hi, Huang,

Already was discussed here [1]. You probably run visor (daemon node) to
join cluster, which switch cluster to compatibility mode. You can restart
to switch it to normal state again. Fix (ticket IGNITE-8774) will be
available in Ignite 2.7

[1]:
http://apache-ignite-users.70518.x6.nabble.com/Node-with-BaselineTopology-cannot-join-mixed-cluster-running-in-compatibility-mode-td22200.html

2018-08-17 10:36 GMT+03:00 Huang Meilong :

> Hi all,
>
>
> I'm new to ignite, I started a ignite cluster with three nodes
> yesterday(with command: ./ignite.sh -v -np /root/apache-ignite-fabric-2.
> 6.0-bin/examples/config/persistentstore/examples-persistent-store.xml), I
> found one node is down without any log today, and when I try to restart the
> lost node, it say that cluster is in compatibility mode and can not join
> new node. How can I restart the new node?
>
>
> """
>
> [15:19:14,299][INFO][tcp-disco-sock-reader-#5][TcpDiscoverySpi] Started
> serving remote node connection [rmtAddr=/172.16.157.129:34695,
> rmtPort=34695]
> [15:19:14,414][SEVERE][tcp-disco-msg-worker-#3][TcpDiscoverySpi]
> TcpDiscoverSpi's message worker thread failed abnormally. Stopping the node
> in order to prevent cluster wide instability.
> class org.apache.ignite.IgniteException: Node with BaselineTopology
> cannot join mixed cluster running in compatibility mode
> at org.apache.ignite.internal.processors.cluster.
> GridClusterStateProcessor.onGridDataReceived(GridClusterStateProcessor.
> java:714)
> at org.apache.ignite.internal.managers.discovery.
> GridDiscoveryManager$5.onExchange(GridDiscoveryManager.java:883)
> at org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.
> onExchange(TcpDiscoverySpi.java:1939)
> at org.apache.ignite.spi.discovery.tcp.ServerImpl$
> RingMessageWorker.processNodeAddedMessage(ServerImpl.java:4354)
> at org.apache.ignite.spi.discovery.tcp.ServerImpl$
> RingMessageWorker.processMessage(ServerImpl.java:2744)
> at org.apache.ignite.spi.discovery.tcp.ServerImpl$
> RingMessageWorker.processMessage(ServerImpl.java:2536)
> at org.apache.ignite.spi.discovery.tcp.ServerImpl$
> MessageWorkerAdapter.body(ServerImpl.java:6775)
> at org.apache.ignite.spi.discovery.tcp.ServerImpl$
> RingMessageWorker.body(ServerImpl.java:2621)
> at org.apache.ignite.spi.IgniteSpiThread.run(
> IgniteSpiThread.java:62)
> [15:19:14,423][SEVERE][tcp-disco-msg-worker-#3][] Critical system error
> detected. Will be handled accordingly to configured handler [hnd=class
> o.a.i.failure.StopNodeOrHaltFailureHandler, failureCtx=FailureContext
> [type=SYSTEM_WORKER_TERMINATION, err=class o.a.i.IgniteException: Node
> with BaselineTopology cannot join mixed cluster running in compatibility
> mode]]
> class org.apache.ignite.IgniteException: Node with BaselineTopology
> cannot join mixed cluster running in compatibility mode
> at org.apache.ignite.internal.processors.cluster.
> GridClusterStateProcessor.onGridDataReceived(GridClusterStateProcessor.
> java:714)
> at org.apache.ignite.internal.managers.discovery.
> GridDiscoveryManager$5.onExchange(GridDiscoveryManager.java:883)
> at org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.
> onExchange(TcpDiscoverySpi.java:1939)
> at org.apache.ignite.spi.discovery.tcp.ServerImpl$
> RingMessageWorker.processNodeAddedMessage(ServerImpl.java:4354)
> at org.apache.ignite.spi.discovery.tcp.ServerImpl$
> RingMessageWorker.processMessage(ServerImpl.java:2744)
> at org.apache.ignite.spi.discovery.tcp.ServerImpl$
> RingMessageWorker.processMessage(ServerImpl.java:2536)
> at org.apache.ignite.spi.discovery.tcp.ServerImpl$
> MessageWorkerAdapter.body(ServerImpl.java:6775)
> at org.apache.ignite.spi.discovery.tcp.ServerImpl$
> RingMessageWorker.body(ServerImpl.java:2621)
> at org.apache.ignite.spi.IgniteSpiThread.run(
> IgniteSpiThread.java:62)
> [15:19:14,424][SEVERE][tcp-disco-msg-worker-#3][] JVM will be halted
> immediately due to the failure: [failureCtx=FailureContext
> [type=SYSTEM_WORKER_TERMINATION, err=class o.a.i.IgniteException: Node
> with BaselineTopology cannot join mixed cluster running in compatibility
> mode]]
>
> """
>
>
> Thanks,
>
> Huang
>

Re: While enabling JCache, JCacheMetrics is throwing NullPointerException in getCacheManager with spring boot

[daya airody]

Hi Slava,

other reply is about issues in caching Spring proxied objects.

I am also seeing "Cache already exists" issue. Could you please throw some
light on this?

Thanks in advance,
--daya--




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

Re: values retrieved from the cache are wrapped with JdkDynamicAopProxy while using springboot and JCache

[daya airody]

Thanks Ivan. 

If methodCache is marked as transient, proxied objects are not meant to be
cached. Since this object is returned by spring JPA, hibernate second level
caching might be enough. Looks like we should not cache JPA returned objects
at method level.



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

why my ignite cluster went to compatibility mode

[Huang Meilong]

Hi all,


I'm new to ignite, I started a ignite cluster with three nodes yesterday(with 
command: ./ignite.sh -v -np 
/root/apache-ignite-fabric-2.6.0-bin/examples/config/persistentstore/examples-persistent-store.xml),
 I found one node is down without any log today, and when I try to restart the 
lost node, it say that cluster is in compatibility mode and can not join new 
node. How can I restart the new node?


"""

[15:19:14,299][INFO][tcp-disco-sock-reader-#5][TcpDiscoverySpi] Started serving 
remote node connection [rmtAddr=/172.16.157.129:34695, rmtPort=34695]
[15:19:14,414][SEVERE][tcp-disco-msg-worker-#3][TcpDiscoverySpi] 
TcpDiscoverSpi's message worker thread failed abnormally. Stopping the node in 
order to prevent cluster wide instability.
class org.apache.ignite.IgniteException: Node with BaselineTopology cannot join 
mixed cluster running in compatibility mode
at 
org.apache.ignite.internal.processors.cluster.GridClusterStateProcessor.onGridDataReceived(GridClusterStateProcessor.java:714)
at 
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$5.onExchange(GridDiscoveryManager.java:883)
at 
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.onExchange(TcpDiscoverySpi.java:1939)
at 
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processNodeAddedMessage(ServerImpl.java:4354)
at 
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2744)
at 
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2536)
at 
org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerAdapter.body(ServerImpl.java:6775)
at 
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.body(ServerImpl.java:2621)
at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
[15:19:14,423][SEVERE][tcp-disco-msg-worker-#3][] Critical system error 
detected. Will be handled accordingly to configured handler [hnd=class 
o.a.i.failure.StopNodeOrHaltFailureHandler, failureCtx=FailureContext 
[type=SYSTEM_WORKER_TERMINATION, err=class o.a.i.IgniteException: Node with 
BaselineTopology cannot join mixed cluster running in compatibility mode]]
class org.apache.ignite.IgniteException: Node with BaselineTopology cannot join 
mixed cluster running in compatibility mode
at 
org.apache.ignite.internal.processors.cluster.GridClusterStateProcessor.onGridDataReceived(GridClusterStateProcessor.java:714)
at 
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$5.onExchange(GridDiscoveryManager.java:883)
at 
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.onExchange(TcpDiscoverySpi.java:1939)
at 
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processNodeAddedMessage(ServerImpl.java:4354)
at 
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2744)
at 
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2536)
at 
org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerAdapter.body(ServerImpl.java:6775)
at 
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.body(ServerImpl.java:2621)
at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
[15:19:14,424][SEVERE][tcp-disco-msg-worker-#3][] JVM will be halted 
immediately due to the failure: [failureCtx=FailureContext 
[type=SYSTEM_WORKER_TERMINATION, err=class o.a.i.IgniteException: Node with 
BaselineTopology cannot join mixed cluster running in compatibility mode]]


"""


Thanks,

Huang