java . util . concurrent。TimeoutException: Futures timed out after [5 seconds]
scala.concurrent.impl.Promise DefaultPromise.ready美元(Promise.scala: 259)
scala.concurrent.impl.Promise DefaultPromise.result美元(Promise.scala: 263)
在scala.concurrent.Await。美元anonfun結果1美元(package.scala: 223)
在scala.concurrent.BlockContext DefaultBlockContext .blockOn美元(BlockContext.scala: 57)
scala.concurrent.Await .result美元(package.scala: 146)
com.databricks.backend.daemon.driver.JupyterDriverLocal RequestStatus.waitForReply美元(JupyterDriverLocal.scala: 210)
com.databricks.backend.daemon.driver.JupyterDriverLocal.repl (JupyterDriverLocal.scala: 972)
在com.databricks.backend.daemon.driver.DriverLocal。anonfun執行23美元美元(DriverLocal.scala: 728)
com.databricks.unity.UCSEphemeralState Handle.runWith美元(UCSEphemeralState.scala: 41)
com.databricks.unity.HandleImpl.runWith (UCSHandle.scala: 99)
com.databricks.backend.daemon.driver.DriverLocal。anonfun執行$ 20美元(DriverLocal.scala: 711)
在com.databricks.logging.UsageLogging。anonfun withAttributionContext美元1美元(UsageLogging.scala: 398)
scala.util.DynamicVariable.withValue (DynamicVariable.scala: 62)
com.databricks.logging.AttributionContext .withValue美元(AttributionContext.scala: 147)
com.databricks.logging.UsageLogging.withAttributionContext (UsageLogging.scala: 396)
在com.databricks.logging.UsageLogging.withAttributionContext (UsageLogging.scala: 393美元)
com.databricks.backend.daemon.driver.DriverLocal.withAttributionContext (DriverLocal.scala: 62)
com.databricks.logging.UsageLogging.withAttributionTags (UsageLogging.scala: 441)
在com.databricks.logging.UsageLogging.withAttributionTags (UsageLogging.scala: 426美元)
com.databricks.backend.daemon.driver.DriverLocal.withAttributionTags (DriverLocal.scala: 62)
com.databricks.backend.daemon.driver.DriverLocal.execute (DriverLocal.scala: 688)
在com.databricks.backend.daemon.driver.DriverWrapper。anonfun tryExecutingCommand美元1美元(DriverWrapper.scala: 622)
在美元scala.util.Try蘋果(Try.scala: 213)
com.databricks.backend.daemon.driver.DriverWrapper.tryExecutingCommand (DriverWrapper.scala: 614)
com.databricks.backend.daemon.driver.DriverWrapper.executeCommandAndGetError (DriverWrapper.scala: 533)
com.databricks.backend.daemon.driver.DriverWrapper.executeCommand (DriverWrapper.scala: 568)
com.databricks.backend.daemon.driver.DriverWrapper.runInnerLoop (DriverWrapper.scala: 438)
com.databricks.backend.daemon.driver.DriverWrapper.runInner (DriverWrapper.scala: 381)
com.databricks.backend.daemon.driver.DriverWrapper.run (DriverWrapper.scala: 232)
java.lang.Thread.run (Thread.java: 750)
我確實有相同的錯誤,但我沒有並行性,尤其是在筆記本上。其他的失敗是在隨後的筆記本並行運行。像下麵的
1 - - > 2、3、4、5 - - > 6 - > 7。這就是我的管道的樣子,2,3,4,5是並行運行的筆記本幾乎相似的代碼,但不同的數據集。但例外發生在6。我沒有多少運氣除了發現這個線程。令我驚奇的是,這個線程是很新的,我希望它不是DBR版本。我使用AWS磚11.3 LTS版啟用了光子的節點。我很高興提供任何其他有用的信息來解決這個問題。謝謝
嗨@sunil kancharlapalli,你還麵臨著同樣的問題?
嗨@Vidula Khanna錯誤依然存在。我試圖解決這個問題,但它依然存在。