dapr: error connecting to placement service

In what area(s)?

/area runtime

/area operator /area placement /area docs /area test-and-release

What version of Dapr?

1.0.0.rc-1

0.2.x Output of git describe --dirty

Expected Behavior

using azure redis cache service as an actor statestore should work on AKS.

Actual Behavior

Sidecar continuosly priniting to debug log (~3k within 15min)

---- try to connect -----
{
--
app_id | polling-app
instance | polling-588cb67b95-stpxj
level | debug
msg | try to connect to placement service: dns:///dapr-placement-server.dapr-system.svc.cluster.local:50005
scope | dapr.runtime.actor.internal.placement
time | 2020-12-01T16:21:07.089588116Z
type | log
ver | 1.0.0-rc.1
}

--- error connecting ----
{
--
app_id | polling-app
instance | polling-588cb67b95-stpxj
level | debug
msg | error connecting to placement service: rpc error: code = Unavailable desc = last resolver error: produced zero addresses
scope | dapr.runtime.actor.internal.placement
time | 2020-12-01T16:21:06.589387093Z
type | log
ver | 1.0.0-rc.1
}

Steps to Reproduce the Problem

Add redis statestore

Name:         statestore
Namespace:    my-ns
Labels:       <none>
Annotations:  API Version:  dapr.io/v1alpha1
Kind:         Component
Metadata:
  Creation Timestamp:  2020-10-12T13:21:54Z
  Generation:          8
  Resource Version:    27834357
  Self Link:           /apis/dapr.io/v1alpha1/namespaces/core/components/statestore
  UID:                 7484bfe1-8edc-424f-960d-7c4bfc0a0037
Spec:
  Metadata:
    Name:   redisHost
    Value:  my-domain.redis.cache.windows.net:6380
    Name:   redisPassword
    Value:  my-sec
    Name:   actorStateStore
    Value:  true
    Name:   enableTLS
    Value:  true
  Type:     state.redis
  Version:  v1
Events:     <none>

Azure Cache for Redis - Overview image

Release Note

RELEASE NOTE: N/A

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 18 (11 by maintainers)

Most upvoted comments

@javageek79 can you please use GitHub UI instead of replying to email? because I do not see any images in your reply.

Seems like runtime cannot connect to placement service because the number of resolved addresses is zero.

From 1.0.0-rc.1, we use headless service dapr-placement-server.dapr-system.svc.cluster.local for placement server. CoreDNS will resolves this name to the IP address of placement server.

please run this to investigate the issue more.

kubectl get pods -n dapr-system -o wide
kubectl describe svc -n dapr-system dapr-placement-server