RedemptionC commented on pull request #2065:
URL: https://github.com/apache/apisix-dashboard/pull/2065#issuecomment-900875354


   > I think the response body should also contain detailed information about 
consistent data, including how much data is consistent for each resource. 
   
   @nic-chen 
   currently,when nothing is inconsistent,the response of this API and the 
ouput of the cache-verify is as follows:
   ```sh
   ❯ curl -s localhost:9000/apisix/admin/cache_verify -H "Authorization: $(curl 
-s  localhost:9000/apisix/admin/user/login -X POST -d 
'{"username":"admin","password":"admin"}'  | jq -r '.data | .token')" | jq
   {
     "code": 0,
     "message": "",
     "data": {
       "inconsistent_consumers": null,
       "inconsistent_routes": null,
       "inconsistent_services": null,
       "inconsistent_ssls": null,
       "inconsistent_upstreams": null,
       "inconsistent_scripts": null,
       "inconsistent_global_plugins": null,
       "inconsistent_plugin_configs": null,
       "inconsistent_server_infos": null
     },
     "request_id": "899e1ffb-0b74-4ecb-93ae-4c19f320b6b9"
   }
   
   ```
   ```sh
   ❯ go run main.go cache-verify 
   cache verification result as follows:
   
   ssls            :       all consistent
   routes          :       all consistent
   scripts         :       all consistent
   services        :       all consistent
   upstreams       :       all consistent
   consumers       :       all consistent
   server infos    :       all consistent
   global plugins  :       all consistent
   plugin configs  :       all consistent
   ```
   
   do you think that we should maintain some statistical data for each 
item,like:
   "there are 10 consumers in cache,4 of them are consistent,6 of them are 
inconsistent."
   and for each inconsistent item,we provide their content in both cache and 
etcd?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to