Uploaded image for project: 'Apache Ozone'
  1. Apache Ozone
  2. HDDS-2866

Intermittent failure in TestOzoneManagerRocksDBLogging

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.5.0
    • Component/s: test
    • Target Version/s:

      Description

      TestOzoneManagerRocksDBLogging fails intermittently. I think the problem is that RocksDB-specific string may appear in the log in the Finalizer thread after after OM is shutdown and restarted in Thread-1:

      output
      2020-01-09 16:17:29,372 [Thread-1] INFO  rocksdb.RocksDB (DBStoreBuilder.java:log(228)) - [/db_impl.cc:390] Shutdown: canceling all background work
      2020-01-09 16:17:29,373 [Thread-1] INFO  rocksdb.RocksDB (DBStoreBuilder.java:log(228)) - [/db_impl.cc:563] Shutdown complete
      2020-01-09 16:17:29,373 [Thread-1] INFO  om.OzoneManager (OzoneManager.java:restart(1127)) - OzoneManager RPC server is listening at localhost/127.0.0.1:33899
      ...
      2020-01-09 16:17:29,561 [Thread-1] INFO  server.BaseHttpServer (BaseHttpServer.java:updateConnectorAddress(216)) - HTTP server of ozoneManager listening at http://0.0.0.0:34495
      ...
      2020-01-09 16:17:37,988 [Finalizer] INFO  rocksdb.RocksDB (DBStoreBuilder.java:log(228)) - [/db_impl.cc:390] Shutdown: canceling all background work
      2020-01-09 16:17:37,989 [Finalizer] INFO  rocksdb.RocksDB (DBStoreBuilder.java:log(228)) - [/db_impl.cc:563] Shutdown complete
      

      Swapping the order of tests (ie. running with logging disabled first) would guarantee that stray messages from the logger do not affect it.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                adoroszlai Attila Doroszlai
                Reporter:
                adoroszlai Attila Doroszlai
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 20m
                  20m