VectorClock MAX_NUMBER_OF_VERSIONS: Why Short.MAX_VALUE?

[Mark Stetzer]

Hey all,

Forgive my limited understanding of the implementation, but I was
wondering why is VectorClock's (integer) MAX_NUMBER_OF_VERSIONS field
set to Short.MAX_VALUE? The reason I ask is we've hit the max number
of versions for some of the keys in one of our clusters, and I wanted
to know what would happen if we changed that value to something like
INTEGER.MAX_VALUE.

Thanks!

-Mark

[Mark Stetzer]

Just wanted to retire an old post. I had asked this question a few
months back, and just now got around to looking into it. Turns out
our problem was related to
http://code.google.com/p/project-voldemort/issues/detail?id=51, which
was resolved quite a while ago (we're still running our production
cluster on a version prior to that commit!). So consider this a
non-issue.

-Mark

> --
> You received this message because you are subscribed to the Google Groups "project-voldemort" group.
> To post to this group, send email to project-...@googlegroups.com.
> To unsubscribe from this group, send email to project-voldem...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/project-voldemort?hl=en.
>
>