Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unpredictable results returned #11

Open
GreenSaaSDev opened this issue Jun 1, 2023 · 1 comment
Open

Unpredictable results returned #11

GreenSaaSDev opened this issue Jun 1, 2023 · 1 comment
Assignees

Comments

@GreenSaaSDev
Copy link

Describe the bug
We set up a Data Lake for our Non-profit client in December. The initial set-up returned all rows for the selected objects we pulled in (Account, Contact, Opportunity, Lead and a couple of custom objects). Subsequent monthly runs of the data lake failed to process and upon inspection this was due to some blocking locks. Now when the process is run manually through the State Machine, # of connections spikes and processing (sf_importprocess) of the data in S3 buckets fails due to postgres

dbinstance-ftienvalzd5x
CPU
13.54%
Status
Available
Class
db.t3.micro
Role
Instance
Current activity
58 Connections
Engine
PostgreSQL
Region & AZ
us-east-1b

To Reproduce
Steps to reproduce the behavior:

  1. Go to Step Function state machine
  2. Click on Execute
  3. Watch as DB connections to Postgres climb to limits
  4. Notice that although there are hundreds of thousands of records in Opportunity, Contact, Accounts only a limited subset are actually processed into the import tables
  5. 17 "Account" "2023-05-31 22:43:19.710286" 1500 168 1421 1618927413
    18 "Lead" "2023-05-31 22:43:19.751178" 0 78 26 22194445
    19 "Opportunity" "2023-05-31 22:43:21.157252" 3400 250 1123 1777352241

Expected behavior
Expect that all rows are processed into the data lake

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • OS: [e.g. iOS]
  • Browser [e.g. chrome, safari]
  • Version [e.g. 22]

Additional context
Add any other context about the problem here.

@simsek97
Copy link
Collaborator

I tried the same but I couldn't replicate the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants