<td>Grace period to allow the backend to shutdown before it is killed. Especially for the ingestor, this must be increased. It must be long enough so backends can be gracefully shutdown flushing/transferring all data and to successfully leave the member ring on shutdown.</td>
<td>Grace period to allow the backend to shutdown before it is killed. Especially for the ingester, this must be increased. It must be long enough so backends can be gracefully shutdown flushing/transferring all data and to successfully leave the member ring on shutdown.</td>
<td><prelang="json">
300
</pre>
@ -3683,7 +3683,7 @@ null
<tr>
<td>write.serviceLabels</td>
<td>object</td>
<td>Labels for ingestor service</td>
<td>Labels for ingester service</td>
<td><prelang="json">
{}
</pre>
@ -3701,7 +3701,7 @@ null
<tr>
<td>write.terminationGracePeriodSeconds</td>
<td>int</td>
<td>Grace period to allow the write to shutdown before it is killed. Especially for the ingestor, this must be increased. It must be long enough so writes can be gracefully shutdown flushing/transferring all data and to successfully leave the member ring on shutdown.</td>
<td>Grace period to allow the write to shutdown before it is killed. Especially for the ingester, this must be increased. It must be long enough so writes can be gracefully shutdown flushing/transferring all data and to successfully leave the member ring on shutdown.</td>
The ingestor, querier, etc. might start, but if those changes are not made, you will see logs like
When installing Loki on Istio service mesh you must complete some additional steps. Without these steps, the ingester, querier, etc. might start, but you will see logs like the following:
When istio-injection is enabled on the namespace running Loki, there are few changes needed. One of the main changes is around the `Service``appProtocols`.
Given that istio will not allow a pod to resolve another pod using an ip address, the pods part of the `memberlist` will fail.
When you enable istio-injection on the namespace where Loki is running, you need to also modify the configuration for the Loki services. Given that Istio will not allow a pod to resolve another mod using an IP address, you must also modify the `memberlist` service.
## Changes Required
## Required changes
### Query Frontend Service
### Query frontend service
Make the following modifications to the file for Loki's Query Frontend service.
1. Change the name of `grpc` port to `grpclb`. This is used by the grpc load balancing strategy which relies on SRV records. Otherwise the `querier` will not be able to reach the `query-frontend`. See https://github.com/grafana/loki/blob/0116aa61c86fa983ddcbbd5e30a2141d2e89081a/production/ksonnet/loki/common.libsonnet#L19
and
@ -62,6 +63,8 @@ spec:
### Querier service
Make the following modifications to the file for Loki's Querier service.
Set the `appProtocol` of the `grpc` service to `tcp`
```
@ -94,7 +97,9 @@ spec:
```
### Ingester Service and Ingester Headless Service
### Ingester service and Ingester headless service
Make the following modifications to the file for Loki's Query Ingester and Ingester Headless service.
Set the `appProtocol` of the `grpc` port to `tcp`
@ -126,7 +131,9 @@ spec:
type: ClusterIP
```
### Distributor Service
### Distributor service
Make the following modifications to the file for Loki's Distributor service.
Set the `appProtocol` of the `grpc` port to `tcp`
@ -158,7 +165,9 @@ spec:
```
## Memberlist Service
### Memberlist service
Make the following modifications to the file for the Memberlist service.