Hi Andrew,
Thanks for the reply. Removing index did helped. But we got the same issue
in one more query. Could you let us know how to what could be the issue
here.
02:51:52.591 [http-/172.30.8.97:8443-27] WARN
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing - Query
execution is
Could any one please help me with the bewlo error.
This is my ignite configuration
**
consumerConfig = new CacheConfiguration<>(CONSUMER_CACHE);
consumerConfig.setMemoryMode(CacheMemoryMode.OFFHEAP_TIERED);
Metrics for local node (to disable set 'metricsLogFrequency' to 0)
^-- Node [id=718e07db, name=null, uptime=00:23:00:107]
^-- H/N/C [hosts=2, nodes=2, CPUs=8]
^-- CPU [cur=1.33%, avg=5.81%, GC=0%]
^-- Heap [used=10261MB, free=42.67%, comm=17900MB]
^-- Non heap [used=1225MB,
Pasting the log for all
13:02:02,263 INFO [stdout] (Thread-2214) Time taken to sucessfully save
binary document with idCBHealthCheck in couchbase 3
13:02:51,402 INFO [org.jboss.web] (ServerService Thread Pool -- 540)
JBAS018224: Unregister web context: /JwDupCheck
13:02:51,457 ERROR [stderr]
Hi All,
We have used the apache ignite in our tool OutSystems. Where we are invoking
the ignite via a external API.
For any time we makes changes to the Espace(i.e. war) we need to re-publish
i.e. deployment again.
When we perform continuous deployment, we see the espace deployment get
stopped.
Its on the same machine. I am not sure how to put these node IP in the
configuration file properly. Could youu guide me please.
From: vkulichenko [via Apache Ignite Users]
[mailto:ml-node+s70518n11124...@n6.nabble.com]
Sent: Friday, March 10, 2017 8:52 PM
To: Abhijit Prusty
I am using the below config for the multicast but seems its not forming the
topology. I am using a JBOSS server which is clustered.
127.0.0.1:47500..47509
TcpDiscoveryMulticastIpFinder has no pre-configured addresses (it is
recommended in production to specify at least one address in
TcpDiscoveryMulticastIpFinder.getAddresses() configuration property)
11:32:54,260 WARNING