HPE 3PAR: SSH Connection rejected - max number of connections reached
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Medium
|
Raghavendra Tilay |
Bug Description
1. CUSTOMER IMPACT:
Limit on SSH connections to 3PAR array is preventing additional connections.
2. DETAILS:
From grepping the cinder logs – customer can see 128 times (over the last week or so) that;
the number of requests to create/delete a volume was greater than 24 requests
per minute with values as high as 110 requests per minute.
As per our understanding, 24 is the maximum number of SSH connections for this model of 3PAR.
3. ROOT CAUSE:
It seems that the hpe3parclient code is creating a new SSH/HTTP session for each request;
instead of creating and reusing sessions.
4. LOGS:
From cinder-volume log:
2021-03-22 10:20:45.703 34 ERROR oslo_messaging.
Logs from backend i.e 3PAR event logs
rhaimi@
2021-03-01 14:08:05.83 GMT 3 20109349 Alert Major Rejecting SSH Connection from IP sw_auth_helper General SSH connection from 10.232.137.10 was rejected because SSH connections have been exhausted for this IP address.
5. SOLUTION:
[a] Instead of creating new session for each operation (eg. create/delete volume),
try to reuse existing session for as many operations as possible.
[b] Since WSAPI of 3PAR has evolved, use wsapi (http/https) requests and
get rid of SSH connections/
Changed in cinder: | |
assignee: | nobody → Raghavendra Tilay (raghavendrat) |
Changed in cinder: | |
importance: | Undecided → Medium |
tags: | added: 3par hpe https requests ssh wsapi |
Fix proposed to branch: master /review. opendev. org/c/openstack /cinder/ +/804698
Review: https:/