Agent Groups
How to split Agents for a cluster into different "groups".
Last updated
Was this helpful?
.svg?alt=media&token=de534435-d87b-4f47-a762-54ed6aae1b02)
.svg?alt=media&token=5df48930-f99f-4779-b05f-359312e79636)
How to split Agents for a cluster into different "groups".
Last updated
Was this helpful?
Agent Groups are distinct sets of Agents that all belong to the same logical cluster. Groups enable a single logical cluster to be split into many different "groups" that are isolated at the network / service discovery layer.
For example, consider the scenario where a single logical WarpStream cluster is "flexed" across multiple VPCs, regions, or even cloud providers:
In the diagram above producer and consumer clients running in vpc_1 will only ever connect to Agents running in group_vpc_1. Similarly, producers and consumer running in vpc_2 will only ever connect to Agents running in group_vpc_2. However, since both Agent Groups belong to the same logical virtual cluster and have access to the same object storage bucket, clients in each VPC will be able to write and read data for all topics and partitions, even those that were created by clients / Agents running in a completely different VPC!
Agent groups are a powerful abstraction that enable a variety of use-cases:
Isolating specific producers or consumers to dedicated Agent Groups to avoid noisy neighbors.
"Flexing" a single logical cluster across multiple VPCs, regions, or even clouds providers without resorting to complex VPC peering setups.
Configuring Agent Groups is simple. Just add the -agentGroup $GROUP_NAME flag to your Agent deployment. For example, if you wanted to flex a single logical WarpStream cluster across two Kubernetes clusters running in different VPCs:
Alternatively, you can set the WARPSTREAM_AGENT_GROUP environment variable instead.
When your Kafka (or Schema Registry) client connects to an Agent in a specific group, the WarpStream service discovery system will ensure that your client only connects to other Agents in the same group. This means that in order to take advantage of the Agent group functionality, you need to ensure that the bootstrap URL you configure in your client will only ever resolve to Agents in the correct group.
Targeting specific Agent Groups in Kubernetes is easy. Each Agent group will have its own helm deployment, and therefore will have its own Kubernetes service. Use the Kubernetes service name that corresponds to the Agent Group that you want to target as the bootstrap URL for your Kafka client.
Most non-Kubernetes deployments use WarpStream's hosted convenience bootstrap URL for service discovery. These URLs are visible in the WarpStream UI under the "Connect" tab in the cluster view and generally look something like this:
api-XXXX-XXXX-XXXX-XXXX-XXXX.kafka.discoveryv2.prod-z.us-east-1.warpstream.com:9092
This bootstrap URL is not group-aware by default and therefore may return Agent I.P addresses for any agent group. To target a specific agent group, modify the bootstrap URL like this:
api-XXXX-XXXX-XXXX-XXXX-XXXX.group$GROUP_NAME.kafka.discoveryv2.prod-z.us-east-1.warpstream.com:9092.
For example, if the agent group name was: "test-group-foo", then the bootstrap URL would become:
api-XXXX-XXXX-XXXX-XXXX-XXXX.grouptest-group-foo.kafka.discoveryv2.prod-z.us-east-1.warpstream.com:9092
