The source should output a line saying something along the lines of 'read records: `n`'

I also believe that's why it fails

2021-05-18 11:11:56 INFO (/tmp/workspace/4/1) LineGobbler(voidCall):69 - 2021-05-18 11:11:56 [32mINFO[m i.a.i.d.j.c.s.S3StreamCopier(removeFileAndDropTmpTable):179 - {} - S3 staging file e1a7b446-6fde-4715-8012-20d757901740/airbyte/mp_pocexport cleaned.
2021-05-18 11:11:56 INFO (/tmp/workspace/4/1) LineGobbler(voidCall):69 - 2021-05-18 11:11:56 [32mINFO[m i.a.i.d.j.c.s.S3StreamCopier(removeFileAndDropTmpTable):181 - {} - Begin cleaning _airbyte_1621336301548_mp_pocexport tmp table in destination.
2021-05-18 11:11:56 INFO (/tmp/workspace/4/1) LineGobbler(voidCall):69 - 2021-05-18 11:11:56 [32mINFO[m i.a.i.d.j.c.s.S3StreamCopier(removeFileAndDropTmpTable):183 - {} - _airbyte_1621336301548_mp_pocexport tmp table in destination cleaned.
2021-05-18 11:11:56 INFO (/tmp/workspace/4/1) LineGobbler(voidCall):69 - 2021-05-18 11:11:56 [32mINFO[m i.a.i.b.IntegrationRunner(run):118 - {} - Completed integration: io.airbyte.integrations.destination.redshift.RedshiftDestination
2021-05-18 11:11:56 INFO (/tmp/workspace/4/1) LineGobbler(voidCall):69 - 2021-05-18 11:11:56 [32mINFO[m i.a.i.d.r.RedshiftDestination(main):99 - {} - completed destination: class io.airbyte.integrations.destination.redshift.RedshiftDestination
2021-05-18 11:11:56 INFO (/tmp/workspace/4/1) TemporalAttemptExecution(lambda$getWorkerThread$2):150 - Completing future exceptionally...
io.airbyte.workers.WorkerException: Sync failed
at io.airbyte.workers.DefaultReplicationWorker.run(DefaultReplicationWorker.java:130) ~[io.airbyte-airbyte-workers-0.22.3-alpha.jar:?]
at io.airbyte.workers.DefaultReplicationWorker.run(DefaultReplicationWorker.java:46) ~[io.airbyte-airbyte-workers-0.22.3-alpha.jar:?]
at io.airbyte.workers.temporal.TemporalAttemptExecution.lambda$getWorkerThread$2(TemporalAttemptExecution.java:147) [io.airbyte-airbyte-workers-0.22.3-alpha.jar:?]
at java.lang.Thread.run(Thread.java:832) [?:?]
Caused by: io.airbyte.workers.WorkerException: Source process wasn't successful
at io.airbyte.workers.protocols.airbyte.DefaultAirbyteSource.close(DefaultAirbyteSource.java:130) ~[io.airbyte-airbyte-workers-0.22.3-alpha.jar:?]
at io.airbyte.workers.DefaultReplicationWorker.run(DefaultReplicationWorker.java:107) ~[io.airbyte-airbyte-workers-0.22.3-alpha.jar:?]
... 3 more
2021-05-18 11:11:56 INFO (/tmp/workspace/4/1) TemporalAttemptExecution(get):134 - Stopping cancellation check scheduling...
2021-05-18 11:11:56 WARN (/tmp/workspace/4/1) POJOActivityTaskHandler$POJOActivityImplementation(execute):243 - Activity failure. ActivityId=8168ae26-4f46-37b8-bea8-6e05020ed886, activityType=Replicate, attempt=1
java.util.concurrent.ExecutionException: io.airbyte.workers.WorkerException: Sync failed
at java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:395) ~[?:?]
at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:2063) ~[?:?]
at io.airbyte.workers.temporal.TemporalAttemptExecution.get(TemporalAttemptExecution.java:132) ~[io.airbyte-airbyte-workers-0.22.3-alpha.jar:?]
at io.airbyte.workers.temporal.SyncWorkflow$ReplicationActivityImpl.replicate(SyncWorkflow.java:151) ~[io.airbyte-airbyte-workers-0.22.3-alpha.jar:?]
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?]
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:?]
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
at java.lang.reflect.Method.invoke(Method.java:564) ~[?:?]
at io.temporal.internal.sync.POJOActivityTaskHandler$POJOActivityInboundCallsInterceptor.execute(POJOActivityTaskHandler.java:277) ~[temporal-sdk-1.0.4.jar:?]
at io.temporal.internal.sync.POJOActivityTaskHandler$POJOActivityImplementation.execute(POJOActivityTaskHandler.java:216) [temporal-sdk-1.0.4.jar:?]
at io.temporal.internal.sync.POJOActivityTaskHandler.handle(POJOActivityTaskHandler.java:181) [temporal-sdk-1.0.4.jar:?]
at io.temporal.internal.worker.ActivityWorker$TaskHandlerImpl.handle(ActivityWorker.java:192) [temporal-sdk-1.0.4.jar:?]
at io.temporal.internal.worker.ActivityWorker$TaskHandlerImpl.handle(ActivityWorker.java:154) [temporal-sdk-1.0.4.jar:?]
at io.temporal.internal.worker.PollTaskExecutor.lambda$process$0(PollTaskExecutor.java:73) [temporal-sdk-1.0.4.jar:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:630) [?:?]
at java.lang.Thread.run(Thread.java:832) [?:?]
Caused by: io.airbyte.workers.WorkerException: Sync failed
at io.airbyte.workers.DefaultReplicationWorker.run(DefaultReplicationWorker.java:130) ~[io.airbyte-airbyte-workers-0.22.3-alpha.jar:?]
at io.airbyte.workers.DefaultReplicationWorker.run(DefaultReplicationWorker.java:46) ~[io.airbyte-airbyte-workers-0.22.3-alpha.jar:?]
at io.airbyte.workers.temporal.TemporalAttemptExecution.lambda$getWorkerThread$2(TemporalAttemptExecution.java:147) ~[io.airbyte-airbyte-workers-0.22.3-alpha.jar:?]
... 1 more
Caused by: io.airbyte.workers.WorkerException: Source process wasn't successful
at io.airbyte.workers.protocols.airbyte.DefaultAirbyteSource.close(DefaultAirbyteSource.java:130) ~[io.airbyte-airbyte-workers-0.22.3-alpha.jar:?]
at io.airbyte.workers.DefaultReplicationWorker.run(DefaultReplicationWorker.java:107) ~[io.airbyte-airbyte-workers-0.22.3-alpha.jar:?]
at io.airbyte.workers.DefaultReplicationWorker.run(DefaultReplicationWorker.java:46) ~[io.airbyte-airbyte-workers-0.22.3-alpha.jar:?]
at io.airbyte.workers.temporal.TemporalAttemptExecution.lambda$getWorkerThread$2(TemporalAttemptExecution.java:147) ~[io.airbyte-airbyte-workers-0.22.3-alpha.jar:?]
... 1 more

Can't quite figure out where the relevant part is

for those logs to appear, your sync actually reached to the end of the replication. this is when the S3 destination starts cleaning up the tmp tables

I agree we can do better on logging - I've created https://github.com/airbytehq/airbyte/issues/3465 for tracking

what did resource usage look like? whenever we see such issues, it's usually due to lack of resource