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

Match Engine Order Placement query #28

Open
blockchain-app12 opened this issue Dec 16, 2021 · 0 comments
Open

Match Engine Order Placement query #28

blockchain-app12 opened this issue Dec 16, 2021 · 0 comments

Comments

@blockchain-app12
Copy link

I start all the servers in the Architecture as mentioned,

  • Zookeeper
  • Kafka
  • Go Engine
  • Redis
  • MySQL with BIN-LOG Config

I added pairs into the match engine, then I placed orders in the match engine.
In the scenario, I have faced sometimes order placement issue when matching, which can be seen in the MySQL status as - "new".
whenever the placed order as "new" that orders couldn't match or Engine couldn't considered that order to matching.Only the engine considered the open orders for matching.
In this type of scenario, I empty the records in all the servers then re-inject the pairs and orders in to the engine.
So kindly let me know, what are all the scenario's that placing orders considered as status as - "new".

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

No branches or pull requests

1 participant