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

Books are not stored in QuestDB but are displayed on TTY #233

Open
c0indev3l opened this issue Mar 19, 2024 · 1 comment
Open

Books are not stored in QuestDB but are displayed on TTY #233

c0indev3l opened this issue Mar 19, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@c0indev3l
Copy link
Contributor

Hello,

I'm using a Docker Compose file like so

version: "3.3"
services:
  cs2questdb_book:
    image: ghcr.io/bmoscon/cryptostore:latest
    container_name: cs2questdb_book
    environment:
      - EXCHANGE=BINANCE
      - SYMBOLS=BTC-USDT,ETH-USDT,BNB-USDT,SOL-USDT,ADA-USDT
      - CHANNELS=l2_book
      - BACKEND=QUEST # TTY
      - HOST=${HOST}
      - PORT=${PORT}
    restart: unless-stopped
    networks:
      - web

networks:
  web:
    external: true

When I set backend to TTY I see

cs2questdb_book  | 2024-03-19 21:15:51 - exchange: BINANCE symbol: ADA-USDT book: <order_book.OrderBook object at 0x7f271e4ea870> timestamp: 1710882951.471

but when I set BACKEND to QUEST, book are not stored into book-BINANCE table.

On the other side, when I set

CHANNELS=candles,trades,ticker

these data are correctly stored into database.

I've no idea why it's not working for L2 book.

I entered into container but feedhandler.log is empty.

Any idea how to overcome that?

Thanks for your project

@c0indev3l c0indev3l added the bug Something isn't working label Mar 19, 2024
@c0indev3l c0indev3l changed the title Book are not stored in QuestDB but are displayed on TTY Books are not stored in QuestDB but are displayed on TTY Mar 19, 2024
@c0indev3l
Copy link
Contributor Author

The problem seems to only occur when book-BINANCE table ever exist.

After dropping it, it works... maybe some more tests are required

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant