Error 429 «Too Many Requests»

Archi
Kilo Expert

Hello, we have hi-load "Jakarta" instance on premice (many users, many transactions, ten nodes, big DB etc).
Last month one time in several days in business time we catched error 429 «Too Many Requests». After we reboot nodes and all became correct.


I checked DB and before error 429 saw there many "sleep" queries (>30-60 rows) with long run time, much longer that usually (20-400 seconds instead 1-10 seconds and 60 rows of queries instead 5 eg ). The impression is that DB cannot give answer to instance for first request and after this request`s queue is growth up.
I saw «sleeping» queries, queue in DB is growth up and then was error 429.

I read community materials about error 429 and thought about reasons of error. It was DB`s or instance`s side?
Hi-portal said it was incorrect DB`s work.
But I saw several symptoms as in Ankit K blog topic "Semaphore queue "leaking" due to RESTAPIProcessor exception» (https://community.servicenow.com/community?id=community_blog&sys_id=ba7d6269dbd0dbc01dcaf3231f9619f4)
Such big queue depth, Increasing session wait times.
Also I saw before error on system overview widget big growing of concurrency, DB connections.


Somebody had same cases.
How you found reasons of this error and repaeired?


Thanks.

1 REPLY 1

Harsh Vardhan
Giga Patron

Did you check the "User Administration >> All Active Transactions" module , did you find any background process which is still running there ? if yes kill it and validate it. 

 

You can also check the "slow Query" module here , 

 

https://docs.servicenow.com/bundle/newyork-platform-administration/page/administer/platform-performa...

If you are still facing the issue , connect with HI team.