You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
recently, the waggle-dance is blocekd when inlitialize CloseableThriftHiveMetastoreIfaceClientFactory.java new instance, then the serve cannot be used. these is jstack
defaultMetaStoreClientFactory
.newInstance(confFactory.newInstance(), "waggledance-" + name, DEFAULT_CLIENT_FACTORY_RECONNECTION_RETRY,
connectionTimeout);
why should use confFactory.newInstance() rather than use hiveConf in the paramter, becasue confFactory.newInstance() will synchronized(HiveConf.class), all the requets can be blocked there
The text was updated successfully, but these errors were encountered:
Hey @chenwyi2, could you add more details of your use case? Which is the input configuration that you set in Waggledance? Does this occur when Waggledance is trying to map databases in parallel?
I didn't see this error before, and we are running multiple instances of Waggledance with different configurations. I would like to know what is different in your use case. Also I'm open to code suggestions :)
recently, the waggle-dance is blocekd when inlitialize CloseableThriftHiveMetastoreIfaceClientFactory.java new instance, then the serve cannot be used. these is jstack
defaultMetaStoreClientFactory
.newInstance(confFactory.newInstance(), "waggledance-" + name, DEFAULT_CLIENT_FACTORY_RECONNECTION_RETRY,
connectionTimeout);
why should use confFactory.newInstance() rather than use hiveConf in the paramter, becasue confFactory.newInstance() will synchronized(HiveConf.class), all the requets can be blocked there
The text was updated successfully, but these errors were encountered: