Enterprise Cache Protocol (ECP): a distributed data caching architecture that manages the distribution of data and locks among a heterogeneous network of server systems.
I need to ensure that the task created/scheduled, by system user, is created in the routine database and not remotely in the ECP to which it is connected. How can I guarantee the creation/scheduling of this task?
Here is a suggestion for creating the routine in both environments:
With ECP we have the option to have a collection of Frontend instances All Frontend servers typically have a common Master in the background Concentrating data on the Master server is the primary goal.
As a side effect, this applies also to Classes, Routines, .. anything stored in Globals. This is probably not the most efficient setup. But rather common anyhow.
Is embedded Python code also stored in Globals?
What is the recommended solution for a similar installation?
Sometimes customers need a small IRIS instance to do something in the cloud and shut it down, or they need hundreds of containers (i.e. one per end user or one per interface) with small workloads. This exercise came about to see how small an IRIS instance could be. For this exercise we focused on what is the smallest amount of memory we can configure for an IRIS instance.Do you know all the parameters that affect the memory allocated by IRIS ?
If several application servers are connected using ECP, and one of them create many locks, so many that lock table became full :
Should we expect only that application server to be impacted ? (usually, when lock table is full the system became instable). Or, are other application servers going to be impacted the same way ? (because that lock table is synchronized and maintained in sync across all servers)
By views