Spice Daily Refresh Issue

Q&A
1

Hi,
I am using an AmazonBI account.
I am struggling to refresh my dataset on a daily basis (size:16.6MB, 18K rows).
Your assistance in this matter will be very much appreciated

image

image

As opposed to
image

Habib

2

Hi @chhbi - Welcome to AWS Quick Sight community and thanks for posting the question. Looking at the stats, need more details.

  1. There are 2 success complete in June 16 and there start time are different. As per you requirement, you should have once in a day refresh. Can you share more details on both stats.
  2. What is your data source, are you using any custom dataset ( like join 2 or 3 data sets) and then do the SPICE, please provide some details on the data set and data source details.
  3. Is it a full refresh or incremental, please confirm.
  4. Also for failure instances, is there any details available why it failed. We need to understand those details as well.

Since Quick Sight is a SaaS, when a SPICE refresh is failed, how it managed internally, we need AWS team to understand in details. I am tagging some of the experts for their feedback as well.

Hi @eperts @ArunSanthosh @Koushik_Muthanna @Max @David_Wong - Any advise on this. In past also i saw when a spice refresh failed, the subsequent refresh took time, do you know how spice worked in backend.

Regards - Sanjeeb

1 Like
3

Hi Sanjeeb, thank you very much for your prompt response

  1. My apologies for the “as-opposed-to” screen capture
    From a different QS,it was just an example of a smooth refresh (please ignore)

  2. I am using a custom SQL with 2 left JOINS
    image

Data source:
image

Error Details
image

  1. One full refresh daily

image
image1023Ă—113 4.08 KB

image
image1411Ă—338 37.4 KB

image

4

Hi @chhbi - Before going down the route of debugging what’s wrong with Quick Sight, can you check with your database admin if there are other processes running at the same time as the Quick Sight extract?

Check the database resources such CPU, memory, connections for anything abnormal. It’s not uncommon to have cleanup jobs and other data extracts all running at about the same time at which point the database may not be able to keep up.

2 Likes
5

Hi,
Will do. i appreciate your help very much.
Kind regards

2 Likes
6

Hi @chhbi - Thanks for the updated screenshot. @eperts is right, please check with your redshift admin as this kind of error happened when there is an issue with Redshift DB side.

Regards - Sanjeeb

1 Like
7

Hi, @eperts, @Sanjeeb2022 -

  • db administrator contacted: i asked for a recommended timeframe to refresh data to avoid high cpu/memory usage et cetera. awaiting result over a couple of days.
  • Would it be possible to share a “Point of Contact” to explain how to obtain an Amazon S3 account and access CloudTrail as an “AmazonBI” user?

Thank you very much for your help.

8

Hi @chhbi - This is purely managed by your AWS admin team who can provisioned the access. Please connect with them? AWS Quick Sight community group may not help you on this.

Regards - Sanjeeb

1 Like