The health test result for HIVESERVER2_SCM_HEALTH has become bad: This
role's process is starting. This role is supposed to be started.
 Time: May 1, 2015 11:08:59 AM

Speak of the devil.

Does anyone care to comment? Is this "just me" can anyone claim
moderate/heavy trouble free usage of hiveserver2. Because its nice to say
like the 'CLI is deprecated', but... In our setup with use hue -> thrift
and jdbc->thrift supporting maybe 10-30 users and a very recent release and
the stability is not there. It is hard for me to believe that anything we
are doing is causing this instability.

Like i said, I get around it by running a load balancer etc, but I do not
want to be 100% reliant on it.

On Thu, Apr 30, 2015 at 10:39 AM, Edward Capriolo <edlinuxg...@gmail.com>
wrote:

> For what it is worth, even with all the enhancements made to hive-server 2
> it is just not as reliable as the CLI. I am actually using cloudera 5.3 and
> we have multiple hive-server2 instances behind a load balancer. The load we
> are doing is not particularly heavy and the mean time to failure is < 3
> days. ClouderaManager even provides a feature "automatically restart
> hiveserver2" it is very prone to issues. Many times I have been at the
> point where I have considered writing queries to a file and then launching
> them from the CLI -f because the reliability of hiveserver2 is
> questionable. I am a serious -1 on removing the CLI because it just plan
> works better.
>
> On Thu, Apr 30, 2015 at 9:29 AM, Xuefu Zhang <xzh...@cloudera.com> wrote:
>
>> FYI. branch "beeline-cli" is created for the ongoing work in HIVE-10511.
>>
>> Thanks,
>> Xuefu
>>
>> On Mon, Apr 27, 2015 at 8:24 PM, Xuefu Zhang <xzh...@cloudera.com> wrote:
>>
>> > Hi all,
>> >
>> > I have created this JIRA per discussion in the "deprecating Hive CLI"
>> > thread. The task is non-trivial, for which I think it makes sense to
>> create
>> > a branch for the development to avoid inference with other ongoing work
>> on
>> > master. If there is no objection, I will create a branch in 24 hours.
>> >
>> > Thanks,
>> > Xuefu
>> >
>>
>
>

Reply via email to