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
In an IPC, we are seeing that the CPU usage of the SDK script is causing 100% usage of a particular core. This appears to be a similar issue to what was seen in the device client here: awslabs/aws-iot-device-client#147
Regression Issue
Select this option if this issue appears to be a regression.
Expected Behavior
CPU usage is very low
Current Behavior
CPU usage is at 100%
Reproduction Steps
We run the attached script as a service within the IPC which is based on AWS documentation.
Your repro doesn't use Greengrass IPC. In fact it doesn't use the v2 SDK which is the repo this issue is created on.
It does however include:
while True:
continue
bretambrose
added
closing-soon
This issue will automatically close in 5 days unless further comments are made.
and removed
bug
This issue is a bug.
needs-triage
This issue or PR still needs to be triaged.
labels
Oct 29, 2024
We are currently using the v2 SDK and have chosen not to utilize Greengrass IPC as we don’t require offline communication between IPCs. We are using AWS IoT Core Things
Are there specific scenarios where Greengrass might offer better advantages? Our primary focus is ensuring secure tunneling within our IPC setup.
Describe the bug
In an IPC, we are seeing that the CPU usage of the SDK script is causing 100% usage of a particular core. This appears to be a similar issue to what was seen in the device client here: awslabs/aws-iot-device-client#147
Regression Issue
Expected Behavior
CPU usage is very low
Current Behavior
CPU usage is at 100%
Reproduction Steps
We run the attached script as a service within the IPC which is based on AWS documentation.
secure_tunneling.txt
Possible Solution
No response
Additional Information/Context
No response
SDK version used
1.5.4
Environment details (OS name and version, etc.)
Ubuntu 22.04
The text was updated successfully, but these errors were encountered: