Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <1908537870.1252099017510.JavaMail.jira@brutus>
Date: Fri, 4 Sep 2009 14:16:57 -0700 (PDT)
From: "stack (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Updated: (HBASE-1809) NPE thrown in
 BoundedRangeFileInputStream
In-Reply-To: <191624543.1251838653048.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

stack updated HBASE-1809:
-------------------------

    Attachment: 1809.patch

This patch would address the immediate NPE (What I do in the constructor might not be the smartest) but something else is going on if we have one thread reading off a closed stream.  Chatting w/ Mathias, he sees this NPE with get and getclosest.  Both take out read locks on the store so another thread shouldn't be doing close this store file.  Mathias is trying to figure more input.

> NPE thrown in BoundedRangeFileInputStream
> -----------------------------------------
>
>                 Key: HBASE-1809
>                 URL: https://issues.apache.org/jira/browse/HBASE-1809
>             Project: Hadoop HBase
>          Issue Type: Bug
>          Components: io
>         Environment: All
>            Reporter: Mathias Herberts
>            Priority: Critical
>             Fix For: 0.20.1
>
>         Attachments: 1809.patch, HFile-returnDecompressor.patch
>
>
> NPE is thrown in BoundedRangeFileInputStream.read when attempting to synchronize on 'in' (line 97).
> This probably means the BRFIS was created with a null FSDIS.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.