[jira] [Commented] (HBASE-8206) Thread safety issues with Compression.Algorithm.GZ and SNAPPY

["Manukranth Kolloju (JIRA)" <ji...@apache.org>]

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

Manukranth Kolloju commented on HBASE-8206:
-------------------------------------------

We found that double locking was not necessarily thread safe and it might be solved by doing the following : 
        if (codec == null) {
          synchronized (lock) {
            if (codec == null) {
              GzipCodec tmpCodec = new ReusableStreamGzipCodec();
              tmpCodec.setConf(new Configuration(conf));
              codec = tmpCodec;
            }
          }

                
> Thread safety issues with Compression.Algorithm.GZ and SNAPPY
> -------------------------------------------------------------
>
>                 Key: HBASE-8206
>                 URL: https://issues.apache.org/jira/browse/HBASE-8206
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.89-fb
>            Reporter: Manukranth Kolloju
>            Priority: Minor
>             Fix For: 0.89-fb
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> The Compression.Algorithm was not completely thread safe. Hence making it thread safe. Trying to fix this the same way it was fixed in HBase trunk(HBASE-5458) with a minor change since the fix in trunk is not completely thread safe.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira