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

Increase transaction list size for /v1/txn endpoint #2921

Closed
adoyle51 opened this issue Apr 18, 2017 · 6 comments
Closed

Increase transaction list size for /v1/txn endpoint #2921

adoyle51 opened this issue Apr 18, 2017 · 6 comments
Labels
theme/api Relating to the HTTP API interface type/enhancement Proposed improvement or new feature

Comments

@adoyle51
Copy link

Because the /v1/txn endpoint has a limit of 64 transactions per request, transaction performance suffers when performing thousands of transactions at once. Much of the degredation appears to be due to waiting for HTTP responses from Consul when sending thousands of 64 operation transaction payloads.

I reached out to the mailing group with this message here, and it was stated that it would be possible to increase the txn transaction limit.

consul version for both Client and Server

Client: 0.8
Server: 0.8

Operating system and Environment details

CentOS7
AWS EC2 t2.large instances

Please let me know if there is any other information I should provide in this request.

@slackpad slackpad added the type/enhancement Proposed improvement or new feature label Apr 18, 2017
@slackpad slackpad added this to the 0.8.2 milestone Apr 18, 2017
@slackpad
Copy link
Contributor

We should do #2652 at the same time.

@slackpad slackpad removed this from the 0.8.2 milestone Apr 25, 2017
@slackpad slackpad added the theme/api Relating to the HTTP API interface label May 25, 2017
@tkrisko
Copy link

tkrisko commented May 16, 2018

I think the transaction size should be either unlimited or there should be a way
to bind subsequent transactions together so API client can commit or revoke them. Current approach with specified limit still forces API client to split operations into "smaller" chunks what requires the client has to implement own transactional approach.

@vaidik
Copy link

vaidik commented Jul 6, 2020

Did we make any progress on this? It looks like that the limit of 64 txns is still there and the only way to handle this is what @krzyszko has suggested

@danparisi
Copy link

I am also wondering if this feature will be implemented

@osher
Copy link

osher commented Aug 22, 2022

we need this too.
the idea of breaking a transaction that should be atomic to separate operations feels wrong...

@msiege2
Copy link
Contributor

msiege2 commented Sep 20, 2022

This issue has been implemented with #14599 and will be in the next major Consul release.

@msiege2 msiege2 closed this as completed Sep 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
theme/api Relating to the HTTP API interface type/enhancement Proposed improvement or new feature
Projects
None yet
Development

No branches or pull requests

7 participants