sailfin
  1. sailfin
  2. SAILFIN-1727

[umbrella] 24x1/7 Subscribe Refresh with failure injection

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: 2.0
    • Fix Version/s: milestone 1
    • Component/s: session_replication
    • Labels:
      None
    • Environment:

      Operating System: Linux
      Platform: Other

    • Issuezilla Id:
      1,727

      Description

      ******************************************************************************************************

      • Template v0.1 ( 05/01/08 )
      • Sailfin Stress test issue
        ******************************************************************************************************
        Sailfin Build : 10
        Cluster size : 10
        Happens in a single instance (y/n) ? : NA
        Test id : st2_4_presence_subscribe-refresh
        Location of the test : as-telco-sqe/stress-ws/presence
        JDK version : 64 bit - 1.6.0_07
        CLB used : Yes
        HW LB used : No.
        SSR: Enabled

      Started 9 SIPp clients with the following command to effectively get 300cps per
      instance in the 10 instance cluster.

      sipp command :
      sipp -t t1 -sf st2_4_presence_subscribe-refresh-failure.xml -r 333 -l 222222 -d
      668000 -nd -trace_err -trace_screen -trace_logs -buff_size 33554433
      -reconnect_close false -max_reconnect 10 -reconnect_sleep 3000
      <sailfin_host:sip_port>

      *****************************************************************************

      This is a umbrella issue to track the Subscribe Refresh with failure injection
      scenario. Issues observed with this scenario are filed as child issues.

      Basic Scenario:
      1. Start all SIPp clients
      2. After about an hour, fail the instance that is not associated with any SIPp
      client
      3. After about an hour, restart the failed instance
      4. Repeat steps 2 and 3 one or more times.

        Issue Links

          Activity

          Hide
          prasads added a comment -

          Re-Assigning to Mahesh

          Show
          prasads added a comment - Re-Assigning to Mahesh
          Hide
          Mahesh Kannan added a comment -

          Elena made a 6.5 days run and it hadn't run into OOM. Steve also has run this
          and could kill and restart an instance twice without any issues.

          Will close the bug after Elena reports success in her new 24x7 run

          Show
          Mahesh Kannan added a comment - Elena made a 6.5 days run and it hadn't run into OOM. Steve also has run this and could kill and restart an instance twice without any issues. Will close the bug after Elena reports success in her new 24x7 run
          Hide
          shreedhar_ganapathy added a comment -

          Marking issue as fixed based on runs on Steve's setup with not only 200K but also 300K sessions and 300
          effective cps. The run included failure and restart.

          If a fresh run shows issues, please open a fresh issue since this was opened for issues from long past.

          Show
          shreedhar_ganapathy added a comment - Marking issue as fixed based on runs on Steve's setup with not only 200K but also 300K sessions and 300 effective cps. The run included failure and restart. If a fresh run shows issues, please open a fresh issue since this was opened for issues from long past.

            People

            • Assignee:
              Mahesh Kannan
              Reporter:
              varunrupela
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: