fixup! fixup! fixup! fixup! Add bloom planner and bloom builder to backend target

Signed-off-by: Christian Haudum <[email protected]>

Author: chaudum

docs/sources/operations/query-acceleration-blooms.md

@@ -43,7 +43,7 @@ and querying the bloom filters that only pays off at large scale deployments.
 {{< /admonition >}}
 
 To start building and using blooms you need to:
-- Deploy the [Bloom Planner and Builder](#bloom-planner-and-builder) components (as a [microservic][microservices] or via the [SSD][ssd] `backend` target) and enable the components in the [Bloom Build config][bloom-build-cfg].
+- Deploy the [Bloom Planner and Builder](#bloom-planner-and-builder) components (as a [microservice][microservices] or via the [SSD][ssd] `backend` target) and enable the components in the [Bloom Build config][bloom-build-cfg].
 - Deploy the [Bloom Gateway](#bloom-gateway) component (as a [microservice][microservices] or via the [SSD][ssd] `backend` target) and enable the component in the [Bloom Gateway config][bloom-gateway-cfg].
 - Enable blooms building and filtering for each tenant individually, or for all of them by default.
 

pkg/bloombuild/planner/planner.go

@@ -159,7 +159,7 @@ func (p *Planner) stopping(_ error) error {
 func (p *Planner) running(ctx context.Context) error {
 	go p.trackInflightRequests(ctx)
 
-	// run once at beginning, but deplay by 1m to allow ring consolidation when running in SSD mode
+	// run once at beginning, but delay by 1m to allow ring consolidation when running in SSD mode
 	initialPlanningTimer := time.NewTimer(time.Minute)
 	defer initialPlanningTimer.Stop()
 
@@ -936,7 +936,7 @@ func (p *Planner) BuilderLoop(builder protos.PlannerForBuilder_BuilderLoopServer
 	logger := log.With(p.logger, "builder", builderID)
 
 	if !p.isLeader() {
-		return fmt.Errorf("planner is not leader")
+		return errPlannerIsNotLeader
 	}
 
 	level.Debug(logger).Log("msg", "builder connected")