[
https://issues.apache.org/jira/browse/HAWQ-1244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15784521#comment-15784521
]
Yi Jin commented on HAWQ-1244:
------------------------------
I agree ONTARY issue should be caused by large value settings, I am
investigating the system cache part to check if there is something going wrong.
> unrecognized configuration parameter "ONETARY"
> ----------------------------------------------
>
> Key: HAWQ-1244
> URL: https://issues.apache.org/jira/browse/HAWQ-1244
> Project: Apache HAWQ
> Issue Type: Bug
> Components: Dispatcher
> Reporter: Jon Roberts
> Assignee: Yi Jin
>
> Fatal error occurs when reading /usr/local/hawq/etc/_mgmt_config when the
> file is large due to many temp directories, a highly parallelized query,
> random distributed tables, and hawq_rm_nvseg_perquery_perseg_limit set higher
> (12 for example).
> Query 88 in TPC-DS fails with random distribution, 10 nodes in AWS, 7TB of
> data, hawq_rm_memory_limit_perseg = 200gb, hawq_rm_stmt_vseg_memory = 16gb,
> hawq_rm_nvseg_perquery_perseg_limit = 12.
> Error raised:
> 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"
> Error from segment:
> 2016-12-14 13:47:34.760839
> UTC,"gpadmin","gpadmin",p737499,th542214432,"172.21.13.196","40327",2016-12-14
> 13:47:34 UTC,0,con23798,,seg-10000,,,,,"FATAL","42704","unrecognized
> configuration parameter ""ONETARY""",,,,,,,0,,"guc.c",10006,
> Workaround is to use less vsegs or reduce the number of temp directories.
> This is probably not related to the number of temp directories but the size
> of the _mgmt_config file. The parameter it apparently is failing to parse is:
> hawq_lc_monetary=en_US.utf8
> The problem is likely in guc.c based on the segment error.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
