worker keep logging of "waiting for db"
See original GitHub issueDescription
I ran the app in kubernetes but worker pod kept logging “waiting for db”
Steps to reproduce the issue, if relevant:
just follow the steps
kubectl create namespace vote
then
kubectl create -f k8s-specifications/
then kubectl logs worker...
you will meet the error of waiting for db
Issue Analytics
- State:
- Created 4 years ago
- Comments:16 (1 by maintainers)
Top Results From Across the Web
Extreme wait-time when taking a SQL Server database offline
For me, I just had to go into the Job Activity Monitor and stop two things that were processing. Then it went offline...
Read more >Threadpool Wait - sql server
The first thing that you would want to do is to find out which queries are consuming the maximum amount of CPU. This...
Read more >sys.dm_os_wait_stats (Transact-SQL) - SQL Server
Indicates that the database mirroring worker task is waiting for more work. DBMIRRORING_CMD, Occurs when a task is waiting for log records to...
Read more >Boost SQL Server Performance with Wait Statistics
WRITELOG wait type indicates the elapsed time when the log records writing into the disk. The possible causes can be as below: Locate...
Read more >Airbyte Server unable to start after configuring an external ...
Hi all, I am running Airbyte locally (hosted on a VM on GCP) and would like to set-up an external database backend for...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I found another way to do this configs.
Include this environment variable inside your k8s-specifictions/db-deployment.yaml:
After changing this configuration above, postgres displays this message:
WARNING: POSTGRES_HOST_AUTH_METHOD has been set to “trust”. This will allow anyone with access to the Postgres port to access your database without a password, even if POSTGRES_PASSWORD is set. See PostgreSQL documentation about “trust”: https://www.postgresql.org/docs/current/auth-trust.html In Docker’s default configuration, this is effectively any other container on the same system.
Important: Use this configuration only in TEST environments and following documentation recommendations
Hi,
Using docker-compose the image is built when running the command as others have mentioned. However, using swarm or Kubernetes, as she is trying to do, the image is pulled from the docker hub, which is outdated.
Using Kubernetes or swarm you have to build the image locally and change the image path accordingly until they fix it.
Best regards,