[broker] Cursor status has always been SwitchingLedger and pendingMarkDeleteOps has accumulated tens of thousands of requests
See original GitHub issueDescribe the bug
The pendingMarkDeleteOps has accumulated tens of thousands of requests, and the cursor status has always been SwitchingLedger
, and the retention cannot be executed, resulting in the situation that the disk space cannot be reclaimed.
Screenshots
Issue Analytics
- State:
- Created a year ago
- Comments:19 (7 by maintainers)
Top Results From Across the Web
BookTrader
When this status is selected, use the Order control section to tell TWS how to handle multiple orders on the same side. Show...
Read more >Interactive Brokers Review - Investopedia
Interactive Brokers (IBKR) leads the list of the most comprehensive investment platforms. Clients can trade stocks, options, futures, forex, cryptocurrencies, ...
Read more >How to Use Hot Keys in Interactive Brokers - YouTube
www.ikbr.com/rltDid you know Interactive Brokers has hot keys? Let's go over these shortcuts and how to use them!This video was made by an ......
Read more >Placing Trade Orders on Interactive brokers Tutorial - YouTube
In this tutorial, I will show you how to place stock and options trade orders on the interactive brokers TWS and mobile platformStock ......
Read more >How to use BookTrader in TWS (Easy Order Placing) - YouTube
This video covers the BookTrader in the Trader Workstation platform by Interactive Brokers. It is one of the most useful tools in the ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@poorbarcode The stack of the three threads of this thread group is as follows:
@poorbarcode I took a look at some thread groups. Other thread groups are all 0. Only this one has a backlog of more than 7,000 tasks.