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
It appears that 0.14.3 introduced a memory leak in the native process.
See this graph of the KPL native process memory usage:
The top two lines are 0.14.3 and 0.15.6. The bottom (flat) line is 0.14.2. These graphs are from three application instances that are identical except for the version of KPL they are using. This a test application whose only operation is to publish to a Kinesis stream in a loop. Eventually, the OS kills the native process and KPL has to restart it. In all three applications, the outstandingRecordsCount stays below 5000, so this does not appear to be back-pressure related.
These are running in ECS with the amazoncorretto docker image on arm64.
It's possible that this is the same issue reported in #447 and #485.
The text was updated successfully, but these errors were encountered:
It appears that 0.14.3 introduced a memory leak in the native process.
See this graph of the KPL native process memory usage:
The top two lines are 0.14.3 and 0.15.6. The bottom (flat) line is 0.14.2. These graphs are from three application instances that are identical except for the version of KPL they are using. This a test application whose only operation is to publish to a Kinesis stream in a loop. Eventually, the OS kills the native process and KPL has to restart it. In all three applications, the
outstandingRecordsCount
stays below 5000, so this does not appear to be back-pressure related.These are running in ECS with the amazoncorretto docker image on arm64.
It's possible that this is the same issue reported in #447 and #485.
The text was updated successfully, but these errors were encountered: