[BUG]: File expiry set on logical files and sasha is not removing them

[rpastrana]

Description

The DataOps team reports they have file expiry set on files located on the anr thor cluster, that are not members of a superifle, and they are not being removed by sasha. This is causing disk space issues on the thor (10.194.27.1 - 8). I looked up one example.

File name: thor::base::ock_p2::inc::20251203_2::monitoring_auto_unsuppressed_backup

Looking in logical files on eclwatch:

image (1)-20260120-161831.png

The file is set to expire on 12/24. I checked the sasha logs that are on 10.194.112.102 and I don’t see where the removal was ever tried on 12/31, which is the only log the file name appears.

saserver.2025_12_31.log:000C3856 2025-12-31 22:26:00.862 1755280 1755697 "XREF: [thor_anr_storage] Process file thor::base::ock_p2::inc::20251203_2::monitoring_auto_unsuppressed_backup"

saserver.2025_12_31.log:0010AE5B 2025-12-31 23:32:34.488 1755280 1755697 "WARNING: /var/lib/HPCCSystems/hpcc-data/thor/thor/base/ock_p2/inc/20251203_2/monitoring_auto_unsuppressed_backup._$P$_of_400: Orphans ignored as thor::base::ock_p2::inc::20251203_2::monitoring_auto_unsuppressed_backup exists"

I am not sure why this is not working. Can someone please investigate? The thors in alpha prod are dangerously low on space and having files not being removed is not helping.

Steps to Reproduce

Expected Behavior

sasha should attempt to remove the file upon expiry

Actual Behavior

file is not removed

HPCC Systems Version

9.10.76

HPCC4J Module

wsclient - Web service clients for HPCC ESP services

HPCC4J Version

9.10.76

Java Version

java 11

Environment/Configuration

https://alpha_prod_thor_esp.risk.regn.net:18012/

Code Sample

Additional Context

No response

Pre-submission Checklist

• I have checked the Common Issues and Solutions wiki

[github-actions]

Thank you for reporting this critical bug and providing detailed environment information!

We appreciate your thorough description and log evidence. To help us investigate and resolve the issue, we need a bit more information from you.

📋 Action Required

1. Provide explicit, step-by-step reproduction instructions
   • List the exact steps you take to set file expiry and observe Sasha's behavior.
2. Share a minimal reproducible code sample
   • Include the Java code (even just connection/init) used to set expiry on logical files.
3. Confirm authentication method and OS/build tool
   • Specify if you use username/password or other authentication, and note your operating system and build tool.

ℹ️ How to Find This Information

Reproduction Steps

• Describe each action you perform, including any API calls or UI steps, from file creation to expiry.

Code Sample

• Copy the relevant Java code that sets file expiry, including connection setup and any options used.

Authentication & Environment

• Indicate your authentication method (e.g., username/password, none).
• State your operating system (e.g., Linux, Windows) and build tool (e.g., Maven, Gradle).

🔍 Related Resources

• Review Sasha configuration for expiry and orphan handling in the HPCC documentation.
• Check HPCC platform release notes and JIRA for similar issues.
• Enable verbose Sasha logging to capture file removal attempts.

⚠️ Important Notes

• HPCC4J 9.10.76 and HPCC Platform 9.10.76 are compatible with Java 11.
• No sensitive information detected; your environment details are appropriate.
• If you encounter Java-side errors, please include the full stack trace.

---

Please update your issue with the requested information. We'll review it again once you've provided these details.