This repository has been archived by the owner on Sep 27, 2022. It is now read-only.
Error Handshake status 429 Too Many Requests running more than 10 workers that connect to node hawking.
#16
Labels
Comments
|
Can not proceed after that bug. Connection with one worker give same "Too Many Requests" 1537824124.631129 - INFO - __init__ - Start processing of scenario file "loop_scenario.json".
1537824125.316673 - WARNING - connect - Handshake status 429 Too Many Requests
1537824125.534600 - WARNING - connect - Handshake status 429 Too Many RequestsNo stray python processes. denis@denis-HP-625:~/p/bitshares-stress-test$ ps aux | grep python
root 5009 0.0 0.2 177632 17076 ? Ssl сен24 0:00 /usr/bin/python3 /usr/bin/networkd-dispatcher --run-startup-triggers
denis 8169 0.0 0.0 21536 1104 pts/2 S+ 00:25 0:00 grep --color=auto python
denis 11186 0.1 0.5 758076 42252 tty1 Sl+ сен24 0:17 python3 /usr/bin/yandex-disk-indicator
denis 30147 1.9 2.9 2479708 230308 tty1 Sl+ сен24 0:58 /usr/bin/python3 /usr/lib/python3/dist-packages/eric6/eric6.py
denis 30158 0.0 0.2 48044 16912 tty1 S+ сен24 0:00 /usr/bin/python3 /usr/lib/python3/dist-packages/eric6/Utilities/BackgroundClient.py 127.0.0.1 41381 0Running scenario {
"scenarios": [
{
"node": "ws://hawking.array.io:8090",
"cycles": 1000,
"workers": 1,
"time_limit": 20,
"stages": [
{
"method": "get_block",
"params": {
"block_num": 8
}
},
{
"method": "get_transaction",
"params": {
"block_num": 8,
"trx_in_block": 0
}
},
{
"method": "get_chain_properties"
},
{
"method": "get_global_properties"
},
{
"method": "get_config"
},
{
"method": "get_chain_id"
},
{
"method": "get_dynamic_global_properties"
},
{
"method": "get_accounts",
"params": {
"account_ids": [
"1.2.0",
"1.2.1"
]
}
}
]
}
]
} |
denis-trofimov
changed the title
|
https://httpstatuses.com/429 The response representations SHOULD include details explaining the condition, and MAY include a Retry-After header indicating how long to wait before making a new request. |
|
Googling I got https://stackoverflow.com/questions/22786068/how-to-avoid-http-error-429-too-many-requests-python |
denis-trofimov
changed the title
hawking.
denis-trofimov
added a commit
that referenced
this issue
Sep 25, 2018
denis-trofimov
changed the title
hawking.hawking.
|
confirm http 1.1 promotion to websocket tcpkali -T 1 -vvv -c1 --channel-lifetime=0.1 -r1 --ws -m '{"method": "call", "params": [1, "login", ["", ""]], "id": 2}' hawking.array.io:8090
WARNING: Dumb terminal, expect unglorified output.
Destination: [104.155.104.137]:8090
Interface enp0s31f6 address [192.168.0.212]:0
Using interface enp0s31f6 to connect to [104.155.104.137]:8090
Connection [192.168.0.212]:44615 -> [104.155.104.137]:8090 opened as 12
Ramped up to 1 connections.
Connection [192.168.0.212]:47565 -> [104.155.104.137]:8090 opened as 12
Connection [192.168.0.212]:38487 -> [104.155.104.137]:8090 opened as 12
Connection [192.168.0.212]:35613 -> [104.155.104.137]:8090 opened as 12
Connection [192.168.0.212]:43897 -> [104.155.104.137]:8090 opened as 12
Connection [192.168.0.212]:55587 -> [104.155.104.137]:8090 opened as 12
Connection [192.168.0.212]:59747 -> [104.155.104.137]:8090 opened as 12
Connection [192.168.0.212]:39317 -> [104.155.104.137]:8090 opened as 12
Connection [192.168.0.212]:33967 -> [104.155.104.137]:8090 opened as 12
Connection [192.168.0.212]:55549 -> [104.155.104.137]:8090 opened as 12
Connection [192.168.0.212]:47855 -> [104.155.104.137]:8090 opened as 12
Exiting worker 0
0↓, 0↑ open connections (0 connecting)
11 connections_counter
↳ 11 connections_initiated
↳ 0 connections_accepted
0 connection_failures
↳ 0 connection_timeouts
1600 worker_data_sent
1600 worker_data_rcvd
10 worker_num_writes
10 worker_num_reads
Last received bytes (160): [HTTP/1.1 101 Switching Protocols\r\n
Connection: upgrade\r\n
Sec-WebSocket-Accept: HSmrc0sMlYUkAGmm5OPpG2HaGWk=\r\n
Server: WebSocket++/0.8.0-dev\r\n
Upgrade: websocket\r\n
\r\n]
Total data sent: 1600 bytes (1600 bytes)
Total data received: 1600 bytes (1600 bytes)
Bandwidth per channel: 0.025⇅ Mbps (3.2 kBps)
Aggregate bandwidth: 0.013↓, 0.013↑ Mbps
Packet rate estimate: 10.0↓, 10.0↑ (1↓, 1↑ TCP MSS/op)
Test duration: 1.00479 s. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Upon doing read operations by means of python-bitshares client-side library for the BitShares Blockchain based on graphenelib on "low level" in the websocket module got "websocket._exceptions.WebSocketBadStatusException: Handshake status 429 Too Many Requests".
During my stress-test I launch 50 workers that connect to node": "ws://hawking.array.io:8090", each one worker performs read operation and got it result, and start over with new connection.
It looks like a server-side connection denial counter flood mechanism. As referenced 429 TOO MANY REQUESTS:
Log
Using
{ "scenarios": [ { "node": "ws://hawking.array.io:8090", "cycles": 1000, "workers": 50, "time_limit": 20, "stages": [ { "method": "get_block", "params": { "block_num": 8 } }, { "method": "get_transaction", "params": { "block_num": 8, "trx_in_block": 0 } }, { "method": "get_chain_properties" }, { "method": "get_global_properties" }, { "method": "get_config" }, { "method": "get_chain_id" }, { "method": "get_dynamic_global_properties" }, { "method": "get_accounts", "params": { "account_ids": [ "1.2.0", "1.2.1" ] } } ] } ] }Got error
The text was updated successfully, but these errors were encountered: