Hi,
I have started four ignite nodes and configured cache in distributed mode.
When I initiated thousands of requests to write the data on this
cache(write through enabled) , facing below error.
>From logs we can see this error is occurring while witting to oracle
database.(using cache
>then we can use `cache group` to share some backend data struct to gain
some
level performance.
It will reduce the overhead for each cache since they will share the same
data structures under the hood.
>Are there any potential issues or potential consideration need to be
takecare of?
Caches in
Thank you reply very much!
If I keep all the caches for my system are created via sql, then all the
backend h2 tables are in public schema.
in this case even all the caches are in the same schema but there are
different cache (one cache per table but all in the same schema)
then we can use
Thanks Pavel - works well! :)
Raymond.
On Tue, Nov 13, 2018 at 9:20 AM Pavel Tupitsyn wrote:
> Hi Raymond,
>
> Yes, you can do that by implementing IBinarySerializer like this:
>
> class BinarizableSerializer : IBinarySerializer
> {
> public void WriteBinary(object obj, IBinaryWriter
Hi Raymond,
Yes, you can do that by implementing IBinarySerializer like this:
class BinarizableSerializer : IBinarySerializer
{
public void WriteBinary(object obj, IBinaryWriter writer)
{
if (obj is IBinarizable bin)
{
bin.WriteBinary(writer);
}
cache and schema is a different things in Ignite. By default, when you
create table with SQL, it will be created in separate cache.
Evgenii
пн, 12 нояб. 2018 г. в 20:00, kcheng.mvp :
> based on my knowledge about ignite, there is a corresponding database
> `schema` for each `cache` in ignite
based on my knowledge about ignite, there is a corresponding database
`schema` for each `cache` in ignite (cache name)
in real case there are always more than one tables in a database `schema`.
that's why I keep more than one tables in a single ignite `cache`
if use one table per cache,
Hello!
I would believe that reduce may run multiple times as you have suggested.
Regards,
--
Ilya Kasnacheev
чт, 1 нояб. 2018 г. в 5:48, gsaxena888 :
> I've been thinking about this some more: I think the ignite solution is
> nearly perfect, *if* the reduce operation runs within every node
Hello!
The last error looks like you have lost contents of work/marshaller
directory on your nodes. Did you? Do you have -1434421210.classname file or
similar?
Regards,
--
Ilya Kasnacheev
пт, 9 нояб. 2018 г. в 4:12, yangjiajun <1371549...@qq.com>:
> Hi,
>
> 1)JDBC thin client becomes not
Hello!
https://issues.apache.org/jira/browse/IGNITE-10224 might be related. Try
closing connections every now and then. If it does not help, collect heap
dump & analyze it.
Regards,
--
Ilya Kasnacheev
пн, 12 нояб. 2018 г. в 12:44, yangjiajun <1371549...@qq.com>:
> My test scenario:
> 1.One
>can you tell me why there is a such limit that new created table via sql
can
not be in the non-public schema?
It is a current restriction, that will be fixed in the future.
>as it's hard to forecast how many tables should be in a caches. If there is
a such limit, then what's the best practice
Thank you very much!
can you tell me why there is a such limit that new created table via sql can
not be in the non-public schema?
I am using ignite with persistent, each `module` in my system is using a
cache, which there are some tables generated via `cfg.setIndexedTypes`
right now for
Hello!
Looks like a bug. Track it at
https://issues.apache.org/jira/browse/IGNITE-10224
Regards,
--
Ilya Kasnacheev
вт, 30 окт. 2018 г. в 16:31, Mikhail :
> Hello,
>
> I need to execute a lot of SQL statements in one connection
> using IgniteJdbcThinDriver. I get memory leak
I have a server node in zone A ,then I start a client from zone B, Now access
between A,B was controlled by firewall,The acl is B can access A,but A can
not access B.
So when client in zone B join the cluster,the communication will fail caused
by firewall.
But when client in zone B closed, The
Hello!
Should be OK. Can you prepare a small reproducer of this problem, upload it
to github?
Regards,
--
Ilya Kasnacheev
пн, 29 окт. 2018 г. в 16:57, jcalahor :
> i forgot to mention that my starting params is:
> Apache.Ignite.exe
>
>
After reconnect unmarshalling of TcpDiscoveryNodeAddedMessage takes 20
seconds:
2018-11-12 14:10:36.105 ERROR 10 --- [-sock-reader-#3]
o.a.ignite.marshaller.jdk.JdkMarshaller : Unmarshall 1
2018-11-12 14:10:36.107 ERROR 10 --- [-sock-reader-#3]
o.a.ignite.marshaller.jdk.JdkMarshaller : Unmarshall
Hi, Andrei. Thank you for reply.
I have found that problem is in unmarshalling:
2018-11-12 13:18:24.375 INFO 10 --- [-sock-reader-#3]
o.a.i.spi.discovery.tcp.TcpDiscoverySpi : 1
2018-11-12 13:18:24.375 DEBUG 10 --- [o-msg-worker-#4]
o.a.i.spi.discovery.tcp.TcpDiscoverySpi : Received metrics
Thanks Stan,
planning to move on to 2.7.
Thanks
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi,
Do you use persistence? Do you have more data on disk than RAM size?
If yes, it’s almost definitely
https://issues.apache.org/jira/browse/IGNITE-9519.
If no, it still can be the same issue.
Try running on 2.7, it should be released soon.
Stan
From: ApacheUser
Sent: 5 ноября 2018 г. 20:10
Hi,
I changed listener code and it worked I got cache from completeale future
inside listener:
IgnitePredicate locLsnr = new IgnitePredicate(){
@IgniteInstanceResource
private Ignite ignite;
@Override
public boolean apply(CacheEvent evt) {
In other words - there is no way to do something with the cache after event
which signals about its creation.
On Mon, Nov 12, 2018, 11:57 Ilya Kasnacheev Cross-posting from SO:
>
> As a rule you should not perform cache operations, or most of other
> operations that block or access Ignite
Cross-posting from SO:
As a rule you should not perform cache operations, or most of other
operations that block or access Ignite internals. Events should be very
fast and lightweight, meaning that they are executed from inside Ignite
threads and Ignite internal locks.
Just schedule an operation
My test scenario:
1.One ignite node uses 12GB heap memory and 30GB off-heap memory with
persistence。Here is my cmd to start the node:
nohup ./ignite.sh ../examples/config/example-ignite.xml -J-server -J-Xms12g
-J-Xmx12g -J-XX:+AlwaysPreTouch -J-XX:+UseG1GC -J-XX:+ScavengeBeforeFullGC
Hi!
Thanks for your reply.
My client application uses jdbc thin connection to test performance of merge
into statement. We also use DPCP connection pooling providers to improve
performance.According to your suggestions and my experiment,I think idle
connections in the connection pool cause
Hi,
The expected behavior is that the only node without space will be failed.
Could you please attach the logs from both of the nodes to get more details?
BR,
Andrei
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi,
Looks like your JVM faces long garbage collection pauses. You can configure
detailed GC logs to see how much time is spent in GC:
https://apacheignite.readme.io/docs/jvm-and-system-tuning#section-detailed-garbage-collection-stats
Also, you can follow next guide and add more heap:
Hi,
Ignite data source should be supported in 2.7 release. The use case you can
see in next test:
https://github.com/apache/ignite/blob/master/modules/clients/src/test/java/org/apache/ignite/jdbc/thin/JdbcThinDataSourceSelfTest.java
However, you can try to ask Taras according to
Hi,
Could you please re-create this issue on development user list:
http://apache-ignite-developers.2346864.n4.nabble.com/
Development user list is the better place to discuss new functionality.
BR,
Andrei
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
28 matches
Mail list logo
