Jakov Varenina created GEODE-7989:
-------------------------------------
Summary: Improve logging of exceptions that happen during
execution of backup
Key: GEODE-7989
URL: https://issues.apache.org/jira/browse/GEODE-7989
Project: Geode
Issue Type: Improvement
Reporter: Jakov Varenina
When backup is executed on server and fails due to exception e.g. "IOException:
Not enough space left on device" then this exception (feedback) is not
propagated to the client. Client will be able to tell that something is wrong
because disk-stores will be reported as offline. But it will not have
indication what caused backup to fail since Exception is not logged on server
when using log level less than debug (config, warn, ...). It would be good to
have at least have better logging for following cases:
1. Disk where oplogs are saved is to small for new oplog created by Geode
backup procedure. This step is executed in Geode backup phase
startDiskStoreBackup . If there is no enough space left on device, Geode will
log that exception in DEBUG log as described in previous comments. We would
like to have this logged in info or warning log level.
2. There is no enough space on disk where oplogs are copied for backup (this
doesn't need to be the same disk as mentioned before, and it is not same disk
for our case). This step in Geode is called completeBackup, and it doesn't log
even debug log if problem appears, but disk stores are reported as offline
(DiskBackupStatus.getOfflineDiskStores()).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
