[jira] [Commented] (HBASE-9374) Client requires write access to hbase.local.dir unnecessarily
[ https://issues.apache.org/jira/browse/HBASE-9374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13860828#comment-13860828 ] Jimmy Xiang commented on HBASE-9374: Other solutions I thought about are all hacks. Should we leave this as Won't Fix? > 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 > 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)
[jira] [Commented] (HBASE-9374) Client requires write access to hbase.local.dir unnecessarily
[ https://issues.apache.org/jira/browse/HBASE-9374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13860549#comment-13860549 ] Jimmy Xiang commented on HBASE-9374: That's right. It works around the problem. The issue is that we don't know if it is in the server side or client side. Let me check if I can add some checking in the server side. > 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)
[jira] [Commented] (HBASE-9374) Client requires write access to hbase.local.dir unnecessarily
[ 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)
[jira] [Commented] (HBASE-9374) Client requires write access to hbase.local.dir unnecessarily
[ https://issues.apache.org/jira/browse/HBASE-9374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753069#comment-13753069 ] Nick Dimiduk commented on HBASE-9374: - While this change is being made, TestProtobufUtil should be moved into hbase-client so that its location is consistent with ProtobufUtil. > 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 > > 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 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
[jira] [Commented] (HBASE-9374) Client requires write access to hbase.local.dir unnecessarily
[ https://issues.apache.org/jira/browse/HBASE-9374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753064#comment-13753064 ] Jimmy Xiang commented on HBASE-9374: That's a good catch. Dynamic class loading should be done in RS side only. Do we have a way to detect it is client side or server side? > 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 > > 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 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