Apache Ignite with PosgreSQL

*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 machin

Re: Blocked: Migrate PosgreSQL JSONB data in Apache Ignite

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 i

SQL Query error

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 querie

Re: Agent not able to connect

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&buildTypeId=Releases_NightlyRelease_ApacheIgniteNigh

Re: Agent not able to connect

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-u

Re: Agent not able to connect

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

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 m

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

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

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

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 processi

Blocked: Migrate PosgreSQL JSONB data in Apache Ignite

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, mobi

Access REST API using HTTPS

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&attr=true&mtr=true&ip=127.0.0.1 My Configuration is as below:

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

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

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

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 th

Re: Failed to connect Apache Ignite cache to Tableau

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 (versio

Re: [TcpCommunicationSpi] Close incoming connection, unknown node

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 segmentatio

Re: Error with ignite-rest-http

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.x