Error loading data to Redshift

For engineers Storage targets
1

When I try to load shredded events into Redshift I get this error:
Snowplow::EmrEtlRunner::EmrExecutionError (EMR jobflow j-2CHILQDXC9ARL failed, check Amazon EMR console and Hadoop logs for details (help: https://github.com/snowplow/snowplow/wiki/Troubleshooting-jobs-on-Elastic-MapReduce). Data files not archived.
Snowplow_RS: TERMINATING [STEP_FAILURE] ~ elapsed time n/a [2019-05-02 10:19:24 +0000 - ]

    1. Elasticity Setup Hadoop Debugging: COMPLETED ~ 00:00:04 [2019-05-02 10:19:26 +0000 - 2019-05-02 10:19:30 +0000]
    1. [rdb_load] Load AWS Redshift enriched events storage Storage Target: FAILED ~ 00:00:10 [2019-05-02 10:19:34 +0000 - 2019-05-02 10:19:44 +0000]
    1. [archive_shredded] s3-dist-cp: Shredded S3 -> S3 Shredded Archive: CANCELLED ~ elapsed time n/a [ - ]
    1. [archive_enriched] s3-dist-cp: Enriched S3 -> S3 Enriched Archive: CANCELLED ~ elapsed time n/a [ - ]):
      uri:classloader:/emr-etl-runner/lib/snowplow-emr-etl-runner/emr_job.rb:783:in run' uri:classloader:/gems/contracts-0.11.0/lib/contracts/method_reference.rb:43:insend_to’
      uri:classloader:/gems/contracts-0.11.0/lib/contracts/call_with.rb:76:in call_with' uri:classloader:/gems/contracts-0.11.0/lib/contracts/method_handler.rb:138:inblock in redefine_method’
      uri:classloader:/emr-etl-runner/lib/snowplow-emr-etl-runner/runner.rb:138:in run' uri:classloader:/gems/contracts-0.11.0/lib/contracts/method_reference.rb:43:insend_to’
      uri:classloader:/gems/contracts-0.11.0/lib/contracts/call_with.rb:76:in call_with' uri:classloader:/gems/contracts-0.11.0/lib/contracts/method_handler.rb:138:inblock in redefine_method’
      uri:classloader:/emr-etl-runner/bin/snowplow-emr-etl-runner:41:in <main>' org/jruby/RubyKernel.java:994:inload’
      uri:classloader:/META-INF/main.rb:1:in <main>' org/jruby/RubyKernel.java:970:inrequire’
      uri:classloader:/META-INF/main.rb:1:in (root)' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1:in’
      I checked the EMR log and I get this in Stdout:
      Configuration error
      DecodingFailure at .aws.s3.buckets.shredded.errors: Bucket name must start with s3:// prefix

Any help, please?

2

What’s your enrich configuration look like? Does the shredded errors S3 location start with the s3:// prefix?

3

Hi @mike,
Thank you for your response!
This is my conf file:

aws:
  # Credentials can be hardcoded or set in environment variables
  access_key_id: xxx
  secret_access_key: xxx
  s3:
region: us-east-2
buckets:
  assets: s3://snowplow-hosted-assets # DO NOT CHANGE unless you are hosting the jarfiles etc yourself in your own bucket
  jsonpath_assets: # If you have defined your own JSON Schemas, add the s3:// path to your own JSON Path files in your own bucket here
  log: s3://sp-logs-acc/logs
  encrypted: false # Whether the buckets below are enrcrypted using server side encryption (SSE-S3)
  raw:
    in:                  # This is a YAML array of one or more in buckets - you MUST use hyphens before each entry in the array, as below
      - s3://sp-raw-acc/raw         # e.g. s3://my-old-collector-bucket
    processing: s3://sp-raw-acc/processing
    archive: s3://sp-raw-acc/archive    # e.g. s3://my-archive-bucket/raw
  enriched:
    good: s3://sp-enrich-acc/good       # e.g. s3://my-out-bucket/enriched/good
    bad: s3://sp-enrich-acc/bad        # e.g. s3://my-out-bucket/enriched/bad
    errors:      # Leave blank unless :continue_on_unexpected_error: set to true below
    archive: s3://sp-enrich-acc/archive    # Where to archive enriched events to, e.g. s3://my-archive-bucket/enriched
    stream: s3://sp-raw-acc/stream
  shredded:
    good: s3://sp-shred-acc/good       # e.g. s3://my-out-bucket/shredded/good
    bad: s3://sp-shred-acc/bad        # e.g. s3://my-out-bucket/shredded/bad
    errors: continue_on_unexpected_error     # Leave blank unless :continue_on_unexpected_error: set to true below
    archive: s3://sp-shred-acc/archive    # Where to archive shredded events to, e.g. s3://my-archive-bucket/shredded
consolidate_shredded_output: false # Whether to combine files when copying from hdfs to s3
  emr:
ami_version: 5.9.0
region: us-east-2        # Always set this
jobflow_role: EMR_EC2_DefaultRole # Created using $ aws emr create-default-roles
service_role: EMR_DefaultRole     # Created using $ aws emr create-default-roles
placement: # Set this if not running in VPC. Leave blank otherwise
ec2_subnet_id: subnet-a9f19bd3 # subnet-80dfe3e8 Set this if running in VPC. Leave blank otherwise
ec2_key_name: snowplow00
security_configuration: # Specify your EMR security configuration if needed. Leave blank otherwise
bootstrap: []           # Set this to specify custom boostrap actions. Leave empty otherwise
software:
  hbase: # Optional. To launch on cluster, provide version, "0.92.0", keep quotes. Leave empty otherwise.
  lingual: # Optional. To launch on cluster, provide version, "1.1", keep quotes. Leave empty otherwise.
# Adjust your Hadoop cluster below
jobflow:
  job_name: Snowplow_RS # Give your job a name
  master_instance_type: r4.xlarge
  core_instance_count: 2
  core_instance_type: r4.xlarge
  core_instance_ebs:    # Optional. Attach an EBS volume to each core instance.
    volume_size: 100    # Gigabytes
    volume_type: "gp2"
    volume_iops: 400    # Optional. Will only be used if volume_type is "io1"
    ebs_optimized: false # Optional. Will default to true
  task_instance_count: 0 # Increase to use spot instances
  task_instance_type: r4.xlarge
  task_instance_bid: 0.015 # In USD. Adjust bid, or leave blank for non-spot-priced (i.e. on-demand) task instances
bootstrap_failure_tries: 3 # Number of times to attempt the job in the event of bootstrap failures
configuration:
  yarn-site:
    yarn.resourcemanager.am.max-attempts: "1"
  spark:
    maximizeResourceAllocation: "true"
additional_info:        # Optional JSON string for selecting additional features
collectors:
  format: thrift # For example: 'clj-tomcat' for the Clojure Collector, 'thrift' for Thrift records, 'tsv/com.amazon.aws.cloudfront/wd_access_log' for Clo$
enrich:
  versions:
spark_enrich: 1.17.0 # Version of the Spark Enrichment process
  continue_on_unexpected_error: false # Set to 'true' (and set :out_errors: above) if you don't want any exceptions thrown from ETL
  output_compression: GZIP # Compression only supported with Redshift, set to NONE if you have Postgres targets. Allowed formats: NONE, GZIP
storage:
  versions:
rdb_loader: 0.14.0
rdb_shredder: 0.13.1        # Version of the Spark Shredding process
hadoop_elasticsearch: 0.1.0 # Version of the Hadoop to Elasticsearch copying process
monitoring:
  tags: {name: "data-pipeline-enrichment"} # Name-value pairs describing this job
  logging:
level: DEBUG # You can optionally switch to INFO for production
#  snowplow:
#    method: get
#    protocol: http
#    port: 80
#    app_id: snowplow # e.g. snowplow
#    collector: d3rkrsqld9gmqf.cloudfront.net # e.g. d3rkrsqld9gmqf.cloudfront.net

Yes, the shredded errors S3 location has the s3:// prefix…

4

@mosan, your shredded/errors bucket has an incorrect format - it has the value continue_on_unexpected_error. I don’t think you meant that.

1 Like
5

Ups, thank you so much!
Now I see records in redshift!