Closed korydraughn closed 6 months ago
okay - so just an exception when it happens. no warning on startup.
so all we need more is a note in the README?
Added note to README.
looks good - surgical.
squash em.
Squashed w/o pound.
So a client connected to NFS will just see an 'I/O Error'... and the NFSRODS admin would see 'why' in the NFSRODS log.
Correct.
This PR originally logged a warning on server startup about the replica truncate API not being supported. That approach was dropped due to NFSRODS becoming unresponsive after attempting to invoke the replica truncate API on a 4.3.1 server.
I've updated the code to check if replica truncate is supported before attempting to invoke it. If the API is not supported, an exception will be thrown. Throwing an exception is important because it lets the user know things didn't work. This approach also allows NFSRODS to remain compatible with earlier versions of iRODS.
The first commit contains the original work. Those changes will be reverted following the squash.