2014-02-03-solving-the-hue-2-x-hanging-problem.md 2.3 KB


title: Solving the Hue 2.X hanging problem author: admin type: post date: 2014-02-03T17:25:00+00:00 url: /solving-the-hue-2-x-hanging-problem/ tumblr_gethue_permalink:

  • http://gethue.tumblr.com/post/75493515493/solving-the-hue-2-x-hanging-problem tumblr_gethue_id:
  • 75493515493 sf_thumbnail_type:
  • none sf_thumbnail_link_type:
  • link_to_post sf_detail_type:
  • none sf_page_title:
  • 1 sf_page_title_style:
  • standard sf_no_breadcrumbs:
  • 1 sf_page_title_bg:
  • none sf_page_title_text_style:
  • light sf_background_image_size:
  • cover sf_social_sharing:
  • 1 sf_sidebar_config:
  • left-sidebar sf_left_sidebar:
  • Sidebar-2 sf_right_sidebar:
  • Sidebar-1 sf_caption_position:
  • caption-right slide_template:
  • default categories:
  • Administration
  • Querying

In the Hue versions before 3, Hue is sometimes getting slow and “stuck”. To fix this problem, it is recommended to switch Hue to use the CherryPy server instead of Spawning. In the hue.ini or the Hue Safety Valve in CM, enter:

[desktop]

use_cherrypy_server = true

Cause:

Most of the time some timeout/Thrift errors can be seen in the Hue logs (/logs page). These errors are due to Beeswax crashing or being very slow and blocking all the requests as the Spawing Server is not perfectly greenified in Hue 2 (the unique Thread is blocked in the RPC IO call). This is fixed in CDH5 and improved in CDH4.5 by switching to HiveServer2.

CherryPy use 10 threads which is a good default. For more performance, 30 can be used.

Note: switching to CherryPy will disable the Shell Application but this one is replaced by the HBase Browser, Sqoop2 Editor and Pig Editor applications.