hi guys, need help please.
one of the pipelines i...
# replication-troubleshootingm
Mark Elayan
11/18/2022, 4:18 AMhi guys, need help please.
one of the pipelines i am running, all of the sudden it stopped creating new sync jobs and showing an error "Uncaught (in promise) Error: A sync is already running for".
i tried restarting the docker stack, and restarted the server, but still the same.
Reset data also same behavior.
Any tips please on how to cancel it?
p.s: there is no job running in the frontend and in the API (/api/v1/jobs/list) all jobs are success. :/
Mark Elayan
11/18/2022, 4:24 AMi am getting 504 - gateway timeout on this endpoint:
api/v1/connections/reset
Mark Elayan
11/18/2022, 4:35 AMand seems this to be in the temporal lnstance:
{"level":"error","ts":"2022-11-18T042658.231Z","msg":"unavailable error","operation":"QueryWorkflow","wf-namespace":"default","error":"consistent query buffer is full, cannot accept new consistent queries","logging-call-at":"telemetry.go:187","stacktrace":"go.temporal.io/server/common/log.(*zapLogger).Error\n\t/temporal/common/log/zap_logger.go:142\ngo.temporal.io/server/common/rpc/interceptor.(*TelemetryInterceptor).handleError\n\t/temporal/common/rpc/interceptor/telemetry.go:187\ngo.temporal.io/server/common/rpc/interceptor.(*TelemetryInterceptor).Intercept\n\t/temporal/common/rpc/interceptor/telemetry.go:117\ngoogle.golang.org/grpc.chainUnaryInterceptors.func1.1\n\t/go/pkg/mod/google.golang.org/grpc@v1.41.0/server.go:1116\ngo.temporal.io/server/common/metrics.NewServerMetricsTrailerPropagatorInterceptor.func1\n\t/temporal/common/metrics/grpc.go:113\ngoogle.golang.org/grpc.chainUnaryInterceptors.func1.1\n\t/go/pkg/mod/google.golang.org/grpc@v1.41.0/server.go:1116\ngo.temporal.io/server/common/metrics.NewServerMetricsContextInjectorInterceptor.func1\n\t/temporal/common/metrics/grpc.go:66\ngoogle.golang.org/grpc.chainUnaryInterceptors.func1.1\n\t/go/pkg/mod/google.golang.org/grpc@v1.41.0/server.go:1116\ngo.temporal.io/server/common/rpc.ServiceErrorInterceptor\n\t/temporal/common/rpc/grpc.go:131\ngoogle.golang.org/grpc.chainUnaryInterceptors.func1.1\n\t/go/pkg/mod/google.golang.org/grpc@v1.41.0/server.go:1116\ngoogle.golang.org/grpc.chainUnaryInterceptors.func1\n\t/go/pkg/mod/google.golang.org/grpc@v1.41.0/server.go:1118\ngo.temporal.io/server/api/historyservice/v1._HistoryService_QueryWorkflow_Handler\n\t/temporal/api/historyservice/v1/service.pb.go:1403\ngoogle.golang.org/grpc.(*Server).processUnaryRPC\n\t/go/pkg/mod/google.golang.org/grpc@v1.41.0/server.go:1279\ngoogle.golang.org/grpc.(*Server).handleStream\n\t/go/pkg/mod/google.golang.org/grpc@v1.41.0/server.go:1608\ngoogle.golang.org/grpc.(*Server).serveStreams.func1.2\n\t/go/pkg/mod/google.golang.org/grpc@v1.41.0/server.go:923"}
u
user
11/18/2022, 1:24 PMHey Mark, this sounds like a strange temporal issue indeed. What version of Airbyte are you on?
m
Mark Elayan
11/19/2022, 12:34 AMhi @Nataly Merezhuk (Airbyte)
i am using 0.40.18
the behavior has happened on 3 connections at the same time, not sure why is that, when i create a new connection, all is good, but the old one cant be deleted nor used.
n
Nataly Merezhuk (Airbyte)
11/28/2022, 8:46 PMAre you using Helm charts? Could you give me a full description of your environment like this:
• Is this your first time deploying Airbyte?:
• Deployment:
• Airbyte Version:
• Source name/version:
• Destination name/version:
• Step to reproduce: