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

ONTAP Tools for VMware vSphere:多数のONTAPクォータが原因でOTV検出が失敗する

Views:
6
Visibility:
Public
Votes:
0
Category:
virtual-storage-console-for-vmware-vsphere<a>2009953950</a>
Specialty:
virt
Last Updated:

環境

  • VMware vSphere(OTV)向けONTAPツール
  • ONTAP 9

問題

ONTAPに多数のクォータがあると、OTV検出がタイムアウトします。

OTVのvsc.logにも同様のエラーが表示されます。

finished loading : [svms] [2024-04-10T15:40:49,727Z] [Controllercluster1] [ INFO] [192.168.0.36 - cluster1] Updated the task progress to 96% [2024-04-10T15:40:49,733Z] [Controllercluster1] [ INFO] [192.168.0.36 - cluster1] Updated the task progress to 96% [2024-04-10T15:40:49,740Z] [Controllercluster1] [ INFO] [192.168.0.36 - cluster1] Updated the task progress to 100%
[2024-04-10T15:40:49,746Z] [Controllercluster1] [DEBUG] [192.168.0.36 - cluster1] Successfully set the task to success
[2024-04-10T15:40:49,749Z] [Controllercluster1] [ INFO] [192.168.0.36 - cluster1] Updated the task progress to 100%
[2024-04-10T15:40:49,755Z] [Controllercluster1] [DEBUG] [192.168.0.36 - cluster1] Successfully set the task to success
[2024-04-10T15:40:49,756Z] [Controllercluster1] [DEBUG] CachingControllerProxy.create exit.
[2024-04-10T15:40:49,756Z] [Controllercluster1] [DEBUG] addConnection: add controller end
[2024-04-10T15:40:49,756Z] [Controllercluster1] [ERROR] addConnection: timedout - Lock duration and processing addController went beyond 45000
[2024-04-10T15:40:49,756Z] [Controllercluster1] [ERROR] discoverWithAeonFlux: discovery failed with exception. java.util.concurrent.TimeoutException: Excesive lock duration and processing addController: 190689 at com.netapp.offtap3.factories.ControllerFactory.addConnection(ControllerFactory.java:168) ~[aeonflux.jar:?]
at com.netapp.vscv.server.controller.VscControllers.addController(VscControllers.java:490) ~[classes/:?] at com.netapp.vscv.server.controller.VscControllers.discoverController(VscControllers.java:310) ~[classes/:?] at com.netapp.vscv.server.ControllerDiscoverer.discover(ControllerDiscoverer.java:185) [classes/:?] at com.netapp.vscv.server.ControllerDiscoverer.call(ControllerDiscoverer.java:154) [classes/:?] at com.netapp.vscv.server.ControllerDiscoverer.call(ControllerDiscoverer.java:40) [classes/:?] at java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?] at java.lang.Thread.run(Thread.java:835) [?:?] [2024-04-10T15:40:49,757Z] [Controllercluster1] [DEBUG] Discovery finished for controller cluster1 [2024-04-10T15:40:49,761Z] [controllerPersistencePool-1-thread-1] [DEBUG] Did not refresh the following resources on object "AbstractController: id: b8170700-c0a0-11e7-8475-00a098afcdc1name: cluster1_vidsecip address: 192.168.0.36" because they do not appear to be loaded: [svm_peers] [2024-04-10T15:40:49,761Z] [controllerPersistencePool-1-thread-1] [DEBUG] AbstractController: id: b8170700-c0a0-11e7-8475-00a098afcdc1name: cluster1_vidsecip address: 192.168.0.36 is going to start loading: [svm_peers]

クラスタ検出に約2分半かかり、timeoutのデフォルト値(i、e timeout.controller.connection)は45秒であるため、タイムアウトが発生しています。

 

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.