Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-744

archive thread finds open log file and aborts

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:

      Description

      While playing around with the fine-grained-durability branch and the txn test, I ran 'wt printlog' on one of the database home dirs and that took an assertion failure. 

      %  ./wt -h WT_TEST/test_txn02.1 printlog
      		 
      [
      		 
        { "lsn" : [1,128],
      		 
          "type" : 3,
      		 
          "txnid" : 1,
      		 
      archive-server: ../src/os_posix/os_remove.c, 35: fh == NULL
      		 
      archive-server: aborting WiredTiger library
      		 
      ...

      Here's the stack:

      (gdb) bt
      		 
      #0  0x00007fff93ba0322 in select$DARWIN_EXTSN ()
      		 
      WT-1  0x000000010787f679 in __wt_sleep (seconds=100, micro_seconds=0) at os_sleep.c:22
      		 
      WT-2  0x00000001078a4363 in __wt_attach (session=0x7ff911004c20) at global.c:105
      		 
      WT-3  0x000000010787b032 in __wt_abort (session=0x7ff911004c20) at os_abort.c:21
      		 
      WT-4  0x00000001078a3b64 in __wt_assert (session=0x7ff911004c20, error=0, file_name=0x1078bbb43 "../src/os_posix/os_remove.c", line_number=35, fmt=0x1078b5180 "%s") at err.c:438
      		 
      WT-5  0x000000010787eed2 in __remove_file_check (session=0x7ff911004c20, name=0x7ff910c09d30 "WiredTigerLog.0000000001") at os_remove.c:35
      		 
      WT-6  0x000000010787ec7b in __wt_remove (session=0x7ff911004c20, name=0x7ff910c09d30 "WiredTigerLog.0000000001") at os_remove.c:54
      		 
      WT-7  0x0000000107861947 in __wt_log_remove (session=0x7ff911004c20, lognum=1) at log.c:151
      		 
      WT-8  0x0000000107844f03 in __log_archive_server (arg=0x7ff911004c20) at conn_log.c:118
      		 
      WT-9  0x00007fff95f5e7a2 in _pthread_start ()
      		 
      WT-10 0x00007fff95f4b1e1 in thread_start ()

      Clearly the wt printlog has the log file open as it reads the log.

      I think the fix is that wt should disable archiving when it opens the connection.

        Attachments

          Issue Links

          is related to

          Task - A task that needs to be done. WT-746 Don't truncate files when running "wt" on a database with logging

          • Closed
          related to

          Task - A task that needs to be done. WT-1 placeholder WT-1

          • Closed

          Task - A task that needs to be done. WT-2 What does metadata look like?

          • Closed

          Task - A task that needs to be done. WT-3 What file formats are required?

          • Closed

          Task - A task that needs to be done. WT-4 Flexible cursor traversals

          • Closed

          Task - A task that needs to be done. WT-5 How does pget work: is it necessary?

          • Closed

          Task - A task that needs to be done. WT-6 Complex schema example

          • Closed

          Task - A task that needs to be done. WT-7 Do we need the handle->err/errx methods?

          • Closed

          Task - A task that needs to be done. WT-8 Do we need table load, bulk-load and/or dump methods?

          • Closed

          Task - A task that needs to be done. WT-9 Does adding schema need to be transactional?

          • Closed

          Task - A task that needs to be done. WT-10 Basic "getting started" tutorial

          • Closed

            Activity

              People

              • Assignee:
                sue.loverso Sue LoVerso
                Reporter:
                sue.loverso Sue LoVerso
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: