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

[Cbbackupmgr] Activity monitor not logging inactivity

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Minor
    • Resolution: Not a Bug
    • 6.6.1
    • 7.0.0
    • tools
    • 6.6.1 build 9147
    • Untriaged
    • 1
    • Unknown

    Description

      Description:

      The activity monitor does not appear to be logging inactivity.

      Steps to reproduce:

      1. Set CB_DCP_ACTIVITY_MONITOR_FREQUENCY equal to 5 seconds
      2. Start a backup asynchronously.
      3. When ' DCP ' is spotted in the logs repeat the following 5 times:
        1. pause the memcached process for a total of 7 seconds by sending a SIGSTOP.
        2. Unpause memcached by sending a SIGCONT.
      4. Scan the logs for the inactivity message.

      What happens:

      In 6.6.1-9174, the inactivity message is not present in the backup logs. 

      However, in 7.0.0-3583, the inactivity message is present:

      2020-11-09T15:42:35.583+00:00 WARN: (DCP) (default) (vb 153) Stream has been inactive for 5s, last seqno 112 -- couchbase.(*DCPAsyncWorker).monitorActivity.func1() at dcp_async_worker.go:247
      2020-11-09T15:42:35.583+00:00 WARN: (DCP) (default) (vb 167) Stream has been inactive for 5s, last seqno 113 -- couchbase.(*DCPAsyncWorker).monitorActivity.func1() at dcp_async_worker.go:247
      2020-11-09T15:42:35.583+00:00 WARN: (DCP) (default) (vb 209) Stream has been inactive for 5s, last seqno 112 -- couchbase.(*DCPAsyncWorker).monitorActivity.func1() at dcp_async_worker.go:247
      2020-11-09T15:42:35.583+00:00 WARN: (DCP) (default) (vb 223) Stream has been inactive for 5s, last seqno 112 -- couchbase.(*DCPAsyncWorker).monitorActivity.func1() at dcp_async_worker.go:247
      

      What I expected to happen:

      I expected the equivalent message to be present in the 6.6.1-9174. backup logs.

       

      Logs for 7.0.0: 

      cbbackupmgr-collectinfo-entbackup_10.112.210.101-2020-11-09T154345.zip

      [^collectinfo-2020-11-09T154308-ns_1@cb.local.zip]

      Logs for 6.6.1: 

      cbbackupmgr-collectinfo-entbackup_10.112.202.101-2020-11-09T160246.zip

      [^collectinfo-2020-11-09T160228-ns_1@cb.local.zip]

       

       

      Attachments

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

        Activity

          asad.zaidi Asad Zaidi (Inactive) created issue -
          asad.zaidi Asad Zaidi (Inactive) made changes -
          Field Original Value New Value
          Description *Description:*

          The activity monitor does not appear to be logging inactivity.

          *Steps to reproduce:*

           
           # Set CB_DCP_ACTIVITY_MONITOR_FREQUENCY equal to 5 seconds
           # Start a backup asynchronously.
           # When ' DCP ' is spotted in the logs repeat the following 5 times:
           ## pause the memcached process for a total of 7 seconds by sending a SIGSTOP.
           ## Unpause memcached by sending a SIGCONT.
           # Scan the logs for the inactivity message.

          *What happens:*

          In 6.6.1-9174, the inactivity message is not present in the backup logs.

          However, in 7.0.0-3583, the inactivity message is present.

           
          {code:java}
          2020-11-09T15:42:35.583+00:00 WARN: (DCP) (default) (vb 153) Stream has been inactive for 5s, last seqno 112 -- couchbase.(*DCPAsyncWorker).monitorActivity.func1() at dcp_async_worker.go:247
          2020-11-09T15:42:35.583+00:00 WARN: (DCP) (default) (vb 167) Stream has been inactive for 5s, last seqno 113 -- couchbase.(*DCPAsyncWorker).monitorActivity.func1() at dcp_async_worker.go:247
          2020-11-09T15:42:35.583+00:00 WARN: (DCP) (default) (vb 209) Stream has been inactive for 5s, last seqno 112 -- couchbase.(*DCPAsyncWorker).monitorActivity.func1() at dcp_async_worker.go:247
          2020-11-09T15:42:35.583+00:00 WARN: (DCP) (default) (vb 223) Stream has been inactive for 5s, last seqno 112 -- couchbase.(*DCPAsyncWorker).monitorActivity.func1() at dcp_async_worker.go:247
          {code}
          *What I expected to happen:*

          I expected the equivalent message to be present in the 6.6.1-9174. backup logs.
          *Description:*

          The activity monitor does not appear to be logging inactivity.

          *Steps to reproduce:*
           # Set CB_DCP_ACTIVITY_MONITOR_FREQUENCY equal to 5 seconds
           # Start a backup asynchronously.
           # When ' DCP ' is spotted in the logs repeat the following 5 times:
           ## pause the memcached process for a total of 7 seconds by sending a SIGSTOP.
           ## Unpause memcached by sending a SIGCONT.
           # Scan the logs for the inactivity message.

          *What happens:*

          In 6.6.1-9174, the inactivity message is not present in the backup logs.

          However, in 7.0.0-3583, the inactivity message is present.

           
          {code:java}2020-11-09T15:42:35.583+00:00 WARN: (DCP) (default) (vb 153) Stream has been inactive for 5s, last seqno 112 -- couchbase.(*DCPAsyncWorker).monitorActivity.func1() at dcp_async_worker.go:247
          2020-11-09T15:42:35.583+00:00 WARN: (DCP) (default) (vb 167) Stream has been inactive for 5s, last seqno 113 -- couchbase.(*DCPAsyncWorker).monitorActivity.func1() at dcp_async_worker.go:247
          2020-11-09T15:42:35.583+00:00 WARN: (DCP) (default) (vb 209) Stream has been inactive for 5s, last seqno 112 -- couchbase.(*DCPAsyncWorker).monitorActivity.func1() at dcp_async_worker.go:247
          2020-11-09T15:42:35.583+00:00 WARN: (DCP) (default) (vb 223) Stream has been inactive for 5s, last seqno 112 -- couchbase.(*DCPAsyncWorker).monitorActivity.func1() at dcp_async_worker.go:247
          {code}
          *What I expected to happen:*

          I expected the equivalent message to be present in the 6.6.1-9174. backup logs.
          asad.zaidi Asad Zaidi (Inactive) made changes -
          Description *Description:*

          The activity monitor does not appear to be logging inactivity.

          *Steps to reproduce:*
           # Set CB_DCP_ACTIVITY_MONITOR_FREQUENCY equal to 5 seconds
           # Start a backup asynchronously.
           # When ' DCP ' is spotted in the logs repeat the following 5 times:
           ## pause the memcached process for a total of 7 seconds by sending a SIGSTOP.
           ## Unpause memcached by sending a SIGCONT.
           # Scan the logs for the inactivity message.

          *What happens:*

          In 6.6.1-9174, the inactivity message is not present in the backup logs.

          However, in 7.0.0-3583, the inactivity message is present.

           
          {code:java}2020-11-09T15:42:35.583+00:00 WARN: (DCP) (default) (vb 153) Stream has been inactive for 5s, last seqno 112 -- couchbase.(*DCPAsyncWorker).monitorActivity.func1() at dcp_async_worker.go:247
          2020-11-09T15:42:35.583+00:00 WARN: (DCP) (default) (vb 167) Stream has been inactive for 5s, last seqno 113 -- couchbase.(*DCPAsyncWorker).monitorActivity.func1() at dcp_async_worker.go:247
          2020-11-09T15:42:35.583+00:00 WARN: (DCP) (default) (vb 209) Stream has been inactive for 5s, last seqno 112 -- couchbase.(*DCPAsyncWorker).monitorActivity.func1() at dcp_async_worker.go:247
          2020-11-09T15:42:35.583+00:00 WARN: (DCP) (default) (vb 223) Stream has been inactive for 5s, last seqno 112 -- couchbase.(*DCPAsyncWorker).monitorActivity.func1() at dcp_async_worker.go:247
          {code}
          *What I expected to happen:*

          I expected the equivalent message to be present in the 6.6.1-9174. backup logs.
          *Description:*

          The activity monitor does not appear to be logging inactivity.

          *Steps to reproduce:*
           # Set CB_DCP_ACTIVITY_MONITOR_FREQUENCY equal to 5 seconds
           # Start a backup asynchronously.
           # When ' DCP ' is spotted in the logs repeat the following 5 times:
           ## pause the memcached process for a total of 7 seconds by sending a SIGSTOP.
           ## Unpause memcached by sending a SIGCONT.
           # Scan the logs for the inactivity message.

          *What happens:*

          In 6.6.1-9174, the inactivity message is not present in the backup logs. 

          However, in 7.0.0-3583, the inactivity message is present:
          {code:java}2020-11-09T15:42:35.583+00:00 WARN: (DCP) (default) (vb 153) Stream has been inactive for 5s, last seqno 112 -- couchbase.(*DCPAsyncWorker).monitorActivity.func1() at dcp_async_worker.go:247
          2020-11-09T15:42:35.583+00:00 WARN: (DCP) (default) (vb 167) Stream has been inactive for 5s, last seqno 113 -- couchbase.(*DCPAsyncWorker).monitorActivity.func1() at dcp_async_worker.go:247
          2020-11-09T15:42:35.583+00:00 WARN: (DCP) (default) (vb 209) Stream has been inactive for 5s, last seqno 112 -- couchbase.(*DCPAsyncWorker).monitorActivity.func1() at dcp_async_worker.go:247
          2020-11-09T15:42:35.583+00:00 WARN: (DCP) (default) (vb 223) Stream has been inactive for 5s, last seqno 112 -- couchbase.(*DCPAsyncWorker).monitorActivity.func1() at dcp_async_worker.go:247
          {code}
          *What I expected to happen:*

          I expected the equivalent message to be present in the 6.6.1-9174. backup logs.

           

          Included:

          Backup logs for 6.6.1: 
          asad.zaidi Asad Zaidi (Inactive) made changes -
          Description *Description:*

          The activity monitor does not appear to be logging inactivity.

          *Steps to reproduce:*
           # Set CB_DCP_ACTIVITY_MONITOR_FREQUENCY equal to 5 seconds
           # Start a backup asynchronously.
           # When ' DCP ' is spotted in the logs repeat the following 5 times:
           ## pause the memcached process for a total of 7 seconds by sending a SIGSTOP.
           ## Unpause memcached by sending a SIGCONT.
           # Scan the logs for the inactivity message.

          *What happens:*

          In 6.6.1-9174, the inactivity message is not present in the backup logs. 

          However, in 7.0.0-3583, the inactivity message is present:
          {code:java}2020-11-09T15:42:35.583+00:00 WARN: (DCP) (default) (vb 153) Stream has been inactive for 5s, last seqno 112 -- couchbase.(*DCPAsyncWorker).monitorActivity.func1() at dcp_async_worker.go:247
          2020-11-09T15:42:35.583+00:00 WARN: (DCP) (default) (vb 167) Stream has been inactive for 5s, last seqno 113 -- couchbase.(*DCPAsyncWorker).monitorActivity.func1() at dcp_async_worker.go:247
          2020-11-09T15:42:35.583+00:00 WARN: (DCP) (default) (vb 209) Stream has been inactive for 5s, last seqno 112 -- couchbase.(*DCPAsyncWorker).monitorActivity.func1() at dcp_async_worker.go:247
          2020-11-09T15:42:35.583+00:00 WARN: (DCP) (default) (vb 223) Stream has been inactive for 5s, last seqno 112 -- couchbase.(*DCPAsyncWorker).monitorActivity.func1() at dcp_async_worker.go:247
          {code}
          *What I expected to happen:*

          I expected the equivalent message to be present in the 6.6.1-9174. backup logs.

           

          Included:

          Backup logs for 6.6.1: 
          *Description:*

          The activity monitor does not appear to be logging inactivity.

          *Steps to reproduce:*
           # Set CB_DCP_ACTIVITY_MONITOR_FREQUENCY equal to 5 seconds
           # Start a backup asynchronously.
           # When ' DCP ' is spotted in the logs repeat the following 5 times:
           ## pause the memcached process for a total of 7 seconds by sending a SIGSTOP.
           ## Unpause memcached by sending a SIGCONT.
           # Scan the logs for the inactivity message.

          *What happens:*

          In 6.6.1-9174, the inactivity message is not present in the backup logs. 

          However, in 7.0.0-3583, the inactivity message is present:
          {code:java}2020-11-09T15:42:35.583+00:00 WARN: (DCP) (default) (vb 153) Stream has been inactive for 5s, last seqno 112 -- couchbase.(*DCPAsyncWorker).monitorActivity.func1() at dcp_async_worker.go:247
          2020-11-09T15:42:35.583+00:00 WARN: (DCP) (default) (vb 167) Stream has been inactive for 5s, last seqno 113 -- couchbase.(*DCPAsyncWorker).monitorActivity.func1() at dcp_async_worker.go:247
          2020-11-09T15:42:35.583+00:00 WARN: (DCP) (default) (vb 209) Stream has been inactive for 5s, last seqno 112 -- couchbase.(*DCPAsyncWorker).monitorActivity.func1() at dcp_async_worker.go:247
          2020-11-09T15:42:35.583+00:00 WARN: (DCP) (default) (vb 223) Stream has been inactive for 5s, last seqno 112 -- couchbase.(*DCPAsyncWorker).monitorActivity.func1() at dcp_async_worker.go:247
          {code}
          *What I expected to happen:*

          I expected the equivalent message to be present in the 6.6.1-9174. backup logs.

           

          Logs:

          Logs for 7.0.0: 

          [^cbbackupmgr-collectinfo-entbackup_10.112.210.101-2020-11-09T154345.zip]

          [^collectinfo-2020-11-09T154308-ns_1@cb.local.zip]

          Logs for 6.6.1: 

          [^cbbackupmgr-collectinfo-entbackup_10.112.202.101-2020-11-09T160246.zip]

          [^collectinfo-2020-11-09T160228-ns_1@cb.local.zip]

           

           
          asad.zaidi Asad Zaidi (Inactive) made changes -
          Description *Description:*

          The activity monitor does not appear to be logging inactivity.

          *Steps to reproduce:*
           # Set CB_DCP_ACTIVITY_MONITOR_FREQUENCY equal to 5 seconds
           # Start a backup asynchronously.
           # When ' DCP ' is spotted in the logs repeat the following 5 times:
           ## pause the memcached process for a total of 7 seconds by sending a SIGSTOP.
           ## Unpause memcached by sending a SIGCONT.
           # Scan the logs for the inactivity message.

          *What happens:*

          In 6.6.1-9174, the inactivity message is not present in the backup logs. 

          However, in 7.0.0-3583, the inactivity message is present:
          {code:java}2020-11-09T15:42:35.583+00:00 WARN: (DCP) (default) (vb 153) Stream has been inactive for 5s, last seqno 112 -- couchbase.(*DCPAsyncWorker).monitorActivity.func1() at dcp_async_worker.go:247
          2020-11-09T15:42:35.583+00:00 WARN: (DCP) (default) (vb 167) Stream has been inactive for 5s, last seqno 113 -- couchbase.(*DCPAsyncWorker).monitorActivity.func1() at dcp_async_worker.go:247
          2020-11-09T15:42:35.583+00:00 WARN: (DCP) (default) (vb 209) Stream has been inactive for 5s, last seqno 112 -- couchbase.(*DCPAsyncWorker).monitorActivity.func1() at dcp_async_worker.go:247
          2020-11-09T15:42:35.583+00:00 WARN: (DCP) (default) (vb 223) Stream has been inactive for 5s, last seqno 112 -- couchbase.(*DCPAsyncWorker).monitorActivity.func1() at dcp_async_worker.go:247
          {code}
          *What I expected to happen:*

          I expected the equivalent message to be present in the 6.6.1-9174. backup logs.

           

          Logs:

          Logs for 7.0.0: 

          [^cbbackupmgr-collectinfo-entbackup_10.112.210.101-2020-11-09T154345.zip]

          [^collectinfo-2020-11-09T154308-ns_1@cb.local.zip]

          Logs for 6.6.1: 

          [^cbbackupmgr-collectinfo-entbackup_10.112.202.101-2020-11-09T160246.zip]

          [^collectinfo-2020-11-09T160228-ns_1@cb.local.zip]

           

           
          *Description:*

          The activity monitor does not appear to be logging inactivity.

          *Steps to reproduce:*
           # Set CB_DCP_ACTIVITY_MONITOR_FREQUENCY equal to 5 seconds
           # Start a backup asynchronously.
           # When ' DCP ' is spotted in the logs repeat the following 5 times:
           ## pause the memcached process for a total of 7 seconds by sending a SIGSTOP.
           ## Unpause memcached by sending a SIGCONT.
           # Scan the logs for the inactivity message.

          *What happens:*

          In 6.6.1-9174, the inactivity message is not present in the backup logs. 

          However, in 7.0.0-3583, the inactivity message is present:
          {code:java}2020-11-09T15:42:35.583+00:00 WARN: (DCP) (default) (vb 153) Stream has been inactive for 5s, last seqno 112 -- couchbase.(*DCPAsyncWorker).monitorActivity.func1() at dcp_async_worker.go:247
          2020-11-09T15:42:35.583+00:00 WARN: (DCP) (default) (vb 167) Stream has been inactive for 5s, last seqno 113 -- couchbase.(*DCPAsyncWorker).monitorActivity.func1() at dcp_async_worker.go:247
          2020-11-09T15:42:35.583+00:00 WARN: (DCP) (default) (vb 209) Stream has been inactive for 5s, last seqno 112 -- couchbase.(*DCPAsyncWorker).monitorActivity.func1() at dcp_async_worker.go:247
          2020-11-09T15:42:35.583+00:00 WARN: (DCP) (default) (vb 223) Stream has been inactive for 5s, last seqno 112 -- couchbase.(*DCPAsyncWorker).monitorActivity.func1() at dcp_async_worker.go:247
          {code}
          *What I expected to happen:*

          I expected the equivalent message to be present in the 6.6.1-9174. backup logs.

           

          Logs for 7.0.0: 

          [^cbbackupmgr-collectinfo-entbackup_10.112.210.101-2020-11-09T154345.zip]

          [^collectinfo-2020-11-09T154308-ns_1@cb.local.zip]

          Logs for 6.6.1: 

          [^cbbackupmgr-collectinfo-entbackup_10.112.202.101-2020-11-09T160246.zip]

          [^collectinfo-2020-11-09T160228-ns_1@cb.local.zip]

           

           
          asad.zaidi Asad Zaidi (Inactive) made changes -
          Description *Description:*

          The activity monitor does not appear to be logging inactivity.

          *Steps to reproduce:*
           # Set CB_DCP_ACTIVITY_MONITOR_FREQUENCY equal to 5 seconds
           # Start a backup asynchronously.
           # When ' DCP ' is spotted in the logs repeat the following 5 times:
           ## pause the memcached process for a total of 7 seconds by sending a SIGSTOP.
           ## Unpause memcached by sending a SIGCONT.
           # Scan the logs for the inactivity message.

          *What happens:*

          In 6.6.1-9174, the inactivity message is not present in the backup logs. 

          However, in 7.0.0-3583, the inactivity message is present:
          {code:java}2020-11-09T15:42:35.583+00:00 WARN: (DCP) (default) (vb 153) Stream has been inactive for 5s, last seqno 112 -- couchbase.(*DCPAsyncWorker).monitorActivity.func1() at dcp_async_worker.go:247
          2020-11-09T15:42:35.583+00:00 WARN: (DCP) (default) (vb 167) Stream has been inactive for 5s, last seqno 113 -- couchbase.(*DCPAsyncWorker).monitorActivity.func1() at dcp_async_worker.go:247
          2020-11-09T15:42:35.583+00:00 WARN: (DCP) (default) (vb 209) Stream has been inactive for 5s, last seqno 112 -- couchbase.(*DCPAsyncWorker).monitorActivity.func1() at dcp_async_worker.go:247
          2020-11-09T15:42:35.583+00:00 WARN: (DCP) (default) (vb 223) Stream has been inactive for 5s, last seqno 112 -- couchbase.(*DCPAsyncWorker).monitorActivity.func1() at dcp_async_worker.go:247
          {code}
          *What I expected to happen:*

          I expected the equivalent message to be present in the 6.6.1-9174. backup logs.

           

          Logs for 7.0.0: 

          [^cbbackupmgr-collectinfo-entbackup_10.112.210.101-2020-11-09T154345.zip]

          [^collectinfo-2020-11-09T154308-ns_1@cb.local.zip]

          Logs for 6.6.1: 

          [^cbbackupmgr-collectinfo-entbackup_10.112.202.101-2020-11-09T160246.zip]

          [^collectinfo-2020-11-09T160228-ns_1@cb.local.zip]

           

           
          *Description:*

          The activity monitor does not appear to be logging inactivity.

          *Steps to reproduce:*
           # Set CB_DCP_ACTIVITY_MONITOR_FREQUENCY equal to 5 seconds
           # Start a backup asynchronously.
           # When ' DCP ' is spotted in the logs repeat the following 5 times:
           ## pause the memcached process for a total of 7 seconds by sending a SIGSTOP.
           ## Unpause memcached by sending a SIGCONT.
           # Scan the logs for the inactivity message.

          *What happens:*

          In 6.6.1-9174, the inactivity message is not present in the backup logs. 

          However, in 7.0.0-3583, the inactivity message is present:
          {code:noformat}
          2020-11-09T15:42:35.583+00:00 WARN: (DCP) (default) (vb 153) Stream has been inactive for 5s, last seqno 112 -- couchbase.(*DCPAsyncWorker).monitorActivity.func1() at dcp_async_worker.go:247
          2020-11-09T15:42:35.583+00:00 WARN: (DCP) (default) (vb 167) Stream has been inactive for 5s, last seqno 113 -- couchbase.(*DCPAsyncWorker).monitorActivity.func1() at dcp_async_worker.go:247
          2020-11-09T15:42:35.583+00:00 WARN: (DCP) (default) (vb 209) Stream has been inactive for 5s, last seqno 112 -- couchbase.(*DCPAsyncWorker).monitorActivity.func1() at dcp_async_worker.go:247
          2020-11-09T15:42:35.583+00:00 WARN: (DCP) (default) (vb 223) Stream has been inactive for 5s, last seqno 112 -- couchbase.(*DCPAsyncWorker).monitorActivity.func1() at dcp_async_worker.go:247
          {code}
          *What I expected to happen:*

          I expected the equivalent message to be present in the 6.6.1-9174. backup logs.

           

          Logs for 7.0.0: 

          [^cbbackupmgr-collectinfo-entbackup_10.112.210.101-2020-11-09T154345.zip]

          [^collectinfo-2020-11-09T154308-ns_1@cb.local.zip]

          Logs for 6.6.1: 

          [^cbbackupmgr-collectinfo-entbackup_10.112.202.101-2020-11-09T160246.zip]

          [^collectinfo-2020-11-09T160228-ns_1@cb.local.zip]

           

           
          asad.zaidi Asad Zaidi (Inactive) made changes -
          Labels backup
          james.lee James Lee made changes -
          Assignee James Lee [ james.lee ] Asad Zaidi [ JIRAUSER25025 ]
          james.lee James Lee made changes -
          wayne Wayne Siu made changes -
          Fix Version/s Cheshire-Cat [ 15915 ]
          asad.zaidi Asad Zaidi (Inactive) made changes -
          Resolution Not a Bug [ 10200 ]
          Status Open [ 1 ] Closed [ 6 ]
          mihir.kamdar Mihir Kamdar (Inactive) made changes -
          Labels backup backup manual_testing
          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

            asad.zaidi Asad Zaidi (Inactive)
            asad.zaidi Asad Zaidi (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Gerrit Reviews

                There are no open Gerrit changes

                PagerDuty