Uploaded image for project: 'HBase'
  1. HBase
  2. HBASE-6814 [WINDOWS] HBase on Windows
  3. HBASE-6833

[WINDOWS] Java Milisecond precision on Windows

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Closed
    • Major
    • Resolution: Abandoned
    • 0.94.3, 0.95.2
    • None
    • None

    Description

      HBase relies on the system clock obtained by System.currentTimeMilis() to supply the version, if it is not provided by the client in Put's and Delete's. At HBASE-6832 and HBASE-6826, we discovered that on some platforms, the milis clock might not be updated every milisecond, which might cause unexpected behavior. We also did some preliminary analysis there.
      In this issue, we can further discuss and inspect whether it is a problem for main target platforms and if so what can be done.

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. HBASE-6832 [WINDOWS] Tests should use explicit timestamp for Puts, and not rely on implicit RS timing

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. HBASE-8927 Use nano time instead of mili time everywhere

          • Major - Major loss of function.
          • Closed

          New Feature - A new feature of the product, which has yet to be developed. HBASE-14070 Hybrid Logical Clocks for HBase

          • Major - Major loss of function.
          • Reopened

          Activity

            People

              Unassigned Unassigned
              enis Enis Soztutar
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: