APAR status
Closed as program error.
Error description
During backup operation cassandra container creates backup files inside /tmp folder for temporary purposes. After uploading to specific sftp/ftp/ebs location script does not cleanup backup files which are temporarily stored /tmp folder.
Local fix
Ø Deleting cassandra pod will clear the files under /tmp and allow the pod to start correctly
Problem summary
On every Cassandra backup operation ( can be trigerred by a cron job or on demand operation), backup files are not cleaned in the /tmp directory in each cassandra container. If backups are taken too frequently, /tmp directly can fill up and cassandra startup scripts which uses `sed` linux command will no longer work as `sed` command needs space in /tmp directory. This can result in downtime as cassandra servers do not start.
Problem conclusion
Fix targeted for release v2018.4.1.2
Temporary fix
Comments
APAR Information
APAR number
LI80503
Reported component name
API CONNECT ENT
Reported component ID
5725Z2201
Reported release
18X
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-12-21
Closed date
2019-01-31
Last modified date
2019-01-31
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
API CONNECT ENT
Fixed component ID
5725Z2201
Applicable component levels
R18X PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSMNED","label":"IBM API Connect"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"18X","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
29 September 2021