From d340b758247c0fdd9335b514b6ed991c5541d1e7 Mon Sep 17 00:00:00 2001 From: Nina Hingerl <76950046+NHingerl@users.noreply.github.com> Date: Thu, 21 Nov 2024 11:57:33 +0100 Subject: [PATCH] docs: Replace Remedy with Solution (#686) --- docs/contributor/troubleshooting.md | 2 +- docs/user/troubleshooting/evnt-01-eventing-troubleshooting.md | 2 +- docs/user/troubleshooting/evnt-02-jetstream-troubleshooting.md | 2 +- docs/user/troubleshooting/evnt-03-type-collision.md | 2 +- docs/user/troubleshooting/evnt-04-free-jetstream-storage.md | 2 +- docs/user/troubleshooting/evnt-05-fix-pending-messages.md | 2 +- 6 files changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/contributor/troubleshooting.md b/docs/contributor/troubleshooting.md index 47315c2cf..d58f06610 100644 --- a/docs/contributor/troubleshooting.md +++ b/docs/contributor/troubleshooting.md @@ -14,7 +14,7 @@ If you cannot find your issue described here, take a look at the [Eventing Troub **Cause:** The namespace of the Deployment does not exist yet. -**Remedy:** Create the namespace. +**Solution:** Create the namespace. ```sh kubectl create ns kyma-system diff --git a/docs/user/troubleshooting/evnt-01-eventing-troubleshooting.md b/docs/user/troubleshooting/evnt-01-eventing-troubleshooting.md index f29b17b11..17f676441 100644 --- a/docs/user/troubleshooting/evnt-01-eventing-troubleshooting.md +++ b/docs/user/troubleshooting/evnt-01-eventing-troubleshooting.md @@ -12,7 +12,7 @@ Trouble with Kyma Eventing may be caused by various issues, so this document guides you through the diagnostic steps to determine the specific root cause. -## Remedy +## Solution Follow these steps to detect the source of the problem: diff --git a/docs/user/troubleshooting/evnt-02-jetstream-troubleshooting.md b/docs/user/troubleshooting/evnt-02-jetstream-troubleshooting.md index e2449a263..ab96b2add 100644 --- a/docs/user/troubleshooting/evnt-02-jetstream-troubleshooting.md +++ b/docs/user/troubleshooting/evnt-02-jetstream-troubleshooting.md @@ -4,7 +4,7 @@ Events were not received by the consumers. -## Remedy +## Solution 1. Follow the diagnostic steps as mentioned in [Eventing Troubleshooting](evnt-01-eventing-troubleshooting.md). diff --git a/docs/user/troubleshooting/evnt-03-type-collision.md b/docs/user/troubleshooting/evnt-03-type-collision.md index 85303443f..c27156af7 100644 --- a/docs/user/troubleshooting/evnt-03-type-collision.md +++ b/docs/user/troubleshooting/evnt-03-type-collision.md @@ -9,7 +9,7 @@ Subscriber receives irrelevant events. To conform to Cloud Event specifications, Eventing modifies the event names to filter out prohibited characters. For details, see [Event name cleanup](../evnt-event-names.md#event-name-cleanup). In some cases, it can lead to a naming collision, which can cause subscribers to receive irrelevant events. -## Remedy +## Solution Follow these steps to detect if naming collision is the source of the problem: diff --git a/docs/user/troubleshooting/evnt-04-free-jetstream-storage.md b/docs/user/troubleshooting/evnt-04-free-jetstream-storage.md index 82e0083b7..1cc9a1cef 100644 --- a/docs/user/troubleshooting/evnt-04-free-jetstream-storage.md +++ b/docs/user/troubleshooting/evnt-04-free-jetstream-storage.md @@ -20,7 +20,7 @@ To prevent event loss, the backend stops receiving events, and no further events > [!NOTE] > If you delete a Subscriber (sink) while there is still a Kyma Subscription pointing to that sink, the events published to that Subscription pile up in the stream and possibly delay the event delivery to other Subscribers. -## Remedy +## Solution There are several ways to free the space on NATS JetStream backend: diff --git a/docs/user/troubleshooting/evnt-05-fix-pending-messages.md b/docs/user/troubleshooting/evnt-05-fix-pending-messages.md index a126ccb02..f63b9c91e 100644 --- a/docs/user/troubleshooting/evnt-05-fix-pending-messages.md +++ b/docs/user/troubleshooting/evnt-05-fix-pending-messages.md @@ -13,7 +13,7 @@ When the leader is elected, all the messages are replicated across the replicas. Sometimes replicas can go out of sync with the other replicas. As a result, messages on some consumers can stop being acknowledged and start piling up in the stream. -## Remedy +## Solution To fix the "broken" consumers with pending messages, trigger a leader reelection. You can do this either on the consumers that have pending messages, or if that fails, on the stream level.