hawq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yi Jin <y...@pivotal.io>
Subject Re: unrecognized configuration parameter "ONETARY"
Date Mon, 19 Dec 2016 10:44:25 GMT
Hi Jon,

I think there is no ONTARY configuration item, so maybe I need the full log
containing that error to check the error routine.

Best,
Yi

On Mon, Dec 19, 2016 at 5:39 PM, Paul Guo <paulguo@gmail.com> wrote:

> You could grep the log to see whether there is "ONETARY" setting before
> this error occurs, and also grep configuration files and related test files
> to find who tried to set this.
>
> 2016-12-14 22:36 GMT+08:00 Jon Roberts <jroberts@pivotal.io>:
>
> > I'm getting the error message: unrecognized configuration parameter
> > "ONETARY" with a few of the TPC-DS queries where I'm increasing the
> number
> > of vsegs to get better performance.  The error message alone is confusing
> > so even if I am doing something wrong, the message should be improved.
> >
> > My environment:
> >
> > AWS d2.8xlarge nodes
> > - 24 2 TB disks
> > - 252 GB RAM
> > - 36 cores
> > - Centos 6
> > - 10 nodes
> > - 1 admin node
> > - 10GB network
> > - 7 TB of data
> > - Standard TPC-DS Queries
> > - hawq_rm_memory_limit_perseg = 200gb
> > - hawq_rm_stmt_vseg_memory = 16gb
> > - Random distribution on all tables
> >
> > I'm tried reducing the statement memory but that doesn't change anything.
> >
> > Query 88 is a good example of this because it fails quickly.
> >
> > set hawq_rm_nvseg_perquery_perseg_limit=12;
> >
> > time psql -f 188.tpcds.88.sql
> > SET
> > Timing is on.
> > SET
> > Time: 0.157 ms
> >  h8_30_to_9 | h9_to_9_30 | h9_30_to_10 | h10_to_10_30 | h10_30_to_11 |
> > h11_to_11_30 | h11_30_to_12 | h12_to_12_30
> > ------------+------------+-------------+--------------+-----
> > ---------+--------------+--------------+--------------
> >    16279055 |   32496701 |    32493080 |     48732586 |     48782652 |
> > 28460584 |     28453299 |     32518016
> > (1 row)
> >
> > Time: 259695.969 ms
> >
> > real 4m19.706s
> > user 0m0.001s
> > sys 0m0.003s
> >
> > Next:
> > set hawq_rm_nvseg_perquery_perseg_limit=14;
> >
> > time psql -f 188.tpcds.88.sql
> > SET
> > Timing is on.
> > SET
> > Time: 0.171 ms
> > psql:188.tpcds.88.sql:95: ERROR:  Error dispatching to seg25
> > ip-172-21-13-189.ec2.internal:40000: connection pointer is NULL
> > DETAIL:  Master unable to connect to seg25
> > ip-172-21-13-189.ec2.internal:40000: FATAL:  unrecognized configuration
> > parameter "ONETARY"
> >
> > real 0m8.787s
> > user 0m0.003s
> > sys 0m0.002s
> >
> >
> > Jon Roberts
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message