PineconeApiException: (429) Reason: Too Many Requests

i am trying to test my api using curl command Invoke-RestMethod -Uri "http://localhost:5000/embed-and-store" -Method Post -Headers @{"Content-Type"="application/json"} -Body '{"url":"https://www.forbes.com/sites/jodiecook/2024/01/02/5-chatgpt-prompts-to-land-a-higher-paying-job-in-2024/?sh=5b527622170fe"}' and i am getting 429 error.

can someone help how i can resolve this?

Hi @vinayakgavariya123.

I suspect you’re running into the request limit mentioned in our Serverless index limitations doc:

During the public preview period, requests are limited to 1000 read units/second, 50,000 write units/second, and 2.5 fetch and describe_index_stats operations/second.strong text

Based on what you’re trying to do, does that limitation make sense? If not, can you provide the name of your index?

i am just exploring the pinecone for now, but getting this error while creating the index.

i think “too many requests” error is coming before creating the index.

and due to which i am not able to create the index.

( it’s just my assumption, i might be wrong here)

I’m facing the same problem.

from pinecone import Pinecone, ServerlessSpec
pc = Pinecone(api_key=‘myapikey’)
pc.create_index(
name=“quickstart-1”,
dimension=8,
metric=“euclidean”,
spec=ServerlessSpec(
cloud=‘aws’,
region=‘us-west-2’
)
)
index = pc.Index(“quickstart-1”)
print(pc.list_indexes())

It throws this error at me,
pinecone.core.client.exceptions.PineconeApiException: (429)
Reason: Too Many Requests

But this code successfully creates an index in starter plan,

pc.create_index(
name=“pod-index”,
dimension=1536,
metric=“cosine”,
spec=PodSpec(
environment=“gcp-starter”
)
)

@vinayakgavariya123, @pream, you can have a max of 20 serverless indexes in a single project. I wonder if this is what you’re running into. Can you please check the number of serverless indexes in the projects where you are trying to create new serverless indexes?

For future reference, our docs now offers some suggested workarounds for this issue.

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.