Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[DeepBookV3 Indexer] /summary endpoint consistently returns 502 error after 60s timeout #20778

Open
avernikoz opened this issue Jan 4, 2025 · 1 comment
Assignees
Labels

Comments

@avernikoz
Copy link

avernikoz commented Jan 4, 2025

Steps to Reproduce Issue

  1. Make a GET request to the DeepBook Indexer /summary endpoint:
bash
curl https://deepbook-indexer.mainnet.mystenlabs.com/summary
  1. Wait for response (typically around 60 seconds)

Expected Result

As per the DeepBookV3 Indexer documentation, the endpoint should return a JSON array containing summary objects for all trading pairs in DeepBook, with each object having the following structure:

json
{
"trading_pairs": "string",
"quote_currency": "string",
"last_price": float,
"lowest_price_24h": float,
"highest_bid": float,
"base_volume": float,
"price_change_percent_24h": float,
"quote_volume": float,
"lowest_ask": float,
"highest_price_24h": float,
"base_currency": "string"
}

Actual Result

The request consistently fails with a 502 Bad Gateway error after approximately 60 seconds of waiting. This makes it impossible to reliably fetch and cache trading pair summaries.

Error details:

  • HTTP Status: 502 Bad Gateway
  • Response time: ~60 seconds
  • Frequency: Almost every request

System Information

Additional Context

This endpoint is critical for applications that need to display trading pair information. While slow response times could be managed through caching, the consistent 502 errors make it impossible to implement reliable caching strategies. Other DeepBook Indexer endpoints appear to work as expected.

@leecchh
Copy link
Contributor

leecchh commented Jan 4, 2025

Steps to Reproduce Issue

  1. Make a GET request to the DeepBook Indexer /summary endpoint:

bash

curl https://deepbook-indexer.mainnet.mystenlabs.com/summary

  1. Wait for response (typically around 60 seconds)

Expected Result

As per the DeepBookV3 Indexer documentation, the endpoint should return a JSON array containing summary objects for all trading pairs in DeepBook, with each object having the following structure:


json

{

"trading_pairs": "string",

"quote_currency": "string",

"last_price": float,

"lowest_price_24h": float,

"highest_bid": float,

"base_volume": float,

"price_change_percent_24h": float,

"quote_volume": float,

"lowest_ask": float,

"highest_price_24h": float,

"base_currency": "string"

}

Actual Result

The request consistently fails with a 502 Bad Gateway error after approximately 60 seconds of waiting. This makes it impossible to reliably fetch and cache trading pair summaries.

Error details:

  • HTTP Status: 502 Bad Gateway

  • Response time: ~60 seconds

  • Frequency: Almost every request

System Information

Additional Context

This endpoint is critical for applications that need to display trading pair information. While slow response times could be managed through caching, the consistent 502 errors make it impossible to implement reliable caching strategies. Other DeepBook Indexer endpoints appear to work as expected.

Hey, we're aware of this issue and currently working on improving this endpoint, thanks for flagging

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants