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

cbimport CSV failing in build 6.5.1-6296 build

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Not a Bug
    • 6.5.1
    • None
    • tools
    • Untriaged
    • Unknown

    Description

      **Logs indicate it completed importing 16906616 documents and then failed .

      error snippet:

      root@172-23-100-213:/home/workspace/leto# ./opt/couchbase/bin/cbimport csv --dataset file:///data/import/data.csv --cluster http://leto-srv-01.perf.couchbase.com --bucket bucket-1 --username Administrator --password password --generate-key "#MONO_INCR#" --threads 16
       
      2020-04-14T13:24:27.226-07:00 ERRO: Data transfer failed: read /data/import/data.csv: input/output error -- plan.(*data).execute() at data.go:91
      CSV import failed: 16906616 documents were imported, 0 documents failed to be imported
      CSV import failed: read /data/import/data.csv: input/output error
      

      Attachments

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

        Activity

          Thanks to Sharath Sulochana I have been looking at the file. As it is massive I was trying to extract a small part around the place where the error occured using sed and the same error occured.

          root@172-23-100-213:/data/import# sed -n -e 1p -e 16906614,16906636p data.csv
          alt_street,city,category,realm,alt_capped_small,capped_small,alt_realm,alt_email,email,alt_county,state,body,coins,country,alt_country,year,street,alt_state,gmtime,alt_city,alt_full_state,county,achievements,full_state,name
          7c4519c57c4519c57c4519c57c4519c57c4519c57c4519c57c4519c5,af6a16af6a16,0,77b45177b45177b45177b45177b45177b451,a338c8a338c8,a338c8a338c8a338c8a338c8a338c8,77b45177b45177b45177b45177b45177b45177b45177b45177b451,ee9c9a@83604c.com,ee9c9a@04cbbb.comee9c9a@04cbbb.comee9c9a@04cbbb.comee9c9a@04cbbb.com,6dbb95,NANANA,5b,7760.639999999999,d666dfd666dfd666dfd666df,d666df,7968,7c4519c57c4519c57c4519c57c4519c57c4519c57c4519c57c4519c57c
           
          ....
           
          3452918834529188,a724eba724eba724eba724eba724eba724eba724eba724eba724eb,0,428cec428cec428cec,0ee6e90ee6e90ee6e90ee6e9,9d90ee9d90ee,428cec428cec428cec428cec428cec,7869d9@924894.com7869d9@924894.com7869d9@924894.com7869d9@924894.com7869d9@924894.com,869d90@924894.com,,,5e,361451.97000000003,2a39212a39212a39212a39212a3921,,3982,3452918834529188345291883452918834529188,ASASAS,"[1970, 1, 1, 0, 0, 0, 3, 1, 0, 1970, 1, 1, 0, 0,
          0, 3, 1, 0, 1970, 1, 1, 0, 0, 0, 3, 1, 0]",a724eb,ArizonaArizonaArizonaArizonaArizona,8f5a108f5a108f5a108f5a108f5a10,"[83, 93, 93, 129, 181, 251]",ArizonaArizonaArizonaArizonaArizona,5ec786 9d90ee5ec786 9d90ee
          sed: read error on data.csv: Input/output error
          ```
          

          We can see we get the exact same error that we did on cbimport which further indicates the issue is with the file. I will keep trying to narrow down what exacly is the issue with the file.

          After doing some googling it seems that this could be a disk issue. Unfortunately this is not my area of expertise. Patrick Varley fo you know how to test if it is a disk issue?

          carlos.gonzalez Carlos Gonzalez Betancort (Inactive) added a comment - - edited Thanks to Sharath Sulochana I have been looking at the file. As it is massive I was trying to extract a small part around the place where the error occured using sed and the same error occured. root@172-23-100-213:/data/import# sed -n -e 1p -e 16906614,16906636p data.csv alt_street,city,category,realm,alt_capped_small,capped_small,alt_realm,alt_email,email,alt_county,state,body,coins,country,alt_country,year,street,alt_state,gmtime,alt_city,alt_full_state,county,achievements,full_state,name 7c4519c57c4519c57c4519c57c4519c57c4519c57c4519c57c4519c5,af6a16af6a16,0,77b45177b45177b45177b45177b45177b451,a338c8a338c8,a338c8a338c8a338c8a338c8a338c8,77b45177b45177b45177b45177b45177b45177b45177b45177b451,ee9c9a@83604c.com,ee9c9a@04cbbb.comee9c9a@04cbbb.comee9c9a@04cbbb.comee9c9a@04cbbb.com,6dbb95,NANANA,5b,7760.639999999999,d666dfd666dfd666dfd666df,d666df,7968,7c4519c57c4519c57c4519c57c4519c57c4519c57c4519c57c4519c57c   ....   3452918834529188,a724eba724eba724eba724eba724eba724eba724eba724eba724eb,0,428cec428cec428cec,0ee6e90ee6e90ee6e90ee6e9,9d90ee9d90ee,428cec428cec428cec428cec428cec,7869d9@924894.com7869d9@924894.com7869d9@924894.com7869d9@924894.com7869d9@924894.com,869d90@924894.com,,,5e,361451.97000000003,2a39212a39212a39212a39212a3921,,3982,3452918834529188345291883452918834529188,ASASAS,"[1970, 1, 1, 0, 0, 0, 3, 1, 0, 1970, 1, 1, 0, 0, 0, 3, 1, 0, 1970, 1, 1, 0, 0, 0, 3, 1, 0]",a724eb,ArizonaArizonaArizonaArizonaArizona,8f5a108f5a108f5a108f5a108f5a10,"[83, 93, 93, 129, 181, 251]",ArizonaArizonaArizonaArizonaArizona,5ec786 9d90ee5ec786 9d90ee sed: read error on data.csv: Input/output error ``` We can see we get the exact same error that we did on cbimport which further indicates the issue is with the file. I will keep trying to narrow down what exacly is the issue with the file. After doing some googling it seems that this could be a disk issue. Unfortunately this is not my area of expertise. Patrick Varley fo you know how to test if it is a disk issue?
          owend Daniel Owen added a comment -

          Given the issues is not with cbimport going to resolve as not a bug.

          owend Daniel Owen added a comment - Given the issues is not with cbimport going to resolve as not a bug.

          Carlos Gonzalez Betancort is correct, disk SDC is failing:

          [Wed Apr 15 01:37:52 2020] blk_update_request: critical medium error, dev sdc, sector 310920800
          [Wed Apr 15 01:38:11 2020] sd 0:0:3:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
          [Wed Apr 15 01:38:11 2020] sd 0:0:3:0: [sdc] tag#0 Sense Key : Medium Error [current] 
          [Wed Apr 15 01:38:11 2020] sd 0:0:3:0: [sdc] tag#0 Add. Sense: Unrecovered read error
          [Wed Apr 15 01:38:11 2020] sd 0:0:3:0: [sdc] tag#0 CDB: Read(10) 28 00 12 88 46 60 00 00 08 00
          [Wed Apr 15 01:38:11 2020] blk_update_request: critical medium error, dev sdc, sector 310920800
          

          pvarley Patrick Varley added a comment - Carlos Gonzalez Betancort is correct, disk SDC is failing: [Wed Apr 15 01:37:52 2020] blk_update_request: critical medium error, dev sdc, sector 310920800 [Wed Apr 15 01:38:11 2020] sd 0:0:3:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [Wed Apr 15 01:38:11 2020] sd 0:0:3:0: [sdc] tag#0 Sense Key : Medium Error [current] [Wed Apr 15 01:38:11 2020] sd 0:0:3:0: [sdc] tag#0 Add. Sense: Unrecovered read error [Wed Apr 15 01:38:11 2020] sd 0:0:3:0: [sdc] tag#0 CDB: Read(10) 28 00 12 88 46 60 00 00 08 00 [Wed Apr 15 01:38:11 2020] blk_update_request: critical medium error, dev sdc, sector 310920800

          Closing this based on comments above

          arunkumar Arunkumar Senthilnathan added a comment - Closing this based on comments above
          wayne Wayne Siu added a comment -

          Re-opening the ticket to remove the fix version.

          wayne Wayne Siu added a comment - Re-opening the ticket to remove the fix version.

          People

            sharath.sulochana Sharath Sulochana (Inactive)
            sharath.sulochana Sharath Sulochana (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Gerrit Reviews

                There are no open Gerrit changes

                PagerDuty