Thanks for the update Andrei. We upgraded from 2.6.0 to 2.7.6.
We followed the same approach and it worked properly.
Can we change INLINE SIZE for every cache at runtime ?
Thanks and Regards,
Kamlesh Joshi
-Original Message-
From: aealexsandrov
Sent: 27 July 2020 19:35
To: user@igni
The client can create a queue, and the servers will keep items of that
queue. Those items will be stored in memory and disk tiers of the servers.
And, yes, physically the records will be persisted in the database folder
(that is under the work folder by default). Hope this helps.
-
Denis
On Fri,
Hi,
Documentation looks not very clean for me. Probably you should prepare your
operating system to use swap space. Can you try to prepare the swap file
first as following:
https://linuxize.com/post/how-to-add-swap-space-on-ubuntu-18-04/
And then choose this file.
BR,
Andrei
--
Sent from: h
Hi,
Are you sure that you don't have connectivity problems there? Is it possible
to share full logs?
BR,
Andrei
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi,
Can you please clarify the version from which you upgraded?
I know that it's possible that if you used a pretty old version then you
should also rebuild your indexes during the upgrade because inline size
calculation logic was changed in last releases.
It can be done by removing index.bin f
Hi,
Your log doesn't have the full thread dumps and I can't find some
information (e.g Topology Snapshots). However, I see that checkpoint thread
was blocked for a long time:
[02:45:50,849][SEVERE][tcp-disco-msg-worker-[3dac150e
10.20.4.18:47500]-#2][G] Blocked system-critical thread has been det
Hi Cameron,
I suppose the correct way of achieving the desired behavior is to modify
WebSessionFilter from the Ignite.
For example it's possible to introduce a new context param with a list of
urls that shouldn't be affected by the filter.
And pass a request to a chain in the doFilter method if th
Tested with Windows and Linux K8 containers all on Java 11.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi,
I am using C++ Ignite Thin Client (2.8.1 version) to store values in cache
on an Ignite local node.
On Ignite log, I get many of the following error messages:
[09:41:13,542][WARNING][grid-nio-worker-client-listener-3-#33][ClientListenerProcessor]
Client disconnected abruptly due to network co
