You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@accumulo.apache.org by "Eric Newton (Created) (JIRA)" <ji...@apache.org> on 2011/10/25 16:52:32 UTC
[jira] [Created] (ACCUMULO-67) zookeeper session id encoded in
metadata in two different ways
zookeeper session id encoded in metadata in two different ways
--------------------------------------------------------------
Key: ACCUMULO-67
URL: https://issues.apache.org/jira/browse/ACCUMULO-67
Project: Accumulo
Issue Type: Improvement
Components: master, tserver
Affects Versions: 1.4.0
Reporter: Eric Newton
Assignee: Eric Newton
Priority: Trivial
The location entries in the !METADATA table encode zookeeper session information as hex. The lock entries are encoded as decimal. The value is used for different purposes, but it does provide identity information for the tablet server, and it would be nice to compare them without getting out a calculator.
The data is transient: we can encode them any way we want between restarts.
--
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] (ACCUMULO-67) zookeeper session id encoded in
metadata in two different ways
Posted by "Keith Turner (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACCUMULO-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Keith Turner updated ACCUMULO-67:
---------------------------------
Affects Version/s: (was: 1.4.0)
> zookeeper session id encoded in metadata in two different ways
> --------------------------------------------------------------
>
> Key: ACCUMULO-67
> URL: https://issues.apache.org/jira/browse/ACCUMULO-67
> Project: Accumulo
> Issue Type: Improvement
> Components: master, tserver
> Reporter: Eric Newton
> Assignee: Eric Newton
> Priority: Trivial
> Fix For: 1.4.0
>
> Original Estimate: 2m
> Remaining Estimate: 2m
>
> The location entries in the !METADATA table encode zookeeper session information as hex. The lock entries are encoded as decimal. The value is used for different purposes, but it does provide identity information for the tablet server, and it would be nice to compare them without getting out a calculator.
> The data is transient: we can encode them any way we want between restarts.
--
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] [Resolved] (ACCUMULO-67) zookeeper session id encoded in
metadata in two different ways
Posted by "Eric Newton (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACCUMULO-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Newton resolved ACCUMULO-67.
---------------------------------
Resolution: Fixed
Fix Version/s: 1.4.0
> zookeeper session id encoded in metadata in two different ways
> --------------------------------------------------------------
>
> Key: ACCUMULO-67
> URL: https://issues.apache.org/jira/browse/ACCUMULO-67
> Project: Accumulo
> Issue Type: Improvement
> Components: master, tserver
> Affects Versions: 1.4.0
> Reporter: Eric Newton
> Assignee: Eric Newton
> Priority: Trivial
> Fix For: 1.4.0
>
> Original Estimate: 2m
> Remaining Estimate: 2m
>
> The location entries in the !METADATA table encode zookeeper session information as hex. The lock entries are encoded as decimal. The value is used for different purposes, but it does provide identity information for the tablet server, and it would be nice to compare them without getting out a calculator.
> The data is transient: we can encode them any way we want between restarts.
--
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