Mailing-List: contact dev-help@hawq.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hawq.incubator.apache.org
MIME-Version: 1.0
In-Reply-To: <CAMjXoAO6UWGs3qXac15hJ8EjjofGSveiDdi-hNJ_0NSkbYxnUQ@mail.gmail.com>
References: <CABQrizfc_HopTGB7MsLBFbM-WuGyFpu+bv1K6hnUb+=BLBH_NA@mail.gmail.com>
 <CABQrizcaVNFJGXT2-aOFNx_3HW0z19iyavg+q8E66J+tEqjZ5A@mail.gmail.com>
 <CAEET0ZGKR7VQDbOHYwnQrVfGBNB=rcUdAxuZJegw_TX47oNwsg@mail.gmail.com> <CAMjXoAO6UWGs3qXac15hJ8EjjofGSveiDdi-hNJ_0NSkbYxnUQ@mail.gmail.com>
From: Yi Jin <yjin@pivotal.io>
Date: Wed, 28 Dec 2016 16:18:47 +1100
Message-ID: <CAMjXoAMNp-XnQUVMPFNrkQ8kFE9b7UKwXV=-VbzBzpBp7S7n3A@mail.gmail.com>
Subject: Re: "unrecognized configuration parameter" in masterdd/pg_log/startup.log
To: Paul Guo <pguo@pivotal.io>, dev <dev@hawq.incubator.apache.org>
Content-Type: multipart/alternative; boundary=001a114116207a0b1b0544b11a70
archived-at: Wed, 28 Dec 2016 05:18:56 -0000

--001a114116207a0b1b0544b11a70
Content-Type: text/plain; charset=UTF-8

I will open a JIRA to fix it by providing correct guc names in
hawq-site.xml file.

Yi

On Wed, Dec 28, 2016 at 3:27 PM, Yi Jin <yjin@pivotal.io> wrote:

> Hi Paul,
>
> HAWQ loads hawq-site.xml and set configuration one by one regardless
> whether the guc is valid, so that's why those non-existing guc variables
> are logged out. I think it is from default hawq-site.xml file. Share we
> update the xml file as the fix?
>
> Best,
> Yi
>
> On Sat, Dec 24, 2016 at 12:37 AM, Paul Guo <pguo@pivotal.io> wrote:
>
>> Hi yi,
>>
>> It seems that more than 1 people are confused by this behaviour. I just
>> talked with
>>
>> Radar without checking the code details. He said RM will read this and
>> should filter
>>
>> this. Could you verify please? Could we easily fix this?
>>
>>
>> (Previous email seems to be blocked so I fwd and then replied using my
>> company email).
>>
>> Thanks.
>>
>>
>> ---------- Forwarded message ----------
>> From: Paul Guo <paulguo@gmail.com>
>> Date: 2016-12-03 11:08 GMT+08:00
>> Subject: "unrecognized configuration parameter" in
>> masterdd/pg_log/startup.log
>> To: dev@hawq.incubator.apache.org
>>
>>
>> I happened to check the log and found some confusing logs.
>> Have not looked into this yet. Anyone sawq this before?
>>
>> 2016-12-02 09:28:05.942583 GMT,,,p366111,th454986016,,,,0
>> ,,,seg-10000,,,,,"LOG","00000","NOTE: Recognized configuration:
>> hawq_dfs_url=localhost:8020/hawq_default",,,,,,,,"processXML
>> Node","kvproperties.c",134,
>>
>> ......
>>
>> 2016-12-02 09:28:05.948051 GMT,,,p366111,th454986016,,,,0
>> ,,,seg-10000,,,,,"LOG","42704","unrecognized configuration parameter
>> ""hawq_standby_address_host""",,,,,,,,"set_config_option","guc.c",10041,
>> 2016-12-02 09:28:05.948203 GMT,,,p366111,th454986016,,,,0
>> ,,,seg-10000,,,,,"LOG","42704","unrecognized configuration parameter
>> ""hawq_dfs_url""",,,,,,,,"set_config_option","guc.c",10041,
>> 2016-12-02 09:28:05.948349 GMT,,,p366111,th454986016,,,,0
>> ,,,seg-10000,,,,,"LOG","42704","unrecognized configuration parameter
>> ""hawq_master_directory""",,,,,,,,"set_config_option","guc.c",10041,
>> 2016-12-02 09:28:05.948493 GMT,,,p366111,th454986016,,,,0
>> ,,,seg-10000,,,,,"LOG","42704","unrecognized configuration parameter
>> ""hawq_segment_directory""",,,,,,,,"set_config_option","guc.c",10041,
>>
>>
>>
>>
>>
>>
>

--001a114116207a0b1b0544b11a70--