Hi,
I took a look at the reproducer and it works just fine with different Ignite
and .net versions.
Is there just a single Ignite server with the default config?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi!
Ignite iterates over the whole keys collection, then performs a remove(keys)
method. So if there are a lot of items and a distributed cluster, then this
would take a long time.
You can take a look into into regular IgniteCache, which has a destroy()
method.
And use put/get for insert/check
Wait a sec, I have already posted an example, but for some reasons it was not
send properly.
Here are we go:
class Program
{
private static IContinuousQueryHandle _continuousQuery;
const string CacheName = "sample";
const string TableName = "entity";
static void Main(string[]
Hi,
You can just save an instance of continuous query somewhere and dispose it
when required
var listener = new SomeListener();
var someFilter= new
CacheEntryEventFilter(_ignite.GetCluster().GetLocalNode(), Const.CacheName);
var query = new ContinuousQuery(listener, someFilter);
Hi, yes, it should work that way.
I was able to caught all events event with the raw SQL using this DBeaver
https://apacheignite-sql.readme.io/docs/sql-tooling
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi,
I would suggest you to move your business logic out of queryable fields.
Put [QuerySqlField] to plain _JoinDate and rewrite your sql to "where
_JoinDate = ..."
This should work as your *cache.Get() result* example.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi,
You can pass JVM arguments only to official standalone executable that actually
takes care of the CLI arguments you provided.
More information here
https://apacheignite-net.readme.io/docs/standalone-nodes#section-configuring-standalone-node-via-command-line
For your IgniteApp.exe you
Hi, Siva!
Can you share a simple example of that?
From: siva
Sent: Friday, July 12, 2019 3:43 PM
To: user@ignite.apache.org
Subject: Error compiling query: entire LINQ expression should be
specifiedwithin lambda passed to Compile method. Part of the query can't be
outsidethe Compile method
Hi, Siva
I have no idea whether you have subscribed to dev list or not, but there is an
active discussion regarding 2.7.6 release and estimated dates.
http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-7-6-Time-Scope-and-Release-manager-td42944.html
Note, that original issue
Hello,
With default configuration Ignite uses MulticastIpFinder that will try to scan
for available Ignite instances within your network automatically.
The default required ports are: 47500 and 47100 for discovery and
communications and localhost(127.0.0.1) is the default alias for docker
Hello,
Not a thin-client tuning in general, but you can check a serialization settings
in order to make sure you do not use a default one.
From: John Smith
Sent: Friday, August 30, 2019 6:04 PM
To: user@ignite.apache.org
Subject: Tuning client performance.
Hi, is there any specific client
Meanwhile, I think it’s true that we are lacking of complete .NET examples for
modern apps.
It would be perfect if anyone would share their Ignite .NET experience so that
we could collect them in a single place.
Incidentally, Pavel’s GitHub page is a good starting point.
From: Pavel Tupitsyn
Hi!
How do you run or install your service? Can you share a cmd?
I believe you need to use IgniteConfiguration.SpringConfigUrl settings for this
[1]
I.e. path
Also get a try with CMD args [2]
[1] - https://apacheignite-net.readme.io/docs/configuration#section-spring-xml
[2] -
Hello!
Client nodes still can keep some utility data that might be required for
application.
I think the most suitable example is near cache [1].
[1] - https://apacheignite.readme.io/docs/near-caches
From: rick_tem
Sent: Friday, September 13, 2019 7:10 PM
To: user@ignite.apache.org
Subject:
Hello!
You can try to use SqlFieldsQuery with “select _key from [CacheTable]” for that.
From: Mikael
Sent: Wednesday, September 11, 2019 3:47 PM
To: user@ignite.apache.org
Subject: Iterator for keys only ?
Hi!
What is the best way to iterate over the keys only from a cache ? I
don't want the
Hello,
There is an open ticket https://issues.apache.org/jira/browse/IGNITE-12032 with
more details.
In general, It’s ok to ignore this error.
You could try to follow Lev’s recommendations with explicit connection closing.
From: Matan Levy
Sent: Thursday, August 1, 2019 9:33 AM
To:
Hello,
Please, send an email to user-unsubscr...@ignite.apache.org and
dev-unsubscr...@ignite.apache.org
More details https://ignite.apache.org/community/resources.html#mail-lists
From: Deepa Kolwalkar
Sent: Monday, September 16, 2019 12:37 PM
To: user@ignite.apache.org;
Json,
Could you share an example of why do you need this feature?
In general, platform-specific nodes should be able to execute only native code.
I.e. C++ -> C++, C#-> C# etc.
But since a thick client is kind of a wrapper around Java one it’s quite easy
to call a Java code on a remote node.
Hello!
As far as my understanding goes, I see that eviction works ok.
>2019-09-09 11:04:03.557 WARN [sys-stripe-5-#6%TemenosGrid%]
>IgniteCacheDatabaseSharedManager - Page-based evictions started. Consider
>increasing 'maxSize' on Data Region configuration: 1G_Region
This message tells that
C++, Scala or anything else). Polyglot is a rising topic, thus I
was surprised I couldn't cross languages barriers when integrating operations
in Ignite and C++ thick nodes.
Am 9/16/2019 um 6:38 PM schrieb Alexandr Shapkin:
Json,
Could you share an example of why do you need this feature?
In general
Hello Siva,
DateTime is a struct and thus should work the expected way.
Please, make sure, that you re-created your cache after some development
modifications.
I checked this with the following example from your sources:
public class Employee
{
…
[QuerySqlField]
Hi,
As far as I can see, [1] is included into 2.8 nightly build and most likely
will be included into next minor release.
Please, clarify, following questions:
1) What is the point of using 2.8 nightly build, since it could be unstable for
now?
2) What was the original issue you’ve been trying
Hi,
You need to configure includeEventTypes configuration property before starting
the grid [1]
Xml:
Code:
cfg.setIncludeEventTypes(EventType.EVT_CACHE_REBALANCE_PART_DATA_LOST);
[1] - https://apacheignite.readme.io/docs/events#section-configuration
From:
Hello,
If I get it right, you are talking about data replication feature.
Ignite does not support it out of the box, but you can take a look at GridGain
edition [1]
[1] -
https://www.gridgain.com/products/software/enterprise-edition/data-center-replication
From: raja24
Sent: Monday, August
Most likely you need to get them aware of each other.
I.e. configure DiscoverySpi addresses range to 49500..49509.
Please, share you Ignite config for containerized nodes.
Alexandr
From: vitalys
Sent: Thursday, August 8, 2019 9:00 PM
To: user@ignite.apache.org
Subject: RE: Running Ignite
Hello,
So, you have fixed IGNITE-10451 for 2.7.5 and now you are good with that?
I see that IGNITE-10451 is included into next Apache Ignite release.
Not necessary 2.8, since community may decide to release some minor update,
just like 2.7.5.
Please, follow @dev mailing list for latest
Hello,
I assume that the main difference is how thin and thick clients handles class
names metadata.
For thick client you definitely need to register such information manually.
I made your solution work by addition this configuration to the Java part (no
changes in c++ consumer):
Hello,
Please, refer to the docker port forwarding documentation [1]
In other words, instead of -p 47503:47503 you need to write -p 47503:47500,
unless you have not configured the default discovery spi port to 47503
explicitly.
Please, recall that Ignite requires a minimum set of open ports
Hi, Raymond!
As far as I can see, there are no plans for porting custom executors
configuration in .NET client right now [1].
Please, remind, why do you need a separate pool instead of a default PublicPool?
[1] - https://issues.apache.org/jira/browse/IGNITE-6566
From: Raymond Wilson
Sent:
fabric traffic from
server B to server A resulting in a deadlock condition.
In the original discussion it was suggested creating a custom thread pool to
handle the Server B to Server A traffic would resolve it.
Thanks,
Raymond.
On Wed, Jul 17, 2019 at 9:48 PM Alexandr Shapkin wrote:
Hi, Raymond
Hi!
As I understand correctly, right now CompiledQuery won’t work if there is a
non-primitive value inside the WHERE clause.
This seems like a bug for me, because it’s pretty common to treat String class
as a primitive one.
Right now you can rewrite your query to “x.Contains(y)” or
Hello Simon,
Can you, please, share a full log? There should be an internal Java exception
with that message.
It would be perfect if you can share a little reproducer as well.
From: simonatelier
Sent: Thursday, July 25, 2019 3:20 PM
To: user@ignite.apache.org
Subject: Ignite .NET 2.7.5 -
Thin client does not store data and is not a part of a cluster, instead, you can think of it as an interface of accessing and manipulating your data.Please, note, that you can not configure these properties for IgniteClientConfiguration.The data region configuration makes sense only for server
Sudhir, What exception are you getting? Can you share a full stacktrace/code snippet?Most likely you have an issue with the underlying DB configuration. You could have a look at Pavel’s examples for 3rd party persistence: https://github.com/ptupitsyn/ignite-net-examples From: Sudhir PatilSent:
tCache function call from client node for a key from cache created in server node. Are there any samples for ReadThrough operation done from normal ignite client node? Regards,SudhirOn Wednesday, November 13, 2019, Alexandr Shapkin <lexw...@gmail.com> wrote:Sudhir, What exception are you gett
Wednesday, November 13, 2019 4:56 PMTo: user@ignite.apache.orgSubject: Re: Ignite.Net Read through approach - error : could not create .Net cachestore Alexandr, Ok. But what is type of those 2 nodes ???On Wednesday, November 13, 2019, Alexandr Shapkin <lexw...@gmail.com> wrote:Sudhir, > Ar
Please, have a look at examples/datagrid/CacheQueryExample.java file. From: devinbostSent: Friday, November 15, 2019 1:31 AMTo: user@ignite.apache.orgSubject: Re: How to query existing cache that was configured via XML ilya.kasnacheev wrote> It's not possible to add table to cache.> > It is
It depends on what kind of information are you interested in. For sample, you can use the Cluster API to inspect a node’s metrics manually [1].Or take a look at some monitoring tools, like WebConsole [2]. [1] -
Have you tried a cache template [1]? After you designed your custom affinity function, you can configure it for a new cache template.You could use it with the CREATE TABLE statement [2].Please, note, that a template should be registered in advance. [1] -
> How do we delete caches? What about DROP TABLE [1]? This should remove both a table and a cache. > Is there a way to run the SQL query that doesn't require us to first get orcreate an existing cache You can use a thin client for that, please, review the JDBC example.With this approach, the
you. I will explore on 1)What are API ways to get details for individual nodes ? For 2) is gridgain a licensed version ?On Friday, November 15, 2019, Alexandr Shapkin <lexw...@gmail.com> wrote: It depends on what kind of information are you interested in. For sample, you can use the Cluster AP
If you take a look at QueryParser#parseH2 then you can see the following statement: catch (IgniteCheckedException | SQLException e) { throw new IgniteSQLException("Failed to parse query. " + e.getMessage(), IgniteQueryErrorCode.PARSING, e);} So any exception on this stage will be considered as
Jira ticket https://issues.apache.org/jira/browse/IGNITE-12381 From: Alexandr ShapkinSent: Monday, November 18, 2019 4:44 PMTo: user@ignite.apache.orgSubject: RE: IgniteSQLException If you take a look at QueryParser#parseH2 then you can see the following statement: catch (IgniteCheckedException
Hello! Have you tried the ML package for Apache Ignite [1]? It definitely should use data frames internally. > So cache keys [0...9] have affinity key 0, keys [10...19] have>affinity key 1 etc? Sure, the easiest one would be to add a new field to your model with[AffinityKeyMapped]
Hello! Is it possible that you had disabled WAL before restarting a cluster? Doing this may cause data loss in some scenarios. From: MikaelSent: Saturday, November 16, 2019 9:58 AMTo: user@ignite.apache.orgSubject: Re: Ignite data loss Hi!So it does not matter what node you restart ? it's always
here?? Regards,SudhirOn Wednesday, November 13, 2019, Sudhir Patil <patilsudhi...@gmail.com> wrote:Alexandr, Can you share the code u used + configuration ? I am not able to send snippets as i have to type in and can't send those from my work.On Wednesday, November 13, 2019, Alexandr S
You can also refer to the BinaryModeExample.cs example and the docs [1] [1] - https://apacheignite-net.readme.io/docs/binary-mode#section-creating-binary-objects From: Ilya KasnacheevSent: Friday, November 15, 2019 4:13 PMTo: user@ignite.apache.orgSubject: Re: Store objects as IBinaryobject in
Please, send this email to user-unsubscr...@ignite.apache.org From: Kurt SembaSent: Friday, November 15, 2019 11:44 AMTo: user@ignite.apache.orgSubject: unsubscribe unsubscribe
Yes, that true in most cases unless you try to call the queue method with a different collection configuration.In such case, an exception will be thrown. From: Narsi Reddy NallamilliSent: Friday, November 15, 2019 10:47 AMTo: user@ignite.apache.orgSubject: Re: query if queue exist and get it like
Hello!
Please, check that you are using the right JDK version (8+).
The proper version is set for JAVA_HOME, and you do not use the JvmDllPath
configuration.
Is it possible that you have multiple Java installations?
From: Sudhir Patil
Sent: Monday, October 21, 2019 2:25 PM
To:
Have you tried to remove ` joinTimeout` value? From: Ilya KasnacheevSent: Tuesday, November 26, 2019 1:48 PMTo: user@ignite.apache.orgSubject: Re: Unable to connect to a remote apache ignite node. Hello! I think you have some kind of connectivity problems between two nodes so the second node can
Hello!
In general, when you want to use SQL API you need to configure a table first.
There are several options for doing it:
- you can use create table statement [1]
- configuring QueryEntities [2]
When you create cache with Create statement, the DEFAULT SQL schema is used,
otherwise, it would
hir Patil <patilsudhi...@gmail.com> wrote:Alexandr, Can you share the code u used + configuration ? I am not able to send snippets as i have to type in and can't send those from my work.On Wednesday, November 13, 2019, Alexandr Shapkin <lexw...@gmail.com> wrote:I configured 1 server nod
>What's worse - they are evicted on one node, and eviction>is not propagated on the other two nodes (so now every node has different>count of entries for that cache, even though it's replicated) Data region configuration defines a local machine’s memory settings, it doesn’t propagate to other
Hello!
Roughly speaking, the getAll() internally being transformed into a sequence
of an individual get() operations. That's why Ignite doesn't provide a
special metric for that and will utilize the same #getAverageGetTime(). At
the same time, Ignite does care about what caches' API is being
Hello!
Roughly speaking, the getAll() internally being transformed into a sequence
of an individual get() operations. That's why Ignite doesn't provide a
special metric for that and will utilize the same #getAverageGetTime(). At
the same time, Ignite does care about what caches' API is being
Hello! Normally, a cache configuration should be transferred between the nodes, once it gets created.There are a couple of methods for accessing it:ICache#GetConfiguration(cacheName)igniteInstance.GetConfiguration().CacheConfiguration.Single(x => x.Name == CacheName) From: sivaSent: Tuesday,
Hello, Your query doesn’t use indices and performs a full scan on your tables.That requires more time in order to execute a join and get records. Please, consider adding the corresponding index:https://www.gridgain.com/docs/latest/sql-reference/ddl#create-index From: nunobSent: Tuesday, January
Hello! You could take a look at putAll method that sends all updates to the server right away. > *What is best way out of above to push continuously updating data like> market data?*For me it seems that the DataStreamer is more suitable for continuous data processing where you are not interested
Hello! I don’t think it could be done out of the box. You could try to start from the opposite side and generate a schema from a RDBMS instead using the WebConsole [1]. [1] - https://www.gridgain.com/docs/web-console/2019.12.02/automatic-rdbms-integration From: crypto_rickleeSent: Friday, January
Hello! Thin clients don’t change topology version, you may think of it as a different API for performing cluster operations alongside withREST API, WebConsole and others.[1] When you call Ignition.StartClient, your application establishes a new TCP connection to a server node using default 10800
Hi, I believe that you need to find the following message: 2020-04-30 16:57:44.8141|INFO|Test|Topology snapshot [ver=53, locNode=26887aac, servers=3, clients=0, state=ACTIVE, CPUs=16, offheap=8.3GB, heap=15.0GB]2020-04-30 16:57:44.8141|INFO|Test| ^-- Baseline [id=0, size=3, _online_=3,
Hi, It looks like a known issue when a server node is not fully initialized but clients are trying to connect to it [1] I’d suggest you try the latest version (2.8.1) and check if the error will be gone. [1] - https://issues.apache.org/jira/browse/IGNITE-11671 From: SanjayaSent: Friday, September
Hi, Just for the record, I noticed that the following tickets has been filed: https://issues.apache.org/jira/browse/IGNITE-13415 https://issues.apache.org/jira/browse/IGNITE-13436 Also seems like the consumer would work if you do at least one cache#put operation. From: Alexandr ShapkinSent:
Hi,
Is it possible to share a simple reproducer or to get the full logs from the
failed node?
-
Alex Shapkin
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi,
Yes, I can reproduce the behavior. It could be an issue with the custom
binary mappers.
The weird thing is that the CustomBinaryIdMapper works fine with a single
node, i.e. if it reads and writes the value from a cache, then the mapper is
working. But fails on the other node.
Meanwhile,
Hi, [33m[2020.09.08 21:19:28.898] [WARN ] [o.a.i.i.p.r.h.t.GridTaskCommandHandler] Failed to execute task due to topology issues (are all mapped nodes alive?) [name=o.a.i.i.v.compute.VisorGatewayTask, clientId=null, err=class o.a.i.IgniteCheckedException: Failed to reduce job results due to
Hi, Am I right that you are using the Azure Kubernetes cluster? If yes, it’s most likely is about the k8s kube-proxy health check probe pinging all open ports including the default thin client one (port 10800). Because of that, Ignite can’t read the message correctly and the
Hi,
Looks like this is the part of the upcoming warmup feature [1] that should
be published with the next Ignite release (2.10) or the upcoming GridGain
edition (v8.7.26?) [2].
Please, check the IEP-40 for the detailed explanation [3]
[1] - https://issues.apache.org/jira/browse/IGNITE-13345
[2]
Hi, In short, yes, it’s licensed and yes, you can use it for free. The project is under development and should be publicly announced in the near future. It’s licensed under the default GridGain community edition license and basically, It means that it’s free to use, you might find more information
Hi, As Wesley mentioned, It’s quite difficult to say something specific about without the logs. As for the additional questions, can you explain, what Ignite API is being used? Is it a Compute API call or a regular cache GETs? It’s totally fine to spawn several user threads and access the server
Hello!
It's not clear, whether the code snippet came from a client or a server. If
it's a client, then I'd recommend you try sending the keys and additional
data directly to a server node and perform the insertion directly on the
node. The Compute API could be an option here [1]
You might also
Hi,
Have you tried to reproduce this behaviour with the latest release - 2.8.1?
If I remember correctly, there were some fixes regarding the partition
counters mismatches, for sample:
https://issues.apache.org/jira/browse/IGNITE-10078
-
Alex Shapkin
--
Sent from:
I just wanted to highlight that there is the Partition Awareness feature
available for thin clients.
When enabled, a client will know to witch node a partition belongs and send
a request directly to that node.
[1] -
https://apacheignite-net.readme.io/docs/thin-client#partition-awareness
[2] -
Hi,
Yes, seems like the https://issues.apache.org/jira/browse/IGNITE-1410 is not
resolved, unfortunately.
Is it possible to listen for predefined events like
LifecycleEventType.AFTER_NODE_START or EVT_CLUSTER_ACTIVATED?
Alternatively, you might want to utilize Ignite data structures, like
Hi, You don’t have to specify the communication settings explicitly, usually it’s ok to leave the defaults. This is indeed your case, if one port is already occupied, the next one is chosenYou can reduce it directly in your node configuration. But it’s static configuration and applicable only for
Hi, Could you share the full logs with the exception? There is an interesting JIRA ticket that could be the reason for this [1] [1] - https://issues.apache.org/jira/browse/IGNITE-13373 From: shivakumarSent: Thursday, December 3, 2020 10:51 AMTo: user@ignite.apache.orgSubject: Could not clear
Hi, What version do you use? Is it possible to share the full log files? From: rihan123Sent: Friday, December 4, 2020 2:32 PMTo: user@ignite.apache.orgSubject: WAL is growing exponentially HiI am doing POC to see if Ignite is good for my usecase and i achievedrequired data ingestion rate but
Hi, I don’t think that ignite support this out of the box, cause data replication is something beyond the default distribution. The usage depends on how your data is replicated, whether you want active-active synchronization, and so on. But if it’s about switching from one cluster to another, and
Hi, I’ve filed a JIRA ticket https://issues.apache.org/jira/browse/IGNITE-13822 to track this issue.Full logs or a simple reproducer would help to debug this more quickly, feel free to share them as well. From: yangjiajunSent: Monday, December 7, 2020 5:40 AMTo: user@ignite.apache.orgSubject: With
Hi, This is kind of expected, cause you don’t keep your client running. Try adding something like Console.ReadLline() at the end of your client’s main method. When a task initiator lefts from the grid, there is no way to send the results back, therefore depending on NODE_FAILED timing your either
Hi, Seems like there is a syntax error and Apache Ignite failed to produce an execution plan Could you try to run it without the parentheses? Like: INSERT INTO desttable (name, lastname, age) SELECT name, lastname, age from srctable From: Alexandr ShapkinSent: Wednesday, November 18, 2020 5:10
Hi, That’s odd, could you please share the logs with the error? From: harinathSent: Wednesday, November 18, 2020 6:52 PMTo: user@ignite.apache.orgSubject: RE: Failed to prepare update plan error while inserting data, when select is used aong with insert Hi Alexandar, I have tried without
Hi, Seems like there is a syntax error. From: harinathSent: Wednesday, November 18, 2020 10:28 AMTo: user@ignite.apache.orgSubject: Failed to prepare update plan error while inserting data, when select is used aong with insert Hi, Using ignite thick client, i'm trying to copy data from one
Hi Siva,
Have you checked the SQL tuning documentation?
https://www.gridgain.com/docs/latest/perf-troubleshooting-guide/sql-tuning
-
Alex Shapkin
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi, Looks like the error message is truncated. Could you please re-send it or attach the full log file? PartitionsEvictManager is part of rebalancing routine and it clears local data before demanding it from other nodes. Also I see the following JIRA
Hi Siva, Nodes started on local machine require more than 80% of physical RAM whatcan lead to significant slowdown due to swapping (please decrease JVM heapsize, data region size or checkpoint buffer size) [required=78152MB,available=65535MB] According to the warning, you don’t have enough heap
Hi, Thanks for the ticket. I’ll check that. What configuration do you use, is it a persistent cluster or in-memory one?Do you use an official Ignite image or a custom assembly? 'kubectl delete pod' should work fine here and forward KILL SIG to a running node internally. Well, at least starting
Hi, It’s too internal details and it’s not possible to catch *Critical Workers HealthCheck* on client side. I think you might want to listen for Ignite events on your clients and apply your custom logic accordingly. The most essential candidate - EVT_NODE_FAILED You might check more available
Hi, As you correctly pointed to the PME implementation details webpage, this is a process of exchanging information about partition holders. And it’s happening on every topology change, cluster deactivation, etc. The process itself is not about data rebalancing, it’s about what node should store a
Hello!
It's recommended to set liveness and readiness probes, though the defaults
should be fine.
As per rebalancing, you might want to set
-DIGNITE_WAIT_FOR_BACKUPS_ON_SHUTDOWN=true meaning, that k8s can't restart a
pod if this could lead to a data loss.
You might check the Apache Ignite
Hi Maxim, Not really, I haven’t used flannel plugin and I’m not quite sure about network recommendations as well. Well, besides something basic, like avoid stretching between multiple availability zones and some persistence tuning,Like disabling MMAP for WAL (IGNITE_WAL_MMAP=false) > The problem
Hello Maxim, Could you please share the current state of this issue? Have you managed to resolve it or it still exists? What is your pods configuration in terms of resource usage? From: Maxim VolkomorovSent: Thursday, March 11, 2021 11:44 PMTo: user@ignite.apache.orgSubject: slow node discovering
Hello!
Please share the exception and attach Ignite logs.
> On 27 Aug 2021, at 15:12, Shubham Shirur wrote:
>
> Hi,
>
> Connector is giving me error while running in distributed mode. But running
> in standalone.
>
> Can you please highlight?
>
> Thanks
> Shubham
Hello!
What Ignite version are you running?
I can see that a similar issue has been fixed in 2.8
https://issues.apache.org/jira/browse/IGNITE-11755
> On 31 Aug 2021, at 19:22, DK wrote:
>
> Hi Team,
>
> Any pointers on this, please?
>
> Seems internally H2StatementCache contains a huge
Hello!
That’s correct, Ignite .NET server/thick client is JVM-dependent and requires
*.jar modules to be present in addition to the .NET dependencies. For console
and test deployments usually, it’s ok to rely on internal $IGNITE_HOME
resolution. By default, Ignite tries to locate it starting
96 matches
Mail list logo
