Apache Ignite with PosgreSQL

[Harsh Mishra]

*Objective:* To scale existing application where PostgreSQL is used as a
data store.

*How can Apache Ignite help:* We have an application which has many modules
and all the modules are using some shared tables. So we have only one
PostgreSQL master database and It's already on AWS large SSD machines. We
already have Redis for caching but as we no limitation of Redis is, It's
not easy partial updates and querying on secondary indexes.

*Our use case:* We have two big tables, one is member and second is
subscription. It's many to many relations where one member is subscribed in
multiple groups and we are maintaining subscriptions in subscription table.
Member table size is around 40 million and size of this table is around 40M
x 1.5KB + more ~= 60GB

*Challenge*

A challenge is, we can't archive this data since every member is working
and there are frequent updates and read on this table.

*My thought:*

Apache Ignite can help to provide a caching layer on top of PostgreSQL
table, as per I read from the documentation.

   -

   Now, I have a couple of questions from an Implementation point of view.
   1. Will Apache Ignite fits in our use case? If Yes then,
  2. Will apache Ignite keep all data 60GB in RAM? Or we can distribute
  RAM load on multiple machines?
  3. On updating PostgreSQL database table, we are using python and
  SQLALchamy (ORM). Will there be a separate call for Apache
Ignite to update
  the same record in memory OR IS there any way that Apache Ignite can sync
  it immediately from Database?
  4. Is there enough support for Python?
  5. Are there REST API support to Interact with Apache Ignite. I can
  avoid ODBC connection.
  6. How about If this load becomes double in next one year?

A quick answer is much appreciated and Thanks in Advance.
Please help.

-- 
Regards,
*Harsh Mishra** | Solution Architect*
Quovantis Technologies
Mobile: +91-9958311308
Skype ID: harshmishra1984
www.quovantis.com

Re: Blocked: Migrate PosgreSQL JSONB data in Apache Ignite

[Harsh Mishra]

Hi Iliya,

Thanks for the reply. I will follow your suggestions.

Does cache API support full document post and Partial update?

API doc seems confusing.

In my case, a table has all normal columns(int, varchar, char, boolean,
date, timestamp) + a custom column that has JSON data.

My requirement is:
1. Add new record.
2. Update - Full or partial. I have JSON, Array fields also.
3. Delete
4. Querying it? by many where clauses which can have string operations,
logical operators and date operators.

5. JoIN(for now, It's optional)
I could not find something which can fulfill all mentioned cases.


- Harsh



On Wed, May 30, 2018 at 9:05 PM, ilya.kasnacheev 
wrote:

> Hello!
>
> Apache Ignite in SQL mode doesn't have special support for
> "destructure-able" datatypes. This means you can put your JSON into VARCHAR
> or BLOB and hope that performance will be sufficient.
>
> I would recommend using Cache API instead of SQL for such use cases, where
> you can collocate processing with data and handle complex data structures.
> Do affinity calls or use StreamReceiver, save on round-trips.
>
> Regards,
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>



-- 
Regards,
*Harsh Mishra** | Solution Architect*
Quovantis Technologies
Mobile: +91-9958311308
Skype ID: harshmishra1984
www.quovantis.com

SQL Query error

[Stéphane Gayet]

Hi all,


We have installed a 2.4 Ignite cluster

- 3 nodes under Windows systems (24 Go, 16 Go, 16 Go)

- 4 caches configured, partitioned, no backup

- no persistence


cache @c0 contains around 60,000 items,

cache @c3 contains few items (around 200) but items are very large.


We run sql queries which aggregate the @c0 items in large collections (until 
14,000 items per collection) and store the result in @c3.


After a while, the sql query stop functionning. The following error is logged :


2018-05-30 23:14:42,716 [282] ERROR 
org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor - 
Failed to execute local query.

Here is our cache configuration :

  


  

  
  


  

  
  

  

  
  

  

  


I tried to clear the items of @c0 cache before re-populate it but I got the 
error :

2018-05-30 23:34:34,333 [16] ERROR ServiceCache - Failed to delete OwItems 
older than 2018-05-31
Apache.Ignite.Core.Common.IgniteException: Failed to execute map query on the 
node: b9f240d6-0ee6-4dee-bda0-51088a743481, class 
org.apache.ignite.internal.processors.query.IgniteSQLException:Failed to set 
schema for DB connection for thread [schema=owproposals] ---> 
Apache.Ignite.Core.Common.JavaException: class 
org.apache.ignite.IgniteCheckedException: Failed to execute map query on the 
node: b9f240d6-0ee6-4dee-bda0-51088a743481, class 
org.apache.ignite.internal.processors.query.IgniteSQLException:Failed to set 
schema for DB connection for thread [schema=owproposals]
at 
org.apache.ignite.internal.processors.platform.utils.PlatformUtils.unwrapQueryException(PlatformUtils.java:519)
at 
org.apache.ignite.internal.processors.platform.cache.query.PlatformAbstractQueryCursor.processOutStream(PlatformAbstractQueryCursor.java:132)
at 
org.apache.ignite.internal.processors.platform.PlatformTargetProxyImpl.outStream(PlatformTargetProxyImpl.java:93)
Caused by: javax.cache.CacheException: Failed to run map query remotely.Failed 
to execute map query on the node: b9f240d6-0ee6-4dee-bda0-51088a743481, class 
org.apache.ignite.internal.processors.query.IgniteSQLException:Failed to set 
schema for DB connection for thread [schema=owproposals]
at 
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:747)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$8.iterator(IgniteH2Indexing.java:1339)
at 
org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:95)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$9.iterator(IgniteH2Indexing.java:1403)
at 
org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:95)
at 
org.apache.ignite.internal.processors.cache.QueryCursorImpl.getAll(QueryCursorImpl.java:127)
at 
org.apache.ignite.internal.processors.platform.cache.query.PlatformAbstractQueryCursor.processOutStream(PlatformAbstractQueryCursor.java:127)
... 1 more
Caused by: javax.cache.CacheException: Failed to execute map query on the node: 
b9f240d6-0ee6-4dee-bda0-51088a743481, class 
org.apache.ignite.internal.processors.query.IgniteSQLException:Failed to set 
schema for DB connection for thread [schema=owproposals]
at 
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.fail(GridReduceQueryExecutor.java:275)
at 
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onFail(GridReduceQueryExecutor.java:265)
at 
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onMessage(GridReduceQueryExecutor.java:244)
at 
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor$2.onMessage(GridReduceQueryExecutor.java:188)
at 
org.apache.ignite.internal.managers.communication.GridIoManager$ArrayListener.onMessage(GridIoManager.java:2332)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1555)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1183)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:126)
at 
org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1090)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

   à Apache.Ignite.Core.Impl.Unmanaged.Jni.Env.ExceptionCheck()
   à Apache.Ignite.Core.Impl.Unmanaged.UnmanagedUtils.TargetOutStream(GlobalRef 
target, Int32 opType, Int64 memPtr)
   à Apache.Ignite.Core.Impl.PlatformJniTarget.OutStream[T](Int32 type, Func`2 
readAction)
   --- Fin de la trace de la pile d'exception interne ---
   à Apache.Ignite.Core.Impl.PlatformJniTarget.OutStream[T](Int32 

Re: Agent not able to connect

[Peter Ivanov]

Humphrey,

AFAIK, Web Console Standalone is deliberately designed to have
self-contained Web Agent.
Can you try separate Web Console docker image from experimental nightly
build? [1]


[1]
https://ci.ignite.apache.org/viewLog.html?buildId=1320479=Releases_NightlyRelease_ApacheIgniteNightlyRelease3AssembleDockerImageIgnite8526=artifacts=1


On Wed, 30 May 2018 at 19:52, Humphrey  wrote:

> Looks like it can't connect to the webconsole as the webconsole is only
> listening to localhost:
>
> Start listening on 127.0.0.1:3000
>
> How can we change this so that the agents (which have different IP) in the
> cluster are able to communicate with the webconsole?
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Agent not able to connect

[Humphrey]

Looks like it can't connect to the webconsole as the webconsole is only
listening to localhost:

Start listening on 127.0.0.1:3000

How can we change this so that the agents (which have different IP) in the
cluster are able to communicate with the webconsole?



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

Re: Agent not able to connect

[Humphrey]

Web agent I used was apacheignite/web-console-standalone from docker hub.
Am able to login and see the corresponding token used in the agent from the
profile.



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

Agent not able

[Humphrey]

Hi,

I'm trying to deploy Ignite in minikube.
I've started in a separate container WebConsole (and separate Pod).
I when I start my other Pod that contains my ServerNode and WebAgent, I get
the error below. How can I solve that?

I suppose that it is able to connect to the rest server on the same machine,
when I do 
curl http://localhost:8080/ignite?cmd=version
I do get:
{"successStatus":0,"sessionToken":null,"response":"2.4.0","error":null}

I also suppose that it can connect to the webconsole:
curl http://demo-webconsole:3001  
curl: (7) Failed to connect to demo-webconsole port 3001: Connection refused

Why is this connection being refused, I'm using a valid token.





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

Re: QueryCursor.getAll() performance is very very low !!!

[ilya.kasnacheev]

Hello!

Please provide your key and value classes in case you're using indexed types
(annotations).

Regards,



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

Re: Access REST API using HTTPS

[ilya.kasnacheev]

Hello!

Have you tried setting sslEnabled=true property on ConnectorConfiguration,
setting sslFactory also?

Regards,



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

Re: Blocked: Migrate PosgreSQL JSONB data in Apache Ignite

[ilya.kasnacheev]

Hello!

Apache Ignite in SQL mode doesn't have special support for
"destructure-able" datatypes. This means you can put your JSON into VARCHAR
or BLOB and hope that performance will be sufficient.

I would recommend using Cache API instead of SQL for such use cases, where
you can collocate processing with data and handle complex data structures.
Do affinity calls or use StreamReceiver, save on round-trips.

Regards,



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

Blocked: Migrate PosgreSQL JSONB data in Apache Ignite

[Harsh Mishra]

Hi,

Objective: JSON handling in Apache Ignite

I am using PostgreSQL database and one table has JSONB data type so I can
add any type of key in DB.
How to handle this case in Apache Ignite.

TABLE STRUCTURE(Partial)

app_member_id character varying(64) DEFAULT NULL::character varying,
mobile_os character varying(64) DEFAULT NULL::character varying,
app_name character varying(64) DEFAULT NULL::character varying,
deleted boolean DEFAULT false,
preferred_language bigint,
client_member_id character varying(256) DEFAULT NULL::character varying,
*custom_data jsonb DEFAULT '{}'::jsonb,*
encrypted_data bytea,
useragent text,


Data in custom_data column is like this but key name is dynamic. I do read
update these custom fields very frequently.

{"date1": "2018-05-16", "time1": "00:30:00", "number2": 123, "picklist1":
5, "paragraph1": "I am loving elasticsearch.", "singleline1": "Singleline1
data", "multipicklist1": [7, 8]}

Please let me know, I am right now blocked.

-- 

Regards,
*Harsh Mishra** | Solution Architect*
Quovantis Technologies
Mobile: +91-9958311308
Skype ID: harshmishra1984
www.quovantis.com

Access REST API using HTTPS

[Sudheer.Panta]

Hi,

I did enable SSL on, but I could not access REST API using https.
I was trying to access as below, it does not work.

Please let me know if I need to configure anything else..?

https://localhost:8443/ignite?cmd=top=true=true=127.0.0.1

My Configuration is as below:


  

  



  






  

  






I could see "tls/ssl=on" in my logs.

[30-05-2018 19:42:48][INFO ][main][IgniteKernal] Security status 
[authentication=off, tls/ssl=on]


This e-mail and any files transmitted with it are for the sole use of the 
intended recipient(s) and may contain confidential and privileged information. 
If you are not the intended recipient(s), please reply to the sender and 
destroy all copies of the original message. Any unauthorized review, use, 
disclosure, dissemination, forwarding, printing or copying of this email, 
and/or any action taken in reliance on the contents of this e-mail is strictly 
prohibited and may be unlawful. Where permitted by applicable law, this e-mail 
and other e-mail communications sent to and from Cognizant e-mail addresses may 
be monitored.


jetty-server.xml
Description: jetty-server.xml

Re: IGNITE-4985: Do not acquire asyncOp semaphore for retry operations and Maximum permit count exceeded on Semaphore in Ignite 2.3...

[Stanislav Lukyanov]

Please resend this to the Ignite developers list - d...@ignite.apache.org. The
discussions of code changes happen there.
user@ignite.apache.org is for more user-oriented questions.

Thanks,
Stan



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

Re: Cache not rebalanced after one node is restarted

[Stanislav Lukyanov]

Most likely you've run into this bug:
https://issues.apache.org/jira/browse/IGNITE-8210

It was fixed in 2.5, try updating to that version.

Thanks,
Stan



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

Re: Large durable caches

[Alexey Goncharuk]

Ray,

Which Ignite version are you running on. You may be affected by [1] which
becomes worse the larger the data set is. Please wait for the Ignite 2.5
release which will be available shortly.

[1] https://issues.apache.org/jira/browse/IGNITE-7638

пт, 18 мая 2018 г. в 5:44, Ray :

> I ran into this issue as well.
> I'm running tests on a six node Ignite node cluster, the data load stuck
> after 1 billion data is ingested.
> Can someone take a look at this issue please?
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Failed to connect Apache Ignite cache to Tableau

[Igor Sapego]

This is OK, you don't need to do anything, Tableau
just tries some queries on connection, that Ignite does
not support. It won't preserve you from working with
Tableau.

Best Regards,
Igor

On Tue, May 29, 2018 at 8:14 PM, manuelmourato 
wrote:

> I am trying to connect Tableau to my Ignite (version 2.2) cache in a
> different host.
>
> I have followed the steps mentioned here
> https://apacheignite-sql.readme.io/docs/tableau , and everything worked
> well.
>
> However, when I try to connect to the Apache Ignite Driver, as described in
> this section:
> https://apacheignite-sql.readme.io/docs/tableau#
> section-connecting-to-cluster
> , I get the following error on the Ignite cluster logs:
>
> 
> ---
>
> 01_E355260B_0EAB_4918_80CD_DD45C322815F_1_Connect (
> COL INTEGER
> ) ON COMMIT PRESERVE ROWS, args=[]]]
> class org.apache.ignite.internal.processors.query.IgniteSQLException:
> Failed
> to parse query: CREATE LOCAL TEMPORARY TABLE
> XT01_E355260B_0EAB_4918_80CD_DD45C322815F_1_Connect (
> COL INTEGER
> ) ON COMMIT PRESERVE ROWS
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.
> queryDistributedSqlFields(IgniteH2Indexing.java:1293)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$6.applyx(
> GridQueryProcessor.java:1856)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$6.applyx(
> GridQueryProcessor.java:1852)
> at
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.
> apply(IgniteOutClosureX.java:36)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.
> executeQuery(GridQueryProcessor.java:2293)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.
> querySqlFieldsNoCache(GridQueryProcessor.java:1860)
> at
> org.apache.ignite.internal.processors.odbc.odbc.OdbcRequestHandler.
> executeQuery(OdbcRequestHandler.java:192)
> at
> org.apache.ignite.internal.processors.odbc.odbc.OdbcRequestHandler.handle(
> OdbcRequestHandler.java:126)
> at
> org.apache.ignite.internal.processors.odbc.SqlListenerNioListener.
> onMessage(SqlListenerNioListener.java:152)
> at
> org.apache.ignite.internal.processors.odbc.SqlListenerNioListener.
> onMessage(SqlListenerNioListener.java:44)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterChain$
> TailFilter.onMessageReceived(GridNioFilterChain.java:279)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.
> proceedMessageReceived(GridNioFilterAdapter.java:109)
> at
> org.apache.ignite.internal.util.nio.GridNioAsyncNotifyFilter$3.
> body(GridNioAsyncNotifyFilter.java:97)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at
> org.apache.ignite.internal.util.worker.GridWorkerPool$1.
> run(GridWorkerPool.java:70)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(
> ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(
> ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: org.h2.jdbc.JdbcSQLException: Syntax error in SQL statement
> "CREATE LOCAL TEMPORARY TABLE
> XT01_E355260B_0EAB_4918_80CD_DD45C322815F_1_CONNECT (
> COL INTEGER
> ) ON COMMIT PRESERVE[*] ROWS "; SQL statement:
> CREATE LOCAL TEMPORARY TABLE
> XT01_E355260B_0EAB_4918_80CD_DD45C322815F_1_Connect (
> COL INTEGER
> ) ON COMMIT PRESERVE ROWS [42000-195]
> at
> org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
> at org.h2.message.DbException.get(DbException.java:179)
> at org.h2.message.DbException.get(DbException.java:155)
> at org.h2.message.DbException.getSyntaxError(DbException.java:191)
> at org.h2.command.Parser.getSyntaxError(Parser.java:533)
> at org.h2.command.Parser.prepareCommand(Parser.java:260)
> at org.h2.engine.Session.prepareLocal(Session.java:573)
> at org.h2.engine.Session.prepareCommand(Session.java:514)
> at
> org.h2.jdbc.JdbcConnection.prepareCommand(JdbcConnection.java:1204)
> at
> org.h2.jdbc.JdbcPreparedStatement.(JdbcPreparedStatement.java:73)
> at
> org.h2.jdbc.JdbcConnection.prepareStatement(JdbcConnection.java:288)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.
> prepareStatement(IgniteH2Indexing.java:398)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.
> queryDistributedSqlFields(IgniteH2Indexing.java:1273)
> ... 17 more
> [16:53:02,274][SEVERE][sql-connector-#112%ignite_node1%][
> OdbcRequestHandler]
> Failed to execute SQL query [reqId=48, req=OdbcQueryExecuteRequest
> [schema=Test_Data, sqlQry=DROP TABLE
> XT01_E355260B_0EAB_4918_80CD_DD45C322815F_1_Connect, args=[]]]
> 

Re: [TcpCommunicationSpi] Close incoming connection, unknown node

[Yakov Zhdanov]

Hi!

>From this log [1] I see that local node (id=06b8bcb7) reported 18 node
failed events 1 for server node and 17 for clients. Communication
sub-system closes incoming connections from nodes that are not in topology.

We need to understand:
1. Why this node failed? Probably it started segmentation process and
should have been shut down soon. Can you grep all logs for "SEGMENTED"
string?

2018/05/24 18:55:21.666 [WARN
][disco-event-worker-#61][GridDiscoveryManager] Node FAILED:
TcpDiscoveryNode [id=a0533414-4d5d-4fa0-9555-9a893e865de9,
addrs=[10.0.0.14, 127.0.0.1], sockAddrs=[/127.0.0.1:47500,
CDNode0I.hlbdeyzzwm2ujgdsre0nhzw3sg.dx.internal.cloudapp.net/10.0.0.14:47500],
discPort=47500, order=5, intOrder=5, lastExchangeTime=1526495846007,
loc=false, ver=2.5.0#20180511-sha1:89c77573, isClient=false]

2. Why clients connected to that server node did not reconnect to another
one? Do you see consistent NODE FAILED events and consistent topology
version among all nodes in topology?

Can you share the logs from the entire topology? I think this will help a
lot with investigations.

[1]
http://apache-ignite-users.70518.x6.nabble.com/file/t1784/ignite-node04.log

--Yakov

2018-05-29 22:18 GMT+03:00 crenique :

> Hi,
>  We have been running ignite v2.5.0 snapshot (2018/5/11) fine for about two
> weeks.
> But suddenly, the grid stopped responding with massive infinite log spams,
> /
> 2018/05/24 18:56:14.909 [INFO
> ][grid-nio-worker-tcp-comm-5-#46][TcpCommunicationSpi] Accepted incoming
> communication connection [locAddr=/10.0.0.38:47102,
> rmtAddr=/10.0.0.29:53819]
> 2018/05/24 18:56:14.910 [WARN
> ][grid-nio-worker-tcp-comm-5-#46][TcpCommunicationSpi] Close incoming
> connection, unknown node [nodeId=2f4ed0a7-cf1f-4ad1-a6eb-e4171985eb97,
> ses=GridSelectorNioSessionImpl [worker=DirectNioClientWorker
> [super=AbstractNioClientWorker [idx=5, bytesRcvd=39218524780,
> bytesSent=34572936118, bytesRcvd0=159844, bytesSent0=273948, select=true,
> super=GridWorker [name=grid-nio-worker-tcp-comm-5,
> igniteInstanceName=null,
> finished=false, hashCode=1499496401, interrupted=false,
> runner=grid-nio-worker-tcp-comm-5-#46]]],
> writeBuf=java.nio.DirectByteBuffer[pos=0 lim=32768 cap=32768],
> readBuf=java.nio.DirectByteBuffer[pos=42 lim=42 cap=32768],
> inRecovery=null,
> outRecovery=null, super=GridNioSessionImpl [locAddr=/10.0.0.38:47102,
> rmtAddr=/10.0.0.29:53819, createTime=1527188174903, closeTime=0,
> bytesSent=18, bytesRcvd=42, bytesSent0=18, bytesRcvd0=42,
> sndSchedTime=1527188174903, lastSndTime=1527188174903,
> lastRcvTime=1527188174903, readsPaused=false,
> filterChain=FilterChain[filters=[GridNioCodecFilter
> [parser=o.a.i.i.util.nio.GridDirectParser@60af162b, directMode=true],
> GridConnectionBytesVerifyFilter], accepted=true]]]
> 2018/05/24 18:56:15.006 [WARN
> ][sys-stripe-14-#15][GridDhtPartitionTopologyImpl] Requested topology
> version does not match calculated diff, will require full iteration
> tocalculate mapping [grp=, topVer=AffinityTopologyVersion [topVer=121,
> minorTopVer=0], diffVer=AffinityTopologyVersion [topVer=138,
> minorTopVer=0]]/
>
>
>  It appears that ignite server in node04 was causing it. So after killed
> the
> specific ignite server instance, the grid stopped spamming errors.
> Please see attached ignite grid configuration and logs.
>
> Can you please provide any tips or information to track down what could
> trigger this problem and fix it ?
>
>
> *Jvm options*
> "-Duser.timezone=UTC",
> "-DIGNITE_QUIET=false",
> "-Djava.net.preferIPv4Stack=true",
> "-Djava.awt.headless=true",
> "-Xms10g",
> "-Xmx10g",
> "-XX:+AlwaysPreTouch",
> "-XX:+UseG1GC",
> "-XX:+ScavengeBeforeFullGC",
> "-XX:+DisableExplicitGC"
>
>
> *Ignite configs*
> Topology snapshot [ver=120, servers=40, clients=80, CPUs=640,
> offheap=480.0GB, heap=560.0GB]
> Default_Region [initSize=2.0 GiB, maxSize=4.0 GiB,
> persistenceEnabled=false]
>
> ignite-config.xml
>  t1784/ignite-config.xml>
> ignite-cache-config.txt
>  t1784/ignite-cache-config.txt>
>
>
> *Logs*
> ignite-startup-logs.txt
>  t1784/ignite-startup-logs.txt>
> ignite-node04.log
>  t1784/ignite-node04.log>
> ignite-node18.log
>  t1784/ignite-node18.log>
>
>
>
> Thanks
> Sam
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Error with ignite-rest-http

[Humphrey]

Hi I had the same issue when using SpringBoot 1.5.10.RELEASE with apache
ignite 2.4.0.

Was fixed when using telling spring boot to use other (older) version by
specifying the following:

9.2.11.v20150529


Humphrey



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