[LONGEVITY BUG] When each peer is running on the only one CPU machine Then iroha throw the error "Failed to push into queue. Queue is full."

[AlexStroke]

OS and Environment

• Ubuntu
• Docker Hub
• 1 CPU per one peer
• s1.stg1.iroha2.iroha.tech

GIT commit hash

52dc18c

Minimum working example / Steps to reproduce

0. Create a stand where each peer are running on the only one CPU machine, run longevity script and wait. (It is all running now on the longevity stands s1-s5: s1.stg1.iroha2.iroha.tech Just connect to them)
1. Send any transaction to the peer http://s1.stg1.iroha2.iroha.tech:8080

Actual result

   0: Failed to create domain
   1: Failed to submit transaction SignedTransaction { payload: Payload { account_id: Id { name: "alice", domain_id: Id { name: "wonderland" } }, instructions: Instructions([Register(RegisterBox { object: EvaluatesTo { expression: Raw(Identifiable(NewDomain(NewDomain { id: Id { name: "ass" }, logo: None, metadata: Metadata { map: {} } }))), _value_type: PhantomData } })]), creation_time: 1669117903206, time_to_live_ms: 100000, nonce: None, metadata: {} }, signatures: {iroha_crypto::signature::SignatureOf<iroha_data_model::transaction::Payload>({ pub_key: ed01207233bfc89dcbd68c19fde6ce6158225298ec1131b6a130d1aeb454c1ab5183c0, payload: DB8116524206673896EEADFECC84C3A664E31F525612ACF6D2D7D4FD7EED4B5662248073935374C8F12A76233EA287F47DCF90B4EF9548A28E4A7D1CAB190A0A })} }
   2: Unexpected transaction response; status: 500 Internal Server Error; response body: Error:
          0: Failed to push into queue    1: Queue is full

Expected result

Successful transaction

Logs in JSON format

Log contents

2022-11-22T13:41:26.200040Z  WARN request{method=POST path=/transaction version=HTTP/1.1 remote.addr=139.178.89.153:56486}: iroha::torii::routing: Failed to push into queue error=Queue is full
2022-11-22T13:41:26.200119Z  INFO request{method=POST path=/transaction version=HTTP/1.1 remote.addr=139.178.89.153:56486}: warp::filters::trace: finished processing with success status=500
2022-11-22T13:41:26.200300Z ERROR iroha::torii::routing: Failure during subscription error=Stream error: Iroha version error: Parity SCALE (de)serialization issue
2022-11-22T13:41:34.402620Z  INFO request{method=GET path=/status version=HTTP/1.1 remote.addr=127.0.0.1:56724}: warp::filters::trace: processing request
2022-11-22T13:41:34.402642Z  INFO request{method=GET path=/status version=HTTP/1.1 remote.addr=127.0.0.1:56724}: warp::filters::trace: finished processing with success status=200
2022-11-22T13:42:26.700250Z  INFO request{method=GET path=/events version=HTTP/1.1 remote.addr=139.178.89.153:56490}: warp::filters::trace: processing request
2022-11-22T13:42:26.700250Z  INFO request{method=POST path=/transaction version=HTTP/1.1 remote.addr=139.178.89.153:56488}: warp::filters::trace: processing request
2022-11-22T13:42:26.700454Z  INFO request{method=GET path=/events version=HTTP/1.1 remote.addr=139.178.89.153:56490}: warp::filters::trace: finished processing with success status=101
2022-11-22T13:42:26.700940Z  WARN request{method=POST path=/transaction version=HTTP/1.1 remote.addr=139.178.89.153:56488}: iroha::torii::routing: Failed to push into queue error=Queue is full
2022-11-22T13:42:26.701018Z  INFO request{method=POST path=/transaction version=HTTP/1.1 remote.addr=139.178.89.153:56488}: warp::filters::trace: finished processing with success status=500
2022-11-22T13:42:26.701070Z ERROR iroha::torii::routing: Failure during subscription error=Stream error: Iroha version error: Parity SCALE (de)serialization issue

Who can help to reproduce?

@astrokov7

Notes

No response