# ERROR piecestore upload rejected, too many requests **URL:** \ **Category:** troubleshooting\ **Created:** [September 18, 2019, 7:07am UTC](https://forum.storj.io/t/error-piecestore-upload-rejected-too-many-requests/1749 "2019-09-18T07:07:28Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![BrightSilence](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/brightsilence/32/6048_2.png) [@BrightSilence](https://forum.storj.io/u/BrightSilence)\ **Post date:** [September 18, 2019, 4:07pm UTC](https://forum.storj.io/t/error-piecestore-upload-rejected-too-many-requests/1749/5 "2019-09-18T16:07:19Z")
Wow, I’ve never seen anyone actually reach thresholds that high. That’s not a good thing, your node is clearly not able to handle those requests as fast as they come in. You’re most likely also failing almost all uploads and a good chunk of downloads. This is exactly why this concurrency limit exists. To make sure your hardware isn’t overloaded. I created a post a while ago outlining how to find your perfect value. In your case there may even be a benefit of lowering it below the default. > [@Should I change max-concurrent-requests? \>\> Note: The implementation has changed. You shouldn't use this setting any longer. Leave it commented out](https://forum.storj.io/t/should-i-change-max-concurrent-requests-error-piecestore-upload-rejected-too-many-requests/845): > > There is not one answer for everyone. If you have low powered hardware, you probably shouldn’t. In worst cases you might want to lower it. But if your hardware is fast and your connection is as well, it could be beneficial to raise this number. How do I change the setting? # Maximum number of simultaneous transfers storage2.max-concurrent-requests: 7 Add these lines at the end of the config.yaml and play with the number a bit. You have to stop the node, make the change, then start the node ag… --- _[View the full topic](https://forum.storj.io/t/error-piecestore-upload-rejected-too-many-requests/1749)._