You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Yohei Abe (JIRA)" <ji...@apache.org> on 2016/01/04 23:18:39 UTC
[jira] [Commented] (HIVE-9820) LLAP: Use a share-nothing scoreboard
/status implementation
[ https://issues.apache.org/jira/browse/HIVE-9820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15081913#comment-15081913 ]
Yohei Abe commented on HIVE-9820:
---------------------------------
Hi Gopal
Would you tell me what kind of information should be shown by /status ?
I found ReflectionUtils::printThreadInfo(), it looks to be used for this purpose.
Can I use this or should I make another function to get thread info?
> LLAP: Use a share-nothing scoreboard /status implementation
> -----------------------------------------------------------
>
> Key: HIVE-9820
> URL: https://issues.apache.org/jira/browse/HIVE-9820
> Project: Hive
> Issue Type: Sub-task
> Components: llap
> Affects Versions: llap
> Reporter: Gopal V
> Assignee: Yohei Abe
>
> To prevent thread-conflicts in executor information, the Apache HTTP servers use a share-nothing data structure known as a scoreboard.
> This is read by various systems like mod_status to read out the current state of executors available for PHP (and similar mod_* engines).
> The /status output is traditionally periodically read by the load-balancers to route requests away from busy machines.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)