You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hawq.apache.org by "Xiang Sheng (JIRA)" <ji...@apache.org> on 2017/04/12 09:16:41 UTC

[jira] [Assigned] (HAWQ-1430) Update ranger related log level to avoid log flood

     [ https://issues.apache.org/jira/browse/HAWQ-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Xiang Sheng reassigned HAWQ-1430:
---------------------------------

    Assignee: Xiang Sheng  (was: Ed Espino)

> Update ranger related log level to avoid log flood
> --------------------------------------------------
>
>                 Key: HAWQ-1430
>                 URL: https://issues.apache.org/jira/browse/HAWQ-1430
>             Project: Apache HAWQ
>          Issue Type: Improvement
>          Components: Security
>            Reporter: Xiang Sheng
>            Assignee: Xiang Sheng
>             Fix For: 2.3.0.0-incubating
>
>
> I've been seeing following log flooding during various tests.
> 2017-04-10 07:31:36.570384 PDT,"hawqsuperuser","olap_window",p28236,th-972322528,,"61316",2017-04-10 07:31:36 PDT,0,con1311,,seg-10000,,,,,"LOG","00000","acl check type is standalone, the acl type value is 0.",,,,,,,0,,"postgres.c",4424,
> Since this log level is LOG, and the rangerrest curl is session level, so we will check this for each session. This will cause a log flood under high concurrency. And this is not that necessary  to log with LOG level. So we should update it.  



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)