Are you actually experiencing this problem? Or is this theoretical? As Ilya says, there’s no built-in timeouts for basic operations like get/put but then, if they take very long Something Bad likely has happened.
There are timeouts available for operations that can take a long time. For example, methods in Transaction and IgniteLock both have timeouts. Regards, Stephen > On 22 Sep 2020, at 13:30, Kamlesh Joshi <[email protected]> wrote: > > Thanks ilya. Does that mean, we have to specifically maintain a time counter > and act accordingly on it? > > I was hoping, if there is any API where we could just pass timeout value as > well, as a parameter and Ignite would handle internally. > > Thanks and Regards, > Kamlesh Joshi > > From: Ilya Kasnacheev <[email protected] > <mailto:[email protected]>> > Sent: 22 September 2020 17:10 > To: [email protected] <mailto:[email protected]> > Subject: [External]Re: how to achieve timeout for get/put/remove operations > > The e-mail below is from an external source. Please do not open attachments > or click links from an unknown or suspicious origin. > > Hello! > > You can use e.g. putAsync() and then wait on the future for the specified > time only. If it did not complete, take your actions. > > Regards, > -- > Ilya Kasnacheev > > > вт, 22 сент. 2020 г. в 14:27, Kamlesh Joshi <[email protected] > <mailto:[email protected]>>: > Hi Igniters, > > How to achieve/get timeout error for particular operation (get/put/remove), > if it crosses certain timeout value then I can take certain action based on > that. Is there any Ignite API readily available for this? > > Any pointers would be helpful ! > > > Thanks and Regards, > Kamlesh Joshi >
