[
https://issues.apache.org/jira/browse/HTRACE-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14647330#comment-14647330
]
stack commented on HTRACE-209:
------------------------------
On UUID format:
"If I remember the copy/paste-able concern, UUID format isn't actually that
great. For example, double-click somewhere in
de305d54-75b4-431b-adb2-eb6b9e546014 and you'll only select one section of the
UUID. This isn't as bad as negative numbers, as those are far more subtle. ex.
double-click on -123456 and it will miss the minus. "
and
"Another unfortunate aspect of UUIDs is arbitrary subsections of the UUID are
unlikely to be unique, in a way that just random bytes are. UUIDs are often
constructed where the first part is based on some hardware serial number that
never changes or something. If you need a UUID, it's almost always better to
just pick a similarly sized string of random bytes from a cryptographic
pseudorandom number generator."
>From
>https://groups.google.com/forum/#!search/distributed-tracing/distributed-tracing/xvYcWxM5nF4/fNqYCSvbDOIJ
>
> Make span ID 128 bit to avoid collisions
> ----------------------------------------
>
> Key: HTRACE-209
> URL: https://issues.apache.org/jira/browse/HTRACE-209
> Project: HTrace
> Issue Type: Sub-task
> Affects Versions: 4.0
> Reporter: Colin Patrick McCabe
> Assignee: Colin Patrick McCabe
> Attachments: HTRACE-209.001.patch, HTRACE-209.002.patch,
> HTRACE-209.004.patch, HTRACE-209.005.patch
>
>
> Make span ID 128 bit to avoid collisions in htrace 4.x
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
