Task #11079
closed
DataMiner - Error in the alignment of dataminer service in the proto cluster
Added by Giancarlo Panichi about 7 years ago.
Updated about 7 years ago.
Infrastructure:
Production
Description
There is an error in the alignment of dataminer service in the proto cluster.
Above all, the dataminer0-proto and dataminer4-proto are not aligned correctly. It could also be a problem of concurrent access to svn.
- Priority changed from Normal to High
- Status changed from New to In Progress
I've found the problem. Working on the fix, then I'll explain what was happening.
- Status changed from In Progress to Feedback
- % Done changed from 0 to 100
Two events occurred:
- Sometimes the
svn update fails because of a write lock on the svn repository. This means that someone is running a commit on the repository and there's nothing that we can do on our side (we do not want doing anything, really). When the svn update fails, the script exits without releasing its own lock file. Not a big deal, but:
- The check that verifies that no other instance of the script is running failed in some situations. It was the case on dataminer0-proto and dataminer4-proto.
I just made that check more robust and installed it on all the production dataminer
- Due date set to Jan 31, 2018
- Status changed from Feedback to Closed
Now, it seems that it works correctly. I close the ticket.
Also available in: Atom
PDF
Updated by 
Updated by 
