Is it possible to initiate and commit/rollback an Ignite transaction when using the Thin Client for .Net? I didn't find the method to begin a transaction.
Thank you!
The transactional API is about to be added to the .NET thin client. Watch this Ignite JIRA ticket.
Related
I have integrated RabbitMQ with Magento to use async bulk APIs, now I have to check the same with MySql as a queue processor instead of RabbitMQ. does anyone has integrated it? the reference of env.php file would be helpful.
Thanks
I send request in Ignite Client and client execute task on Ignite servers in cluster. Server need calculate some data from cache and return response to client. Client use IgniteCompute for execute, but if server was lost (crashed, connect lost, timeout) Ignite not balance this task for execute another server.
My question
Can Ignite repair (repeat) execute if connection lost with server in cluster? Or i need check this errors in client myself and send repeat request ?
I found some properties :
setAckTimeout
setSocketTimeout
setNetworkTimeout
setDiscoverySpi
setFailureDetectionTimeout
setClientFailureDetectionTimeout
setRebalanceTimeout
But it is not work....
My stack
Java 1.8
SpringBoot 2.4.5
Ignite 2.10
Ignite supports failover in terms of jobs. In order to achieve that you need to configure FailoverSPI. More information could be found in the documentation.
I am trying to build an apache ignite thinclient poc and am able to connect to a cluster and also read the data using a ScanQuery. But am stuck at creating a Listener for any cache updates. I looked through but could not find anything for thin clients. Does ignite thin client even support listening on cache updates? How do I do that?
No, thin clients don't support Continuous Queries. You'll need to use a thick client to get that functionality.
I have set up Tomcat cluster, behiind Apache Httpd server, with 2 nodes. I read the Tomcat documentation at Tomcat cluster how to and the first requirement is:"All your session attributes must implement java.io.Serializable". I've done and session replication, failover mechanism seems to work. Now I'm using a framework for Web app develop and it seems that the object classes that are stored in the session don't implement Serializable. I'm looking for a workaround to solve this problem in the simplier manner. I've read a lot of questions/answer but not solution so far. Any idea? Tomcat version 7.0.76. Thank you.
I have an NServiceBus installation (a single server, obviously).
Is it possible to configure the NSB persistence to use a single RavenDB database (not server)?
If so, what would the configuration be?
The scenario I am thinking about is whether it is possible to use RavenHQ so that all my NSB data is backed up off the machine running the bus.
Just use the connectionstring option(NServiceBus.Persistence) and point all your endpoints to the same db. Be aware that you need to use NSB 3.2.3 since the TimeoutManager was patched to support this in that version