Re: Re: Cache size getting zero after first restart of server node in 2.13 version

Yes, after starting server node and cluster active and then only pulling cache.size. Krishna, attached server log also, please refer if required. Regards, Ganguly On Wed, May 17, 2023 at 1:45 AM Gianluca Bonetti wrote: > Hello > > You start a client node, do you start a server node too? > >

Re: Assigning specific name to thin client

Hi, Could not see any update on the ticket. https://issues.apache.org/jira/browse/IGNITE-18832 How do we know the plan for the change? Regards, Ganguly On Fri, Feb 17, 2023 at 3:48 AM Ganguly Gundeboina wrote: > Hi, > > I have tried this without enabling authentication and assigning

Cache size getting zero after first restart of server node in 2.13 version

Hi, We recently setup the 2.13 ignite cluster having three server nodes and enabled write services to write the records to the cluster. After few days, want to restart the cluster as part of maintenance activity. After restart all cache sizes showing zero even though data is there and getting

Re: Assigning specific name to thin client

ient_connections > [3] > https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/configuration/ClientConfiguration.html#getUserName-- > > > 17 февр. 2023 г., в 14:06, Ganguly Gundeboina > написал(а): > > Raised ticket for the same > > https://issues.apache.org/jira/b

Re: Assigning specific name to thin client

Documentation (apache.org) > <https://ignite.apache.org/docs/2.14.0/monitoring-metrics/system-views> > > пт, 17 февр. 2023 г. в 09:34, Ganguly Gundeboina >: > >> Hi, >> >> Can someone take the enhancement to capture thin client name in >> sys.client_

Re: Assigning specific name to thin client

on (apache.org) > <https://ignite.apache.org/docs/2.14.0/monitoring-metrics/system-views> > > пт, 17 февр. 2023 г. в 09:34, Ganguly Gundeboina >: > >> Hi, >> >> Can someone take the enhancement to capture thin client name in >> sys.client_connections table

Re: Assigning specific name to thin client

Hi, Can someone take the enhancement to capture thin client name in sys.client_connections table. This is required for monitoring clients. Regards, Gangaiah On Wed, Feb 15, 2023 at 2:05 AM Ganguly Gundeboina wrote: > Hi, > > We could see the sys.client_connections table, but does not

Re: Assigning specific name to thin client

.setUserAttributes to assign custom > key/value pairs to a client instance. Those attributes are accessible on > the server side. > 3. For client-side only logic, there is no built-in way to assign a name > to a client, but you can do that with a HashMap > > On Thu, Nov 11

Re: Unable to join using thick client when authentication is enabled

> IgniteConfiguration#setAuthenticationEnabled(true). > > On 19 Nov 2021, at 11:28, Ganguly Gundeboina > wrote: > > Hi Pavel, > > Yes, we have enabled authentication on server nodes only. > > We could provide user credentials for thin clients, so thin clients are > abl

Re: Unable to join using thick client when authentication is enabled

d as part of [1]. > > Overall, I think it is a good idea to have security on all nodes > configured in the same way. > Do you have it enabled only on server nodes? > > [1] https://issues.apache.org/jira/browse/IGNITE-14335 > > On Fri, Nov 19, 2021 at 9:42 AM Ganguly Gundebo

Re: Unable to join using thick client when authentication is enabled

rovide a full exception for this node? If you can > provide complete logs, it will be even better. > > I see locCls=null, but as I can see from the code it should be > locCls=processor.getClass().getName(). I'm not sure how it can be null. > > Regards, > Andrei > 11/17/2021 8:56 PM

Unable to join using thick client when authentication is enabled

Hi Igniters, We recently started using Ignite version 2.11.0 (native persistence enabled) with authentication enabled. When am trying to connect to cluster using thick client, getting error as below. This was not there with earlier version. I have checked

Assigning specific name to thin client

Hi, Want to assign specific instance name to thin clients to monitor the clients. When thin client disconnected due to any reason, want to take manual action like starting the client. We are using 2.11, can we assign? Regards, Gangaiah

Re: Unable to fetch cache data using thin client for composite keys

ompactFooter(true)) > > On Sun, Nov 7, 2021 at 10:23 PM Ganguly Gundeboina < > gangaiah.ya...@gmail.com> wrote: > >> Hi Pavel, >> >> We are facing the same issue which is mentioned in the below ticket. >> >> https://issues.apache.org/jira/projects/IGNITE

Re: Unable to fetch cache data using thin client for composite keys

iah, > > 1. Can you please share a minimal reproducer? > 2. Did it work before in 2.7.6? > > > On Sun, Nov 7, 2021 at 9:21 PM Ganguly Gundeboina < > gangaiah.ya...@gmail.com> wrote: > >> Hi Igniters, >> >> >> >> We have upgraded to 2.11 fr

Unable to fetch cache data using thin client for composite keys

Hi Igniters, We have upgraded to 2.11 from 2.7.6 and trying to use Ignite thin clients in the latest version i.e. 2.11.0, we found one weird issue, *get/getAll* call is not returning data for caches which has *complex/composite key *(Same is working with thick clients properly). Has anyone came

Re: [External]Re: Client taking long time to connect to cluster

Hi Gianluca, Thanks for your response. Below are jvm details for both server and client, *SERVER:* [tibusr@SERVERIP bin]$ ./java -version java version "1.8.0_251" Java(TM) SE Runtime Environment (build 1.8.0_251-b08) Java HotSpot(TM) 64-Bit Server VM (build 25.251-b08, mixed mode) export