schema for persistent cache will be stored into appropriate config.
>Hi Team,
>
>Thanks for the response.
>If we create schema(table) with indexes using existing cache , will this
>schema be created in memory?
>in our existing xml config , we are using persistence for ignite node, will
Hi
If I have an ignite node running on a machine with 16GB of physical memory
and I want to create a data-region that may hold 5GB of data but only
consume 1GB of memory on the off-heap, then how do I configure my cluster
node to use swap when exceeding 1GB off-heap memory?
I'm trying to get my
I am trying to build a low latency machine learning system from scratch using
apache ignite. Note: I am in design phase, and have not implemented
anything yet.
General data pipeline is:
Json Data via socket -> Ignite Cache -> Ignite ML (Updating) -> Ignite Cache
-> App (via continuous query)
Hi Team,
Thanks for the response.
If we create schema(table) with indexes using existing cache , will this
schema be created in memory?
in our existing xml config , we are using persistence for ignite node, will
apache use same persistence storage or create schema in-memory(RAM)?
Is there a way
> Are async Compute methods susceptible to a similar issue
Short answer - yes, but to a lesser degree.
In a striped pool, threads are assigned to partitions.
If a thread for a partition gets blocked, other operations for that
partitions block,
potentially causing a deadlock.
Compute simply uses
Hello!
Yes, it does indeed seem that you can now enable indexing on a cache by
doing "CREATE TABLE ... WITH "cache_name=";
+ dev@
Do we have this documented anywhere? Updating CREATE TABLE docs and Schema
and Indexing would be nice.
Hello!
Unfortunately, the exception snippet that you have pasted is not sufficient
to understand what's going on.
Regards,
--
Ilya Kasnacheev
ср, 10 мар. 2021 г. в 19:35, Pelado :
> Take a look at the data node. If the data node has restarted you might see
> a client disconnected exception.
Ilya, seems you mistaken, check [1]
Seems there is no additional documentation, but API is simple , check example
[2].
[1] https://issues.apache.org/jira/browse/IGNITE-12808
[2]
Hello!
You may choose to avoid destroying cache, instead just try to clean & reuse
them.
Number of partitions will likely not affect PME length because it is slow
due to its blocking nature, which forces all operations on the cluster to
finish before any new ops may be started.
Regards,
--
Hello!
Once a cache is created, you can't add indexes. You will need to recreate
cache / restart cluster with updated configuration.
You can define caches with Query Entities in spring XML configuration, pass
it to IgniteConfguration instance.
Regards,
--
Ilya Kasnacheev
пт, 12 мар. 2021 г.
10 matches
Mail list logo