There is a bug in the ValidationOnNodeJoinUtils class

The validation class ValidationOnNodeJoinUtils has been added. It does not matter if the write cache is not configured. After the cache is configured in the cache, it will verify ctx.discovery (). CacheAffinityNode (ctx.discovery (). LocalNode (), cc. getName () this method, ctx.discovery ().

Re: Connection reset by peer

Detailed error message： Established outgoing communication connection [locAddr=/10.122.64.129:40870, rmtAddr=/10.122.64.128:48339] [01:01:59,775][SEVERE][grid-nio-worker-tcp-comm-1-#48%SubScriptionCluster%][TcpCommunicationSpi] Failed to process selector key [ses=GridSelectorNioSessionImpl

Connection reset by peer

^-- System thread pool [active=0, idle=6, qSize=0] [16:57:36,455][SEVERE][grid-nio-worker-tcp-comm-3-#50%SubScriptionCluster%][TcpCommunicationSpi] Failed to process selector key [ses=GridSelectorNioSessionImpl [worker=DirectNioClientWorker [super=AbstractNioClientWorker [idx=3,

Failed to send message

[11:32:46,462][SEVERE][sys-stripe-20-#21%SubScriptionCluster%][query] Failed to send event notification to node: 5995d947-e1f6-4210-8507-cfe7d805503e class org.apache.ignite.IgniteCheckedException: Failed to send message (node may have left the grid or TCP connection cannot be established due to

Re: Getting javax.cache.CacheException after upgrading to Ignite 2.7

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

when cluster restart then client need deactived

When the xml configuration file of the ignite cluster changes, the cluster stops, and the cluster needs to be restarted. After the startup, because the cluster is configured with the baseline, the cluster is automatically activated after the restart, but the client connection will be, prompting

Mysql and ignite persistence inheritance issues

Ignite does not enable the persistence function. The startup is to connect to the MySql database. The Sql statement can be run in Ignite to automatically load the data in mysql. In Ignite, select, insert, update, delete, etc., if the data in the memory does not exist, then Automatically load data

the third-party persistence problem

If don't open the persistence in Ignite server startup, as in-memory database to use, can achieve using the Sql query data, if not in the memory, automatic to from the mysql database and loaded into memory, there is a new data to the automatic synchronization to mysql, or Ignite in future versions

third-party persistence problem

If don't open the persistence in Ignite server startup, as in-memory database to use, can achieve using the Sql query data, if not in the memory, automatic to from the mysql database and loaded into memory, there is a new data to the automatic synchronization to mysql, or Ignite in future versions

Ignite is a third-party persistence problem

If don't open the persistence in Ignite server startup, as in-memory database to use, can achieve using the Sql query data, if not in the memory, automatic to from the mysql database and loaded into memory, there is a new data to the automatic synchronization to mysql, or Ignite in future versions

Ignite and third party database realize data persistence real - time loading problem

If don't open the persistence in Ignite server startup, as in-memory database to use, can achieve using the Sql query data, if not in the memory, automatically pulled from the mysql database and loaded into memory, there is a new data to the automatic synchronization to mysql, or Ignite in future

server always shutdown

Ignite. Sh start multi-node server side is very unstable, often appear process termination situation, I now is running on a server three cluster nodes, three servers make up three cluster environment, often a server node will hang, I do not know what situation -- Sent from:

server ignite.sh always shutdown

Ignite. Sh start multi-node server side is very unstable, often appear process termination situation, I now is running on a server three cluster nodes, three servers make up three cluster environment, often a server node will hang, I do not know what situation -- Sent from:

server ignite.sh always shutdown

Ignite. Sh start multi-node server side is very unstable, often appear process termination situation, I now is running on a server three cluster nodes, three servers make up three cluster environment, often a server node will hang, I do not know what situation -- Sent from:

Multiple table data load problems are configured in a cache

Two tables are configured in a Customer cache, including the JDBC map of the third-party database. How to import the data using the LoadCache method? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Unix timestamp conversion problem

Now the time stamp of conversion positive number is not a problem, but the time of conversion negative number is not accurate, is this BUG, which god has encountered again -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Data index loss problem

Recently discovered a problem, don't know what the reason, one of the data in the Table a Long field with the Select * from Table where nameid = value when the query data, but the use of Select * from Table where nameid like '% value can find data, prove the existence of the data is the data, but

Additional field problems occurred in ignite2.6

Ignite2.6 configured POJO field mapping, in the case of Ignite2.3 field is uppercase or lowercase, only will be mapped to Ignite the memory among the field names, but in the ignite2.6 if the field names in the JAVA entity class and Ignite the Config fields in the configuration file name case is

Transaction return value problem

Ignite enables transactions to determine how to perform certain operations after a successful transaction is executed, is transaction propagation currently supported, and how to inherit from Spring's transactions? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: The problem after the ignite upgrade

I opened the persistent storage cluster, version 2.3 as long as the boot server and then activate the cluster when the client can be connected directly, after upgrading to 2.6, after activation server cluster for the first time the client connection complains, you then need to Deactive the cluster

The problem after the ignite upgrade

The problem with the Ignite version upgrading from 2.3 to 2.6 is that when the Server side starts up, the client will report an error when connecting to the Server side. The client must first stop activating the Server side, then connect with the client once, and then reactivate the Server side

How do I rename multiple clusters

The ignite official console monitors multiple clusters, but all cluster names are uuid names, which are difficult to manage. How do you change multiple clusters to other names Ignite Web Control Like this： Cluster:0D8FC815 Cluster:0E30C03F When there are many clusters, it is not

If the authenticationEnabled is true Ignite web control conneced failed

If the attribute is opened, an error is reported when starting the monitoring cluster using the official web control platform Agent configuration: User's security tokens: 5NfQ URI to Ignite node REST server: http://127.0.0.1:9380 URI to Ignite Console server :

Missing shu is a cross-cache associated query.

My ignite configuration file looks something like this.

How do you configure affinityKey in xml

How do you configure affinityKey in apache ignite and implement the Join between multiple partition caches after the JDBC client connects to the cluster? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

How to query cross-node Cache data with JDBC correlation?

Hello, ask, apache ignite using JDBC thin client connection, use the select the from the cache. The table where the name in (select the name from otherCache. Table) when the returned result is data of the current connection node, other nodes can't return of data, how to solve this problem --

如何用jdbc 关联查询跨节点Cache数据

Hello, ask, apache ignite using JDBC thin client connection, use the select the from the cache. The table where the name in (select the name from otherCache. Table) when the returned result is data of the current connection node, other nodes can't return of data, how to solve this problem --

Re: apache ignite Id return null

For example: mysql has two fields create table testa (id bigint not null, name varchar (20), primary key (id)) and in Ignite corresponding entity class private Long id; private String name; When using springboot to start The client creates an entity class object using the object's Set method to

apache ignite Id return null

Hello, the project is on my side to Ignite + mysql + springboot build platform, mysql do persistent storage, Save in the client program through the program records at the time of the query can return to normal content ID, but the client via JDBC Insert Into to Cache the data at the time of the