Uploaded image for project: 'Couchbase Server'
  1. Couchbase Server
  2. MB-41833

cbbackupmgr: logging to stdout should also log to the log file

    XMLWordPrintable

    Details

    • Triage:
      Triaged
    • Story Points:
      1
    • Is this a Regression?:
      Unknown

      Description

      Problem
      Logging to STDOUT does not log to the log files.

      Currently in Cloud we have to choose between logging to stdout or logging to a file. Being able to do both would provide a dual benefit in that we can troubleshoot using a log collection tool for backup jobs but also retain logs for the customer in their backup storage. We do not have access to those logs without customer intervention and by having the stdout we would remove the need to contact a customer.

      Expectation
      Logging should always happen to the files

      Set a stdout flag to add that functionality without removing the ability to still use the log file.

        Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

          pvarley Patrick Varley created issue -
          greg.lane Greg Lane (Inactive) made changes -
          Field Original Value New Value
          Description +Problem+
          Logging to STDOT does not log to the log files.

          +Expectation+
          Logging should always happen to the files
          +Problem+
           Logging to STDOT does not log to the log files.

          Currently in Cloud we have to choose between logging to stdout or logging to a file. Being able to do both would provide a dual benefit in that we can troubleshoot using a log collection tool for backup jobs but also retain logs for the customer in their backup storage. We do not have access to those logs without customer intervention and by having the stdout we would remove the need to contact a customer.

          +Expectation+
           Logging should always happen to the files

          Set a stdout flag to add that functionality without removing the ability to still use the log file.
          pvarley Patrick Varley made changes -
          Priority Major [ 3 ] Critical [ 2 ]
          james.lee James Lee made changes -
          Assignee Patrick Varley [ pvarley ] James Lee [ james.lee ]
          james.lee James Lee made changes -
          Status Open [ 1 ] In Progress [ 3 ]
          pvarley Patrick Varley made changes -
          Fix Version/s 6.6.1 [ 17002 ]
          pvarley Patrick Varley made changes -
          Link This issue is cloned by MB-42030 [ MB-42030 ]
          pvarley Patrick Varley made changes -
          Link This issue blocks CBSE-9055 [ CBSE-9055 ]
          pvarley Patrick Varley made changes -
          Link This issue is cloned by CBSE-9055 [ CBSE-9055 ]
          owend Daniel Owen made changes -
          Description +Problem+
           Logging to STDOT does not log to the log files.

          Currently in Cloud we have to choose between logging to stdout or logging to a file. Being able to do both would provide a dual benefit in that we can troubleshoot using a log collection tool for backup jobs but also retain logs for the customer in their backup storage. We do not have access to those logs without customer intervention and by having the stdout we would remove the need to contact a customer.

          +Expectation+
           Logging should always happen to the files

          Set a stdout flag to add that functionality without removing the ability to still use the log file.
          +Problem+
           Logging to STDOUT does not log to the log files.

          Currently in Cloud we have to choose between logging to stdout or logging to a file. Being able to do both would provide a dual benefit in that we can troubleshoot using a log collection tool for backup jobs but also retain logs for the customer in their backup storage. We do not have access to those logs without customer intervention and by having the stdout we would remove the need to contact a customer.

          +Expectation+
           Logging should always happen to the files

          Set a stdout flag to add that functionality without removing the ability to still use the log file.
          owend Daniel Owen made changes -
          Labels approved-for-6.6.1
          pvarley Patrick Varley made changes -
          Link This issue depends on MB-40528 [ MB-40528 ]
          Hide
          build-team Couchbase Build Team added a comment -

          Build couchbase-server-6.6.1-9128 contains backup commit eb28625 with commit message:
          MB-41833 When logging to stdout, also log to a log file

          Show
          build-team Couchbase Build Team added a comment - Build couchbase-server-6.6.1-9128 contains backup commit eb28625 with commit message: MB-41833 When logging to stdout, also log to a log file
          james.lee James Lee made changes -
          Assignee James Lee [ james.lee ] Patrick Varley [ pvarley ]
          Resolution Fixed [ 1 ]
          Status In Progress [ 3 ] Resolved [ 5 ]
          Hide
          build-team Couchbase Build Team added a comment -

          Build couchbase-server-7.0.0-3443 contains backup commit eb28625 with commit message:
          MB-41833 When logging to stdout, also log to a log file

          Show
          build-team Couchbase Build Team added a comment - Build couchbase-server-7.0.0-3443 contains backup commit eb28625 with commit message: MB-41833 When logging to stdout, also log to a log file
          james.lee James Lee made changes -
          Assignee Patrick Varley [ pvarley ] James Lee [ james.lee ]
          Resolution Fixed [ 1 ]
          Status Resolved [ 5 ] Reopened [ 4 ]
          james.lee James Lee made changes -
          Assignee James Lee [ james.lee ] Patrick Varley [ pvarley ]
          Resolution Fixed [ 1 ]
          Status Reopened [ 4 ] Resolved [ 5 ]
          Hide
          build-team Couchbase Build Team added a comment -

          Build couchbase-server-6.6.1-9140 contains backup commit 571126d with commit message:
          MB-41833 Switch order in which stderr is redirected

          Show
          build-team Couchbase Build Team added a comment - Build couchbase-server-6.6.1-9140 contains backup commit 571126d with commit message: MB-41833 Switch order in which stderr is redirected
          Hide
          build-team Couchbase Build Team added a comment -

          Build couchbase-server-7.0.0-3507 contains backup commit 571126d with commit message:
          MB-41833 Switch order in which stderr is redirected

          Show
          build-team Couchbase Build Team added a comment - Build couchbase-server-7.0.0-3507 contains backup commit 571126d with commit message: MB-41833 Switch order in which stderr is redirected
          Hide
          arunkumar Arunkumar Senthilnathan added a comment -

          Verified in 6.6.1-9151:

          backup:
          020-10-31T13:31:01.421-07:00 (Plan) Transfer of all data complete
          2020-10-31T13:31:01.423-07:00 (Stats) Stopping stat collection
          2020-10-31T13:31:01.423-07:00 (Cmd) Backup successfully completed
          2020-10-31T13:31:01.423-07:00 (Backup) Backed up bucket "travel-sample" succeeded
          2020-10-31T13:31:01.423-07:00 (Backup) Mutations backed up: 31591, Mutations failed to backup: 0
          2020-10-31T13:31:01.423-07:00 (Backup) Deletions backed up: 0, Deletions failed to backup: 0
          2020-10-31T13:31:01.423-07:00 (Backup) Skipped due to purge number or conflict resolution: Mutations: 0 Deletions: 0

          restore:
          2020-10-31T13:36:07.739-07:00 (Plan) Data transfer completed after 29.534072ms
          2020-10-31T13:36:07.739-07:00 (Plan)

          {"total_vbuckets":1024,"vbuckets_complete":1024,"bytes_received":28672,"failover_logs_received":1024,"complete":true,"errored":false}

          2020-10-31T13:36:07.739-07:00 (Plan) Transfer for cluster complete
          2020-10-31T13:36:07.739-07:00 (Plan) Transfer of all data complete
          2020-10-31T13:36:07.739-07:00 (Cmd) Restore bucket 'travel-sample' succeeded
          2020-10-31T13:36:07.739-07:00 (Cmd) Mutations restored: 0, Mutations failed to restore: 0
          2020-10-31T13:36:07.739-07:00 (Cmd) Deletions restored: 0, Deletions failed to restore: 0
          2020-10-31T13:36:07.739-07:00 (Cmd) Skipped due to purge number or conflict resolution: Mutations: 0 Deletions: 0
          2020-10-31T13:36:07.739-07:00 (Stats) Stopping stat collection
          2020-10-31T13:36:07.744-07:00 (Cmd) Restore completed successfully

          merge:
          2020-10-31T13:37:18.950-07:00 (Plan) Transfer for cluster complete
          2020-10-31T13:37:18.950-07:00 (Plan) Transfer of all data complete
          2020-10-31T13:37:18.951-07:00 (Merge) Merge bucket 'travel-sample' succeeded
          2020-10-31T13:37:18.951-07:00 (Merge) Mutations merged: 31591, Mutations failed to merged: 0
          2020-10-31T13:37:18.951-07:00 (Merge) Deletions merged: 0, Deletions failed to merged: 0

          Show
          arunkumar Arunkumar Senthilnathan added a comment - Verified in 6.6.1-9151: backup: 020-10-31T13:31:01.421-07:00 (Plan) Transfer of all data complete 2020-10-31T13:31:01.423-07:00 (Stats) Stopping stat collection 2020-10-31T13:31:01.423-07:00 (Cmd) Backup successfully completed 2020-10-31T13:31:01.423-07:00 (Backup) Backed up bucket "travel-sample" succeeded 2020-10-31T13:31:01.423-07:00 (Backup) Mutations backed up: 31591, Mutations failed to backup: 0 2020-10-31T13:31:01.423-07:00 (Backup) Deletions backed up: 0, Deletions failed to backup: 0 2020-10-31T13:31:01.423-07:00 (Backup) Skipped due to purge number or conflict resolution: Mutations: 0 Deletions: 0 restore: 2020-10-31T13:36:07.739-07:00 (Plan) Data transfer completed after 29.534072ms 2020-10-31T13:36:07.739-07:00 (Plan) {"total_vbuckets":1024,"vbuckets_complete":1024,"bytes_received":28672,"failover_logs_received":1024,"complete":true,"errored":false} 2020-10-31T13:36:07.739-07:00 (Plan) Transfer for cluster complete 2020-10-31T13:36:07.739-07:00 (Plan) Transfer of all data complete 2020-10-31T13:36:07.739-07:00 (Cmd) Restore bucket 'travel-sample' succeeded 2020-10-31T13:36:07.739-07:00 (Cmd) Mutations restored: 0, Mutations failed to restore: 0 2020-10-31T13:36:07.739-07:00 (Cmd) Deletions restored: 0, Deletions failed to restore: 0 2020-10-31T13:36:07.739-07:00 (Cmd) Skipped due to purge number or conflict resolution: Mutations: 0 Deletions: 0 2020-10-31T13:36:07.739-07:00 (Stats) Stopping stat collection 2020-10-31T13:36:07.744-07:00 (Cmd) Restore completed successfully merge: 2020-10-31T13:37:18.950-07:00 (Plan) Transfer for cluster complete 2020-10-31T13:37:18.950-07:00 (Plan) Transfer of all data complete 2020-10-31T13:37:18.951-07:00 (Merge) Merge bucket 'travel-sample' succeeded 2020-10-31T13:37:18.951-07:00 (Merge) Mutations merged: 31591, Mutations failed to merged: 0 2020-10-31T13:37:18.951-07:00 (Merge) Deletions merged: 0, Deletions failed to merged: 0
          arunkumar Arunkumar Senthilnathan made changes -
          Status Resolved [ 5 ] Closed [ 6 ]
          matt.carabine Matt Carabine made changes -
          Labels approved-for-6.6.1 DBaaS approved-for-6.6.1
          lynn.straus Lynn Straus made changes -
          Fix Version/s 7.0.0 [ 17233 ]
          lynn.straus Lynn Straus made changes -
          Fix Version/s Cheshire-Cat [ 15915 ]

            People

            Assignee:
            pvarley Patrick Varley
            Reporter:
            pvarley Patrick Varley
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Gerrit Reviews

                There are no open Gerrit changes

                  PagerDuty