https://linen.dev logo
l

Liren Tu

06/29/2021, 11:40 PM
I am seeing
DEADLINE_EXCEEDED
errors even if I launch Airbyte from scratch. Based on previous threads related to this issue, is that because my laptop does not have enough resource? I did only have 8GB of memory.
u

user

06/29/2021, 11:41 PM
Logs look like this:
Copy code
airbyte-scheduler  | 2021-06-29 23:36:12 WARN i.t.i.w.Poller(lambda$new$0):66 - {} - Failure in thread Activity Poller taskQueue="SYNC", namespace="default": 2
airbyte-scheduler  | io.grpc.StatusRuntimeException: DEADLINE_EXCEEDED: deadline exceeded after 120.993026700s. [remote_addr=airbyte-temporal/172.18.0.6:7233]
airbyte-scheduler  | 	at io.grpc.stub.ClientCalls.toStatusRuntimeException(ClientCalls.java:262) ~[grpc-stub-1.34.1.jar:1.34.1]
airbyte-scheduler  | 	at io.grpc.stub.ClientCalls.getUnchecked(ClientCalls.java:243) ~[grpc-stub-1.34.1.jar:1.34.1]
airbyte-scheduler  | 	at io.grpc.stub.ClientCalls.blockingUnaryCall(ClientCalls.java:156) ~[grpc-stub-1.34.1.jar:1.34.1]
airbyte-scheduler  | 	at io.temporal.api.workflowservice.v1.WorkflowServiceGrpc$WorkflowServiceBlockingStub.pollActivityTaskQueue(WorkflowServiceGrpc.java:2696) ~[temporal-serviceclient-1.0.4.jar:?]
airbyte-scheduler  | 	at io.temporal.internal.worker.ActivityPollTask.poll(ActivityPollTask.java:105) ~[temporal-sdk-1.0.4.jar:?]
airbyte-scheduler  | 	at io.temporal.internal.worker.ActivityPollTask.poll(ActivityPollTask.java:39) ~[temporal-sdk-1.0.4.jar:?]
airbyte-scheduler  | 	at io.temporal.internal.worker.Poller$PollExecutionTask.run(Poller.java:265) ~[temporal-sdk-1.0.4.jar:?]
airbyte-scheduler  | 	at io.temporal.internal.worker.Poller$PollLoopTask.run(Poller.java:241) [temporal-sdk-1.0.4.jar:?]
airbyte-scheduler  | 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130) [?:?]
airbyte-scheduler  | 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:630) [?:?]
airbyte-scheduler  | 	at java.lang.Thread.run(Thread.java:832) [?:?]
airbyte-scheduler  | Publish operation is approaching monitor period. Increase period or risk compromising fixed rate.
u

user

06/30/2021, 12:04 AM
Are you hitting the max memory for your machine? The fact that this is taking 2 minutes to list the activities in temporal (which is a simple postgres lookup) seems like something is at capacity on your computer
u

user

06/30/2021, 12:05 AM
I would normally suggest increasing timeout values, but 2min seems excessive for this grpc call to temporal
u

user

06/30/2021, 12:06 AM
unless there’s something problematic in the temporal logs when this query is happening I’d guess that your computer is just running super slowly
u

user

06/30/2021, 12:52 AM
Got it. I am planning to get a new Mac mini, and replace the 8GB memory with a 64GB one. That should solve the problem for good.
e

Eamon Taaffe

06/30/2021, 12:58 AM
Liren if this is wasting your time, feel free to spend up a dev cluster on GKE to develop with
11 Views