ALM-43028 JDBCServer Session Overflow
This section applies only to MRS 3.3.1 or later.
Alarm Description
This alarm is generated when the JDBCServer process forwards requests and triffic control is triggered due to insufficient session resources. In this case, too many requests are sent to the JDBCServer process, exceeding the processing capability of the JDBCServer process.
Alarm Attributes
Alarm ID |
Alarm Severity |
Auto Cleared |
---|---|---|
43028 |
Minor (default threshold: 9 for three consecutive times) Critical (default threshold: 12 for three consecutive times) |
No |
Alarm Parameters
Type |
Parameter |
Description |
---|---|---|
Location Information |
Source |
Specifies the cluster for which the alarm was generated. |
ServiceName |
Specifies the service for which the alarm was generated. |
|
RoleName |
Specifies the role for which the alarm was generated. |
|
HostName |
Specifies the host for which the alarm was generated. |
|
Additional Information |
Trigger Condition |
Specifies the alarm triggering condition. |
Impact on the System
Requests that cannot be processed are responded with a failure message.
Possible Causes
The JDBCServer process on the node is overloaded.
Handling Procedure
Check the source of the requests for connecting to the JDBCServer service.
- On FusionInsight Manager, choose O&M > Alarm > Alarms and select the alarm whose ID is 43028. Check the role name and the IP address of the host where the alarm is generated in Location.
- On FusionInsight Manager, choose Cluster > Name of the desired cluster > Services > Spark > Instances, click the JDBCServer for which this alarm is generated, and click jdbcserver-audit in the Log column on the left.
- Click the download button in the lower left corner to download the logs to the local PC.
- Search for UserIP in the logs, collect statistics on the IP addresses of the clients that submit a large number of requests, and limit the traffic of these clients to reserve resources for other clients.
Collect fault information.
- On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
- Expand the Service drop-down list, and select Spark for the target cluster.
- Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
- Contact O&M engineers and provide the collected logs.
Alarm Clearance
This alarm needs to be cleared manually.
Related Information
None.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot