Hi,
1)JDBC thin client becomes not work after one node fails.I think the cause
is my node uses too many heap space and jvm pause too much time.I was doing
write performance test at that time.
2)I use control.sh script to active the cluster,but it does not exit .
3)Yes.I use persistence.
4)I
Hi,
I am currently playing around with Apache Ignite 2.6. I was just wondering if
there is a way to supply multiple directories/filesystems for the storagePath,
walPath, walArchivePath .
Thank you
Hi!
You said: "And it still uses 80%-85% of heap memory after I stop my
application", I assume you mean your client application ?
So after a GC it will still stay at 80% java heap usage ?
I assume you are using off-heap memory ?
I am not sure what the problem is, I am running an application
HI.
I have an ignite node which is version 2.6 and has fixed 12GB heap memory
and 30GB data region.I use it as a database with persistence.It uses 90%-95%
of heap memory when my application is busy(My application uses jdbc thin
connection).And it still uses 80%-85% of heap memory after I stop my
I use ZookeeperDiscovery,but sometimes the cluster will be wried,client can
not join the cluster,and the zookeeper node /jd will have many children
nodes.
When I restart a server node,the exception is:
19:14:06.675 [zk-192_0_0_1_DAEMON_NODE_8991-EventThread] INFO
know that the coming release (2.7) support
JDBC:
* Implemented DataSource interface for thin driver
and there is a jira about the connection pool
https://issues.apache.org/jira/browse/IGNITE-6145
it comments as below
W have to support connection pool to JDBC compliance.
At the very least
Known from mail list ignite 2.7 will support jdbc datasource.
and there is a jira about jdbc connection support
https://issues.apache.org/jira/browse/IGNITE-6145
it's blocked by
https://issues.apache.org/jira/browse/IGNITE-6140
right now https://issues.apache.org/jira/browse/IGNITE-6140
Hi Pavel
We are using Ignite 2.6
You were saying, usage of cache groups is definitely needed to improve to
the cluster activation time ?
I could see below documentation on the usage of cache groups.
Should the grouping be used all the times?
With all the benefits the cache groups have,
HI All
Initiating a new thread on the cluster activation time
We are using Ignite 2.6
You were saying, usage of cache groups is definitely needed to improve to
the cluster activation time ?
I could see below documentation on the usage of cache groups.
Should the grouping be used all the
Hi,
We are using ignite to share in memory data across the spark jobs. When we
are running the spark job we see following warnings in ignite logs. We have
done garbage collection tuning as suggested in apache ignite performance
tips but still we see below warning.
Please suggest.
Warning 1
Hi we use ignite as our searching backend.
Our cache is in replicated mode and primary_sync. Our query is more like the
following. We find that that the query time is the sum of two sub-select
query. Since our two sub select query is independent, is there a way to run
them in parallel ? Thanks
I meant I have it locally so if any of our community member needs it I can
provide a sample application.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi,
I don't think that Ignite has the example for exactly spring boot
integration. But you can see the example for Spring integration.
https://github.com/apache/ignite/blob/master/examples/src/main/java/org/apache/ignite/examples/misc/springbean/SpringBeanExample.java
Do you have any problems
Hi.
I have a cluster which has 2 data nodes of version 2.6.I use it as a
in-memory database.It stores tens of millions size data and all data are
replicated.I try to recover it after one node failed but I still can not
operate on it by jdbc thin connection. So I try to do a full cluster restart
I commented below line:
#spring.cache.cache-names=users,cannedReports
I am creating cache explicitly in CacheConfiguration class:
if (cm.getCache("users") == null)
cm.createCache("users", cacheConfiguration);
if (cm.getCache("cannedReports") == null)
Hello Team,
Any update on the Spark Structred streaming support with Ignite?
https://issues.apache.org/jira/browse/IGNITE-9357
Thanks
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Thanks Andrei,
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi,
Yes, default atomicity mode is ATOMIC. Next code used by Ignite to set the
atomicityMode
initializeConfigDefaults method used for default config. It contains:
if (cfg.getAtomicityMode() == null)
cfg.setAtomicityMode(CacheConfiguration.DFLT_CACHE_ATOMICITY_MODE);
So you
Hi Team
Apache Ignite atomicityMode is "ATOMIC" by default or do we need to
explictly include in defaul-config.xml? Pleae advise.
Thanks
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi Denis,
Yes, I understand reflective serialisation uses binarizable serialisation
under the hood (and it's fast and easy to use). But it has issues in the
face of schema changes so it is better (and recommended in the Ignite docs)
to use Binarizable serialization for production.
I want to make
Hi guys,
I have the following query which is slow. Below is the explain plan. Any clue
whats going wrong ?
[WARNING][client-connector-#62][IgniteH2Indexing] Query execution is too long
[time=9649 ms, sql='SELECT
2018-10-31T17:09:25.071Z __Z0.ACCOUNTNUMBER __C0_0,
2018-10-31T17:09:25.071Z
I commented below line:
#spring.cache.cache-names=users,cannedReports
I am creating cache explicitly in CacheConfiguration class:
if (cm.getCache("users") == null)
cm.createCache("users", cacheConfiguration);
if (cm.getCache("cannedReports") == null)
class org.apache.ignite.IgniteCheckedException: Cannot find metadata for
object with compact footer: -1434421210
at
org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7307)
at
I find an exception message after retries.
class org.apache.ignite.IgniteCheckedException: Cannot find metadata for
object with compact footer: -1434421210
at
org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7307)
at
Hi Pavel
We are using Ignite 2.6
You were saying, usage of cache groups is definitely needed to improve to
the cluster activation time ?
I could see below documentation on the usage of cache groups.
*Should the grouping be used all the times?
With all the benefits the cache groups have, they
Hi,
What do you mean when say that
1)JDBC thin client isn't worked
2)cluster block in activate stage
How you activate your cluster? Are you use the persistence?
To get more logs try to add next option to java options of Ignite:
-DIGNITE_QUIET=false
BR,
Andrei
--
Sent from:
26 matches
Mail list logo