Hi, I was wondering if anyone already dealt with this issue:
"System has been suspended for over X seconds, exceeding the maximum duration specified. Allowing system activity to resume. Any ongoing backup has presumably failed. Next InterSystems IRIS backup must be a full one"

our backup system "Commvault" is automatic, how do you tell it once you get this message that the next backup should be full?

thanks,

Eyal

1 11
0 225

Just got the new beta version of Docker, with depreciation warning of AUFS. It's so bad news when InterSystems does not support used by default storage driver overlay2. Recently I thought to play with Google Kubernetes Engine, and realized that I can't work with InterSystems products there due to incompatibility with Storage Driver. Maybe it's already time to think about support?

4 5
0 749

I am currently using IKO 3.6 to deploy an irisCluster on EKS, but I am facing some challenges. Firstly, I need assistance in understanding how to connect to the Web Gateway sidecar. If anyone has experience with this, I would greatly appreciate any guidance or advice you can offer. Secondly, I am trying to utilize the 'seed: path' options of irisDatabases, but I am unsure of the best approach. If anyone has successfully implemented this feature, I would love to hear about your approach and any insights you can provide. Thank you in advance for any help you can offer!

1 4
0 238

Hi Everyone,

I've been working on deploying an IRIS for Health environment in EKS. There is a video session in the InterSystems learning portal about this feature but I have not succeeded in finding the proper documentation and resources to use this in my Kubernetes cluster.

Has this been deprecated/discontinued? Any idea where can I find the resources? Should I stick to StatefulSets instead of using the IrisCluster resource type provided by this operator?

0 3
1 385

In the context of IKO (Iris Kubernetes Operator) the question of Service not redirecting dynamically to the correct Pod is still pending.
In production this can be dangerous since an overload (or any other simpler problem) can cause you to change the main Pod and leave the application inoperable until we intervene.

Intersystems support warned that this is still an issue of IKO, but there are some possibilities that I am studying.

To explore an idea I had, I would like the help of this Forum to answer the following question:

0 3
0 279

We have solution which uses IRIS with IAM and webgateway integrated.

After integration, we notice that in the kong configuration in the kongdb upstreams are not created as listed in the kong.yml

We noticed that, IAM api calls are failing with enterprise license expired.

[kong@iam-deployment-75f485954c-ssdfv /]$ curl --location --request POST 'http://localhost:8001/services/'
{"message":"Enterprise license missing or expired"}

From Logs:

0 3
0 271

greetings Community!

InterSystems Learning Services is working to identify and create libraries of high-quality learning resources for third-party technologies, platforms, and systems that are part of, integrated with, or commonly used with InterSystems products and technologies. we don't create content for these ourselves, but want to support our clients, external and internal, in learning about them and how to use them.

2 2
0 343

Hi,

Are we correct to assume that the IKO topology only allows for the use of one 'data' node type, and one 'compute' node type? So if we want to use several different iris based compute nodes (or data nodes) we have to apply several yaml files? So the following topology config is not possible:

topology:
data:
image: dvza.healthexchange.nl/mmres:0.1
data:
image: dvza.healthexchange.nl/mmauth:0.1
data:
image: dvza.healthexchange.nl/somethingelsethatisbasedonirisimage:0.1

Thanks in advance.

0 1
0 255