Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    AbserAri
    @abserari
    Hello guys, I wonder how Dapr realized the at-least-once semantics? Is Dapr depend on the underlying message bus? Nats don't promise the ack but nats-streaming do. Does it mean that when use nats as pubsub component dapr couldn't promise the at-least-once semantics?
    2 replies
    Ravindra
    @Ravindra-a
    Hi, Today when I installed dapr in my AKS cluster I see following error in dapr-operator pod
    kubectl logs -n dapr-system dapr-operator-d7fb8dc96-srrn5
    time="2020-08-30T19:07:44.595756486Z" level=info msg="log level set to: info" instance=dapr-operator-d7fb8dc96-srrn5 scope=dapr.operator type=log ver=0.10.0
    time="2020-08-30T19:07:44.596221515Z" level=info msg="metrics server started on :9090/" instance=dapr-operator-d7fb8dc96-srrn5 scope=dapr.metrics type=log ver=0.10.0
    time="2020-08-30T19:07:44.59679205Z" level=info msg="starting Dapr Operator -- version 0.10.0 -- commit 6032dc2" instance=dapr-operator-d7fb8dc96-srrn5 scope=dapr.operator type=log ver=0.10.0
    time="2020-08-30T19:07:45.005094919Z" level=info msg="Dapr Operator is started" instance=dapr-operator-d7fb8dc96-srrn5 scope=dapr.operator type=log ver=0.10.0
    I0830 19:07:45.005169 1 leaderelection.go:242] attempting to acquire leader lease dapr-system/operator.dapr.io...
    E0830 19:07:45.007903 1 reflector.go:153] pkg/mod/k8s.io/client-go@v0.17.2/tools/cache/reflector.go:105: Failed to list v1alpha1.Component: v1alpha1.ComponentList.Items: []v1alpha1.Component: v1alpha1.Component.Spec: v1alpha1.ComponentSpec.Metadata: []v1alpha1.MetadataItem: v1alpha1.MetadataItem.Value: ReadString: expects " or n, but found 6, error found in #10 byte of ...|,"value":60},{"name"|..., bigger context ...|gqc7ypnZUV4Ixw="},{"name":"timeoutInSec","value":60},{"name":"disableEntityManagement","value":false|...
    E0830 19:07:46.010398 1 reflector.go:153] pkg/mod/k8s.io/client-go@v0.17.2/tools/cache/reflector.go:105: Failed to list     v1alpha1.Component: v1alpha1.ComponentList.Items: []v1alpha1.Component: v1alpha1.Component.Spec: v1alpha1.ComponentSpec.Metadata: []v1alpha1.MetadataItem: v1alpha1.MetadataItem.Value: ReadString: expects " or n, but found 6, error found in #10 byte of ...|,"value":60},{"name"|..., bigger context ...|gqc7ypnZUV4Ixw="},{"name":"timeoutInSec","value":60},{"name":"disableEntityManagement","value":false|...
    E0830 19:07:47.012701 1 reflector.go:153] pkg/mod/k8s.io/client-go@v0.17.2/tools/cache/reflector.go:105: Failed to list v1alpha1.Component: v1alpha1.ComponentList.Items: []v1alpha1.Component: v1alpha1.Component.Spec: v1alpha1.ComponentSpec.Metadata: []v1alpha1.MetadataItem: v1alpha1.MetadataItem.Value: ReadString: expects " or n, but found 6, error found in #10 byte of ...|,"value":60},{"name"|..., bigger context ...|gqc7ypnZUV4Ixw="},{"name":"timeoutInSec","value":60},{"name":"disableEntityManagement","value":false|...
    E0830 19:07:48.015172 1 reflector.go:153] pkg/mod/k8s.io/client-go@v0.17.2/tools/cache/reflector.go:105: Failed to list     v1alpha1.Component: v1alpha1.ComponentList.Items: []v1alpha1.Component: v1alpha1.Component.Spec: v1alpha1.ComponentSpec.Metadata: []v1alpha1.MetadataItem: v1alpha1.MetadataItem.Value: ReadString: expects " or n, but found 6, error found in #10 byte of ...|,"value":60},{"name"|..., bigger context ...|gqc7ypnZUV4Ixw="},{"name":"timeoutInSec","value":60},{"name":"disableEntityManagement","value":false|...
    E0830 19:07:49.017291 1 reflector.go:153] pkg/mod/k8s.io/client-go@v0.17.2/tools/cache/reflector.go:105: Failed to list v1alpha1.Component: v1alpha1.ComponentList.Items: []v1alpha1.Component: v1alpha1.Component.Spec: v1alpha1.ComponentSpec.Metadata: []v1alpha1.MetadataItem: v1alpha1.MetadataItem.Value: ReadString: expects " or n, but found 6, error found in #10 byte of ...|,"value":60},{"name"|..., bigger context ...|gqc7ypnZUV4Ixw="},{"name":"timeoutInSec","value":60},{"name":"disableEntityManagement","value":false|...
    E0830 19:07:50.019669 1 reflector.go:153] pkg/mod/k8s.io/client-go@v0.17.2/tools/cache/reflector.go:105: Failed to list     v1alpha1.Component: v1alpha1.ComponentList.Items: []v1alpha1.Component: v1alpha1.Component.Spec: v1alpha1.ComponentSpec.Metadata: []v1alpha1.MetadataItem: v1alpha1.MetadataItem.Value: ReadString: expects " or n, but found 6, error found in #10 byte of ...|,"value":60},{"name"|..., bigger context ...|gqc7ypnZUV4Ixw="},{"name":"timeoutInSec","value":60},{"name":"disableEntityManagement","value":false|...
    E0830 19:07:51.022027 1 reflector.go:15
    I see now there is version 0.10, this was working fine 2 weeks back when version was 0.9 . Is there a way that I can use specify version during helm chart installation as I am using helm to install dapr
    Ravindra
    @Ravindra-a
    My main issue is I have configured pub-sub using Azure Service Bus, however when I am publishing anything to service bus although it gets posted to the sidecar it doesn't gets posted to the Service bus
    when I check logs for my pod I see this
    {"app_id":"notification","instance":"<redacted>","level":"info","msg":"mTLS is disabled. Skipping certificate request and tls validation","scope":"dapr.runtime","time":"2020-08-30T19:03:27.049587447Z","type":"log","ver":"0.10.0"}
    {"app_id":"notification","instance":"<redacted>","level":"warning","msg":"failed to load components: rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial tcp 10.0.120.180:80: connect: connection refused\"","scope":"dapr.runtime","time":"2020-08-30T19:03:36.068384958Z","type":"log","ver":"0.10.0"}
    Ravindra
    @Ravindra-a
    finally figured out my issue, something is definitely wrong in 0.10.0, so used --set global.tag=0.9.0. Eventually there wasn't any error in logs, however none of my components were getting detected so have to install everything in same namespace, including core dapr components. Found this link talking something about scopes - dapr/dapr#1181 . Is it necessary to have everything within same namespace ?
    19 replies
    Yaron Schneider
    @yaron2
    hey @Ravindra-a, I responded in a new thread on your latest message.
    Tugay Ersoy
    @Admiralkheir
    Hi, I have a problem with rabbitMQ, Running 2 service on my local machine with local dapr, all have a different port (grpc, metrics, etc) one service published event then subscriber triggering and returning 500 (for testing pub/sub mechanism) after that I restarted and didn't notice any triggering for my subscriber, I edited yaml component like this 
    apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
  name: messagebus
  namespace: default
spec:
  type: pubsub.rabbitmq
  metadata:
  - name: host
    value: amqp://localhost:5672 # Required. Example: "amqp://rabbitmq.default.svc.cluster.local:5672", "amqp://localhost:5672"
  - name: consumerID
    value: rabbitMqConsumer # Required. Any unique ID. Example: "myConsumerID"
  # - name: durable
  #   value: "true" # Optional. Default: "false"
  # # - name: deletedWhenUnused
  # #   value: <REPLACE-WITH-DELETE-WHEN-UNUSED> # Optional. Default: "false"
  - name: autoAck
    value: "true" # Optional. Default: "false"
  # # - name: deliveryMode
  # #   value: "0" # Optional. Default: "0". Values between 0 - 2.
  # - name: requeueInFailure
  #   value: "true" # Optional. Default: "false".
    Amit Hansda
    @amitHansda
    @Admiralkheir Does your publishing work? I think you need to specify username password in spec.metadata in host value.
    @Admiralkheir Watch out for dapr logs. If a component is not being initialized properly it's ought to say so
    Tugay Ersoy
    @Admiralkheir
    y it worked @amitHansda and component initialized
    Amit Hansda
    @amitHansda
    @Admiralkheir So publishing an event is working as you said. What application is you are using for subscribing? GO, NodeJs or Dotnetcore?
    Tugay Ersoy
    @Admiralkheir
    dotnetcore @amitHansda
    with redis component it worked but with rabbit this ack mechanism is not working
    Amit Hansda
    @amitHansda
    @Admiralkheir Okay... In my case of autoAck to set to false. Let me try again with setting it to false.
    Tugay Ersoy
    @Admiralkheir
    it did not work
    Amit Hansda
    @amitHansda
    @Admiralkheir Try cloning my repo https://github.com/amitHansda/store-manager
    It uses tye to start all service together. Also in components folder you may need to change the connection string. Mine uses possibly a different username password than yours
    3 replies
    Tugay Ersoy
    @Admiralkheir
    did you try this mechanism is it work with your app?
    Tugay Ersoy
    @Admiralkheir
    problem is ack mechanism, re-try logic. I don't have a problem with publishing or subscription
    FluentGuru
    @FluentGuru
    Hey guys, is there a sample for service to service RPC I can't see it on dapr/samples
    Yaron Schneider
    @yaron2
    @FluentGuru see here: https://github.com/dapr/quickstarts/tree/v0.10.0/hello-world
    ozturkcagtay
    @ozturkcagtay
    Is there an example project of grpc invocation with dotnet sdk?
    2 replies
    AbserAri
    @abserari
    This message was deleted
    @Admiralkheir image.png Hah, I think our YAML set correctly. so if there is a problem, it's on rabbitMQ component realization.
    Tugay Ersoy
    @Admiralkheir
    @abserari so what should i do? i dont get it
    AbserAri
    @abserari
    @Admiralkheir I did the test again and it looks like the autoAck mechanism didn't work.
    Unfortunately, no matter how many times I started a subscriber, he wouldn't have received a return of 500. The next step I think is to debug the dapr runtime. check if the autoAck parameters have been read according to our YAML.
    apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
  name: messagebus
  namespace: default
spec:
  type: pubsub.rabbitmq
  metadata:
  - name: host
    value: amqp://user:GSlU5LpIa1:32421 # Required. Example: "amqp://rabbitmq.default.svc.cluster.local:5672", "amqp://localhost:5672"
  - name: consumerID
    value: rabbitMqConsumer # Required. Any unique ID. Example: "myConsumerID"
  # - name: durable
  #   value: "true" # Optional. Default: "false"
  # # - name: deletedWhenUnused
  # #   value: <REPLACE-WITH-DELETE-WHEN-UNUSED> # Optional. Default: "false"
  - name: autoAck
    value: true # Optional. Default: "false"
  # # - name: deliveryMode
  # #   value: "0" # Optional. Default: "0". Values between 0 - 2.
  # - name: requeueInFailure
  #   value: "true" # Optional. Default: "false".
    and I even get the log but the at-least-once semantics not work.
    == APP == 2020/09/02 00:27:58 event - PubsubName: messagebus, Topic: neworder, ID: 5dc38ceb-9a1a-4d71-9c8e-0d44f98f4845, Data: ping

== DAPR == time="2020-09-02T00:27:58.172224+08:00" level=error msg="rabbitmq pub/sub: error handling message from topic 'neworder', error returned from app while processing pub/sub event: . status code returned: 500" app_id=faildsub1 instance=ArideMacBook-Air.local scope=dapr.contrib type=log ver=0.10.0
    Yaron Schneider
    @yaron2
    hey everyone, community call starting now. password: eWRhSklVTjJjSnhTaURDcFZaU2ZzQT09. url: https://us02web.zoom.us/j/85305980190
    David Aronchick
    @aronchick
    Is anyone having trouble on the android client with the passcode? It only allows ~8 characters :(
    2 replies
    Yaron Schneider
    @yaron2
    @abserari I'll debug this today
    2 replies
    Yanzhi Li
    @Li-Yanzhi

    DAPR won’t distribute message from input binding to multiple instances of consumer?

    I have the following scenario and issue:

    1) External system publish 500 TODO job message to RabbitMQ
    2) Consumer Pod use input binding (AMQP protocol) to receive messages from RabbitMQ, and Consumer Pod is running on demand (if no message, then no instances running)
    2) KEDA scale the Consumer Pod from 0 to 5 based on custom metrics of RabbitMQ queueLength
    3) Kubernetes create 5 instances of Consumer Pod based on scale rule (incoming 500 messages)
    4) The daprd sidecar of first instances of Consumer Pod will get all 500 messages and processed them one by one, each message will use 20 seconds to complete, at meantime, the status of all messages in RabbitMQ changed from Ready to Unacked - UnAcknoledged
    5) The other 4 instances of consumer Pod did NOT get any un-processed messages from RabbitMQ and free all time

    I need all 5 instances of Consumer Pod parallelly process all non-complete messages in RabbitMQ, What configuration I missed or did wrong?

    13 replies
    AbserAri
    @abserari
    image.png
    In my opinion, Yes, input binding only sequencingly sends to one app. @Li-Yanzhi . And it seems that use Pub/Sub and queueSubscribe meet your needs.
    Yanzhi Li
    @Li-Yanzhi
    Thanks @abserari , is this the only way to fix issue? it seems I have a lot code to refactor. I originally thought input binding can fully support the scenario of "competing consumer" mode, on the other hand, is such greedy algorithm of daprd sidecar safe enough? I means that if daprd sidecar get all current messages from queue (all message's status changed from Ready to Unack), when main container crashed for some reason, then all left messages cannot be picked up and processed by other pod?
    MohsenM
    @mohsenm53
    @yaron2 me again with another issue I am facing. I am currently using NATS as pubsub backend in my project. The problem is when handling a message fails, it doesn't retry even if I kill the pod and create it again.
    3 replies
    Tugay Ersoy
    @Admiralkheir
    like yaron said in this version ack mechanism with nats does not supported by dapr runtime, with version 0.11.0 it will be, you can look my thread on August 28
    7 replies
    David Aronchick
    @aronchick
    what's the agreed upon pattern for starting a service locally and then going into the background?
    Yaron Schneider
    @yaron2
    @aronchick if using the Dapr CLI, see this: https://github.com/dapr/cli#running-sidecar-only
    4 replies
    Christian Kaps
    @akkie
    Hi, could someone explain how HTTP requests in dapr are handled and what exactly happens under the hood? As an example I have a dapr service that exposes an HTTP API, implemented with the .NET core framework. So what happens exactly if I call the API from another dapr service with the InvokeMethod method of the dapr client? Am I right that the DaprClient makes a gRPC request to the sidecar, then the sidecar searches for the service and makes a gRPC request to the sidecar of the API service. And then the sidecar makes an HTTP call to the API? If so, can someone point me to the right code in GitHub?
    stepro71
    @stepro71
    Hi, I am struggling with Bindings. So how would I start if I wanted to create a new binding for a type of software (Database, DMS) I provide?
    1 reply
    sedat-eyuboglu
    @sedat-eyuboglu
    resim.png
    sedat-eyuboglu
    @sedat-eyuboglu
    There are some messages talking to integrate dapr with istio. Considering there will be two sidecar in the system, what is the benefit of using istio? I am trying to understand what istio does and dapr doesn't in service mesh? I have a look at https://istio.io/latest/docs/concepts/what-is-istio/ and didn't see a big difference between dapr consepts and istio consepts. Considering i will start to build a new design and all i need service to service communication, should i place istio in a daprized environment?
    1 reply
    Matt Carter
    @m-carter1
    Hi, after a while we seem to lose connection to pubsub (using redis) or state store (using sql). Our application will work for a while then we start to see ERR_PUBSUB_NOT_FOUND or ERR_STATE_STORE_NOT_CONFIGURED errors in the logs. Restarting the pods will get it working again, usually. Any ideas what is causing this? We are on version 0.10.0 and also using Istio
    13 replies
    Hanz van Aardt
    @hanzvanaardt
    Hi guys, I would like to clarify the best approach for a certain use case. We have a front end react app which publishes events as messages to a Google Cloud PubSub topic. We would like to pull these messages into our dapr-enabled back-end and then process them amongst back-end Microservices using a standard Dapr redis.pubsub component. With the new ability of Dapr to connect to multiple pubsub components (in our case Google Cloud PubSub for messaging coming from outside the Dapr-system environment and Redis PubSub for messages inside Dapr) what is die best approach. Should we use Dapr Pub Sub to get messages from Google PubSub or should we use the Dapr Binding which also supports Google PubSub? Is Dapr PubSub only for communication between Dapr enabled Microservices or is it feasible to use it to get messages from an external topic source as described. What will the pros and cons be between using Dapr PubSub with Google PubSub or Dapr Bindings with Google PubSub. We are discussing architecture and this question came up without clear answers. Any insight will be very valuable - thank you!
    1 reply
    FluentGuru
    @FluentGuru
    Hey guys!
    FluentGuru
    @FluentGuru
    Has anyone here setup a dapr deployment with docker compose on which each microservice is in their own compose deployment?
    with different IPs and all?
    Kyle Housley
    @khous
    @yaron2 I'm seeing the sidecar injector fail with this message:
    2020/09/04 00:02:52 http: TLS handshake error from 100.96.2.0:41578: remote error: tls: bad certificate
    It goes away for a while after restarting the deployment and then returns. Any idea what the problem could be? I saw the workaround here dapr/dapr#1621 (which is what was followed), but there was no link in that issue to the corresponding change in documentation. This is a version 0.8 installation.
    2 replies