Apache Ignite Workshop: Developing Applications That Are Easy to Manage

Igniters, FYI: next Wednesday, December 9 2020 at 21:00 UTC+3 I am giving an Apache Ignite Workshop "Developing Applications That Are Easy to Manage". Use this link to register: https://www.gridgain.com/resources/webinars/apache-ignite-workshop-developing-applications-are-easy-manage Abstract T

Re: Programmatically triggering of write behind

Cache expiry policy evicts entries only from the cache and native persistent store: the external DB is not modified. So your expiry policy has nothing to do with write-behind. If you want to evict entries from both the cache and external DB you may consider implementing such a policy as a replicat

Re: persistent caches not rebalancing when new node is added

Alan, My understanding is you have to rebalance caches with rebalanceDelay set to -1 manually. I did not find the "rebalance" command in the control script documentation . As I remember, the Web Console and Client Center from GridGain hav

Re: Server stuck while joining cluster

Check if you have active transactions running on your Server3 at the time when Servers 1 and 2 are trying to join. Servers wait for active transactions to complete before joining the cluster and if a transaction takes longer than the join timeout (10 seconds by default) the joining node would be se

Re: Ignite Stopping Abruptly

You enabled eager TTL, which means you have a background thread that cleans expired entries. The message you copied from the log says the TTL thread was blocked for more than IgniteConfiguration/sysWorkerBlockedTimeout, which by default equals IgniteConfiguration/failureDetectionTimeout, which by

Re: Difference between Ignite Kafka Streamer and Kafka consumer (2.0)

About your question "/What is difference between Ignite Kafka Streamer and Kafka consumer?/": Kafka Consumer is Kafka API to poll data from Kafka while Ignite Kafka Streamer is a complete solution to stream data from Kafka into Ignite. Internally Kafka Streamer starts one or many Kafka Consumers an

Re: Ignite Data Streamer Kafka version 2.0

Hi Mahesh, I do not think Kafka streamer uses any 2.x specific Kafka client APIs. From what you say I think kafka-client-1.1 (that Ignite 2.7 uses) cannot connect to Kafka 2.x cluster. Can you manually replace kafka-client-1.1.jar with kafka-client-2.0 jar on the Kafka streamer side and see if it

Re: Job Listeners

Hi Chandrika, I would use ComputeTaskSession and ComputeTaskSessionAttributeListener to achieve that: - Inject ComputeTaskSession to your task and/or jobs like this: @TaskSessionResource private ComputeTaskSession taskSes; You also need to annotate your task with @ComputeTaskSessionFullS

Re: When cache node switch between primary and backup any notification be received?

Hi, Unless you customize affinity function there are always 1024 partitions and every node holds one or more primary partitions evenly distributed among the nodes. The affinity function tries to minimize re-partitioning as topology changes. Just want to confirm - are you really looking for an even

Re: Job Listeners

Hi Chandrika, You would need to make an assumption about your jobs duration to display remaining time or percentage. For example, the below task predicts remaining duration assuming remaining jobs will have duration equal to the average of the completed ones : @ComputeTaskSessionFullSupport publi

Re: Issue when executing sql query using REST API

Hi Ray, Just copied your code into a simple single file sample project, ran it and your query worked fine for me: 1. Request URL: http://127.0.0.1:8080/ignite?cacheName=person&pageSize=1&qry=limit+2&cmd=qryexe&type=Person&; 2. Request Method: GET 3. Status Code: 200 OK 4.

Re: Issue when executing sql query using REST API

, 2017 at 12:15 PM, Ray Liu (rayliu) wrote: > Can you share your configuration xml? > > I think it’s a binary masharller configuration issue. > > > > *From: *Alexey Kukushkin > *Reply-To: *"user@ignite.apache.org" > *Date: *Wednesday, 13 September 2017 at

Re: Issue when executing sql query using REST API

he) classes. On Wed, Sep 13, 2017 at 12:23 PM, Ray Liu (rayliu) wrote: > Do I have to deploy my classes on all of the server nodes manually? > > Every time I added some new classes, I have to do this again? > > > > > > *From: *Alexey Kukushkin > *Reply-To: *"use

Re: Issue when executing sql query using REST API

Hi Ray, The exception seems not related to Ignite to me. I believe you see it on the client side. Are you sure you have all Jackson runtime dependencies? For example, I have jackson-annotations, jackson-core and jackson-databind. Id you do not have it then you forgot to reference ignite-rest-http

Re: Ignite cluster with persistent store enabled did not load from wal after restarting.

Ray, Yes, enabling persistence must automatically bring all your data and metadata upon the cluster startup. Please give us more details why you think the cache was not created. BTW, do you activate the cluster after startup? Enabling persistence requires explicit cluster activation: $IGNITE_HOME

Re: Issue when executing sql query using REST API

Hi Ray, The REST response is in plan text so you do not need those dependencies if you do nothing with the received plain text. But looking at your exception my guess was that your application deserialises received text into POJO, cannot find a deserialiser and displays that error. Can you please

Re: Ignite cluster with persistent store enabled did not load from wal after restarting.

Ray, You will not see anything in WebConsole until you activate the cluster. Could you please confirm you did step #7: 1. You started the cluster with persistence enabled 2. Activated the cluster 3. Ran your IgniteTest app 4. Checked the person cache in WebConsole - you should see it.

Re: Ignite cluster with persistent store enabled did not load from wal after restarting.

Ray, Yakov just pointed me to this thread where user had a problem with IP address changing between the cluster restarts. The persistent data directories inside work/db have names built

Re: Job Listeners

Hi Chandrika - sorry for the delay - did not have time to review this list. Once you start using custom types in your compute jobs, the server nodes will have to know your custom types. You have two options to let the server nodes know your types: 1. Manual deployment: copy all JARs containing

Re: (.NET) localPort and localPortRange question

Hi Jeff, This output "Socket[addr=/ServerIP2,port=47500,localport=58071]" indicates your server is correctly bound to port 47500 you configured. You have to open only port 47500 and subsequent ports in your range in your firewall. Do not worry about localport=58071 in that output. Sockets are bi-d

Re: Using igniteAtomicLong or igniteAtomicSequence as uniqueId in ignite cache

Hi, Some thoughts that might help you to make a decision: - IgniteAtomicLong and IgniteAtomicSequence are both public interfaces but their implementations are inside the internal part of Ignite. It is a bad practice to reference Ignite internals so you cannot configure them in the XML

Re: Ignite.NET 2.2 crashes on startup without any information

Patrick, Is that output from Visual Studio console window? Ignite writes information to standard output and error and not to the Visual Studio console. Can you either run your app from cmd.exe or put a breakpoint on the last line and see output in the cmd.exe that Visual Studio opens? On Fri, Sep

Re: Ignite.NET 2.2 crashes on startup without any information

gt;> What is your JAVA_HOME? >>>>> Looks like either JAVA_HOME is incorrect, or JRE/JDK install is >>>>> corrupted. >>>>> >>>>> On Fri, Sep 29, 2017 at 6:33 PM, Patrick Brunmayr < >>>>> patrick.brunm...@kpibench.c

Re: Ignite.NET 2.2 crashes on startup without any information

BTW, I have MSVC++ 2010 redistributable. On Fri, Sep 29, 2017 at 7:13 PM, Alexey Kukushkin wrote: > Pavel, > > It does not work for me - seems same problem. I also have VisualStudio > 2017 and Oracle JDK 8.144. I suggest we open a ticket and investigate. I > have jvm.dll inside

Re: Ignite.NET 2.2 crashes on startup without any information

exact same message like you Alexey > > 2017-09-29 18:13 GMT+02:00 Alexey Kukushkin : > >> Pavel, >> >> It does not work for me - seems same problem. I also have VisualStudio >> 2017 and Oracle JDK 8.144. I suggest we open a ticket and investigate. I >> have

Re: Ignite.NET 2.2 crashes on startup without any information

ot;Prefer 32 bit" in project settings: >>>> https://ptupitsyn.github.io/images/prefer32bit.png >>>> >>>> > I still do not understand why Any CPU does not work. >>>> Because "Prefer 32 bit" is enabled by default for some reason, see >>>>

Re: Ignite.NET 2.2 crashes on startup without any information

seems different. Let us know if it still does not work. On Fri, Sep 29, 2017 at 7:47 PM, Patrick Brunmayr < patrick.brunm...@kpibench.com> wrote: > okay i try that > > 2017-09-29 18:44 GMT+02:00 Alexey Kukushkin : > >> OK, I solved all my issues. I can run the console app

Re: Ignite.NET 2.2 crashes on startup without any information

ager > > API-MS-WIN-CORE-WINRT-ERROR-L1-1-0.DLL > API-MS-WIN-CORE-WINRT-L1-1-0.DLL > API-MS-WIN-CORE-WINRT-ROBUFFER-L1-1-0.DLL > API-MS-WIN-CORE-WINRT-STRING-L1-1-0.DLL > DCOMP.DLL > IESHIMS.DLL > > > 2017-09-29 18:56 GMT+02:00 Alexey Kukushkin : > >> Patrick

Re: Ignite.NET 2.2 crashes on startup without any information

Patrick, With the configuration above (App built for x64 platform and having x64 Java installed), do you still see this output ? Error occurred during initialization of VM Unable to load native library: Can't find dependent libraries

Re: Persistence store(MSSQL) using cross-platform c#(Ignite Client windows) and java(Ignite Server linux version)

Hi, Please can you give more details: - What exactly your issue is? Can you copy all the error output? - Are you using Microsoft SQL server for persistence? - What API does your C# client use to work with Ignite with the persistence enabled? Is it C# API or SQL or something else? -

Re: Job Listeners

Hi Chandrika, Is it possible for you to share your Ignite task implementation? Or are you just running the above example I created? It looks you have some deadlock and it is hard to guess without having the code.

Re: Persistence store(MSSQL) using cross-platform c#(Ignite Client windows) and java(Ignite Server linux version)

It appears if you use a .NET cache store then all your server nodes must be .NET nodes. Another option is to use a Java cache store - then your can mixed .NET and Java server nodes.

Re: Persistence store(MSSQL) using cross-platform c#(Ignite Client windows) and java(Ignite Server linux version)

Hi JP, Please let me first explain some basics: Ignite is implemented in Java and presently all other APIs including .NET are "wrappers" of the Ignite JVM. When you start your .NET node, it automatically creates an Ignite Java node and talks to it using some thin JNI layer for .NET/Java interopera

Re: Persistence store(MSSQL) using cross-platform c#(Ignite Client windows) and java(Ignite Server linux version)

Can you use config-based configuration approach instead of code, for example: You would have to create a C# wrapper

Re: Persistence store(MSSQL) using cross-platform c#(Ignite Client windows) and java(Ignite Server linux version)

No one forces you to provide credentials in the XML config file. In my previous example I assumed the credentials were somehow evaluated in the code - there are no configurable parameters.

Re: Persistence store(MSSQL) using cross-platform c#(Ignite Client windows) and java(Ignite Server linux version)

Unlike C# API, which allows you to automatically keep your cache and SQL server consistent using read-through and write-through policies, the SQL API works only with data already loaded to the cache. In other words, the data updates you do with Ignite SQL are not automatically written to the SQL se

Re: SqlQuery results missing

Pim, Can you confirm you really have 5000 items loaded to the cache (using visor or Web Console). Can you also share how you load the data. Normally your queries must find all 5000 items as you expected.

Re: SqlQuery results missing

Hi Pim, Can you make sure: - Your SqlQuery is NOT local (sql.isLocal() must be false) - You did not restart any of your 5 server nodes during your exercises. Remember, if you restarted a node after loading data to the cluster, the data on that node is gone and you no longer have 5000

Re: Persistence store(MSSQL) using cross-platform c#(Ignite Client windows) and java(Ignite Server linux version)

Hi, you cannot rename a cache at runtime. There is currently no "renameCache" Java Api (we have only "create" and "destroy" cache APIs) and "ALTER TABLE RENAME TO" SQL API is currently not supported. Do you have a real use case when such a feature would be useful?

Re: Persistence store(MSSQL) using cross-platform c#(Ignite Client windows) and java(Ignite Server linux version)

Siva, I am still not sure I completely understood why you need to rename a cache. I see you have a multi-tenant app. You might either create a cache per tenant or introduce a "tenant ID" and keep all the tenants in single cache. No rename is required. Is it to keep cache name in sync with the under

Re: Persistence store(MSSQL) using cross-platform c#(Ignite Client windows) and java(Ignite Server linux version)

Siva, JP, Ignite .NET has no special support for calling Java from .NET. If you google for something like "call Java from C#" you will find lots of examples telling it to 1) expose Java method through JNI 2) Build a DLL with your Java native methods and all other required Java dependencies include

Re: Persistence store(MSSQL) using cross-platform c#(Ignite Client windows) and java(Ignite Server linux version)

Also, I am still not sure why you decided to create dynamic caches for each tenant instead of having single pre-configured cache and having the Tenant ID as the cache value type field. How are you going to manage all those caches? The more caches you have the more effort you need to manage and ev

Re: Persistence store(MSSQL) using cross-platform c#(Ignite Client windows) and java(Ignite Server linux version)

Siva, JP, Please ignore my suggestion to add cache configuration at runtime - it is not supported and it will not work. Thus, I see only two options left - either you call Java from C# or change your model to have the Tenant ID as the cache value type field.

Re: Persistence store(MSSQL) using cross-platform c#(Ignite Client windows) and java(Ignite Server linux version)

Siva, JP, This approach to add cache configuration at runtime actually works!!! Just tested it: Assuming initially you have no caches: http://ignite.apache.org/schema/dotnet/IgniteConfigurationSection"; gridName="myGrid1" clientMode="true"> This application adds

Re: Job Listeners

Hi, your jobs shall not cause any deadlocks since you have no synchronisation inside execute(). I ran your job on 3 nodes on the same machine OK - the job completed in about 9 seconds, which matches the random delay inside execute(). I only had to replace executeAsync() with execute(). The problem

Re: Job Listeners

Hi Chandrika, I can run your task on 1 node OK (see the output below) and I really do not see what might cause a deadlock in your code. You said "*with one node it was always failing causing a deadlock*" - what do you mean by "failing"? Do you see an exception? Can you reproduce the problem with v

Re: Some questions regard Cache Query and performance

Aaron, let me forward this to DEV: Ignite DEV community, I tried to confirm setLocal(true) semantics for ContinuousQuery and I have got not what I expected. I found that executing a ContinuousQuery with setLocal(true): - Still executes initial query remotely - Listens for modifications loc

Re: Is there a way to know mapping of keys and machine nodes

Hi, Ignite Affinity#mapKeysToNodes returns a map node -> keys. This is copied from CacheAffinityExample you can find in Ignite distribution: // Map all keys to nodes. Map> mappings = ignite.affinity(CACHE_NAME).mapKeysToNodes(keys); for (Map.Entry> mapping : mappings.entrySet()) { ClusterNode

Re: integrate with prestodb

Cross-sending to the DEV community. On Mon, Oct 16, 2017 at 12:14 PM, shawn.du wrote: > Hi community, > > I am trying to implement a connector for presto to connect ignite. > I think it will be a very interest thing to connect ignite and presto. > > In fact, currently we use ignite and it works

Re: Error with ScanQuery

Raymond, Do you have native or 3-rd party persistence? If you have 3rd-party persistence, then this "Requesting mapping from grid failed" error I see in your screenshot was fixed in release 2.3 .

Re: Cannot insert data into table using JDBC

James, Just to confirm - are you saying that Statement.executeUpdate("create table Sample_Superstore ...") throws that exception but still creates the cache as expected?

Re: Cannot insert data into table using JDBC

Hi James, Can you please set "streaming=false" and try again? If it worked, I will open a bug about this "schema not found" issue in the streaming mode. Thanks!

Re: Job Listeners

Hi Chandrika, I cannot reproduce the problem with the code you provided. I created a public GIT repo with your code from the previous post and suggest this: 1. You clone the repo: git clone https://github.com/kukushal/ignite-userlist-joblisteners.git 2. Try to reproduce the problem with

Re: Ignite Events Remote Filter

Hi, I think it is a documentation bug. I do not think remote listener will be unsubscribed if it returns false. Let's confirm with the developers community. *Ignite Developers*, We have this comment for the remoteListener argument of the IgniteEvents#remoteListen(...): rmtFilter - Filter callba

Re: Ignite Events Remote Filter

Also, I ran our CacheEventsExample and I confirm the remote filter is NOT unsubscribed when it returns false. So it looks like a documentation bug only. On Fri, Oct 27, 2017 at 1:10 PM, Alexey Kukushkin wrote: > Hi, > > I think it is a documentation bug. I do not think remote listene

Re: NullPointerException in FileWriteAheadLogManager.java:1313

Hi, Please set WAL archive path to be different from WAL store path. Indicating this misconfiguration with NullPointerException is a usability issue. I will open a ticket. On Tue, Oct 31, 2017 at 7:13 PM, Sébastien Bouchex Bellomié < sbouc...@infovista.com> wrote: > Hello, > > > > I’m getting t

Re: NullPointerException in FileWriteAheadLogManager.java:1313

Opened a ticket to address this: https://issues.apache.org/jira/browse/IGNITE-6802

Re: What's the maximum number of nodes for an Apache Ignite cluster?

Hi, As I know there is no limit on the number of nodes. The largest cluster one of Ignite users is building that I know about will have 2000 nodes - may be that was what caused confusion. Please note that the default affinity function (RendezvousAffinityFunction) manages 1024 partitions by defaul

Re: Is WAL a memory-mapped file?

John, The default mode is the slowest of the 3 WAL write modes available. The other two are OS buffered write "LOG_ONLY" and Ignite buffered write "BACKGROUND". You might need some benchmarking in your real environment (hardware and software) with your specific task to understand if it is "slow".

Re: Some concern regards the DataRegionConfiguration of the 2.3

Hi, When you said "old memory configuration" did you mean using cacheStoreFactory? Ignite has two persistence options: native and 3rd-party persistence and having cacheStoreFactory configured means you use the latter one. Unlike Ignite native persistence, the 3rd party persistence is slower in m

Re: Re: Some concern regards the DataRegionConfiguration of the 2.3

Apache Ignite has no data migration/archiving tool but Ignite supports plugins and Ignite native persistence exposes org.apache.ignite.internal.processors.cache.persistence.snapshot.IgniteCacheSnapshotManager that you could use to implement your own tool. There are commercial solutions available,

Re: Trouble with v 2.3.0 on AIX

Hi Vladimir, Can you share your Ignite configuration or give a list of features you have configured if sharing configuration is not possible (whether you have persistence, cache store, what discovery you use, etc.). -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Trouble with v 2.3.0 on AIX

Vladimir, right now I have no idea what is happening. Maybe Community will help. The stack trace goes deep into Big-Endian code that I cannot even troubleshoot since I have no Big-Endian platform available. Gathering logs might be helpful: I would stop all the nodes, clean $IGNITE_HOME/work/logs/*,

Re: Ignite with Spark on Yarn

Hi, The problem is Ignite cannot find your configuration file. Ignite tries these 3 steps to find configuration file: 1. Try to resolve it as a URI 2. If previous step fails, try to resolve it as $IGNITE_HOME + 3. If previous step fails, try to resolve it in CLASSPATH. Thus, you have

Re: Question on On-Heap Caching

Hi, Ignite always stores data off-heap. Enabling on-heap caching just turns Java heap into a cache for the off-heap memory, allowing you to configure eviction policies specific for such a heap cache. I believe the idea is tha

Re: Spring Data and XML configuration

Hi, just replace code-based configuration inside SpringAppCfg#igniteInstance() with single line XML file-based initialisation: @Bean public Ignite igniteInstance() { return Ignition.start("ignite-config.xml"); }

Re: Problem with spring-data-commons 2

Hi, Apparently you cannot just bump the Spring dependency due to that new deleteAll(Iterable ids) they added in CrudRepository 2.0 that conflicts with the same method in our IgniteRepository. I opened a tickets to support Spring 2.0: https://issues.apache.org/jira/browse/IGNITE-6879

Re: Use IgniteQueue in client

Hi, Two things: 1. You must use same configuration (limit and CollectionConfiguration) on both client and server 2. You cannot pass "null" as CollectionConfiguration. Pass empty CollectionConfiguration (new CollectionConfiguration()) if you have no specific settings. This code mus

Re: Use IgniteQueue in client

Created https://issues.apache.org/jira/browse/IGNITE-6889 (ignite.queue() returns null when queue configuration is null)

Re: Initial query resent the data when client got reconnect

Hi, Initial query just gets the data according to the query. It will always bring all data if you query all data. You need to manually control what data you want your initial query to get. For example, if your key is incremental (like numeric ID or timestamp) then you could save the last extracted

Re: Apache Ignite binary type invalidation

Hi, Ignite really caches metadata but restarting cluster clears the cache. If you want to change field type at runtime (without restarting the cluster), then you need to first remove field and then add the field something like: BinaryObject o = binary.builder("MyType").removeField("f").build();

Re: Initial query resent the data when client got reconnect

Hi, Ignite presently does not support auto-incremental keys. You can start discussing this feature on the Ignite Dev list and open an enhancement request if the Community agrees it worths implementation. Right you can use Ignite's AtomicSequence

Re: what's best practice of “in” operator?

Hi, The "table" in documentation is a keyword "table" to create a temporary table. Your query shall be like SELECT p.* FROM "personCache".Person p join table(area varchar =('london','paris','roma',...)) o on p.org_id = o. area

Re: Issues with multiple kafka connectors, questions regarding ignite caches

Hi, 1. IgniteSinkTask source code shows that Ignite Kafka Connector has this "feature" that stopping any task

Re: Failed to start near cache (a cache with the same name without near cache is already started

Hi, Near caches are configured per cache and not per query. You cannot start different near caches for the same distributed cache. Start separate near caches for TableA and TableB.

Re: Failed to start near cache (a cache with the same name without near cache is already started

Hi, Near caches are transparent for you - there is no user API to get reference to or work with near caches. The purpose of a near cache is to "cache the cache", that is to be a local cache for a distributed cache. Ignite transparently fills near cache with the most recent data when you work with

Re: Unable to read all the entries in present single cache using Streamer

Hi, You must use IgniteDataStreamer#addData(key, value) to stream data into Ignite. What you did when you attached a receiver would make the data streamer execute the receiver on the nodes in co-located mode (that is the receiver logic will be called on the node where the receiver's input data is

Re: Transport compression (not store compression)

Forwarding to DEV list: Ignite developers, could you please share your thoughts on how hard it is to extend Ignite to compress data on the network. On Wed, Nov 22, 2017 at 10:04 AM, Gordon Reid (Nine Mile) < gordon.r...@ninemilefinancial.com> wrote: > Hi Igniters, > > > > I see there is a lot of

Re: Unable to start Hadoop Accelerator with Persistence

Hi, I had same issue when I played with Hadoop a month ago. Developers told me it did not make sense having both Hadoop and native persistence :) However I still think we have at least a usability issue here since the exception does not tell much. Please let me know if you really need both persist

Re: Rest API not working for GET

Hi, Please make sure: - com.ril.edif.Account is on the server Ignite's CLASSPATH. You can just deploy the JAR to $IGNITE_HOME/libs/user direcgtory - com.ril.edif.Account has public getters and setters

Re: SQL Join not giving results

Hi, Your data is not collocated explains why your JOIN query gets no data. By default distributed joins are disabled since it really negatively impacts performance. Please do setDistributedJoins(true) on your JOIN SqlQuery and try again. But I really encourage you to refactor your data model to m

Re: SQL Join not giving results

Please add distributedJoins=true parameter to a connection URL when you run sqlline.

Re: SQL Join not giving results

JDBC connection string is a URL. Please use question mark "?" to separate parameters list and ampersand "&" to delimit multiple parameters. Try this: jdbc:ignite:thin://127.0.0.1?*distributedJoins=true*

Re: Ignite Service and node failure

Hi, You do not need to always create a service proxy. You can get a proxy once and it will always find a service even if the current node where the service is deployed failed: the service would be re-deployed and the service proxy would find it on the new node. That is true even if you created a "

Re: multiple service instances in a single node

Hi, You do not need to overprovision a service to achieve resource utilisation. Ignite will do it for you even if you have just one service instance on a node. Internally Ignite services are based on Compute grid: it will use threads from the public pool to process the service invocations. You can

Re: Compute async Job from Ignite Service and return IgniteFuture

Val, My understanding is Krzysztof asks how to call a long-running service asynchronously. It looks like right now Ignite does not support that. What do you think about extending Ignite so that we could write something like: IgniteServices services = ignite.services(); AsyncServiceProxy asyncPr

Re: Ignite DataStream vs cache putAll

Hi, putAll just sends all data right away. DataStreamer locally builds batches of 512 entries (configurable) and does an equivalent of "putAll" for the batches as they become full. DataStreamer also retries "putAll" if it fails. DataStreamer allows you to configure server-side processing of added

Re: Ignite node crashes after one query fetches many entries from cache

Ignite Developers, I know community is developing an "Internal Problems Detection" feature . Do you know if it addresses the problem Ray described below? May be we already have a setting to prevent this

Re: Facing issue Ignite 2.3 and Vertex-ignite 3.5.0

Hi, You can enable Ignite persistence only explicitly using a command line tool or in the code . There is a reason why enabling persistence makes cluster inactive upon startup: the reason is the data is already in Ignite. Suppose you do a "ge

Re: Facing issue Ignite 2.3 and Vertex-ignite 3.5.0

Hi, No, you cannot activate cluster through XML config. Do you really need persistence enabled? The cluster is active by default if you disable persistence. You might also consider creating a simple ignite.sh wrapper that would also call "control.sh --activate" to activate the cluster. In this ca

Re: Issues with multiple kafka connectors, questions regarding ignite caches

Hi, I opened a ticket for this issue: https://issues.apache.org/jira/browse/IGNITE-7065. If no one pick it up by next week then I might find time to fix it next week (although I cannot promise). I am not sure when community is going to release 2.4 but I (or anyone who fixes it) could share a branc

Re: Index not getting created

Naveen, Your "CREATE INDEX" syntax seems valid to me. Can you start server nodes with debugging enabled, reproduce the problem and share the debug log output from the servers?

Re: Out of memory error

Hi, You identified the problem right: there is not enough memory to handle 15G of Postgres data on your server. Your idea to configure a memory policy to increase available memory is right but 16G is also not enough. Ignite data size is noticeably larger (up to 3 times, depends on many factors lik

Re: class org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to find SQL table for type:

Hi, make sure you registered key and values types with the SQL engine using CacheConfiguration#setIndexedTypes(keyClass, UserAppInfo.class)

Re: Obtaining metadata about items in the cache

Hi Raymond, I do not think Ignite supports iterating other metadata but you could minimise IO by: - collocated processing (analyse entries locally without sending them over the network) - working with binary object representation directly (without serialisation/deserialisation) You c

Re: query operator in local node

Hi, IgniteQuery#setLocal(true) will make the query to execute only on local node. Use IgniteCompute#affinityCall / affinityRun to send a job that would execute your local query to specific node. For example, this will execute a local query on a node where "myKey" is stored: compute.*affinityRun*

Re: How to do 'stream processing' and more questions of a Ignite newbie

Hi, What you described sounds like an Event Processing architecture, which includes never-ending stream of input data, limited time window, analysis of data within the time window and taking an action if necessary. Ignite supports Event Processing architecture with the following components: -

Re: ClassNotFoundException when using IgniteHadoopIgfsSecondaryFileSystem

Hi, I do not see any other reasons for a "class not found" exception but the class is not on the CLASSPATH. Can you make sure "ignite-core-xxx.jar" and "ignite-hadoop-xxx.jar" are on the hadoop's CLASSPATH.

Re: How IGFS URIs work

You do not need to specify the "host" part of the Hadoop URI at all if you do not want to limit processing to that specific host. Just specify "igfs://myIgfs@/" and Hadoop will load-balance the load for you across all IGFS nodes.

Re: How IGFS URIs work

That is right - you cannot use SHMEM connection type if you have no local Ignite. SHMEM means "shared memory" and requires local Ignite. Change IGFS endpoint type to TCP (below replace __HOST__ and __PORT__ with IP and port of any host running Ignite):

  1   2   >