... | ... | @@ -1562,15 +1562,15 @@ If the above didn't help, find out which "half" of the datapoint exists. |
|
|
|
|
|
2. The metadata exists, and the current value is missing
|
|
|
|
|
|
Define the following shell functions:
|
|
|
Define the following shell functions (note: not applicable to redis-clusters):
|
|
|
```
|
|
|
function oldb_ela_list { curl -s -X GET localhost:9200/configuration_instance/_search?q=data.uri.value:\"$1\" | jq -r '.hits.hits[]._id' | sort ; }
|
|
|
|
|
|
function oldb_ela_del { curl -s -X POST localhost:9200/configuration_instance/_delete_by_query?q=data.uri.value:\"$1\" | jq -r '.deleted' ; }
|
|
|
|
|
|
function oldb_red_list { redis-cli --scan --pattern *$1* ; }
|
|
|
function oldb_red_list { redis-cli --scan --pattern "*$1*" ; }
|
|
|
|
|
|
function oldb_red_del { redis-cli --scan --pattern *$1* | xargs redis-cli del ; }
|
|
|
function oldb_red_del { redis-cli --scan --pattern "*$1*" | xargs redis-cli del ; }
|
|
|
```
|
|
|
|
|
|
Then check if the problematic key is in the volatile store:
|
... | ... | |