Please find below
ignite version: apache-ignite-2.11.1
VM information: OpenJDK Runtime Environment 11.0.15+9-LTS
On Wed, Aug 31, 2022 at 12:12 AM Stephen Darlington <
stephen.darling...@gridgain.com> wrote:
> Which version of Ignite? Which version of Java?
>
> On 30 Aug 2022, at 13:40, Surinder
hello,
When there is insufficient memory, if a page replacement occurs, will
the data be swapped out of memory first, or will the index also be
swapped out of memory?
Or are there any optimized algorithms?
Which version of Ignite? Which version of Java?
On 30 Aug 2022, at 13:40, Surinder Mehra wrote:
>
>
> Hi Stephen ,
> yes that is implemented correctly and it's running on server nodes as well.
> Somehow it doesn't work when accessed through proxy
>
>> On Tue, Aug 30, 2022 at 5:45 PM
Hi Stephen ,
yes that is implemented correctly and it's running on server nodes as
well. Somehow it doesn't work when accessed through proxy
On Tue, Aug 30, 2022 at 5:45 PM Stephen Darlington <
stephen.darling...@gridgain.com> wrote:
> Your service needs to implement
Your service needs to implement org.apache.ignite.services.Service.
> On 30 Aug 2022, at 12:40, Surinder Mehra wrote:
>
> Hi,
> can you help me find out the reason for this exception in thick client while
> getting instance of ignite service:
>
> getIgnite()
> .services()
>
Hi,
can you help me find out the reason for this exception in thick client
while getting instance of ignite service:
getIgnite()
.services()
.serviceProxy("sampleService", SampleService.class, false)
java.lang.ClassCastException: class com.sun.proxy.$Proxy148 cannot be cast
to class
Hi,
Sorry for the late reply, I somehow missed your message.
Yes, thick client starts a JVM with the whole Ignite inside, while thin
client does not and does not depend on JDK.
Actually, thick client is not only a client but can also be a C++ server
node.
You are right, NearCache is not
