Merge pull request #185132 from kcheeeung/kcfix

Correct Ambari hive view TSG

Author: v-shils

articles/hdinsight/interactive-query/interactive-query-troubleshoot-view-time-out.md

@@ -15,8 +15,22 @@ This article describes troubleshooting steps and possible resolutions for issues
 When running certain queries from the Apache Hive view, the following error may be encountered:
 
 ```
-result fetch timed out
+Result fetch timed out
+
 java.util.concurrent.TimeoutException: deadline passed
+    at akka.actor.dsl.Inbox$InboxActor$$anonfun$receive$1.applyOrElse(Inbox.scala:117)
+    at scala.PartialFunction$AndThen.applyOrElse(PartialFunction.scala:189)
+    at akka.actor.Actor$class.aroundReceive(Actor.scala:467)
+    at akka.actor.dsl.Inbox$InboxActor.aroundReceive(Inbox.scala:62)
+    at akka.actor.ActorCell.receiveMessage(ActorCell.scala:516)
+    at akka.actor.ActorCell.invoke(ActorCell.scala:487)
+    at akka.dispatch.Mailbox.processMailbox(Mailbox.scala:238)
+    at akka.dispatch.Mailbox.run(Mailbox.scala:220)
+    at akka.dispatch.ForkJoinExecutorConfigurator$AkkaForkJoinTask.exec(AbstractDispatcher.scala:397)
+    at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)
+    at scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339)
+    at scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)
+    at scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)
 ```
 
 ## Cause
@@ -31,7 +45,7 @@ The Hive View default timeout value may not be suitable for the query you are ru
   views.request.read.timeout.millis=300000
   views.ambari.hive.<HIVE_VIEW_INSTANCE_NAME>.result.fetch.timeout=300000
   ```
-  The value of `HIVE_VIEW_INSTANCE_NAME` is available at the end of the Hive View URL.
+  The value of `HIVE_VIEW_INSTANCE_NAME` is available by clicking YOUR_USERNAME > Manage Ambari > Views > Names column. Do not use the URL name.
 
 2. Restart the active Ambari server by running the following. If you get an error message saying it's not the active Ambari server, just ssh into the next headnode and repeat this step.
   ```