[
https://issues.apache.org/jira/browse/HBASE-9374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13860476#comment-13860476
]
Nick Dimiduk commented on HBASE-9374:
-------------------------------------
This patch works around the problem, doesn't really solve it. What happens when
this code runs on the RegionServer, the directory isn't created/doesn't exist,
and only the warning is printed? Does the process limp along in a broken state?
Nit: the test doesn't explicitly create this condition, it just assumes the
user running the test won't have access to that path. It also assumes a UNIX
directory structure, so will not work on Windows.
> Client requires write access to hbase.local.dir unnecessarily
> -------------------------------------------------------------
>
> Key: HBASE-9374
> URL: https://issues.apache.org/jira/browse/HBASE-9374
> Project: HBase
> Issue Type: Bug
> Components: Client, Protobufs
> Affects Versions: 0.95.2
> Reporter: Nick Dimiduk
> Assignee: Jimmy Xiang
> Fix For: 0.98.0, 0.96.2, 0.99.0
>
> Attachments: hbase-9374.patch
>
>
> Per this
> [thread|http://mail-archives.apache.org/mod_mbox/hbase-dev/201308.mbox/%3cCANZa=GuLO0jTLs1fF+5_NRDczO+M=ssqjeagveeicy8injb...@mail.gmail.com%3e]
> from the dev list.
> {quote}
> It appears that as of HBASE-1936, we now require that client applications
> have write access to hbase.local.dir. This is because ProtobufUtil
> instantiates a DyanamicClassLoader as part of static initialization. This
> classloader is used for instantiating Comparators, Filters, and Exceptions.
> {quote}
> Client applications do not need to use DynamicClassLoader and so should not
> require this write access.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
