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

After Upgrade from 1.8.1.x to 2.0.0.x Keys do not get expired after expired time elapsed

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.0
    • Component/s: ns_server
    • Security Level: Public
    • Labels:
      None
    • Environment:

      Description

      After Upgrade from 1.8.1.x to 2.0.0.x Keys do not get expired after expired time elapsed

      Create 3 node cluster of 1.8.1.x nodes
      Create 1 default bucket and other as SASL bucket
      Load data time on default with no expiration while on SASL bucket with expiration set to 5 minutes
      Upgrade one node to 2.0.0.x.
      Verify whether items get expired after 5 minutes or not.
      Keys stays there even after expired time elapsed

      1. 10.3.121.103-8091-diag.txt.gz
        4.98 MB
        Rohit
      2. 10.3.121.39-8091-diag.txt.gz
        9.64 MB
        Rohit
      3. 10.3.121.42-8091-diag.txt.gz
        8.37 MB
        Rohit
      No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

        Hide
        alkondratenko Aleksey Kondratenko (Inactive) added a comment -

        Either bug in Steve's tools or in ep-engine

        Show
        alkondratenko Aleksey Kondratenko (Inactive) added a comment - Either bug in Steve's tools or in ep-engine
        Hide
        steve Steve Yen added a comment -

        Hi Bin,
        I'm thinking this is likely in the pump_mbf / cbtransfer code, where it's not handling the expiration field values correctly.

        Show
        steve Steve Yen added a comment - Hi Bin, I'm thinking this is likely in the pump_mbf / cbtransfer code, where it's not handling the expiration field values correctly.
        Hide
        bcui Bin Cui added a comment -

        on Ubuntu setup, I installed 1.8.1 release, populated 1000 items with expiration time as 5 minutes. Then upgrade to 2.0.0 release.
        After 5 min, i won't be able to get the expired item. and UI refreshes item count from 1000 to 999.

        Chisheng has a more detailed description regarding how to check if items are expired in a more accurate way.

        See MB-6575.

        Show
        bcui Bin Cui added a comment - on Ubuntu setup, I installed 1.8.1 release, populated 1000 items with expiration time as 5 minutes. Then upgrade to 2.0.0 release. After 5 min, i won't be able to get the expired item. and UI refreshes item count from 1000 to 999. Chisheng has a more detailed description regarding how to check if items are expired in a more accurate way. See MB-6575 .
        Hide
        Rohit Rohit Sinha (Inactive) added a comment -

        Hi Bin, didnt get the comment, as you stated that you had loaded 1000 items with expiration of 5 minutes and after 5 minutes the item count reduced to 999 which is reduced by only 1 count isn't the item count should be zero now on UI after expiration.

        Show
        Rohit Rohit Sinha (Inactive) added a comment - Hi Bin, didnt get the comment, as you stated that you had loaded 1000 items with expiration of 5 minutes and after 5 minutes the item count reduced to 999 which is reduced by only 1 count isn't the item count should be zero now on UI after expiration.
        Hide
        bcui Bin Cui added a comment -

        Oh, my comment was not quite clear. After 5 minutes, i used get command to retrieve a key, and the key was not not found, and the total item number was reduced by one, which means the item was expired as expected. But other expired items hadn't been picked up and processed by the flusher pager yet, which was running within ep-engine to periodically process expired items. You can run requests from command line to ask the pager to clean up those expired items, as steps described in mb-6575.

        Show
        bcui Bin Cui added a comment - Oh, my comment was not quite clear. After 5 minutes, i used get command to retrieve a key, and the key was not not found, and the total item number was reduced by one, which means the item was expired as expected. But other expired items hadn't been picked up and processed by the flusher pager yet, which was running within ep-engine to periodically process expired items. You can run requests from command line to ask the pager to clean up those expired items, as steps described in mb-6575.
        Hide
        Chisheng Chisheng Hong (Inactive) added a comment -

        2012-10-17 20:28:16,023 - root - INFO - running command.raw /opt/couchbase/bin/cbepctl 10.3.3.21:11210 -b bucket0 -p "password" set flush_param exp_pager_stime 5
        2012-10-17 20:28:16,033 - paramiko.transport - INFO - Secsh channel 51 opened.
        2012-10-17 20:28:16,101 - root - INFO - command executed successfully
        2012-10-17 20:28:16,101 - root - INFO - setting param: exp_pager_stime 5
        2012-10-17 20:28:16,102 - root - INFO - set exp_pager_stime to 5

        We should run the above command and then check whether those items have expired or not. Actually they will expire when I check with build 1862. You can also see it on jenkins: http://qa.hq.northscale.net/job/centos-64-2.0-upgrade/. We have some test cases to verify expiration.

        Show
        Chisheng Chisheng Hong (Inactive) added a comment - 2012-10-17 20:28:16,023 - root - INFO - running command.raw /opt/couchbase/bin/cbepctl 10.3.3.21:11210 -b bucket0 -p "password" set flush_param exp_pager_stime 5 2012-10-17 20:28:16,033 - paramiko.transport - INFO - Secsh channel 51 opened. 2012-10-17 20:28:16,101 - root - INFO - command executed successfully 2012-10-17 20:28:16,101 - root - INFO - setting param: exp_pager_stime 5 2012-10-17 20:28:16,102 - root - INFO - set exp_pager_stime to 5 We should run the above command and then check whether those items have expired or not. Actually they will expire when I check with build 1862. You can also see it on jenkins: http://qa.hq.northscale.net/job/centos-64-2.0-upgrade/ . We have some test cases to verify expiration.

          People

          • Assignee:
            bcui Bin Cui
            Reporter:
            Rohit Rohit Sinha (Inactive)
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Gerrit Reviews

              There are no open Gerrit changes