Uploaded image for project: 'Engineering'
  1. Engineering
  2. ENG-4802

@SnapshotStatus shows 0 END_TIME, DURATION and THROUGHPUT for partitioned tables on hosts that aren't also writing replicated table data

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: V3.3
    • Fix Version/s: V3.5
    • Component/s: Core
    • Labels:
      None
    • Team Backlog:
      xDISTRIBUTED team
    • Sprint:
      DIST-6, DIST-7

      Description

      In 3nodek1 running Voter.
      The only host that has correct timing data in SnapshotStatus is the host that is selected to write the replicated tables. Note: this is not the same as the node selected as snapshot leader.

      Note: after dropping the partitioned tables from the schema, the scan data (and the log messages) were all correct.

      1) Start a 3node cluster with an example app and run the client for a bit to fill it with data (I used 3nk1s4)
      2) In sqlcmd:
      exec @SnapshotSave, '

      {uripath:"file:///tmp/rmorgenstein/wan",nonce:"mydba",block:true,format:"csv"}

      ';
      exec @SnapshotStatus;

      Result:
      Only volt6a reports correct timing data.

      3> exec @SnapshotStatus;
      TIMESTAMP HOST_ID HOSTNAME TABLE PATH FILENAME NONCE TXNID START_TIME END_TIME SIZE DURATION THROUGHPUT RESULT
      -------------- -------- --------- ---------------- ---------------------- -------------------------- ------ ----------------- -------------- -------------- --------- --------- ------------------- --------
      1371148850885 0 volt8a VOTES /tmp/rmorgenstein/wan mydba-VOTES-host_0.csv mydba 3619631923265535 1371148839394 0 89930676 0 0.0 SUCCESS
      1371148850887 1 volt8b VOTES /tmp/rmorgenstein/wan mydba-VOTES-host_1.csv mydba 3619631923265535 1371148839383 0 89961718 0 0.0 SUCCESS
      1371148850891 2 volt6a VOTES /tmp/rmorgenstein/wan mydba-VOTES-host_2.csv mydba 3619631923265535 1371148839446 1371148843646 89851256 4 20.402893338884624 SUCCESS
      1371148850891 2 volt6a AREA_CODE_STATE /tmp/rmorgenstein/wan mydba-AREA_CODE_STATE.csv mydba 3619631923265535 1371148839446 1371148843646 3355 4 20.402893338884624 SUCCESS
      1371148850891 2 volt6a CONTESTANTS /tmp/rmorgenstein/wan mydba-CONTESTANTS.csv mydba 3619631923265535 1371148839446 1371148843646 123 4 20.402893338884624 SUCCESS

      The log messages are also weird.

      volt8a: No messages at all about the snapshot
      volt8b: This node has the SnapshotDaemon thread and notes the snapshot initiation, but no completion info
      2013-06-13 18:40:39,216 INFO [Iv2ExecutionSite: 1:4] SNAPSHOT: Synchronously saving database to path: /tmp/rmorgenstein/wan, ID: mydba at 1371148839216
      2013-06-13 18:40:43,789 INFO [Iv2ExecutionSite: 1:4] SNAPSHOT: Snapshot initiation took 4573 milliseconds
      volt6a: Only node that mentions the snapshot completion
      2013-06-13 18:40:43,646 INFO [Snapshot terminator] SNAPSHOT: Snapshot mydba finished at 1371148843646 and took 4.2 seconds

        Attachments

          Activity

            People

            Assignee:
            izzy Mike Ismert
            Reporter:
            rmorgenstein Ruth Morgenstein
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Zendesk Support