hawq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jane Beckman (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HAWQ-1519) Ambiguous or conflicting information about max_segments/max_prepared_transactions
Date Thu, 17 Aug 2017 22:50:01 GMT
Jane Beckman created HAWQ-1519:
----------------------------------

             Summary: Ambiguous or conflicting information about max_segments/max_prepared_transactions
                 Key: HAWQ-1519
                 URL: https://issues.apache.org/jira/browse/HAWQ-1519
             Project: Apache HAWQ
          Issue Type: Bug
          Components: Documentation
            Reporter: Jane Beckman
            Assignee: David Yozie
             Fix For: 2.3.0.0-incubating


Feedback from Eli Lily:
We currently state: "When you set max_connections, you must also set the dependent parameter
max_prepared_transactions. This value must be at least as large as the value of max_connections,
and all HAWQ instances should be set to the same value." However, Radar  has stated "HAWQ
updated ‘max_connections’ value to 1280 since HDB2.0. For ‘max_prepared_transactions’
value, we’d better keep the default value as 250 since now it’s working fine. " This will
need clarification, since the default values now differ and either the first statement is
no longer true, and should be removed, or the user must reset one of the defaults.

 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message