Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 8A972200B40 for ; Fri, 17 Jun 2016 03:02:07 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 891BE160A51; Fri, 17 Jun 2016 01:02:07 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id D6265160A52 for ; Fri, 17 Jun 2016 03:02:06 +0200 (CEST) Received: (qmail 98795 invoked by uid 500); 17 Jun 2016 01:02:05 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 98768 invoked by uid 99); 17 Jun 2016 01:02:05 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Jun 2016 01:02:05 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 47FE82C1F60 for ; Fri, 17 Jun 2016 01:02:05 +0000 (UTC) Date: Fri, 17 Jun 2016 01:02:05 +0000 (UTC) From: "Andrew Purtell (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (HBASE-13096) NPE from SecureWALCellCodec$EncryptedKvEncoder#write when using WAL encryption and Phoenix secondary indexes MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 17 Jun 2016 01:02:07 -0000 [ https://issues.apache.org/jira/browse/HBASE-13096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell resolved HBASE-13096. ------------------------------------ Resolution: Cannot Reproduce Assignee: (was: Andrew Purtell) Fix Version/s: (was: 0.98.21) Closing as Cannot Reproduce. If someone is seeing this and can post a reproduction of the issue we can reopen it. > NPE from SecureWALCellCodec$EncryptedKvEncoder#write when using WAL encryption and Phoenix secondary indexes > ------------------------------------------------------------------------------------------------------------ > > Key: HBASE-13096 > URL: https://issues.apache.org/jira/browse/HBASE-13096 > Project: HBase > Issue Type: Bug > Affects Versions: 0.98.6 > Reporter: Andrew Purtell > Labels: phoenix > > On user@phoenix Dhavi Rami reported: > {quote} > I tried using phoenix in hBase with Transparent Encryption of Data At Rest enabled ( AES encryption) > Works fine for a table with primary key column. > But it doesn't work if I create Secondary index on that tables.I tried to dig deep into the problem and found WAL file encryption throws exception when I have Global Secondary Index created on my mutable table. > Following is the error I was getting on one of the region server. > {noformat} > 2015-02-20 10:44:48,768 ERROR org.apache.hadoop.hbase.regionserver.wal.FSHLog: UNEXPECTED > java.lang.NullPointerException > at org.apache.hadoop.hbase.util.Bytes.toInt(Bytes.java:767) > at org.apache.hadoop.hbase.util.Bytes.toInt(Bytes.java:754) > at org.apache.hadoop.hbase.KeyValue.getKeyLength(KeyValue.java:1253) > at org.apache.hadoop.hbase.regionserver.wal.SecureWALCellCodec$EncryptedKvEncoder.write(SecureWALCellCodec.java:194) > at org.apache.hadoop.hbase.regionserver.wal.ProtobufLogWriter.append(ProtobufLogWriter.java:117) > at org.apache.hadoop.hbase.regionserver.wal.FSHLog$AsyncWriter.run(FSHLog.java:1137) > at java.lang.Thread.run(Thread.java:745) > 2015-02-20 10:44:48,776 INFO org.apache.hadoop.hbase.regionserver.wal.FSHLog: regionserver60020-WAL.AsyncWriter exiting > {noformat} > I had to disable WAL encryption, and it started working fine with secondary Index. So Hfile encryption works with secondary index but WAL encryption doesn't work. > {quote} > Parking this here for later investigation. For now I'm going to assume this is something in SecureWALCellCodec that needs looking at, but if it turns out to be a Phoenix indexer issue I will move this JIRA there. -- This message was sent by Atlassian JIRA (v6.3.4#6332)