You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are facing issue with mediator even when 200+ users are trying to connect with mediator using pickupv2 as a mediator pickup strategy. We are observing Database CPU usage crosses 99% with instance type : RDS m6i.xlarge & RDS m6i.2xlarge both are tried
We are getting high CPU utilisation due to the below query
SELECT id, kind, category, name, value, (SELECT ARRAY_TO_STRING(ARRAY_AGG(it.plaintext ? ENCODE(it.name, ?) ? ENCODE(it.value, ?)), ?) FROM items_tags it WHEREit.item_id=i.id) tags FROM items i WHERE profile_id = $1AND (kind = $2OR $2 IS NULL) AND (category = $3OR $3 IS NULL) AND (expiry IS NULLOR expiry >CURRENT_TIMESTAMP) AND ((i.idIN (SELECT item_id FROM items_tags WHERE name = $4AND value = $5AND SUBSTR(value, ?, ?) = $6AND plaintex
Please suggest if any changes required or any recommendations for configurations
The text was updated successfully, but these errors were encountered:
sairanjit
changed the title
Issue with mediator even when many users are trying to connect with mediator using PickUpV2 as a mediator pickup strategy.
Issue with mediator when many users are trying to connect with mediator using PickUpV2 as a mediator pickup strategy.
Nov 1, 2024
We are facing issue with mediator even when 200+ users are trying to connect with mediator using pickupv2 as a mediator pickup strategy. We are observing Database CPU usage crosses 99% with instance type : RDS
m6i.xlarge
& RDSm6i.2xlarge
both are triedWe also tried using the AWS RDS Proxy as suggested here https://github.com/hyperledger/aries-askar/blob/main/docs/storage.md#aws-rds-proxy but are still facing the same problem.
We are using the following
mediator https://github.com/credebl/mediator-agent
We are getting high CPU utilisation due to the below query
Please suggest if any changes required or any recommendations for configurations
The text was updated successfully, but these errors were encountered: