hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-14512) Cache UGI groups
Date Wed, 30 Sep 2015 02:24:04 GMT

    [ https://issues.apache.org/jira/browse/HBASE-14512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14936267#comment-14936267
] 

Hadoop QA commented on HBASE-14512:
-----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12764349/HBASE-14512-v2.patch
  against master branch at commit c04d18970e066c1c5879a7ac1d261ef69cae5c3e.
  ATTACHMENT ID: 12764349

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified
tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:green}+1 hadoop versions{color}. The patch compiles with all supported hadoop versions
(2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.0 2.6.1 2.7.0 2.7.1)

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 protoc{color}.  The applied patch does not increase the total number of
protoc compiler warnings.

    {color:green}+1 javadoc{color}.  The javadoc tool did not generate any warning messages.

    {color:green}+1 checkstyle{color}.  The applied patch does not increase the total number
of checkstyle errors

    {color:green}+1 findbugs{color}.  The patch does not introduce any  new Findbugs (version
2.0.3) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:green}+1 lineLengths{color}.  The patch does not introduce lines longer than 100

  {color:green}+1 site{color}.  The mvn post-site goal succeeds with this patch.

     {color:red}-1 core tests{color}.  The patch failed these unit tests:
                       org.apache.hadoop.hbase.security.TestSecureRPC
                  org.apache.hadoop.hbase.mapred.TestRowCounter
                  org.apache.hadoop.hbase.mapreduce.TestTableMapReduceUtil
                  org.apache.hadoop.hbase.procedure.TestProcedureManager
                  org.apache.hadoop.hbase.ipc.TestRpcClientLeaks
                  org.apache.hadoop.hbase.ipc.TestIPC
                  org.apache.hadoop.hbase.mob.mapreduce.TestMobSweepMapper
                  org.apache.hadoop.hbase.regionserver.TestRegionMergeTransaction
                  org.apache.hadoop.hbase.ipc.TestAsyncIPC

     {color:red}-1 core zombie tests{color}.  There are 1 zombie test(s): 

Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/15816//testReport/
Release Findbugs (version 2.0.3) 	warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/15816//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors: https://builds.apache.org/job/PreCommit-HBASE-Build/15816//artifact/patchprocess/checkstyle-aggregate.html

  Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/15816//console

This message is automatically generated.

> Cache UGI groups
> ----------------
>
>                 Key: HBASE-14512
>                 URL: https://issues.apache.org/jira/browse/HBASE-14512
>             Project: HBase
>          Issue Type: Bug
>          Components: Performance, security
>    Affects Versions: 1.2.0
>            Reporter: Elliott Clark
>            Assignee: Elliott Clark
>             Fix For: 2.0.0, 1.2.0, 1.3.0
>
>         Attachments: HBASE-14512-v1.patch, HBASE-14512-v2.patch, HBASE-14512-v3.patch,
HBASE-14512.patch
>
>
> Right now every call gets a new User object.
> We should keep the same user for the life of a connection. We should also cache the group
names. However we can't cache the groups for forever as that would mean groups don't get refreshed
every 5 mins.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message