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
Create queues with the provider, possibly define tags.
What happened?
We are running a version v0.47.1 of provider-aws-sqs. The SQS provider seems to exit due to a concurrent map write. The maps causing this seem to be the ones in the QueueObservation struct, see.
The queues have a tags section which might be the culprit:
It seems that these should be made safe for concurrent access. Perhaps Upjet should use sync.Map or it should use a locking mechanism for map typed fields. There seems to be a similar issue reported previously about ECS Tasks, but unfortunately got no attention so far.
That particular environment has over 400 Queues created with the provider and this results in the provider restarting quite often, once every 5 to 20 minutes.
Is there an existing issue for this?
Affected Resource(s)
sqs.aws.upbound.io - Queue
Resource MRs required to reproduce the bug
No response
Steps to Reproduce
Create queues with the provider, possibly define tags.
What happened?
We are running a version v0.47.1 of provider-aws-sqs. The SQS provider seems to exit due to a concurrent map write. The maps causing this seem to be the ones in the QueueObservation struct, see.
The queues have a tags section which might be the culprit:
It seems that these should be made safe for concurrent access. Perhaps Upjet should use sync.Map or it should use a locking mechanism for map typed fields. There seems to be a similar issue reported previously about ECS Tasks, but unfortunately got no attention so far.
Relevant Error Output Snippet
Crossplane Version
v1.15.3
Provider Version
v0.47.1
Kubernetes Version
No response
Kubernetes Distribution
No response
Additional Info
No response
The text was updated successfully, but these errors were encountered: