Return-Path: 
 <user-return-434-apmail-bigtop-user-archive=bigtop.apache.org@bigtop.apache.org>
X-Original-To: apmail-bigtop-user-archive@www.apache.org
Delivered-To: apmail-bigtop-user-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id A08D610803
	for <apmail-bigtop-user-archive@www.apache.org>;
 Tue, 29 Oct 2013 22:49:25 +0000 (UTC)
Received: (qmail 33536 invoked by uid 500); 29 Oct 2013 22:49:25 -0000
Delivered-To: apmail-bigtop-user-archive@bigtop.apache.org
Received: (qmail 33467 invoked by uid 500); 29 Oct 2013 22:49:24 -0000
Mailing-List: contact user-help@bigtop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@bigtop.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@bigtop.apache.org>
List-Post: <mailto:user@bigtop.apache.org>
List-Id: <user.bigtop.apache.org>
Reply-To: user@bigtop.apache.org
Delivered-To: mailing list user@bigtop.apache.org
Received: (qmail 33293 invoked by uid 99); 29 Oct 2013 22:49:24 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Oct 2013 22:49:24 +0000
X-ASF-Spam-Status: No, hits=-0.7 required=5.0
	tests=RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of shaposhnik@gmail.com
 designates 209.85.219.48 as permitted sender)
Received: from [209.85.219.48] (HELO mail-oa0-f48.google.com) (209.85.219.48)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Oct 2013 22:49:20 +0000
Received: by mail-oa0-f48.google.com with SMTP id m17so655415oag.35
        for <multiple recipients>; Tue, 29 Oct 2013 15:49:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:sender:in-reply-to:references:date:message-id:subject
         :from:to:cc:content-type:content-transfer-encoding;
        bh=iioutvPGOc70TIaKIqkarzEdwvbORtbbgBKglsuMXhI=;
        b=mgIyPgUHaRqPPLwKu8iXxyzQ3tBpmkuzPawwaWV0GplRLbq90MFTDjNojJsvbEWK3X
         96I1MfJbOgynwx3xMS3E4sieBplf0CkspW6SUOyOhPOSw9YVVbAatn8Cz01NwHB2o6Gm
         pVl24lPzsB99qVnhUfDUmRvn2tpMxgKEjw9LFuDYVHMelHIwEET9onuITC6x5aRLMkBx
         cx/QjbP982NEIRxD+n/FwNl3tKciamj9n5dQ4prCOWQF1uN++Qja3TXl6CzeSblLxZxV
         8Q9tYqG+9Dl+HQSwmFcuVwmHUMSp5OGJbHN1Qny6KeDQSrxUEVXzUgKfLhTZKqxwgD0O
         EdRw==
MIME-Version: 1.0
X-Received: by 10.60.140.168 with SMTP id rh8mr1628599oeb.76.1383086940086;
 Tue, 29 Oct 2013 15:49:00 -0700 (PDT)
Sender: shaposhnik@gmail.com
Received: by 10.182.133.101 with HTTP; Tue, 29 Oct 2013 15:49:00 -0700 (PDT)
In-Reply-To: <526F5260.9010308@apache.org>
References: 
 <CA+ULb+s16bh-Qces3X5=7eq3VQDgg3GsfQ8tyvrVJgu1hRcL-g@mail.gmail.com>
	<526E32BE.4000600@apache.org>
	<CA+ULb+ubwv6CxYzOe2_0R0sjzBwEHOB7rVjfaYs2g1yhv0RTCw@mail.gmail.com>
	<526F5260.9010308@apache.org>
Date: Tue, 29 Oct 2013 15:49:00 -0700
X-Google-Sender-Auth: 0W9CUAlSwbc6Kyow55oracGG03U
Message-ID: 
 <CA+ULb+toT0EU1cDTZNePFdoYA9Be8haOuOTsz_DZtGYFkmMt=g@mail.gmail.com>
Subject: Re: [VOTE] Bigtop 0.7.0 RC0
From: Roman Shaposhnik <rvs@apache.org>
To: =?ISO-8859-1?Q?Bruno_Mah=E9?= <bmahe@apache.org>
Cc: dev@bigtop.apache.org, "user@bigtop.apache.org" <user@bigtop.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Virus-Checked: Checked by ClamAV on apache.org

On Mon, Oct 28, 2013 at 11:14 PM, Bruno Mah=E9 <bmahe@apache.org> wrote:
>> I would agree with that. The only trouble is I can't repro it :-(
>> Could you please provide additional details on the JIRA?
>>
>> But if it is easy to repro (and I'm just missing something)
>> I'd agree with you.
>>
>
> I updated the ticket with some more information.
> If you still cannot reproduce it, feel free to ping me and I will give yo=
u
> access to the instance.
> At some point I was wondering if it is because I am mixing the amazon ami
> with centos6 repos, but given every other service I try do work...

Thanks for the details instructions on how to repro. It is indeed
easily reproducible and it is also extremely easy to fix.

Now, at this point, I'm absolutely in favor of spinning up RC1
with the following fixes in: BIGTOP-1132 and BIGTOP-1129

Both of those are really isolated fixes and here's what I'd like
to propose: I respin on Wed and send out a new VOTE thread.
This time, however, the voting will only go till noon on Sun 11/3.

If anybody objects to that -- please let me know ASAP.

The rest of my comments inline:

>> I can help with that. ;-) At least with the default use case. Let me kno=
w
>> if you're still interested.
>>
>
> Sure. Any recommendations?

Basically, you can simply follow this setup docs:
    http://www.cloudera.com/content/cloudera-content/cloudera-docs/Search/l=
atest/Cloudera-Search-Installation-Guide/csig_install_search.html
and especially this part:
    http://www.cloudera.com/content/cloudera-content/cloudera-docs/Search/l=
atest/Cloudera-Search-Installation-Guide/csig_deploy_search_solrcloud.html

It also covers Hue Search app. It would very nice if somebody
can help come up with Bigtop-specific wiki docs, but for now
Cloudera Search is close enough.

>> At this point Puppet code is the most reliable way to deploy Hue. Part o=
f
>> it has to do that Hue now depends on way more external services than
>> it uses to -- which means that you have to get configs 'just right'. Our
>> puppet works great for that -- but that's for a fully distributed cluste=
r.
>>
>
> I was not using puppet (on purpose).
> I will give it another shot by looking at what our puppet recipes are doi=
ng
> and see if any of these changes can be baked directly into our packages.

Thanks! That would be appreciated.

> Actually, it was the elasticsearch sink for flume which had me update Apa=
che
> Lucene jars.
>
> I will probably open a ticket against Apache Flume directly sometimes thi=
s
> week to ask for some clarification.

Please do. I believe I fixed some of those issues in upcoming Flume 1.5.0

>> WAT? Really. I'm pretty curious at this point
>>
>
> I had the same reaction.
> But this was reported as blocked by noscript.
> Also it seems to be a configuration activated by default:
> https://github.com/cloudera/hue/blob/master/desktop/conf.dist/hue.ini#L63

Do you think we can convince Hue upstream to not spy
on its users by default? ;-)

I guess worst case scenario -- we can always disable it downstream in Bigto=
p.

>> Great! Would you be willing to help with a blog post on the release? ;-)
>>
>
> Sure.
> Do you have anything particular in mind?

Just a bit more verbose version of the feedback you've provided on this
thread, I guess. Makes sense?

>> Well, there's Hue Search app. Have you had a chance to try it?
>>
>
> Not yet. But will do.

Give it a try -- its like Google, but on your data ;-)

And the docs I quoted above cover it as well.

Thanks,
Roman.