Production Issue with NATs on AKS 1.30.x – Intermittent NoStreamResponseError

Mohamed Shahir

unread,

Feb 19, 2025, 1:51:08 PMFeb 19

to nats

Hi All,

We are experiencing an intermittent issue with NATs deployed on AKS 1.30.x in our production environment. When posting messages to the NATs queue, we occasionally receive the following error:

nats.js.errors.NoStreamResponseError: nats: no response from stream

The issue occurs sporadically—some messages are successfully posted, while others fail. Notably, our lower environments (Dev and UAT) are functioning without any issues.

Details:

Helm version of NATs: 1.1.8
Terraform configuration for NATs installation: [Included below]

resource "helm_release" "nats" {
  name       = "nats"
  chart      = "nats"
  version    = "1.1.8"
  namespace  = var.namespace  # Specify your namespace here
  create_namespace = true
  repository = "https://nats-io.github.io/k8s/helm/charts/"  # NATS Helm repository URL

  set {
    name  = "replicas"
    value = 2
  }

  set {
    name  = "natsBox.enabled"
    value = "false"
  }

  set {
    name  = "config.jetstream.enabled"
    value = "true"
  }

  set {
    name  = "config.jetstream.memoryStore.enabled"
    value = "true"
  }

  set {
    name  = "config.jetstream.memoryStore.maxSize"
    value = "256Mi"
  }

  set {
    name  = "config.jetstream.fileStore.enabled"
    value = "true"
  }

  set {
    name  = "config.jetstream.fileStore.pvc.enabled"
    value = "true"
  }

  set {
    name  = "config.jetstream.fileStore.pvc.size"
    value = "256Mi"
  }
  set {
    name  = "nodeSelector.app"
    value = "srg"
  }
  set {
    name  = "replicaCount"
    value = "2"
  }

}

--------

ERROR - 140164478696248 - ThreadPoolExecutor-1_0] Exception publish_to_stream.nats: no response from stream

Traceback (most recent call last):

File "/usr/local/lib/python3.12/site-packages/nats/js/client.py", line 181, in publish

msg = await self._nc.request(

^^^^^^^^^^^^^^^^^^^^^^^

File "/usr/local/lib/python3.12/site-packages/nats/aio/client.py", line 1026, in request

raise errors.NoRespondersError

nats.errors.NoRespondersError: nats: no responders available for request

During handling of the above exception, another exception occurred:

Traceback (most recent call last):

File "/svc/Common/common/components/message_broker.py", line 151, in publish_to_stream

await js.publish(subject, message.encode("utf-8"))

File "/usr/local/lib/python3.12/site-packages/nats/js/client.py", line 188, in publish

raise nats.js.errors.NoStreamResponseError

nats.js.errors.NoStreamResponseError: nats: no response from stream.

-------------

Could you please help us identify the root cause of this issue? Your guidance would be greatly appreciated.

Thanks & Regards,

Shahir

Alex Bozhenko

unread,

Feb 20, 2025, 12:51:12 PMFeb 20

to nats

If you are using default version from the helm chart, I assume you are on nats version 2.10.10
https://github.com/nats-io/k8s/blob/nats-1.1.8/helm/charts/nats/Chart.yaml#L2

That version is 1 year old. There were many bug fixes since then: https://github.com/nats-io/nats-server/compare/v2.10.10...v2.10.25
I would recommend to start with upgrading to the latest released version of helm chart and nats-server.

Regards,

Alex

Mohamed Shahir

unread,

Feb 20, 2025, 3:28:07 PMFeb 20

to nat...@googlegroups.com

Thank you, Alex, for your suggestion. We have completed the upgrade and are currently testing to confirm whether the issue has been resolved.

Regards,

Shahir

--
You received this message because you are subscribed to the Google Groups "nats" group.
To unsubscribe from this group and stop receiving emails from it, send an email to natsio+un...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/natsio/f51d6f7f-1991-426d-afc6-0c2aa81caffbn%40googlegroups.com.

Reply all

Reply to author

Forward