Re: [2.9.0]Entryprocessor cannot be hot deployed properly via UriDeploymentSpi
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 DeployClient to deploy the service named "deployService"; 4.Execute the test through ThickClientTest, and the result is correct; 5.Modify the code of DeployServiceImpl and DeployEntryProcessor, for example, change "Hello" to "Hi", then repackage it and put it into the specified folder of uriList; 6.Redeploy services by RedeployClient; 7.Execute the test again through ThickClientTest, and the result is incorrect,we will find that if the Entryprocessor accessed by the service is on another node, the Entryprocessor uses the old version of the class definition.
Re: Server created remotely, C# client not able to connect to cluster with IP address
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:
https://ignite.apache.org/releases/latest/dotnetdoc/api/Apache.Ignite.Core.Client.IgniteClientConfiguration.html
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Client App Object Allocation Rate
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 > 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/ >
Re: Server created remotely, C# client not able to connect to cluster with IP address
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: http://apache-ignite-users.70518.x6.nabble.com/
Re: Client App Object Allocation Rate
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/
Re: Client App Object Allocation Rate
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 > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
Re: Server created remotely, C# client not able to connect to cluster with IP address
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 171.159.66.12 that needs to be in the cluster then include it in the discovery section. If the cluster consists of only one server, you can leave the discovery section blank. Read through this section: https://ignite.apache.org/docs/latest/clustering/tcp-ip-discovery -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: L2-cache slow/not working as intended
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 enable Ignite persistence, but I assume that's not what you want. Regards, -- Ilya Kasnacheev пн, 9 нояб. 2020 г. в 20:05, Bastien Durel : > Le lundi 09 novembre 2020 à 19:11 +0300, Ilya Kasnacheev a écrit : > > Hello! > > > > Why Hibernate won't use it for reads of that user, I don't know, it's > > outside of scope of Ignite. > > > > Putting 1,000,000 records in 5 minutes sounds reasonable, especially > > since L2 population is optimized for latency, not throughput (as > > opposed to e.g. CacheLoader). > > Hello, > > I'm OK if the L2C make 5 minutes to load (as I said, there will > probably never be such a query in the real application), the real > problem here is that this cache does not persist between Sessions, and > therefore is recreated each time. > > It may be a configuration problem, but reading [1], I cannot find why > > Regards, > > [1] > https://ignite.apache.org/docs/latest/extensions-and-integrations/hibernate-l2-cache > > -- > Bastien Durel > DATA > Intégration des données de l'entreprise, > Systèmes d'information décisionnels. > > bastien.du...@data.fr > tel : +33 (0) 1 57 19 59 28 > fax : +33 (0) 1 57 19 59 73 > 45 avenue Carnot, 94230 CACHAN France > www.data.fr > > >
partition-exchanger system-critical thread blocked
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 triggered, it is blocked for 60s which is huge time from prod perspective. Below are error details, [2020-11-09T10:55:18,888][ERROR][sys-stripe-118-#119%EDIFCustomerCC%][G] Blocked system-critical thread has been detected. This can lead to cluster-wide undefined behaviour [threadName=partition-exchanger, blockedFor=60s] [2020-11-09T10:55:18,888][WARN ][sys-stripe-118-#119%EDIFCustomerCC%][G] Thread [name="exchange-worker-#344%EDIFCustomerCC%", id=391, state=TIMED_WAITING, blockCnt=16, waitCnt=2469961] Cluster is responding but these errors priting, we are not understanding what's the cause, could you please help us. Below is log snippet, [2020-11-09T10:51:21,458][INFO ][db-checkpoint-thread-#384%EDIFCustomerCC%][GridCacheDatabaseSharedManager] Checkpoint started [checkpointId=3bd28c8f-d9c9-4110-ab8c-24cf3a5c44a3, startPtr=FileWALPointer [idx=1279664, fileOff=28148165, len=49557], checkpointLockWait=0ms, checkpointLockHoldTime=34ms, walCpRecordFsyncDuration=7ms, pages=84152, reason='timeout'] [2020-11-09T10:51:23,499][INFO ][db-checkpoint-thread-#384%EDIFCustomerCC%][GridCacheDatabaseSharedManager] Checkpoint finished [cpId=3bd28c8f-d9c9-4110-ab8c-24cf3a5c44a3, pages=84152, markPos=FileWALPointer [idx=1279664, fileOff=28148165, len=49557], walSegmentsCleared=5, walSegmentsCovered=[1279658 - 1279663], markDuration=79ms, pagesWrite=1195ms, fsync=845ms, total=2119ms] [2020-11-09T10:51:36,788][INFO ][wal-file-archiver%EDIFCustomerCC-#345%EDIFCustomerCC%][FileWriteAheadLogManager] Starting to copy WAL segment [absIdx=1279664, segIdx=4, origFile=/datastore1/wal/node00-651e4920-2fb4-4dd5-9258-52a9f359ac35/0004.wal, dstFile=/datastore1/archive/node00-651e4920-2fb4-4dd5-9258-52a9f359ac35/01279664.wal] [2020-11-09T10:51:36,954][INFO ][wal-file-archiver%EDIFCustomerCC-#345%EDIFCustomerCC%][FileWriteAheadLogManager] Copied file [src=/datastore1/wal/node00-651e4920-2fb4-4dd5-9258-52a9f359ac35/0004.wal, dst=/datastore1/archive/node00-651e4920-2fb4-4dd5-9258-52a9f359ac35/01279664.wal] [2020-11-09T10:52:02,018][INFO ][wal-file-archiver%EDIFCustomerCC-#345%EDIFCustomerCC%][FileWriteAheadLogManager] Starting to copy WAL segment [absIdx=1279665, segIdx=5, origFile=/datastore1/wal/node00-651e4920-2fb4-4dd5-9258-52a9f359ac35/0005.wal, dstFile=/datastore1/archive/node00-651e4920-2fb4-4dd5-9258-52a9f359ac35/01279665.wal] [2020-11-09T10:52:02,200][INFO ][wal-file-archiver%EDIFCustomerCC-#345%EDIFCustomerCC%][FileWriteAheadLogManager] Copied file [src=/datastore1/wal/node00-651e4920-2fb4-4dd5-9258-52a9f359ac35/0005.wal, dst=/datastore1/archive/node00-651e4920-2fb4-4dd5-9258-52a9f359ac35/01279665.wal] [2020-11-09T10:52:36,541][INFO ][wal-file-archiver%EDIFCustomerCC-#345%EDIFCustomerCC%][FileWriteAheadLogManager] Starting to copy WAL segment [absIdx=1279666, segIdx=6, origFile=/datastore1/wal/node00-651e4920-2fb4-4dd5-9258-52a9f359ac35/0006.wal, dstFile=/datastore1/archive/node00-651e4920-2fb4-4dd5-9258-52a9f359ac35/01279666.wal] [2020-11-09T10:52:36,703][INFO ][wal-file-archiver%EDIFCustomerCC-#345%EDIFCustomerCC%][FileWriteAheadLogManager] Copied file [src=/datastore1/wal/node00-651e4920-2fb4-4dd5-9258-52a9f359ac35/0006.wal, dst=/datastore1/archive/node00-651e4920-2fb4-4dd5-9258-52a9f359ac35/01279666.wal] [2020-11-09T10:53:11,068][INFO ][wal-file-archiver%EDIFCustomerCC-#345%EDIFCustomerCC%][FileWriteAheadLogManager] Starting to copy WAL segment [absIdx=1279667, segIdx=7, origFile=/datastore1/wal/node00-651e4920-2fb4-4dd5-9258-52a9f359ac35/0007.wal, dstFile=/datastore1/archive/node00-651e4920-2fb4-4dd5-9258-52a9f359ac35/01279667.wal] [2020-11-09T10:53:11,239][INFO ][wal-file-archiver%EDIFCustomerCC-#345%EDIFCustomerCC%][FileWriteAheadLogManager] Copied file [src=/datastore1/wal/node00-651e4920-2fb4-4dd5-9258-52a9f359ac35/0007.wal, dst=/datastore1/archive/node00-651e4920-2fb4-4dd5-9258-52a9f359ac35/01279667.wal] [2020-11-09T10:53:45,694][INFO ][wal-file-archiver%EDIFCustomerCC-#345%EDIFCustomerCC%][FileWriteAheadLogManager] Starting to copy WAL segment [absIdx=1279668, segIdx=8, origFile=/datastore1/wal/node00-651e4920-2fb4-4dd5-9258-52a9f359ac35/0008.wal, dstFile=/datastore1/archive/node00-651e4920-2fb4-4dd5-9258-52a9f359ac35/01279668.wal] [2020-11-09T10:53:45,868][INFO ][wal-file-archiver%EDIFCustomerCC-#345%EDIFCustomerCC%][FileWriteAheadLogManager] Copied file [src=/datastore1/wal/node00-651e4920-2fb4-4dd5-9258-52a9f359ac35/0008.wal,
