Sidecar crashing when state.sqlserver included

[andycwk]

Expected Behavior

When I attempted to include a sql server state component in my Dapr app configuration within a local Kind Kubernetes cluster the Dapr sidecar for my service should initiate the state store and the Dapr sidecar should spin up and start servicing requests for the associated service.

Actual Behavior

The sidecar starts to initialise the state component, but a panic is thrown and the sidecar spins into a spiral of restarts.

The following logs are generated..
dapr-sidecar.log

After discussion within Discord it was suggested that the sql dependency may require updating.. a quick check shows that this looks like the most likely issue.

Steps to Reproduce the Problem

Install the latest version of Dapr (v1.3.0 at point of raising this issue), ensure a sidecar is being injected into a service pod and then add a sql state component - I had the following state config..

apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
  name: idea-state
  namespace: default
spec:
  type: state.sqlserver
  version: v1
  metadata:
    - name: connectionString
      value: Server=xxxxxxx.database.windows.net;Database=xxxxx-xxxx;User ID=uxxx;Password=xxxx;
    - name: tableName
      value: state # Required.
    - name: schema
      value: "idea" # Optional. defaults to "dbo"

As above I guess :/

Release Note

RELEASE NOTE: UPDATE Bumped go-mssqldb dependency version

[andycwk]

As mentioned in Discord, I don't really have a fantastic level of skill with Go but should be able to pull a PR together that bumps the go-mssqldb version.. fingers crossed all the tests still work and I don't hit too many issues though!

Unless someone else beats me to it, I'll have a look over the weekend.

[berndverst]

Hi @andycwk, I am not surprised it's crashing. I am currently working on getting this component ready for GA and I noticed that it doesn't work at all. After much research I found that this is caused by a bug in the underlying SQL library when combined with Go 1.16.

You can expect that component to be fixed (and hopefully also generally available) in the next Dapr release.

This is the underlying root cause:
denisenkom/go-mssqldb#639

[berndverst]

/assign

[andycwk]

Ah cool, I was planning on getting a fix in for this - but then life stepped in and gave me a swift kick :/

If you need me to beta test it just shout up 👍

[berndverst]

@andycwk sounds great -- would definitely love to have you verify this once we have one of the release candidates for the 1.4 release.