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

Crash Event is not available for GSI System Events

    XMLWordPrintable

Details

    • 1

    Description

      None of the crash events are available for GSI System Events.

      EVENT NAME - EVENT ID

      IndexerCrash - 2051
      ProjectorCrash - 2052
      QueryClientCrash - 2053

       

      Attachments

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

        Activity

          hemant.rajput Hemant Rajput created issue -
          jeelan.poola Jeelan Poola made changes -
          Field Original Value New Value
          Assignee Sai Krishna Teja [ JIRAUSER25045 ] Amit Kulkarni [ amit.kulkarni ]

          Hemant Rajput,

          Do you have a cbcollect for this one ?

          amit.kulkarni Amit Kulkarni added a comment - Hemant Rajput , Do you have a cbcollect for this one ?
          amit.kulkarni Amit Kulkarni made changes -
          Assignee Amit Kulkarni [ amit.kulkarni ] Hemant Rajput [ hemant.rajput ]

          There is no cbcollect as the code block for mentioned event ids were not added. It's feature incomplete.

          hemant.rajput Hemant Rajput added a comment - There is no cbcollect as the code block for mentioned event ids were not added. It's feature incomplete.

          Hi Hemant Rajput

          As discussed on slack, These events are not listed in the PRD. Crash events in PRD means that if the Service starts and runs some processes without knowledge of the ns_server then it must log events when those child processes crash. In GSI we don't have any such child processes. So i like to call this improvement rather than feature incomplete. We just happened to reserve the EventIds for the same.

          Thanks
          Sai

          sai.teja Sai Krishna Teja added a comment - Hi Hemant Rajput As discussed on slack, These events are not listed in the PRD. Crash events in PRD means that if the Service starts and runs some processes without knowledge of the ns_server then it must log events when those child processes crash. In GSI we don't have any such child processes. So i like to call this improvement rather than feature incomplete. We just happened to reserve the EventIds for the same. Thanks Sai

          These events can be used by indexer when indexer is crashing due to un expected behaviour from user like invalid folder permissions or ports being used by other processes and etc.

          sai.teja Sai Krishna Teja added a comment - These events can be used by indexer when indexer is crashing due to un expected behaviour from user like invalid folder permissions or ports being used by other processes and etc.
          amit.kulkarni Amit Kulkarni made changes -
          Fix Version/s Neo [ 17615 ]
          Fix Version/s Morpheus [ 17651 ]
          amit.kulkarni Amit Kulkarni made changes -
          Assignee Hemant Rajput [ hemant.rajput ] Sai Krishna Teja [ JIRAUSER25045 ]
          amit.kulkarni Amit Kulkarni made changes -
          Is this a Regression? No [ 10451 ]
          Operating System Centos 64-bit [ 10020 ]
          Triage Untriaged [ 10351 ]
          Issue Type Bug [ 1 ] Task [ 3 ]

          People

            sai.teja Sai Krishna Teja
            hemant.rajput Hemant Rajput
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:

              Gerrit Reviews

                There are no open Gerrit changes

                PagerDuty