Re: Daemon threads

Hello, you can deploy a compute task with infinite loop and check time inside. And if condition is true halt a local node. org.apache.ignite.internal.util.typedef.G.stop(igniteInstanceName, true); пт, 4 мар. 2022 г. в 21:58, Joan Pujol : > Hi, > > Is there any way to configure the threads used

Re: Ignite on a server

Hello, Yes sure, you can use it. Why not. - Ilya вт, 16 нояб. 2021 г. в 11:04, Timothy Peng : > Hello > > I just have one dedicated server who has 128GB memory and 16 cores. > Can I deploy Ignite on this server and just use the memory cache feature? > > Thanks >

Re: Unsubscribe

For unsubscribe please send an email to user-unsubscr...@ignite.apache.org --- Ilya ‪пт, 12 нояб. 2021 г. в 02:28, ‫אריאל מסלאטון‬‎ :‬ > Unsubscribe-- > *054-2116997* > *arielmasla...@gmail.com * >

Re: "Failed to update store" cacheCriticalSize

Hi Mike. In your case try one of two ways. In cache configuration: 1. Increase writeBehindFlushSize parameter (default is 10240 bytes). or 2. Decrease writeBehindFlushFreq parameter (default is 5000 ms).

Re: Add field on cached class without restarting the whole cluster

Hi Rick. Actually, if you do not need to use your POJO classes on the server-side (e.g. for some compute tasks or in services) you can try just enabling peerClassLoding and put a new object from your client without any interruption. In this case, Ignite will serialize a new object and create in

Re: Problem with ScanQuery with filter on ClinetCache

Hello, it looks like you should enable Peer Class Loading: https://ignite.apache.org/docs/latest/code-deployment/peer-class-loading -- Ilya Kazakov сб, 16 окт. 2021 г. в 02:47, Prasad Kommoju : > > > Hi > > > > I am having trouble getting ScanQuery to work wi

Re: Subscribe

Hi Ibrahim, to subscribe please email: user-subscr...@ignite.apache.org And welcome! --- Ilya вт, 7 сент. 2021 г. в 20:20, Ibrahim Altun : > please subscribe me > > -- > İbrahim Halil AltunSenior Software Engineer+90 > 536 3327510 • segmentify.com →

Re: Ignite CheckpointReadLock /Long running cache futures

ically? > > On Tue, Sep 7, 2021 at 4:14 AM Ilya Kazakov > wrote: > >> Hello Mike. According to your description, there was a hanging PME. If >> you need more detailed analysis, could you share your logs and thread dumps? >> >> --- >> Ilya &g

Re: Ignite CheckpointReadLock /Long running cache futures

Hello Mike. According to your description, there was a hanging PME. If you need more detailed analysis, could you share your logs and thread dumps? --- Ilya пн, 6 сент. 2021 г. в 22:21, Mike Wiesenberg : > Using Ignite 2.10.0 > > We had a frustrating series of issues with Ignite

Re: Ignite-code 2.10.0 Failed to find empty constructor for class: org.apache.ignite.internal.processors.platform.websession.PlatformDotNetSessionLockResult

Hello Pankaj. Could you please clarify, what JDK do you use? In such cases (when a class does not have a default constructor), Ignite creates a default constructor via sun.reflect.ReflectionFactory. But this feature is available/tested only in SUN JDK's [1]. Thus I have a question, what JDK do

Re: Unsubscribe

Hi Michael, please send email to this email: user-unsubscr...@ignite.apache.org вт, 13 июл. 2021 г. в 00:19, Michael Cherkasov : > >

Re: Unsubscribe

Hello, please send to this address: user-unsubscr...@ignite.apache.org вт, 13 июл. 2021 г. в 01:08, Saifullah Zahid : > >

Re: Unsubscribe

hello, please send email to: user-unsubscr...@ignite.apache.org вт, 13 июл. 2021 г. в 08:47, Martin : > > > Martin > 邮箱：ghx02...@126.com > >

Re: Received incoming connection from remote node while connecting to this node, rejecting(2.7.5)

Hello. this is not an error, this is INFO message. It just means that an outgoing connection to a remote node is establishing right now, and any new attempts to establish incoming connections from the same remote node are rejected. чт, 8 июл. 2021 г. в 19:54, 38797715 <38797...@qq.com>: > Hi

Re: Cannot start ignite nodes with shared memory - Ignite version 2.10.0

Also, as I know, shmem is not recommended to use. Shmem will not be used in Ignite 3. пн, 21 июн. 2021 г. в 15:30, Ilya Kazakov : > Hello, as I can see no one from the community wants to take this ticket. > Try to ask on dev-list: d...@ignite.apache.org > > ср, 2 июн. 2021 г. в 05:11

Re: Cannot start ignite nodes with shared memory - Ignite version 2.10.0

Hello, as I can see no one from the community wants to take this ticket. Try to ask on dev-list: d...@ignite.apache.org ср, 2 июн. 2021 г. в 05:11, sarahsamji : > Hi, is there a fix expected for this issue in the next release? > > > > -- > Sent from:

Re: Threads are going into LockSupport.park and are not getting unpark

Hello, could you share a full thread dump and logs for analysis? Ilya вт, 25 мая 2021 г. в 19:12, swara : > Hi > > In our application suddenly ignite is getting Locked for 1 > to 5 hours and then all threads are releasing at the same time and working > normally. > > Below are the logs for

Re: Cannot disable system view JMX exporter via configuration

hello. As I see in sources now when starting a GridSystemViewManager [1] JmxSystemViewExporterSpi SPI is always added [2][3] regardless of what is specified in the configuration. There is no any way to change its behavior. Also, I have found a ticket where it was implemented [4]. Ilya [1]

Re: Cannot start ignite nodes with shared memory - Ignite version 2.10.0

Hello. It looks like a bug. I have reported it: https://issues.apache.org/jira/browse/IGNITE-14634 Ilya пт, 16 апр. 2021 г. в 05:09, sarahsamji : > Sample > > import org.apache.ignite.Ignite; > import org.apache.ignite.Ignition; > import org.apache.ignite.configuration.*; > import

Re: Is there any way to get cache and node status programatically?

There is no explicit read-only state on cache level. But cache can be in a read-only state according to Partition Loss Policy [1]. I mean if there are loss partitions and READ_ONLY SAFE policy is set in this case the cache could be in read-only mode. To check are there loss parts:

Re: List all available distributed locks in cluster

Hello. There is no such API in Ignite. But it is a good idea to implement it. I have created a ticket for this: https://issues.apache.org/jira/browse/IGNITE-14569 Ilya чт, 15 апр. 2021 г. в 22:05, Paolo Bazzi : > Hi all, > > Is there a way to list all available distributed locks within the

Re: Is there any way to get cache and node status programatically?

Hello. You can get all nodes online nodes: ignite.cluster().nodes() To check cluster state you can use this code: ignite.cluster().state() -- Ilya пт, 16 апр. 2021 г. в 01:39, facundo.maldonado : > Is there any API or recommended way to get if a node is Online or Offline >

Re: NPE on control.sh --cache indexes_force_rebuild

m the code point of view, this line of code does appear null pointer. > > > 在 2021/4/14 下午3:56, Ilya Kazakov 写道: > > Hello! What version do you use? > > Ilya > > ср, 14 апр. 2021 г. в 14:57, 38797715 <38797...@qq.com>: > >> Hello, >> >> Do

Re: NPE on control.sh --cache indexes_force_rebuild

Hello! What version do you use? Ilya ср, 14 апр. 2021 г. в 14:57, 38797715 <38797...@qq.com>: > Hello, > > Does indexes_force_rebuild command have a demo to run? > > The following error will be thrown during current execution: > > ./control.sh --cache indexes_force_rebuild --cache_names City >

Re: Cannot start ignite nodes with shared memory - Ignite version 2.10.0

Hello. It will be great if you can share some simple reproducer. ср, 14 апр. 2021 г. в 03:39, sarahsamji : > Hi, > > * > Tested with:* > - Ignite version - 2.10.0 > - Multinode cluster on single/different JVM - localhost > - First node successfully starts, shared memory endpoint also starts but

Re: Fastest way to iterate over a persistence cache

Hi Sebastian. You can try to use QueryParallelism feature, also try to use LazyLoading feature. More details is here: https://ignite.apache.org/docs/latest/perf-and-troubleshooting/sql-tuning Thanks, Ilya ср, 14 апр. 2021 г. в 02:28, Sebastian Macke : > Hi Ignite Team, > > I have stumbled

Re: [2.7.6] Bug with query parallelization + sorting nulls

Hello, Maxi! The issue was reported: https://issues.apache.org/jira/browse/IGNITE-14177 Ilya пн, 15 февр. 2021 г. в 13:38, Ilya Kazakov : > Thank you, Maxi! > > It really looks like a bug. I will report it! > > -- > Ilya > > пт, 12 февр.

Re: Insert with JDBC Thin driver into caches

It is marked as deprecated because there were plans to make it enabled by default. But it is still not... Now the property is already deprecated, but the feature is still disabled by default. -- Thanks вт, 16 февр. 2021 г. в 20:06, Benjamin : > Thanks. It fixes the issue. > >

Re: Insert with JDBC Thin driver into caches

But this property should be set on the empty cluster before you create your schema - Ilya вт, 16 февр. 2021 г. в 16:53, Ilya Kazakov : > Hello, Benjamin! > > Try to run your Ignite with system property: > -DIGNITE_BINARY_SORT_OBJECT_FIELDS=true >

Re: Insert with JDBC Thin driver into caches

Hello, Benjamin! Try to run your Ignite with system property: -DIGNITE_BINARY_SORT_OBJECT_FIELDS=true Or from Java: public static void main(String[] args) throws SQLException { System.setProperty("IGNITE_BINARY_SORT_OBJECT_FIELDS", "true"); ... -

Re: [2.7.6] Bug with query parallelization + sorting nulls

Thank you, Maxi! It really looks like a bug. I will report it! -- Ilya пт, 12 февр. 2021 г. в 22:13, maxi628 : > Hello everyone, I think I've found a bug. > > I created a test to reproduce it. > Basically, it creates two caches, one with *queryParallelization=1* and > another one with

Re: System.Collections.Generic.KeyNotFoundException: The given key was not present in the cache during load test with ignite 2.9.1

Hello, Charlin! Could you show any reproducer, please? Thanks, Ilya! пт, 12 февр. 2021 г. в 18:43, Charlin S : > Hi, > I am getting below error while running load test with ignite 2.9.1 but > ContainsKey is successful and thereafter Get by key is failed > The given

Re: [2.9.1] Out of memory in data region

Hello! Ignite uses off-heap memory, whether the persistence is on or not (it depends on another parameter [1]), but only for a data storing. Transaction processing is performing on heap, therefore an OOM may occur here. [1].

Re: Requesting mapping from grid failed issue with Ignite 2.9.0 and C# model with ICloneable interface but same was working with Ignite 2.8.1

Hello, Charlin! Try to enable peer class loading: https://ignite.apache.org/docs/latest/code-deployment/peer-class-loading -- Ilya Kazakov вт, 5 янв. 2021 г. в 14:52, Charlin S : > Hi, > > i'm getting exception on when a new record is added, which was working >

Re: [2.9.0]NPE on invoke IgniteCache.destroy()

Hello! Can you provide some details, or show some short reproducer? - Ilya Kazakov пн, 7 дек. 2020 г. в 21:31, 38797715 <38797...@qq.com>: > Hi community, > > Call IgniteCache.destroy Method, NPE appears,logs are as follows: > 2020-12-07 17:32:18.870 [] [e

Re: Large Heap with lots of BinaryMetaDataHolders

Hmmm. Well, each node shares with other nodes (including clients) all metadata (all CQ and etc...). Did you try to check this situation in a thin client? I think this is the normal amount of heap for a cluster like this. Ilya Kazakov пт, 13 нояб. 2020 г. в 22:15, ssansoy : >

Re: Large Heap with lots of BinaryMetaDataHolders

? -- Ilya Kazakov чт, 5 нояб. 2020 г. в 21:03, ssansoy : > Hi Andrew any thoughts on this? thanks! > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >

Re: Live coding session next week

Hello Valentin! Could you provide a link for a meeting, please? - Ilya Kazakov пт, 13 нояб. 2020 г. в 07:07, Valentin Kulichenko < valentin.kuliche...@gmail.com>: > Igniters, > > On Tuesday next week (Nov 17), Denis Magda and I will conduct a live &

Re: Using @SpringResource & @SpringApplicationContextResource in IgniteCallable

Hello, Asish! Does it work? -- Ilya Kazakov пн, 9 нояб. 2020 г. в 21:26, ashishb888 : > Thank you Ilya! > > I did replace Ignite bean with IgniteSpringBean by using Java configuration > (and not the XML) as below, > > @Slf4j > @Configu

Re: Using @SpringResource & @SpringApplicationContextResource in IgniteCallable

Pay attention! In igniteSpringBean we use IgniteSpringBean class (not Ignite). This is a prerequisite if you want to use @SpringApplicationContextResource in IgniteCallable on remote nodes. Ilya Kazakov вт, 3 нояб. 2020 г. в 14:25, ashishb888 : > Hi Ilya, > > My bad I forgot

Re: How to get column names for a query in Ignite thin client mode

ames = new ArrayList<>(); for (int i = 0; i < count; i++) { String columnName = cursor.getFieldName(i); columnNames.add(columnName); } System.out.println("columnNames:::"+columnNames); } But if this is the correct behavior I do not know yet, I will try to find out.

Re: Using @SpringResource & @SpringApplicationContextResource in IgniteCallable

Hello, Ashish! But I can not find poc.ignite.service.ComputeService class by your link. Maybe you sent the wrong link? Check, please. Ilya Kazakov вт, 3 нояб. 2020 г. в 12:11, ashishb888 : > Awaiting response. If you anything else let me know > > BR, > Ashish > > > &

Re: Using @SpringResource & @SpringApplicationContextResource in IgniteCallable

Hello, Ashish! But I see in your example only config and Main classes. Can you show, please, some actions in your code? -- Ilya Kazakov вт, 20 окт. 2020 г. в 17:06, ashishb888 : > Thank you Ilya for the response. > > I have two application first one is the server and s

Re: Ignite 2.x - can I take advantage of offheap storage and also still have time based eviction (from the on & off heap storage)?

read.sleep(5000); int matches = 0; for (long i = 0; i < 4_000_000; i++) { if (cache.get(i) != null) ++matches; } System.out.println("Matches: " + matches); } } Ilya Kazakov ср, 21 окт. 2020 г. в 21:27, Nichola

Re: NullPointerException when destroying caches

. Ilya Kazakov пн, 19 окт. 2020 г. в 22:31, Kseniya Romanova : > Hi Benjamin! Just in case the question is still relevant, you can join > tomorrow's Q session[1] to reach Ignite developers with this question. > > Cheers, > Kseniya > > [1] https://www.meetup.com/Apache-

Re: Using @SpringResource & @SpringApplicationContextResource in IgniteCallable

Hello! I am trying to reproduce your issue and in my example everything is ok. It looks like you create your spring application without igniteSpringBean. Look at my example, please. / public class Main { public static void