Hello Igor,
If start two nodes on two hosts and create a cluster, you can reproduce
this problem. If start multiple server nodes on one host, it seems that
there is no problem.
Thin clients only need one.
在 2021/2/3 下午10:02, Igor Sapego 写道:
Hi, I've tried to reproduce an issue you described
Paolo,
> I could get rid of most of them by changing my configuration (e.g. setting
> a
default non-logging CheckpointSpi or non-logging CollisionSpi
implementation)
Would you have the snippet for this config? If they are your custom
non-logging classes are you comfortable sharing them here
Hi All,
Here it's a sample scala application,
https://gist.github.com/PingHao/0369a6d14c1de7072de57041a3fec0f7
I had compiled it with both Ignite 2.7.5 and 2.9.1 libraries, and got result by
run on a 3 server nodes + 1 client node cluster. all nodes have 56 cpu cores
and 100G+ free memory.
ilya.kasnacheev wrote
> Yes, it would be great!
Done: https://issues.apache.org/jira/browse/IGNITE-14125
Regards, Paolo
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Thanks for updating!
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi, I've tried to reproduce an issue you described and could not reproduce
it.
Can you share more details? How many nodes do you run? How many clients
are run? Do you run any other operations in parallel?
Best Regards,
Igor
On Wed, Feb 3, 2021 at 3:00 PM 18624049226 <18624049...@163.com>
Hello!
This will usually mean that some other operation is blocking the
checkpoint. Until it finishes, and the checkpoint starts, no new operations
may proceed.
You need a full thread dumps to find any operations not waiting
on GridCacheDatabaseSharedManager.checkpoint*Lock
Regards,
--
Ilya
Hello Folks
The attempts to partition rebalancing in my ignite clusters fail with the
following errors. Any help would be greatly appreciated. I am using ignite
2.8.1.
[2021-02-02 19:57:03,428][WARN ][tcp-disco-msg-worker-[ef238b3f
10.244.69.14:47500]-#2][root] Possible failure suppressed
Hi team,
Using the 2.10 branch code and the transaction function of cpp thin
client, the transaction with id 1 not found error will be throw. the
reproduce steps are as follows:
1.start a node use the following config file:
http://www.springframework.org/schema/beans;
Hello!
Yes, it would be great!
Regards,
--
Ilya Kasnacheev
ср, 3 февр. 2021 г. в 10:22, Paolo Bazzi :
> Thanks for your replies and creating the issue.
>
>
> ilya.kasnacheev wrote
> > The second one is clearly also a bug. You can sidestep it by setting log
> > level to INFO.
>
> Shall I
Hi,
In our case, server nodes are always online and there is no server node
downtime until we make it manually. so how are partitions getting lost
frequently? and if this error occurred read and write operations will not
work with the respective cache.
Thanks
--
Sent from:
Hi,
currently, I am using 2.9.1 and at present, we can't rollback for older
versions so can you assist me with a temporary solution for this version,
and can I get the estimated date for Ignite 2.11.0 release.
Thanks
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hello!
For the curious, the ticket is
https://issues.apache.org/jira/browse/IGNITE-14076
Regards,
--
Ilya Kasnacheev
пт, 29 янв. 2021 г. в 18:55, jjimeno :
> Ok... thanks!
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
13 matches
Mail list logo
