メインコンテンツへスキップ

Tridentバックエンドがオフラインになり、コントローラポッドの再起動後に回復しない

  1. 最後の更新
  2. PDFとして保存
Views:
Visibility:
Public
Votes:
0
Category:
trident-kubernetes
Specialty:
snapx
Last Updated:

環境

  • Trident
  • Kubernetesクラスター

問題

Tridentバックエンドがオフラインになり、コントローラポッドの再起動後に回復しない

DNS サーバーが過負荷になりました。

Tridentが例外をログに記録：「Host lookup failed for ManagementLIF ... server misbehaving」、 

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.