A significant part of sql server process memory has been paged out
問題現象:
Sqlserver 2014 alwayson架構主節點日誌依次報錯:
日期 2017/12/25 10:02:35
日誌 SQL Server (當前 - 2017/12/25 10:33:00)
源 spid33s
A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 840, committed (KB): 48081936, memory utilization: 0%.
日期 2017/12/25 10:02:35
日誌 SQL Server (當前 - 2017/12/25 10:33:00)
源 Server
The lease between availability group 'HKERP_AlwaysOn' and the Windows Server Failover Cluster has expired. A connectivity issue occurred between the instance of SQL Server and the Windows Server Failover Cluster. To determine whether the availability group is failing over correctly, check the corresponding availability group resource in the Windows Server Failover Cluster.
日期 2017/12/25 10:02:35
日誌 SQL Server (當前 - 2017/12/25 10:33:00)
源 Server
AlwaysOn: The local replica of availability group 'HKERP_AlwaysOn' is going offline because either the lease expired or lease renewal failed. This is an informational message only. No user action is required.
日期 2017/12/25 10:02:35
日誌 SQL Server (當前 - 2017/12/25 10:33:00)
源 Server
The state of the local availability replica in availability group 'HKERP_AlwaysOn' has changed from 'PRIMARY_NORMAL' to 'RESOLVING_NORMAL'. The state changed because the lease between the local availability replica and Windows Server Failover Clustering (WSFC) has expired. For more information, see the SQL Server error log, Windows Server Failover Clustering (WSFC) management console, or WSFC log.
記憶體的page out導致sqlserver的網路超時進而導致sqlserver cluster超時。
因為在10:02時候有Mcafee對伺服器的掃描,懷疑是mcafee的掃描導致的記憶體的page out。
進而導致了網路問題而引起sqlserver cluster的超時。
解決辦法:
對sqlserver的伺服器進行資料庫的記憶體鎖定。
修改組策略的“鎖定記憶體頁”
Sqlserver 2014 alwayson架構主節點日誌依次報錯:
日期 2017/12/25 10:02:35
日誌 SQL Server (當前 - 2017/12/25 10:33:00)
源 spid33s
A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 840, committed (KB): 48081936, memory utilization: 0%.
日期 2017/12/25 10:02:35
日誌 SQL Server (當前 - 2017/12/25 10:33:00)
源 Server
The lease between availability group 'HKERP_AlwaysOn' and the Windows Server Failover Cluster has expired. A connectivity issue occurred between the instance of SQL Server and the Windows Server Failover Cluster. To determine whether the availability group is failing over correctly, check the corresponding availability group resource in the Windows Server Failover Cluster.
日期 2017/12/25 10:02:35
日誌 SQL Server (當前 - 2017/12/25 10:33:00)
源 Server
AlwaysOn: The local replica of availability group 'HKERP_AlwaysOn' is going offline because either the lease expired or lease renewal failed. This is an informational message only. No user action is required.
日期 2017/12/25 10:02:35
日誌 SQL Server (當前 - 2017/12/25 10:33:00)
源 Server
The state of the local availability replica in availability group 'HKERP_AlwaysOn' has changed from 'PRIMARY_NORMAL' to 'RESOLVING_NORMAL'. The state changed because the lease between the local availability replica and Windows Server Failover Clustering (WSFC) has expired. For more information, see the SQL Server error log, Windows Server Failover Clustering (WSFC) management console, or WSFC log.
記憶體的page out導致sqlserver的網路超時進而導致sqlserver cluster超時。
因為在10:02時候有Mcafee對伺服器的掃描,懷疑是mcafee的掃描導致的記憶體的page out。
進而導致了網路問題而引起sqlserver cluster的超時。
解決辦法:
對sqlserver的伺服器進行資料庫的記憶體鎖定。
修改組策略的“鎖定記憶體頁”
設定鎖定記憶體頁,把sqlserver服務啟動賬號加入
後續觀察後,問題不再發生,解決。
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/22996654/viewspace-2149233/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- RuntimeError: An attempt has been made to start a new process before the current process hasError
- An out of memory error has occurred.Error
- Out of memory: Kill process 2249 (nginx) score 1 or sacrifice childNginx
- oracle LOGICAL standby ORA-04030: out of process memoryOracle
- ORACLE ORA-04030之 out of process memory when trying to allocateOracle
- Invalid configuration object webpack dev server has been initialisedObjectWebdevServer
- getOutputStream() has already been called
- OOM(Out Of Memory)OOM
- java out of memoryJava
- /dev/root filesystem full-unable to log into server-This thread has been closeddevServerthread
- Your account has been locked out. Please contact the system administrator for further assistance.
- ORA-04030: out of process memory ...(initSubHeap:qk...)的錯誤解決
- OOM--OUT OF MEMORYOOM
- PyTorch出現:RuntimeError: An attempt has been made to start a new process...報錯 (已解決)PyTorchError
- JIRA startup failed, JIRA has been locked.AI
- InnoDB Plugin has been upgraded to version 1.0.8Plugin
- ORA-06550 ,has been detected in fnd_global.initialize[fnd_init_sql].SQL
- Process object has no attribute '_popen'Object
- Oracle dedicated server process and shared server processOracleServer
- OOM(Out Of Memory)是什麼?OOM
- Uncaught SyntaxError: Identifier 'Geometry' has already been declaredErrorIDE
- An unexpected error has been detected by Java Runtime EnvironmentErrorJava
- 【HMS Core】ToolKit,Merchant Service has not been enabled yet
- Transaction rolled back because it has been marked as rollback-only
- AIX平臺下報ORA-04030: out of process memory when trying to allocate string bytesAI
- Thread 1: Fatal error: init(coder:) has not been implementedthreadError
- has been blocked by CORS policy跨域問題解決BloCCORS跨域
- java.lang.IllegalStateException: getOutputStream() has already been called for this responseJavaException
- ORA-04068: existing state of packages has been discardedPackage
- Caused by: java.lang.IllegalStateException: getWriter() has already been called for this responseJavaException
- FeignClientSpecification‘ could not be registered. A bean with that name has already been definedclientBean
- Out of sort memory, consider increasing server sort buffer size的兩種情況IDEServer
- 怎麼會出現 Cannot forward after response has been committed???ForwardMIT
- ES叢集搭建問題:memory locking requested for elasticsearch process but memory is not lockedElasticsearch
- note the ORA-27102: out of memory errorError
- 解決MYSQL工具mysqldump 遇到 Out of memory 方法MySql
- MySQL server has gone awayMySqlServerGo
- innobackupex:Error:xtrabackup child process has died at /usr/bin/innobackupexError