Google Analytics Source Fails

  • Is this your first time deploying Airbyte?: No
  • OS Version / Instance: EC2
  • Memory / Disk: Enough of both
  • Deployment: Docker
  • Airbyte Version: 0.38.1
  • Source name/version: Google Analytics latest
  • Destination name/version: Redshift latest
  • Step: Sync runs fully, dbt executes, job reports failure and attempts to retry
  • Description: Error below
2022-05-10 19:23:44 e[43mdestinatione[0m > Exception in thread "main" java.sql.SQLException: [Amazon](500310) Invalid operation: current transaction is aborted, commands ignored until end of transaction block;
2022-05-10 19:23:44 e[43mdestinatione[0m > 	at com.amazon.redshift.client.messages.inbound.ErrorResponse.toErrorException(Unknown Source)
2022-05-10 19:23:44 e[43mdestinatione[0m > 	at com.amazon.redshift.client.PGMessagingContext.handleErrorResponse(Unknown Source)
2022-05-10 19:23:44 e[43mdestinatione[0m > 	at com.amazon.redshift.client.PGMessagingContext.handleMessage(Unknown Source)
2022-05-10 19:23:44 e[43mdestinatione[0m > 	at com.amazon.jdbc.communications.InboundMessagesPipeline.getNextMessageOfClass(Unknown Source)
2022-05-10 19:23:44 e[43mdestinatione[0m > 	at com.amazon.redshift.client.PGMessagingContext.doMoveToNextClass(Unknown Source)
2022-05-10 19:23:44 e[43mdestinatione[0m > 2022-05-10 19:23:44 e[1;31mERRORe[m i.a.i.d.b.BufferedStreamConsumer(close):191 - Close failed.
2022-05-10 19:23:44 e[43mdestinatione[0m > 	at com.amazon.redshift.client.PGMessagingContext.moveThroughMetadata(Unknown Source)
2022-05-10 19:23:44 e[43mdestinatione[0m > java.sql.SQLException: [Amazon](500310) Invalid operation: current transaction is aborted, commands ignored until end of transaction block;
2022-05-10 19:23:44 e[43mdestinatione[0m > 	at com.amazon.redshift.client.PGMessagingContext.getNoData(Unknown Source)
2022-05-10 19:23:44 e[43mdestinatione[0m > 	at com.amazon.redshift.client.messages.inbound.ErrorResponse.toErrorException(Unknown Source) ~[redshift-jdbc42-no-awssdk-1.2.51.1078.jar:RedshiftJDBC_1.2.51.1078]
2022-05-10 19:23:44 e[43mdestinatione[0m > 	at com.amazon.redshift.client.PGClient.directExecuteExtraMetadataWithMessage(Unknown Source)
2022-05-10 19:23:44 e[43mdestinatione[0m > 	at com.amazon.redshift.dataengine.PGQueryExecutor$CallableExecuteTask.call(Unknown Source)
2022-05-10 19:23:44 e[43mdestinatione[0m > 	at com.amazon.redshift.dataengine.PGQueryExecutor$CallableExecuteTask.call(Unknown Source)
2022-05-10 19:23:44 e[43mdestinatione[0m > 	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
2022-05-10 19:23:44 e[43mdestinatione[0m > 	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
2022-05-10 19:23:44 e[43mdestinatione[0m > 	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
2022-05-10 19:23:44 e[43mdestinatione[0m > Caused by: com.amazon.support.exceptions.ErrorException: [Amazon](500310) Invalid operation: current transaction is aborted, commands ignored until end of transaction block;
2022-05-10 19:23:44 e[43mdestinatione[0m > 	... 13 more
2022-05-10 19:23:44 e[43mdestinatione[0m > 	at com.amazon.redshift.client.PGMessagingContext.handleErrorResponse(Unknown Source) ~[redshift-jdbc42-no-awssdk-1.2.51.1078.jar:RedshiftJDBC_1.2.51.1078]
2022-05-10 19:23:44 e[43mdestinatione[0m > 	at com.amazon.redshift.client.PGMessagingContext.handleMessage(Unknown Source) ~[redshift-jdbc42-no-awssdk-1.2.51.1078.jar:RedshiftJDBC_1.2.51.1078]
2022-05-10 19:23:44 e[43mdestinatione[0m > 	at com.amazon.jdbc.communications.InboundMessagesPipeline.getNextMessageOfClass(Unknown Source) ~[redshift-jdbc42-no-awssdk-1.2.51.1078.jar:RedshiftJDBC_1.2.51.1078]
2022-05-10 19:23:44 e[43mdestinatione[0m > 	at com.amazon.redshift.client.PGMessagingContext.doMoveToNextClass(Unknown Source) ~[redshift-jdbc42-no-awssdk-1.2.51.1078.jar:RedshiftJDBC_1.2.51.1078]
2022-05-10 19:23:44 e[43mdestinatione[0m > 	at com.amazon.redshift.client.PGMessagingContext.moveThroughMetadata(Unknown Source) ~[redshift-jdbc42-no-awssdk-1.2.51.1078.jar:RedshiftJDBC_1.2.51.1078]
2022-05-10 19:23:44 e[43mdestinatione[0m > 	at com.amazon.redshift.client.PGMessagingContext.getNoData(Unknown Source) ~[redshift-jdbc42-no-awssdk-1.2.51.1078.jar:RedshiftJDBC_1.2.51.1078]
2022-05-10 19:23:44 e[43mdestinatione[0m > 	at com.amazon.redshift.client.PGClient.directExecuteExtraMetadataWithMessage(Unknown Source) ~[redshift-jdbc42-no-awssdk-1.2.51.1078.jar:RedshiftJDBC_1.2.51.1078]
2022-05-10 19:23:44 e[43mdestinatione[0m > 	at com.amazon.redshift.dataengine.PGQueryExecutor$CallableExecuteTask.call(Unknown Source) ~[redshift-jdbc42-no-awssdk-1.2.51.1078.jar:RedshiftJDBC_1.2.51.1078]
2022-05-10 19:23:44 e[43mdestinatione[0m > 	at com.amazon.redshift.dataengine.PGQueryExecutor$CallableExecuteTask.call(Unknown Source) ~[redshift-jdbc42-no-awssdk-1.2.51.1078.jar:RedshiftJDBC_1.2.51.1078]
2022-05-10 19:23:44 e[43mdestinatione[0m > 	at java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[?:?]
2022-05-10 19:23:44 e[43mdestinatione[0m > 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) ~[?:?]
2022-05-10 19:23:44 e[43mdestinatione[0m > 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) ~[?:?]
2022-05-10 19:23:44 e[43mdestinatione[0m > Caused by: com.amazon.support.exceptions.ErrorException: [Amazon](500310) Invalid operation: current transaction is aborted, commands ignored until end of transaction block;
2022-05-10 19:23:44 e[43mdestinatione[0m > 	... 13 more
2022-05-10 19:23:44 e[1;31mERRORe[m i.a.w.DefaultReplicationWorker(run):172 - Sync worker failed.
java.util.concurrent.ExecutionException: io.airbyte.workers.DefaultReplicationWorker$DestinationException: Destination process exited with non-zero exit code 1

Can you share the complete logs Jeff? Do you have other sources to the same destination? Are they working? If you create a new connection from the same source to a local json it works?

Mongo is now working after I repaired, Stripe still has issues. Above are the only log errors, was working before upgrade

Jeff I’ll close this in favor of the Stripe Topic.

Why are we closing? This is still an issue. The Mongo v2 connector is still taking 45 minutes for a task that took 1 minute previous. I’m still waiting on the Stripe load to finish despite the log spam to see if its working or not