Now that atskafka provides the basic functionalities required, we should deploy it to production, perhaps starting with a limited set of nodes. The test deployment should obviously write to a test kafka topic.
Analytics: should we create a kafka topic with a specific configuration for this, or is it sufficient to keep on using ema_test_ats?
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | • ema | T237993 Create replacement for Varnishkafka | |||
| Resolved | • ema | T247497 Test atskafka deployment |
Change 579247 had a related patch set uploaded (by Ema; owner: Ema):
[operations/puppet@production] atskafka: add puppet module
I had a chat with Ema, reporting what we discussed in here. The test will run on a couple of cp hosts, so I proposed to create 2 new topics called atskafka_test_webrequest_text and atskafka_test_webrequest_upload with three partitions each to test the client's ability to produce load balancing between multiple partitions.
Change 579513 had a related patch set uploaded (by Ema; owner: Ema):
[operations/puppet@production] cache: add atskafka webrequest test instance
Change 579514 had a related patch set uploaded (by Ema; owner: Ema):
[operations/puppet@production] cache: test atskafka webrequest on cp3050
Mentioned in SAL (#wikimedia-operations) [2020-03-17T10:02:41Z] <ema> create kafka topic atskafka_test_webrequest_text T247497
Change 579247 merged by Ema:
[operations/puppet@production] atskafka: add puppet module
Change 579513 merged by Ema:
[operations/puppet@production] cache: add atskafka webrequest test instance
Change 579514 merged by Ema:
[operations/puppet@production] cache: test atskafka webrequest on cp3050
Change 580364 had a related patch set uploaded (by Ema; owner: Ema):
[operations/puppet@production] atskafka: rdkafka configuration support
Change 580364 merged by Ema:
[operations/puppet@production] atskafka: rdkafka configuration support
Change 580908 had a related patch set uploaded (by Ema; owner: Ema):
[operations/puppet@production] atskafka: specify TLS settings
Change 580908 merged by Ema:
[operations/puppet@production] atskafka: specify TLS configuration
Change 580943 had a related patch set uploaded (by Ema; owner: Ema):
[operations/puppet@production] atskafka: rotate statistics file
elukey@kafka-jumbo1001:~$ kafka acls --add --allow-principal User:CN=varnishkafka --producer --topic atskafka_test_webrequest_text kafka-acls --authorizer-properties zookeeper.connect=conf1004.eqiad.wmnet,conf1005.eqiad.wmnet,conf1006.eqiad.wmnet/kafka/jumbo-eqiad --add --allow-principal User:CN=varnishkafka --producer --topic atskafka_test_webrequest_text Adding ACLs for resource `Topic:atskafka_test_webrequest_text`: User:CN=varnishkafka has Allow permission for operations: Write from hosts: * User:CN=varnishkafka has Allow permission for operations: Describe from hosts: * Adding ACLs for resource `Cluster:kafka-cluster`: User:CN=varnishkafka has Allow permission for operations: Create from hosts: * Current ACLs for resource `Topic:atskafka_test_webrequest_text`: User:CN=varnishkafka has Allow permission for operations: Write from hosts: * User:CN=varnishkafka has Allow permission for operations: Describe from hosts: * elukey@kafka-jumbo1001:~$ kafka acls --add --deny-principal User:ANONYMOUS --operation Write --topic atskafka_test_webrequest_text kafka-acls --authorizer-properties zookeeper.connect=conf1004.eqiad.wmnet,conf1005.eqiad.wmnet,conf1006.eqiad.wmnet/kafka/jumbo-eqiad --add --deny-principal User:ANONYMOUS --operation Write --topic atskafka_test_webrequest_text Adding ACLs for resource `Topic:atskafka_test_webrequest_text`: User:ANONYMOUS has Deny permission for operations: Write from hosts: * Current ACLs for resource `Topic:atskafka_test_webrequest_text`: User:CN=varnishkafka has Allow permission for operations: Write from hosts: * User:CN=varnishkafka has Allow permission for operations: Describe from hosts: * User:ANONYMOUS has Deny permission for operations: Write from hosts: *
Change 580943 abandoned by Ema:
atskafka: rotate statistics file
Reason:
Not needed any longer, see https://gerrit.wikimedia.org/r/#/c/operations/software/atskafka/ /580987/
Change 581435 had a related patch set uploaded (by Ema; owner: Ema):
[operations/puppet@production] ATS: add dt to atskafka log format
Change 581435 merged by Ema:
[operations/puppet@production] ATS: add dt to atskafka log format
We do have an atskafka instance currently running in production on cp3050. This task can be considered now done, further improvements to atskafka and extending its deployment should be tracked elsewhere.
Change 760895 had a related patch set uploaded (by Ema; author: Ema):
[operations/puppet@production] Revert \"cache: test atskafka webrequest on cp3050\"
Change 760895 merged by Ema:
[operations/puppet@production] Revert \"cache: test atskafka webrequest on cp3050\"
Mentioned in SAL (#wikimedia-operations) [2022-02-09T09:41:22Z] <ema> cp3050: stop and disable atskafka-webrequest.service T247497
Change 761288 had a related patch set uploaded (by Ema; author: Ema):
[operations/puppet@production] prometheus::ops: remove atskafka job definition
Change 761288 merged by Ema:
[operations/puppet@production] prometheus::ops: remove atskafka job definition
Mentioned in SAL (#wikimedia-operations) [2022-02-09T14:43:13Z] <ema> prometheus: remove atskafka target files - '/srv/prometheus/ops/targets/atskafka_*' T247497