You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Roman Shaposhnik (JIRA)" <ji...@apache.org> on 2012/06/29 18:52:42 UTC
[jira] [Created] (BIGTOP-660) hbase client is getting confused
because of importing /etc/default/hadoop
Roman Shaposhnik created BIGTOP-660:
---------------------------------------
Summary: hbase client is getting confused because of importing /etc/default/hadoop
Key: BIGTOP-660
URL: https://issues.apache.org/jira/browse/BIGTOP-660
Project: Bigtop
Issue Type: Bug
Components: General
Affects Versions: 0.4.0
Reporter: Roman Shaposhnik
Assignee: Roman Shaposhnik
Fix For: 0.5.0
In general /etc/default/<component> settings are supposed to be there for daemon configuration (since daemons typically lack any other means of setting up an environment for themselves).
We've been piggybacking on those for the client side of things, but it does cause troubles with certain user-level settings sometimes. The correct solution here would be to completely decouple daemon setting from the client ones (as BIGTOP-492 suggests) but until this happens we have to workaround.
Removing HBase client's dependency on /etc/default/hadoop seems to be harmless and it lets users tweak the environment.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (BIGTOP-660) hbase client is getting confused
because of importing /etc/default/hadoop
Posted by "Andrew Bayer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BIGTOP-660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13404045#comment-13404045 ]
Andrew Bayer commented on BIGTOP-660:
-------------------------------------
+1
> hbase client is getting confused because of importing /etc/default/hadoop
> -------------------------------------------------------------------------
>
> Key: BIGTOP-660
> URL: https://issues.apache.org/jira/browse/BIGTOP-660
> Project: Bigtop
> Issue Type: Bug
> Components: General
> Affects Versions: 0.4.0
> Reporter: Roman Shaposhnik
> Assignee: Roman Shaposhnik
> Fix For: 0.5.0
>
> Attachments: BIGTOP-660.patch.txt
>
>
> In general /etc/default/<component> settings are supposed to be there for daemon configuration (since daemons typically lack any other means of setting up an environment for themselves).
> We've been piggybacking on those for the client side of things, but it does cause troubles with certain user-level settings sometimes. The correct solution here would be to completely decouple daemon setting from the client ones (as BIGTOP-492 suggests) but until this happens we have to workaround.
> Removing HBase client's dependency on /etc/default/hadoop seems to be harmless and it lets users tweak the environment.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (BIGTOP-660) hbase client is getting confused
because of importing /etc/default/hadoop
Posted by "Roman Shaposhnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BIGTOP-660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roman Shaposhnik updated BIGTOP-660:
------------------------------------
Attachment: BIGTOP-660.patch.txt
Trivial patch attached.
> hbase client is getting confused because of importing /etc/default/hadoop
> -------------------------------------------------------------------------
>
> Key: BIGTOP-660
> URL: https://issues.apache.org/jira/browse/BIGTOP-660
> Project: Bigtop
> Issue Type: Bug
> Components: General
> Affects Versions: 0.4.0
> Reporter: Roman Shaposhnik
> Assignee: Roman Shaposhnik
> Fix For: 0.5.0
>
> Attachments: BIGTOP-660.patch.txt
>
>
> In general /etc/default/<component> settings are supposed to be there for daemon configuration (since daemons typically lack any other means of setting up an environment for themselves).
> We've been piggybacking on those for the client side of things, but it does cause troubles with certain user-level settings sometimes. The correct solution here would be to completely decouple daemon setting from the client ones (as BIGTOP-492 suggests) but until this happens we have to workaround.
> Removing HBase client's dependency on /etc/default/hadoop seems to be harmless and it lets users tweak the environment.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (BIGTOP-660) hbase client is getting confused
because of importing /etc/default/hadoop
Posted by "Roman Shaposhnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BIGTOP-660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roman Shaposhnik updated BIGTOP-660:
------------------------------------
Fix Version/s: (was: 0.5.0)
0.4.0
> hbase client is getting confused because of importing /etc/default/hadoop
> -------------------------------------------------------------------------
>
> Key: BIGTOP-660
> URL: https://issues.apache.org/jira/browse/BIGTOP-660
> Project: Bigtop
> Issue Type: Bug
> Components: General
> Affects Versions: 0.4.0
> Reporter: Roman Shaposhnik
> Assignee: Roman Shaposhnik
> Fix For: 0.4.0
>
> Attachments: BIGTOP-660.patch.txt
>
>
> In general /etc/default/<component> settings are supposed to be there for daemon configuration (since daemons typically lack any other means of setting up an environment for themselves).
> We've been piggybacking on those for the client side of things, but it does cause troubles with certain user-level settings sometimes. The correct solution here would be to completely decouple daemon setting from the client ones (as BIGTOP-492 suggests) but until this happens we have to workaround.
> Removing HBase client's dependency on /etc/default/hadoop seems to be harmless and it lets users tweak the environment.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira