Closed scorphus closed 5 years ago
As a temporary solution to this issue, two hooks were introduced in the app.yml
file (check tsuru's deployment hooks for details):
hooks:
build:
# Temporary solution to clear the locks created by material
- redis-cli -h 10.11.165.8 -p 49153 DEL material-girl-domains_details-lock material-girl-violation_count_by_category_for_domains-lock material-girl-blacklist_domain_count-lock material-girl-most_common_violations-lock material-girl-failed_responses_count-lock
restart:
before:
# Temporary solution to clear the locks created by material
- redis-cli -h 10.11.165.8 -p 49153 DEL material-girl-domains_details-lock material-girl-violation_count_by_category_for_domains-lock material-girl-blacklist_domain_count-lock material-girl-most_common_violations-lock material-girl-failed_responses_count-lock
If purging all the locks solves the initial problem, move the solution to holmes-material
console and update the hooks accordingly.
Upon start, material girl doesn't refresh locked materials and, in many cases, these materials were left locked by some extinguished instance of material girl that was in an update process and was abruptly terminated. As it is more a business-related issue, this feature should be implemented in the
holmes-material
console.