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

[BP MB-44005 6.6.2] - Make DEFAULT_WINDOW_SIZE on eventing DCP connections configurable

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Critical
    • Resolution: Fixed
    • Cheshire-Cat, 6.6.1
    • 6.6.2
    • eventing
    • Untriaged
    • 1
    • Unknown

    Description

      Related to MB-40674.

      Attachments

        Issue Links

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

          Activity

            Ritam Sharma and Jeelan Poola this dial DCP_WINDOW even if we eventually change it CC.next to a smaller value wouldn't have detrimental impacts as Dave Rigby points out

            regardless of connection buffer size, the buffer can expand to fit the largest document sizes

            jon.strabala Jon Strabala added a comment - Ritam Sharma and Jeelan Poola this dial DCP_WINDOW even if we eventually change it CC.next to a smaller value wouldn't have detrimental impacts as Dave Rigby points out regardless of connection buffer size, the buffer  can  expand to fit the largest document sizes

            Ankit Prabhu can you please provide me how validate this issue?

            chanabasappa.ghali Chanabasappa Ghali added a comment - Ankit Prabhu  can you please provide me how validate this issue?

            Ankit Prabhu can let us know how to validate this issue?

            chanabasappa.ghali Chanabasappa Ghali added a comment - Ankit Prabhu  can let us know how to validate this issue?

            You can test that an undeployed or paused Eventing Function can get this setting, but I don't know how to read it from the DCP/KV side.

            First create an Eventign Function MYFUNC in the UI then try to read "dcp_window_size" it will be "null" or non existent.

            curl -X GET -s 'http://'${CB_USERNAME}:${CB_PASSWORD}'@localhost:8096/api/v1/functions/MYFUNC/settings' | jq .dcp_window_size
             
            null

            The default is added internally if it is never added to the function MYFUNC 20*1024*1024 or 20971520.  Now set it to something smaller say 80*1000 or 80000 this is 80K bytes.

            curl -X POST -d '{"deployment_status":false,"processing_status":false,"dcp_window_size":80000}' -s 'http://'${CB_USERNAME}:${CB_PASSWORD}'@localhost:8096/api/v1/functions/MYFUNC/settings'

            Now verify the Function definition has the setting we expect 80K or "80000".

            curl -X GET -s 'http://'${CB_USERNAME}:${CB_PASSWORD}'@localhost:8096/api/v1/functions/MYFUNC/settings' | jq 
            .dcp_window_size
             
            80000

            jon.strabala Jon Strabala added a comment - You can test that an undeployed or paused Eventing Function can get this setting, but I don't know how to read it from the DCP/KV side. First create an Eventign Function MYFUNC in the UI then try to read "dcp_window_size" it will be "null" or non existent. curl -X GET -s 'http://'${CB_USERNAME}:${CB_PASSWORD}'@localhost:8096/api/v1/functions/MYFUNC/settings' | jq .dcp_window_size   null The default is added internally if it is never added to the function MYFUNC 20*1024*1024 or 20971520.  Now set it to something smaller say 80*1000 or 80000 this is 80K bytes. curl -X POST -d '{"deployment_status":false,"processing_status":false,"dcp_window_size":80000}' -s 'http://'${CB_USERNAME}:${CB_PASSWORD}'@localhost:8096/api/v1/functions/MYFUNC/settings' Now verify the Function definition has the setting we expect 80K or "80000". curl -X GET -s 'http://'${CB_USERNAME}:${CB_PASSWORD}'@localhost:8096/api/v1/functions/MYFUNC/settings' | jq .dcp_window_size   80000

            followed above mentioned steps and was able to set required  dcp window size.

            chanabasappa.ghali Chanabasappa Ghali added a comment - followed above mentioned steps and was able to set required  dcp window size.

            People

              ankit.prabhu Ankit Prabhu
              jeelan.poola Jeelan Poola
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty