14,983
edits
Troubleshooting of Google Vertex AI Search: Difference between revisions
Jump to navigation
Jump to search
Troubleshooting of Google Vertex AI Search (edit)
Revision as of 23:24, 28 April 2025
, 28 April 2025→Troubleshooting: "Requested Entity Already Exists" Error When Saving Data Stores
(+ Troubleshooting: "Requested Entity Already Exists" Error When Saving Data Stores) |
|||
| Line 89: | Line 89: | ||
'''Solution:''' | '''Solution:''' | ||
Simply remove one of the patterns to resolve the issue. It's recommended to keep the broader pattern <code>''.example.com/''</code> as it already includes <code>example.com</code>. | Simply remove one of the patterns to resolve the issue. It's recommended to keep the broader pattern <code>''.example.com/''</code> as it already includes <code>example.com</code>. | ||
=== Troubleshooting: "Quota exceeded for Search lite requests" Error in Discovery Engine === | |||
'''Issue Description''': | |||
When using Discovery Engine API to retrieve search results, the following error occurs: | |||
<pre> | |||
{ | |||
"error" : { | |||
"code" : 429, | |||
"message" : "Quota exceeded for quota metric 'Search lite requests' and limit 'Search lite requests per minute' of service 'discoveryengine.googleapis.com' for consumer 'project_number:XXX'.", | |||
"status" : "RESOURCE_EXHAUSTED", | |||
... | |||
} | |||
} | |||
</pre> | |||
'''Root cause:''' | |||
The metadata in the error response has indicated that the quota value is 100 requests per minute | |||
'''Resolution Steps''': Resolve API Quota Limit Exceedance | |||
Option 1: Increase the delay time between requests | |||
# Add a 1-second pause between each request to stay within rate limits | |||
# Implement this timing delay in your code to prevent 429 errors | |||
# Adjust the delay time as needed based on your quota and request patterns | |||
Option 2: Increase quota limit | |||
# Go to the Quotas page in Google Cloud Console and find "Search lite requests per minute" | |||
# Select the relevant quota, click "EDIT QUOTAS", and submit a request for a higher limit | |||
# Wait for Google Cloud Support to review and approve | |||
Option 3: Implement exponential backoff retry mechanism | |||
# Detect HTTP 429 errors in your application and set an initial delay (e.g., 1 second) | |||
# Increase the delay time with each failed retry (e.g., 2 seconds, 4 seconds, 8 seconds, etc.) | |||
# Continue retrying until the request succeeds or maximum retry count is reached | |||
== Related Pages == | == Related Pages == | ||