Hi Ilya,
Great! Thank you for the JIRA ticket.
Kind regards,
Kamil Mišúth
On 2020-08-11 18:38, Ilya Kasnacheev wrote:
Hello!
I think you are correct. I have filed
https://issues.apache.org/jira/browse/IGNITE-13352
Regards,
--
Ilya Kasnacheev
вт, 11 авг. 2020 г. в 13:35, kimec.ethome.sk [
Hello!
I recommend setting the additional JVM arg -Djava.net.preferIPv4Stack=true on
all nodes. You have IPv6 addresses there, which can cause issues in some
cases.
Regards,
--
Ilya Kasnacheev
вт, 11 авг. 2020 г. в 23:40, Homer Kommrad :
> Thank you for the quick response. First of wall ,non
Hello!
Please elaborate wrt "doesn't really remove the key".
REST, etc, do not have access to system caches (where atomics are stored)
neither do they have API to deal with atomics.
Regards.
--
Ilya Kasnacheev
ср, 12 авг. 2020 г. в 08:12, Pavel Strashkin :
> Hi there,
>
> It seems atomic lon
There are “incr” and “decr” commands for atomics exposed via REST, but what
if I need to delete it?
On Wed, Aug 12, 2020 at 6:42 AM Ilya Kasnacheev
wrote:
> Hello!
>
> Please elaborate wrt "doesn't really remove the key".
>
> REST, etc, do not have access to system caches (where atomics are stor
Hello!
You need to issue atomicLong.close().
Regards,
--
Ilya Kasnacheev
ср, 12 авг. 2020 г. в 16:58, Pavel Strashkin :
> There are “incr” and “decr” commands for atomics exposed via REST, but
> what if I need to delete it?
>
> On Wed, Aug 12, 2020 at 6:42 AM Ilya Kasnacheev
> wrote:
>
>> He
I don't see it being part of REST API - is it missing indeed or my eyes
aren't that good anymore? :)
(clients aren't Java-based - mostly node.js).
Thanks for prompt responses. I appreciate it.
On Wed, Aug 12, 2020 at 7:13 AM Ilya Kasnacheev
wrote:
> Hello!
>
> You need to issue atomicLong.clos
Hi Denis. I will asap but you I think you were right it is the query that
blocks.
My application first first runs a select on the cache and then does a put
to cache.
On Tue, 11 Aug 2020 at 19:22, Denis Magda wrote:
> John,
>
> It sounds like a deadlock caused by the application logic. Is there
Thanks Evgenii for your response. Will look into gridgain version. Though not
sure how it will behave with our existing ignite version 2.7.6 which is being
used by other services which are already in production. So cannot change the
entire version to gridgain version but hopefully gridgain versi
Ok Denis here they are...
3 nodes and I capture a yourlit screenshot of what it thinks are deadlocks
on the client app.
https://www.dropbox.com/sh/2cxjkngvx0ubw3b/AADa--HQg-rRsY3RBo2vQeJ9a?dl=0
On Wed, 12 Aug 2020 at 11:07, John Smith wrote:
> Hi Denis. I will asap but you I think you were rig
John,
I don't see any traits of an application-caused deadlock in the thread
dumps. Please elaborate on the following:
7- Restart 1st node, run operation, operation fails with
> ClientDisconectedException but application still able to complete it's
> request.
What's the IP address of the server
I have the following index created:
CELL_CREATE_INDEX = '''
CREATE INDEX IF NOT EXISTS idx_cell_enodeb_id ON erilte01_cell
(PERIOD_START_TIME,REGION_ID)'''
So I used now the created INDEX and the EXPLAIN tells me I used it:
['PLAN']
["SELECT\nP__Z0.PERIOD_START_TIME AS __C0_0,\nP__Z0.REGI
Well, it uses index now:
/*
PUBLIC.IDX_CELL_ENODEB_ID: PERIOD_START_TIME < TIMESTAMP '2020-08-04
00:00:00'\nAND REGION_ID = 'NORTHEAST'\nAND
PERIOD_START_TIME >= TIMESTAMP '2020-08-03 00:00:00'\n */
Is it better now, after using the hint for index? How much time was it
taking
Hi,
Use Ignite Spring Data module to query some selected fields from
a table or join query from tables, the return value is just the first field of
the record??
Sample code:
public interface ObjectARepository extends
IgniteRepository
Hello,
I have below scenario
1)I have two server nodes i.e one on local machine and one on remote host.
2)When I start the first node the local node is added in the Baseline
topology:Here adc1c71b-c21b-47aa-8be6-6fa5ebaaa035 is the local node.
Current topology version: 2 (Coordinator:
Consistent
14 matches
Mail list logo
