From 48cf9625846139cd0600dca58cc6d9d8f991a98a Mon Sep 17 00:00:00 2001 From: Biswarup Date: Mon, 17 Oct 2022 22:36:48 +0530 Subject: [PATCH] typo fix in docs (workerdef) (#3297) Co-authored-by: Biswarup Dass --- docs/docs/configuration/workerdef.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/docs/configuration/workerdef.md b/docs/docs/configuration/workerdef.md index 34347a2ad8..7081f989ff 100644 --- a/docs/docs/configuration/workerdef.md +++ b/docs/docs/configuration/workerdef.md @@ -3,7 +3,7 @@ A worker is responsible for executing a task. Operator and System tasks are handled by the Conductor server, while user defined tasks needs to have a worker created that awaits the work to be scheduled by the server for it to be executed. Workers can be implemented in any language, and Conductor provides support for Java, Golang and Python worker framework that provides features such as -polling threads, metrics and server communication that makes creating workers each. +polling threads, metrics and server communication that makes creating workers easy. Each worker embodies Microservice design pattern and follows certain basic principles: @@ -11,4 +11,4 @@ Each worker embodies Microservice design pattern and follows certain basic princ 2. Each worker executes a very specific task and produces well defined output given specific inputs. 3. Workers are meant to be idempotent (or should handle cases where the task that partially executed gets rescheduled due to timeouts etc.) 4. Workers do not implement the logic to handle retries etc, that is taken care by the Conductor server. - \ No newline at end of file +