Any further conclusions?
在 2020/11/6 上午11:00, 18624049226 写道:
Hi community,
Entryprocessor cannot be hot deployed properly via
UriDeploymentSpi,the operation steps are as follows:
1.put jar in the specified folder of uriList;
2.Use example-deploy.xml,start two ignite nodes;
3.Use the
Follow the example here:
https://github.com/apache/ignite/blob/master/modules/platforms/dotnet/examples/Apache.Ignite.Examples/ThinClient/ThinClientPutGetExample.cs
if you are running your server on host ABC then set the cfg as
var cfg = new IgniteClientConfiguration("ABC");
see:
Hello!
Good question. Did something at all change after you set it? I'm not sure
why the message is so large in your cases, it's tens of kb.
Regards,
--
Ilya Kasnacheev
вт, 10 нояб. 2020 г. в 20:27, ssansoy :
> Yep theyre the ones we'd like to turn off... is that possible with
>
I see--
If I were to scrap the client/server idea entirely, what changes would I
need to make in order to connect a node created locally and programmatically
with C# with an IP address of DEF to a node created remotely on another
computer with an IP address of ABC?
--
Sent from:
Yep theyre the ones we'd like to turn off... is that possible with
IGNITE_DISCOVERY_DISABLE_CACHE_METRICS_UPDATE=true? it doesn't seem to have
an effect
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hello!
Yes, it's not cache statistics but node statistics
(org.apache.ignite.cluster.ClusterMetrics)
Regards,
--
Ilya Kasnacheev
пн, 9 нояб. 2020 г. в 21:09, ssansoy :
> Also according to the heap dump they aren't cache statistic messages, but
> rather, TcpDiscoveryClientMetricsUpdateMessage
To see that an IP is reachable from the client node, try using telnet
from the client host.
In your case the port should be 10800 and the IP is the one you are starting
the server from.
The discovery section tells Ignite where to find other nodes needed to form
a cluster. If there is a node on
Hello!
You can make it semi-persistent by changing the internal Ignite node type
inside Hibernate to client (property clientMode=true) and starting a few
stand-alone nodes (one per each VM?)
This way, its client will just connect to the existing cluster with data
already there.
You can also
Hi Igniters,
Sometimes 'Blocked system-critical thread' errors are getting printed in prod
cluster logs. As per below logs, it's saying exchange-worker blocked for 60s.
There is no node join/left or cluster activation or cache creation, still why
partition exchange is triggered. Even it is
