Skip to content

Instantly share code, notes, and snippets.

@deferraz

deferraz/output_docker_tests

Created June 21, 2022 02:20
Show Gist options

  • Select an option

    Learn more about clone URLs
  • Save deferraz/be2c4efd77a5ea69b66da61ce78593b9 to your computer and use it in GitHub Desktop.

Select an option

Learn more about clone URLs
Save deferraz/be2c4efd77a5ea69b66da61ce78593b9 to your computer and use it in GitHub Desktop.
Download ZIP
docker_tests
Raw
output_docker_tests
docker build -f Dockerfile.integration . -t envoyproxy/ratelimit_integration:0a9d1ff6 && \
docker run $(tty -s && echo "-it" || echo) envoyproxy/ratelimit_integration:0a9d1ff6
#1 [internal] load build definition from Dockerfile.integration
#1 sha256:cdf179ed3d8fb24fc0c0de39a9524ce4d5d2efc5da54b5b0c867ec4bb89b6534
#1 transferring dockerfile: 55B 0.0s done
#1 DONE 0.0s
#2 [internal] load .dockerignore
#2 sha256:6e076c9b381accc1f7990eb9880f986770261beb095596f2ef6540f4cc28491d
#2 transferring context: 2B done
#2 DONE 0.0s
#3 [internal] load metadata for docker.io/library/golang:1.18
#3 sha256:f4e19f57653cc0a228a51c5d1fec5bdbe88100edb970ccdd95e88e0dfac945b1
#3 DONE 1.5s
#4 [1/9] FROM docker.io/library/golang:1.18@sha256:1c3d22f95ce57821fff1dcd857c54809ea62f33634e2696e0d623e077c97bb8f
#4 sha256:24750b4c7d1f3b9fd4e7833090053c630108c21b0311978e41d93b55c3b7e6de
#4 DONE 0.0s
#7 [internal] load build context
#7 sha256:384a293e566dff56cb3b2b7245a4d12f0a8dfff819c71c55c3f7ea922c402cdb
#7 transferring context: 5.59kB 0.0s done
#7 DONE 0.0s
#6 [3/9] WORKDIR /workdir
#6 sha256:1bc90d60bf9dd4b95d85acb43b0c42cb6cf5fbf05d49d3deeae6090cc23add20
#6 CACHED
#10 [6/9] COPY Makefile /workdir
#10 sha256:f9600fa69a491e0adef75d43e314b5ec19598a6840c047bffae9dfae56d9522e
#10 CACHED
#8 [4/9] COPY go.mod go.sum /workdir/
#8 sha256:2fc624b49766dd93eeffae3ca45be0518d74f2f07d6d6388ac75e4aa8e654b69
#8 CACHED
#12 [8/9] COPY src /workdir/src
#12 sha256:d75d4ed974318b8cc5e92cfb2f7dd2008dea63004f9f01ec2a881562582574b0
#12 CACHED
#5 [2/9] RUN apt-get update -y && apt-get install sudo stunnel4 redis memcached -y && rm -rf /var/lib/apt/lists/*
#5 sha256:039a4362aa660d25418357bf4562e537563de524f7f65b114b02bfbe34aa15a1
#5 CACHED
#9 [5/9] RUN go mod download
#9 sha256:49b2822b534d9473f82cd0a1156b7ed2483904c7b2b876d9d504ad0843b5bf0b
#9 CACHED
#11 [7/9] RUN make bootstrap
#11 sha256:556702d3dba3b2bda04d0049e5cc70374248b9a4b9687bba5565f0729efd4f70
#11 CACHED
#13 [9/9] COPY test /workdir/test
#13 sha256:5f93094d291281dcd1284125679b5902105569dde17db44e5ada1e04e89ec5a5
#13 CACHED
#14 exporting to image
#14 sha256:e8c613e07b0b7ff33893b694f7759a10d42e180f2b4dc349fb57dc6b71dcab00
#14 exporting layers done
#14 writing image sha256:d5a5cda70d6809089d8fa39ad14f1735122d3ffb86e7fef700b4d7f69784205b done
#14 naming to docker.io/envoyproxy/ratelimit_integration:0a9d1ff6 done
#14 DONE 0.0s
Use 'docker scan' to run Snyk tests against images to find vulnerabilities and learn how to fix them
echo "$REDIS_STUNNEL" >> redis.conf
echo "$REDIS_PER_SECOND_STUNNEL" >> redis-per-second.conf
echo "$REDIS_VERIFY_PEER_STUNNEL" >> redis-verify-peer.conf
openssl req -new -newkey rsa:4096 -days 365 -nodes -x509 \
-subj "/C=US/ST=Denial/L=Springfield/O=Dis/CN=localhost" \
-addext "subjectAltName = DNS:localhost" \
-keyout key.pem -out cert.pem
Generating a RSA private key
......................++++
.......................................................................++++
writing new private key to 'key.pem'
-----
cat key.pem cert.pem > private.pem
sudo cp cert.pem /usr/local/share/ca-certificates/redis-stunnel.crt
chmod 640 key.pem cert.pem private.pem
sudo update-ca-certificates
Updating certificates in /etc/ssl/certs...
1 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d...
done.
sudo stunnel redis.conf
stunnel: LOG5[ui]: stunnel 5.56 on x86_64-pc-linux-gnu platform
stunnel: LOG5[ui]: Compiled with OpenSSL 1.1.1k 25 Mar 2021
stunnel: LOG5[ui]: Running with OpenSSL 1.1.1n 15 Mar 2022
stunnel: LOG5[ui]: Threading:PTHREAD Sockets:POLL,IPv6,SYSTEMD TLS:ENGINE,FIPS,OCSP,PSK,SNI Auth:LIBWRAP
stunnel: LOG5[ui]: Reading configuration from file /workdir/redis.conf
stunnel: LOG5[ui]: UTF-8 byte order mark not detected
stunnel: LOG5[ui]: FIPS mode disabled
stunnel: LOG5[ui]: Configuration successful
sudo stunnel redis-per-second.conf
stunnel: LOG5[ui]: stunnel 5.56 on x86_64-pc-linux-gnu platform
stunnel: LOG5[ui]: Compiled with OpenSSL 1.1.1k 25 Mar 2021
stunnel: LOG5[ui]: Running with OpenSSL 1.1.1n 15 Mar 2022
stunnel: LOG5[ui]: Threading:PTHREAD Sockets:POLL,IPv6,SYSTEMD TLS:ENGINE,FIPS,OCSP,PSK,SNI Auth:LIBWRAP
stunnel: LOG5[ui]: Reading configuration from file /workdir/redis-per-second.conf
stunnel: LOG5[ui]: UTF-8 byte order mark not detected
stunnel: LOG5[ui]: FIPS mode disabled
stunnel: LOG5[ui]: Configuration successful
sudo stunnel redis-verify-peer.conf
stunnel: LOG5[ui]: stunnel 5.56 on x86_64-pc-linux-gnu platform
stunnel: LOG5[ui]: Compiled with OpenSSL 1.1.1k 25 Mar 2021
stunnel: LOG5[ui]: Running with OpenSSL 1.1.1n 15 Mar 2022
stunnel: LOG5[ui]: Threading:PTHREAD Sockets:POLL,IPv6,SYSTEMD TLS:ENGINE,FIPS,OCSP,PSK,SNI Auth:LIBWRAP
stunnel: LOG5[ui]: Reading configuration from file /workdir/redis-verify-peer.conf
stunnel: LOG5[ui]: UTF-8 byte order mark not detected
stunnel: LOG5[ui]: FIPS mode disabled
stunnel: LOG5[ui]: Configuration successful
mkdir -p ./bin
go build -mod=readonly -o ./bin/ratelimit github.com/envoyproxy/ratelimit/src/service_cmd
go build -mod=readonly -o ./bin/ratelimit_client github.com/envoyproxy/ratelimit/src/client_cmd
go build -mod=readonly -o ./bin/ratelimit_config_check github.com/envoyproxy/ratelimit/src/config_check_cmd
go test -race github.com/envoyproxy/ratelimit/...
? github.com/envoyproxy/ratelimit/src/assert [no test files]
? github.com/envoyproxy/ratelimit/src/client_cmd [no test files]
? github.com/envoyproxy/ratelimit/src/config [no test files]
? github.com/envoyproxy/ratelimit/src/config_check_cmd [no test files]
? github.com/envoyproxy/ratelimit/src/limiter [no test files]
ok github.com/envoyproxy/ratelimit/src/memcached 0.082s
? github.com/envoyproxy/ratelimit/src/metrics [no test files]
? github.com/envoyproxy/ratelimit/src/redis [no test files]
? github.com/envoyproxy/ratelimit/src/server [no test files]
? github.com/envoyproxy/ratelimit/src/service [no test files]
? github.com/envoyproxy/ratelimit/src/service_cmd [no test files]
? github.com/envoyproxy/ratelimit/src/service_cmd/runner [no test files]
ok github.com/envoyproxy/ratelimit/src/settings 0.058s
ok github.com/envoyproxy/ratelimit/src/srv 0.028s
? github.com/envoyproxy/ratelimit/src/stats [no test files]
? github.com/envoyproxy/ratelimit/src/trace [no test files]
? github.com/envoyproxy/ratelimit/src/utils [no test files]
? github.com/envoyproxy/ratelimit/test/common [no test files]
ok github.com/envoyproxy/ratelimit/test/config 0.094s
ok github.com/envoyproxy/ratelimit/test/limiter 0.115s
ok github.com/envoyproxy/ratelimit/test/memcached 0.154s
ok github.com/envoyproxy/ratelimit/test/metrics 0.560s
? github.com/envoyproxy/ratelimit/test/mocks [no test files]
? github.com/envoyproxy/ratelimit/test/mocks/config [no test files]
? github.com/envoyproxy/ratelimit/test/mocks/limiter [no test files]
? github.com/envoyproxy/ratelimit/test/mocks/memcached [no test files]
? github.com/envoyproxy/ratelimit/test/mocks/redis [no test files]
? github.com/envoyproxy/ratelimit/test/mocks/rls [no test files]
? github.com/envoyproxy/ratelimit/test/mocks/runtime/loader [no test files]
? github.com/envoyproxy/ratelimit/test/mocks/runtime/snapshot [no test files]
? github.com/envoyproxy/ratelimit/test/mocks/srv [no test files]
? github.com/envoyproxy/ratelimit/test/mocks/stats [no test files]
? github.com/envoyproxy/ratelimit/test/mocks/utils [no test files]
ok github.com/envoyproxy/ratelimit/test/redis 0.291s
ok github.com/envoyproxy/ratelimit/test/server 0.073s
ok github.com/envoyproxy/ratelimit/test/service 0.113s
ok github.com/envoyproxy/ratelimit/test/srv 0.057s
redis-server --port 6381 --requirepass password123 &
redis-server --port 6382 --requirepass password123 &
redis-server --port 6361 --requirepass password123 &
redis-server --port 6392 --requirepass password123 &
6967:C 21 Jun 2022 02:17:39.385 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
6967:C 21 Jun 2022 02:17:39.385 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=6967, just started
6967:C 21 Jun 2022 02:17:39.385 # Configuration loaded
redis-server --port 6393 --requirepass password123 --slaveof 127.0.0.1 6392 --masterauth password123 &
_._
_.-``__ ''-._
_.-`` `. `_. ''-._ Redis 6.0.16 (00000000/0) 64 bit
.-`` .-```. ```\/ _.,_ ''-._
( ' , .-` | `, ) Running in standalone mode
|`-._`-...-` __...-.``-._|'` _.-'| Port: 6381
| `-._ `._ / _.-' | PID: 6967
`-._ `-._ `-./ _.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' | http://redis.io
`-._ `-._`-.__.-'_.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' |
`-._ `-._`-.__.-'_.-' _.-'
`-._ `-.__.-' _.-'
`-._ _.-'
`-.__.-'
6967:M 21 Jun 2022 02:17:39.387 # Server initialized
6967:M 21 Jun 2022 02:17:39.387 * Ready to accept connections
6969:C 21 Jun 2022 02:17:39.389 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
6969:C 21 Jun 2022 02:17:39.389 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=6969, just started
6969:C 21 Jun 2022 02:17:39.389 # Configuration loaded
mkdir 26394 && cp test/integration/conf/sentinel.conf 26394/sentinel.conf && redis-server 26394/sentinel.conf --sentinel --port 26394 &
6971:C 21 Jun 2022 02:17:39.390 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
6971:C 21 Jun 2022 02:17:39.390 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=6971, just started
6971:C 21 Jun 2022 02:17:39.390 # Configuration loaded
_._
_.-``__ ''-._
_.-`` `. `_. ''-._ Redis 6.0.16 (00000000/0) 64 bit
.-`` .-```. ```\/ _.,_ ''-._
( ' , .-` | `, ) Running in standalone mode
|`-._`-...-` __...-.``-._|'` _.-'| Port: 6382
| `-._ `._ / _.-' | PID: 6969
`-._ `-._ `-./ _.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' | http://redis.io
`-._ `-._`-.__.-'_.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' |
`-._ `-._`-.__.-'_.-' _.-'
`-._ `-.__.-' _.-'
`-._ _.-'
`-.__.-'
6969:M 21 Jun 2022 02:17:39.391 # Server initialized
6969:M 21 Jun 2022 02:17:39.392 * Ready to accept connections
mkdir 26395 && cp test/integration/conf/sentinel.conf 26395/sentinel.conf && redis-server 26395/sentinel.conf --sentinel --port 26395 &
_._
_.-``__ ''-._
_.-`` `. `_. ''-._ Redis 6.0.16 (00000000/0) 64 bit
.-`` .-```. ```\/ _.,_ ''-._
( ' , .-` | `, ) Running in standalone mode
|`-._`-...-` __...-.``-._|'` _.-'| Port: 6361
| `-._ `._ / _.-' | PID: 6971
`-._ `-._ `-./ _.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' | http://redis.io
`-._ `-._`-.__.-'_.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' |
`-._ `-._`-.__.-'_.-' _.-'
`-._ `-.__.-' _.-'
`-._ _.-'
`-.__.-'
6971:M 21 Jun 2022 02:17:39.393 # Server initialized
6971:M 21 Jun 2022 02:17:39.394 * Ready to accept connections
mkdir 26396 && cp test/integration/conf/sentinel.conf 26396/sentinel.conf && redis-server 26396/sentinel.conf --sentinel --port 26396 &
6973:C 21 Jun 2022 02:17:39.396 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
6973:C 21 Jun 2022 02:17:39.396 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=6973, just started
6973:C 21 Jun 2022 02:17:39.396 # Configuration loaded
redis-server --port 6397 --requirepass password123 &
_._
_.-``__ ''-._
_.-`` `. `_. ''-._ Redis 6.0.16 (00000000/0) 64 bit
.-`` .-```. ```\/ _.,_ ''-._
( ' , .-` | `, ) Running in standalone mode
|`-._`-...-` __...-.``-._|'` _.-'| Port: 6392
| `-._ `._ / _.-' | PID: 6973
`-._ `-._ `-./ _.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' | http://redis.io
`-._ `-._`-.__.-'_.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' |
`-._ `-._`-.__.-'_.-' _.-'
`-._ `-.__.-' _.-'
`-._ _.-'
`-.__.-'
6973:M 21 Jun 2022 02:17:39.398 # Server initialized
6973:M 21 Jun 2022 02:17:39.399 * Ready to accept connections
6979:C 21 Jun 2022 02:17:39.400 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
6979:C 21 Jun 2022 02:17:39.400 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=6979, just started
6979:C 21 Jun 2022 02:17:39.400 # Configuration loaded
redis-server --port 6398 --requirepass password123 --slaveof 127.0.0.1 6397 --masterauth password123 &
_._
_.-``__ ''-._
_.-`` `. `_. ''-._ Redis 6.0.16 (00000000/0) 64 bit
.-`` .-```. ```\/ _.,_ ''-._
( ' , .-` | `, ) Running in standalone mode
|`-._`-...-` __...-.``-._|'` _.-'| Port: 6393
| `-._ `._ / _.-' | PID: 6979
`-._ `-._ `-./ _.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' | http://redis.io
`-._ `-._`-.__.-'_.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' |
`-._ `-._`-.__.-'_.-' _.-'
`-._ `-.__.-' _.-'
`-._ _.-'
`-.__.-'
6979:S 21 Jun 2022 02:17:39.402 # Server initialized
6979:S 21 Jun 2022 02:17:39.402 * Ready to accept connections
6979:S 21 Jun 2022 02:17:39.403 * Connecting to MASTER 127.0.0.1:6392
6979:S 21 Jun 2022 02:17:39.403 * MASTER <-> REPLICA sync started
6979:S 21 Jun 2022 02:17:39.403 * Non blocking connect for SYNC fired the event.
6979:S 21 Jun 2022 02:17:39.403 * Master replied to PING, replication can continue...
mkdir 26399 && cp test/integration/conf/sentinel-pre-second.conf 26399/sentinel.conf && redis-server 26399/sentinel.conf --sentinel --port 26399 &
6979:S 21 Jun 2022 02:17:39.404 * Partial resynchronization not possible (no cached master)
6973:M 21 Jun 2022 02:17:39.404 * Replica 127.0.0.1:6393 asks for synchronization
6973:M 21 Jun 2022 02:17:39.404 * Full resync requested by replica 127.0.0.1:6393
6973:M 21 Jun 2022 02:17:39.404 * Replication backlog created, my new replication IDs are 'edbfa233664ce85e6a187c305d312ae9290dcdd3' and '0000000000000000000000000000000000000000'
6973:M 21 Jun 2022 02:17:39.404 * Starting BGSAVE for SYNC with target: disk
6973:M 21 Jun 2022 02:17:39.405 * Background saving started by pid 7014
6979:S 21 Jun 2022 02:17:39.405 * Full resync from master: edbfa233664ce85e6a187c305d312ae9290dcdd3:0
mkdir 26400 && cp test/integration/conf/sentinel-pre-second.conf 26400/sentinel.conf && redis-server 26400/sentinel.conf --sentinel --port 26400 &
mkdir 26401 && cp test/integration/conf/sentinel-pre-second.conf 26401/sentinel.conf && redis-server 26401/sentinel.conf --sentinel --port 26401 &
7004:C 21 Jun 2022 02:17:39.411 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
7004:C 21 Jun 2022 02:17:39.411 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=7004, just started
7004:C 21 Jun 2022 02:17:39.411 # Configuration loaded
7001:X 21 Jun 2022 02:17:39.412 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
7001:X 21 Jun 2022 02:17:39.412 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=7001, just started
7001:X 21 Jun 2022 02:17:39.412 # Configuration loaded
7011:C 21 Jun 2022 02:17:39.413 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
7011:C 21 Jun 2022 02:17:39.413 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=7011, just started
7011:C 21 Jun 2022 02:17:39.413 # Configuration loaded
_._
_.-``__ ''-._
_.-`` `. `_. ''-._ Redis 6.0.16 (00000000/0) 64 bit
.-`` .-```. ```\/ _.,_ ''-._
( ' , .-` | `, ) Running in standalone mode
|`-._`-...-` __...-.``-._|'` _.-'| Port: 6397
| `-._ `._ / _.-' | PID: 7004
`-._ `-._ `-./ _.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' | http://redis.io
`-._ `-._`-.__.-'_.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' |
`-._ `-._`-.__.-'_.-' _.-'
`-._ `-.__.-' _.-'
`-._ _.-'
`-.__.-'
7004:M 21 Jun 2022 02:17:39.414 # Server initialized
_._
_.-``__ ''-._
_.-`` `. `_. ''-._ Redis 6.0.16 (00000000/0) 64 bit
.-`` .-```. ```\/ _.,_ ''-._
( ' , .-` | `, ) Running in sentinel mode
|`-._`-...-` __...-.``-._|'` _.-'| Port: 26394
| `-._ `._ / _.-' | PID: 7001
`-._ `-._ `-./ _.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' | http://redis.io
`-._ `-._`-.__.-'_.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' |
`-._ `-._`-.__.-'_.-' _.-'
`-._ `-.__.-' _.-'
`-._ _.-'
`-.__.-'
7004:M 21 Jun 2022 02:17:39.415 * Ready to accept connections
_._
_.-``__ ''-._
_.-`` `. `_. ''-._ Redis 6.0.16 (00000000/0) 64 bit
.-`` .-```. ```\/ _.,_ ''-._
( ' , .-` | `, ) Running in standalone mode
|`-._`-...-` __...-.``-._|'` _.-'| Port: 6398
| `-._ `._ / _.-' | PID: 7011
`-._ `-._ `-./ _.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' | http://redis.io
`-._ `-._`-.__.-'_.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' |
`-._ `-._`-.__.-'_.-' _.-'
`-._ `-.__.-' _.-'
`-._ _.-'
`-.__.-'
7011:S 21 Jun 2022 02:17:39.416 # Server initialized
7011:S 21 Jun 2022 02:17:39.416 * Ready to accept connections
7015:X 21 Jun 2022 02:17:39.416 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
7015:X 21 Jun 2022 02:17:39.416 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=7015, just started
7015:X 21 Jun 2022 02:17:39.416 # Configuration loaded
7011:S 21 Jun 2022 02:17:39.416 * Connecting to MASTER 127.0.0.1:6397
7011:S 21 Jun 2022 02:17:39.416 * MASTER <-> REPLICA sync started
7011:S 21 Jun 2022 02:17:39.416 * Non blocking connect for SYNC fired the event.
7011:S 21 Jun 2022 02:17:39.417 * Master replied to PING, replication can continue...
mkdir 6386 && cd 6386 && redis-server --port 6386 --cluster-enabled yes --requirepass password123 &
7011:S 21 Jun 2022 02:17:39.418 * Partial resynchronization not possible (no cached master)
7004:M 21 Jun 2022 02:17:39.418 * Replica 127.0.0.1:6398 asks for synchronization
7004:M 21 Jun 2022 02:17:39.418 * Full resync requested by replica 127.0.0.1:6398
7004:M 21 Jun 2022 02:17:39.418 * Replication backlog created, my new replication IDs are '0c79729eb426ad8087c49595e95fb76466bf7712' and '0000000000000000000000000000000000000000'
7004:M 21 Jun 2022 02:17:39.418 * Starting BGSAVE for SYNC with target: disk
_._
_.-``__ ''-._
_.-`` `. `_. ''-._ Redis 6.0.16 (00000000/0) 64 bit
.-`` .-```. ```\/ _.,_ ''-._
( ' , .-` | `, ) Running in sentinel mode
|`-._`-...-` __...-.``-._|'` _.-'| Port: 26395
| `-._ `._ / _.-' | PID: 7015
`-._ `-._ `-./ _.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' | http://redis.io
`-._ `-._`-.__.-'_.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' |
`-._ `-._`-.__.-'_.-' _.-'
`-._ `-.__.-' _.-'
`-._ _.-'
`-.__.-'
7004:M 21 Jun 2022 02:17:39.419 * Background saving started by pid 7042
7011:S 21 Jun 2022 02:17:39.419 * Full resync from master: 0c79729eb426ad8087c49595e95fb76466bf7712:0
mkdir 6387 && cd 6387 && redis-server --port 6387 --cluster-enabled yes --requirepass password123 &
7021:X 21 Jun 2022 02:17:39.422 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
7021:X 21 Jun 2022 02:17:39.422 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=7021, just started
7021:X 21 Jun 2022 02:17:39.422 # Configuration loaded
mkdir 6388 && cd 6388 && redis-server --port 6388 --cluster-enabled yes --requirepass password123 &
_._
_.-``__ ''-._
_.-`` `. `_. ''-._ Redis 6.0.16 (00000000/0) 64 bit
.-`` .-```. ```\/ _.,_ ''-._
( ' , .-` | `, ) Running in sentinel mode
|`-._`-...-` __...-.``-._|'` _.-'| Port: 26396
| `-._ `._ / _.-' | PID: 7021
`-._ `-._ `-./ _.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' | http://redis.io
`-._ `-._`-.__.-'_.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' |
`-._ `-._`-.__.-'_.-' _.-'
`-._ `-.__.-' _.-'
`-._ _.-'
`-.__.-'
mkdir 6389 && cd 6389 && redis-server --port 6389 --cluster-enabled yes --requirepass password123 &
mkdir 6390 && cd 6390 && redis-server --port 6390 --cluster-enabled yes --requirepass password123 &
7047:X 21 Jun 2022 02:17:39.431 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
7047:X 21 Jun 2022 02:17:39.431 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=7047, just started
7047:X 21 Jun 2022 02:17:39.431 # Configuration loaded
_._
_.-``__ ''-._
_.-`` `. `_. ''-._ Redis 6.0.16 (00000000/0) 64 bit
.-`` .-```. ```\/ _.,_ ''-._
( ' , .-` | `, ) Running in sentinel mode
|`-._`-...-` __...-.``-._|'` _.-'| Port: 26399
| `-._ `._ / _.-' | PID: 7047
`-._ `-._ `-./ _.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' | http://redis.io
`-._ `-._`-.__.-'_.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' |
`-._ `-._`-.__.-'_.-' _.-'
`-._ `-.__.-' _.-'
`-._ _.-'
`-.__.-'
mkdir 6391 && cd 6391 && redis-server --port 6391 --cluster-enabled yes --requirepass password123 &
7050:X 21 Jun 2022 02:17:39.434 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
7050:X 21 Jun 2022 02:17:39.434 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=7050, just started
7050:X 21 Jun 2022 02:17:39.434 # Configuration loaded
7053:C 21 Jun 2022 02:17:39.437 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
sleep 2
7053:C 21 Jun 2022 02:17:39.437 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=7053, just started
7053:C 21 Jun 2022 02:17:39.437 # Configuration loaded
_._
_.-``__ ''-._
_.-`` `. `_. ''-._ Redis 6.0.16 (00000000/0) 64 bit
.-`` .-```. ```\/ _.,_ ''-._
( ' , .-` | `, ) Running in sentinel mode
|`-._`-...-` __...-.``-._|'` _.-'| Port: 26401
| `-._ `._ / _.-' | PID: 7050
`-._ `-._ `-./ _.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' | http://redis.io
`-._ `-._`-.__.-'_.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' |
`-._ `-._`-.__.-'_.-' _.-'
`-._ `-.__.-' _.-'
`-._ _.-'
`-.__.-'
7060:X 21 Jun 2022 02:17:39.440 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
7060:X 21 Jun 2022 02:17:39.440 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=7060, just started
7060:X 21 Jun 2022 02:17:39.440 # Configuration loaded
7059:C 21 Jun 2022 02:17:39.440 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
7059:C 21 Jun 2022 02:17:39.440 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=7059, just started
7059:C 21 Jun 2022 02:17:39.440 # Configuration loaded
7053:M 21 Jun 2022 02:17:39.441 * No cluster configuration found, I'm 6885a10725d55686fd561f7ebd24e74585aa53ff
_._
_.-``__ ''-._
_.-`` `. `_. ''-._ Redis 6.0.16 (00000000/0) 64 bit
.-`` .-```. ```\/ _.,_ ''-._
( ' , .-` | `, ) Running in sentinel mode
|`-._`-...-` __...-.``-._|'` _.-'| Port: 26400
| `-._ `._ / _.-' | PID: 7060
`-._ `-._ `-./ _.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' | http://redis.io
`-._ `-._`-.__.-'_.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' |
`-._ `-._`-.__.-'_.-' _.-'
`-._ `-.__.-' _.-'
`-._ _.-'
`-.__.-'
7059:M 21 Jun 2022 02:17:39.443 * No cluster configuration found, I'm 716d7e2774d78f5c0a4be0fc81e1c3c07ff34776
7081:C 21 Jun 2022 02:17:39.449 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
7081:C 21 Jun 2022 02:17:39.449 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=7081, just started
7081:C 21 Jun 2022 02:17:39.449 # Configuration loaded
7081:M 21 Jun 2022 02:17:39.450 * No cluster configuration found, I'm 9702f727458439f67814d40ec0ff67c91e69920b
7074:C 21 Jun 2022 02:17:39.451 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
7074:C 21 Jun 2022 02:17:39.451 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=7074, just started
7074:C 21 Jun 2022 02:17:39.451 # Configuration loaded
7084:C 21 Jun 2022 02:17:39.451 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
7084:C 21 Jun 2022 02:17:39.451 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=7084, just started
7084:C 21 Jun 2022 02:17:39.451 # Configuration loaded
7083:C 21 Jun 2022 02:17:39.451 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
7083:C 21 Jun 2022 02:17:39.451 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=7083, just started
7083:C 21 Jun 2022 02:17:39.451 # Configuration loaded
7084:M 21 Jun 2022 02:17:39.453 * No cluster configuration found, I'm 5b14756df11dc0fabf6217deafe5c7aba6bdf0f4
7074:M 21 Jun 2022 02:17:39.453 * No cluster configuration found, I'm dd2bd909a02802b97d1cac3f1c80d42343cbe8fa
7083:M 21 Jun 2022 02:17:39.453 * No cluster configuration found, I'm 3ec07bfed0db3c506366032b2d6b3206567a3992
7014:C 21 Jun 2022 02:17:39.567 * DB saved on disk
7014:C 21 Jun 2022 02:17:39.568 * RDB: 0 MB of memory used by copy-on-write
7042:C 21 Jun 2022 02:17:39.569 * DB saved on disk
_._
_.-``__ ''-._
_.-`` `. `_. ''-._ Redis 6.0.16 (00000000/0) 64 bit
.-`` .-```. ```\/ _.,_ ''-._
( ' , .-` | `, ) Running in cluster mode
|`-._`-...-` __...-.``-._|'` _.-'| Port: 6387
| `-._ `._ / _.-' | PID: 7059
`-._ `-._ `-./ _.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' | http://redis.io
`-._ `-._`-.__.-'_.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' |
`-._ `-._`-.__.-'_.-' _.-'
`-._ `-.__.-' _.-'
`-._ _.-'
`-.__.-'
_._
_.-``__ ''-._
_.-`` `. `_. ''-._ Redis 6.0.16 (00000000/0) 64 bit
.-`` .-```. ```\/ _.,_ ''-._
( ' , .-` | `, ) Running in cluster mode
|`-._`-...-` __...-.``-._|'` _.-'| Port: 6391
| `-._ `._ / _.-' | PID: 7083
`-._ `-._ `-./ _.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' | http://redis.io
`-._ `-._`-.__.-'_.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' |
`-._ `-._`-.__.-'_.-' _.-'
`-._ `-.__.-' _.-'
`-._ _.-'
`-.__.-'
7059:M 21 Jun 2022 02:17:39.570 # Server initialized
7083:M 21 Jun 2022 02:17:39.570 # Server initialized
_._
_.-``__ ''-._
_.-`` `. `_. ''-._ Redis 6.0.16 (00000000/0) 64 bit
.-`` .-```. ```\/ _.,_ ''-._
( ' , .-` | `, ) Running in cluster mode
|`-._`-...-` __...-.``-._|'` _.-'| Port: 6386
| `-._ `._ / _.-' | PID: 7053
`-._ `-._ `-./ _.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' | http://redis.io
`-._ `-._`-.__.-'_.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' |
`-._ `-._`-.__.-'_.-' _.-'
`-._ `-.__.-' _.-'
`-._ _.-'
`-.__.-'
7053:M 21 Jun 2022 02:17:39.571 # Server initialized
_._
_.-``__ ''-._
_.-`` `. `_. ''-._ Redis 6.0.16 (00000000/0) 64 bit
.-`` .-```. ```\/ _.,_ ''-._
( ' , .-` | `, ) Running in cluster mode
|`-._`-...-` __...-.``-._|'` _.-'| Port: 6390
| `-._ `._ / _.-' | PID: 7084
`-._ `-._ `-./ _.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' | http://redis.io
`-._ `-._`-.__.-'_.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' |
`-._ `-._`-.__.-'_.-' _.-'
`-._ `-.__.-' _.-'
`-._ _.-'
`-.__.-'
7084:M 21 Jun 2022 02:17:39.572 # Server initialized
7083:M 21 Jun 2022 02:17:39.571 * Ready to accept connections
7042:C 21 Jun 2022 02:17:39.571 * RDB: 0 MB of memory used by copy-on-write
7059:M 21 Jun 2022 02:17:39.571 * Ready to accept connections
7047:X 21 Jun 2022 02:17:39.572 # Sentinel ID is 40c0a9025aa3e6c578f3b2b865e68573682f0a84
7047:X 21 Jun 2022 02:17:39.573 # +monitor master mymaster 127.0.0.1 6397 quorum 2
7084:M 21 Jun 2022 02:17:39.573 * Ready to accept connections
7021:X 21 Jun 2022 02:17:39.573 # Sentinel ID is a1287ead9dd80e1695bc38f557301fb2974983ee
7021:X 21 Jun 2022 02:17:39.573 # +monitor master mymaster 127.0.0.1 6392 quorum 2
7047:X 21 Jun 2022 02:17:39.574 * +slave slave 127.0.0.1:6398 127.0.0.1 6398 @ mymaster 127.0.0.1 6397
_._
_.-``__ ''-._
_.-`` `. `_. ''-._ Redis 6.0.16 (00000000/0) 64 bit
.-`` .-```. ```\/ _.,_ ''-._
( ' , .-` | `, ) Running in cluster mode
|`-._`-...-` __...-.``-._|'` _.-'| Port: 6389
| `-._ `._ / _.-' | PID: 7074
`-._ `-._ `-./ _.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' | http://redis.io
`-._ `-._`-.__.-'_.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' |
`-._ `-._`-.__.-'_.-' _.-'
`-._ `-.__.-' _.-'
`-._ _.-'
`-.__.-'
7074:M 21 Jun 2022 02:17:39.574 # Server initialized
_._
_.-``__ ''-._
_.-`` `. `_. ''-._ Redis 6.0.16 (00000000/0) 64 bit
.-`` .-```. ```\/ _.,_ ''-._
( ' , .-` | `, ) Running in cluster mode
|`-._`-...-` __...-.``-._|'` _.-'| Port: 6388
| `-._ `._ / _.-' | PID: 7081
`-._ `-._ `-./ _.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' | http://redis.io
`-._ `-._`-.__.-'_.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' |
`-._ `-._`-.__.-'_.-' _.-'
`-._ `-.__.-' _.-'
`-._ _.-'
`-.__.-'
7081:M 21 Jun 2022 02:17:39.574 # Server initialized
7081:M 21 Jun 2022 02:17:39.575 * Ready to accept connections
7053:M 21 Jun 2022 02:17:39.575 * Ready to accept connections
7021:X 21 Jun 2022 02:17:39.575 * +slave slave 127.0.0.1:6393 127.0.0.1 6393 @ mymaster 127.0.0.1 6392
7060:X 21 Jun 2022 02:17:39.576 # Sentinel ID is e237683d828cd60cd65f8d7da19a75712150684b
7060:X 21 Jun 2022 02:17:39.576 # +monitor master mymaster 127.0.0.1 6397 quorum 2
7050:X 21 Jun 2022 02:17:39.576 # Sentinel ID is 7322c6f0fe46963c13b0fb7015214a953bc130dd
7050:X 21 Jun 2022 02:17:39.576 # +monitor master mymaster 127.0.0.1 6397 quorum 2
7074:M 21 Jun 2022 02:17:39.576 * Ready to accept connections
7001:X 21 Jun 2022 02:17:39.576 # Sentinel ID is 475c06f6fa96ec72b95ee9e3d890cd744e14d091
7001:X 21 Jun 2022 02:17:39.576 # +monitor master mymaster 127.0.0.1 6392 quorum 2
7015:X 21 Jun 2022 02:17:39.577 # Sentinel ID is c16483dab180cc26a7d275ba35bf5704085c9b2c
7015:X 21 Jun 2022 02:17:39.577 # +monitor master mymaster 127.0.0.1 6392 quorum 2
7060:X 21 Jun 2022 02:17:39.578 * +slave slave 127.0.0.1:6398 127.0.0.1 6398 @ mymaster 127.0.0.1 6397
7050:X 21 Jun 2022 02:17:39.578 * +slave slave 127.0.0.1:6398 127.0.0.1 6398 @ mymaster 127.0.0.1 6397
7001:X 21 Jun 2022 02:17:39.579 * +slave slave 127.0.0.1:6393 127.0.0.1 6393 @ mymaster 127.0.0.1 6392
7015:X 21 Jun 2022 02:17:39.580 * +slave slave 127.0.0.1:6393 127.0.0.1 6393 @ mymaster 127.0.0.1 6392
6973:M 21 Jun 2022 02:17:39.601 * Background saving terminated with success
6973:M 21 Jun 2022 02:17:39.601 * Synchronization with replica 127.0.0.1:6393 succeeded
6979:S 21 Jun 2022 02:17:39.601 * MASTER <-> REPLICA sync: receiving 176 bytes from master to disk
6979:S 21 Jun 2022 02:17:39.601 * MASTER <-> REPLICA sync: Flushing old data
6979:S 21 Jun 2022 02:17:39.601 * MASTER <-> REPLICA sync: Loading DB in memory
6979:S 21 Jun 2022 02:17:39.604 * Loading RDB produced by version 6.0.16
6979:S 21 Jun 2022 02:17:39.604 * RDB age 0 seconds
6979:S 21 Jun 2022 02:17:39.604 * RDB memory usage when created 1.83 Mb
6979:S 21 Jun 2022 02:17:39.604 * MASTER <-> REPLICA sync: Finished with success
7004:M 21 Jun 2022 02:17:39.616 * Background saving terminated with success
7011:S 21 Jun 2022 02:17:39.616 * MASTER <-> REPLICA sync: receiving 176 bytes from master to disk
7004:M 21 Jun 2022 02:17:39.616 * Synchronization with replica 127.0.0.1:6398 succeeded
7011:S 21 Jun 2022 02:17:39.617 * MASTER <-> REPLICA sync: Flushing old data
7011:S 21 Jun 2022 02:17:39.617 * MASTER <-> REPLICA sync: Loading DB in memory
7011:S 21 Jun 2022 02:17:39.619 * Loading RDB produced by version 6.0.16
7011:S 21 Jun 2022 02:17:39.619 * RDB age 0 seconds
7011:S 21 Jun 2022 02:17:39.619 * RDB memory usage when created 1.83 Mb
7011:S 21 Jun 2022 02:17:39.619 * MASTER <-> REPLICA sync: Finished with success
echo "yes" | redis-cli --cluster create -a password123 127.0.0.1:6386 127.0.0.1:6387 127.0.0.1:6388 --cluster-replicas 0
Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe.
7001:X 21 Jun 2022 02:17:41.436 * +sentinel sentinel a1287ead9dd80e1695bc38f557301fb2974983ee 127.0.0.1 26396 @ mymaster 127.0.0.1 6392
7015:X 21 Jun 2022 02:17:41.436 * +sentinel sentinel a1287ead9dd80e1695bc38f557301fb2974983ee 127.0.0.1 26396 @ mymaster 127.0.0.1 6392
>>> Performing hash slots allocation on 3 nodes...
Master[0] -> Slots 0 - 5460
Master[1] -> Slots 5461 - 10922
Master[2] -> Slots 10923 - 16383
M: 6885a10725d55686fd561f7ebd24e74585aa53ff 127.0.0.1:6386
slots:[0-5460] (5461 slots) master
M: 716d7e2774d78f5c0a4be0fc81e1c3c07ff34776 127.0.0.1:6387
slots:[5461-10922] (5462 slots) master
M: 9702f727458439f67814d40ec0ff67c91e69920b 127.0.0.1:6388
slots:[10923-16383] (5461 slots) master
Can I set the above configuration? (type 'yes' to accept): >>> Nodes configuration updated
>>> Assign a different config epoch to each node
7053:M 21 Jun 2022 02:17:41.455 # configEpoch set to 1 via CLUSTER SET-CONFIG-EPOCH
7059:M 21 Jun 2022 02:17:41.455 # configEpoch set to 2 via CLUSTER SET-CONFIG-EPOCH
7081:M 21 Jun 2022 02:17:41.456 # configEpoch set to 3 via CLUSTER SET-CONFIG-EPOCH
>>> Sending CLUSTER MEET messages to join the cluster
7021:X 21 Jun 2022 02:17:41.473 * +sentinel sentinel c16483dab180cc26a7d275ba35bf5704085c9b2c 127.0.0.1 26395 @ mymaster 127.0.0.1 6392
7001:X 21 Jun 2022 02:17:41.474 * +sentinel sentinel c16483dab180cc26a7d275ba35bf5704085c9b2c 127.0.0.1 26395 @ mymaster 127.0.0.1 6392
7015:X 21 Jun 2022 02:17:41.482 * +sentinel sentinel 475c06f6fa96ec72b95ee9e3d890cd744e14d091 127.0.0.1 26394 @ mymaster 127.0.0.1 6392
7021:X 21 Jun 2022 02:17:41.482 * +sentinel sentinel 475c06f6fa96ec72b95ee9e3d890cd744e14d091 127.0.0.1 26394 @ mymaster 127.0.0.1 6392
7053:M 21 Jun 2022 02:17:41.487 # IP address for this node updated to 127.0.0.1
7050:X 21 Jun 2022 02:17:41.511 * +sentinel sentinel e237683d828cd60cd65f8d7da19a75712150684b 127.0.0.1 26400 @ mymaster 127.0.0.1 6397
7047:X 21 Jun 2022 02:17:41.511 * +sentinel sentinel e237683d828cd60cd65f8d7da19a75712150684b 127.0.0.1 26400 @ mymaster 127.0.0.1 6397
7050:X 21 Jun 2022 02:17:41.515 * +sentinel sentinel 40c0a9025aa3e6c578f3b2b865e68573682f0a84 127.0.0.1 26399 @ mymaster 127.0.0.1 6397
7060:X 21 Jun 2022 02:17:41.515 * +sentinel sentinel 40c0a9025aa3e6c578f3b2b865e68573682f0a84 127.0.0.1 26399 @ mymaster 127.0.0.1 6397
7047:X 21 Jun 2022 02:17:41.530 * +sentinel sentinel 7322c6f0fe46963c13b0fb7015214a953bc130dd 127.0.0.1 26401 @ mymaster 127.0.0.1 6397
7060:X 21 Jun 2022 02:17:41.530 * +sentinel sentinel 7322c6f0fe46963c13b0fb7015214a953bc130dd 127.0.0.1 26401 @ mymaster 127.0.0.1 6397
7081:M 21 Jun 2022 02:17:41.587 # IP address for this node updated to 127.0.0.1
7059:M 21 Jun 2022 02:17:41.587 # IP address for this node updated to 127.0.0.1
Waiting for the cluster to join
.7053:M 21 Jun 2022 02:17:42.494 # Cluster state changed: ok
7081:M 21 Jun 2022 02:17:42.594 # Cluster state changed: ok
7059:M 21 Jun 2022 02:17:42.594 # Cluster state changed: ok
>>> Performing Cluster Check (using node 127.0.0.1:6386)
M: 6885a10725d55686fd561f7ebd24e74585aa53ff 127.0.0.1:6386
slots:[0-5460] (5461 slots) master
M: 716d7e2774d78f5c0a4be0fc81e1c3c07ff34776 127.0.0.1:6387
slots:[5461-10922] (5462 slots) master
M: 9702f727458439f67814d40ec0ff67c91e69920b 127.0.0.1:6388
slots:[10923-16383] (5461 slots) master
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
echo "yes" | redis-cli --cluster create -a password123 127.0.0.1:6389 127.0.0.1:6390 127.0.0.1:6391 --cluster-replicas 0
Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe.
>>> Performing hash slots allocation on 3 nodes...
Master[0] -> Slots 0 - 5460
Master[1] -> Slots 5461 - 10922
Master[2] -> Slots 10923 - 16383
M: dd2bd909a02802b97d1cac3f1c80d42343cbe8fa 127.0.0.1:6389
slots:[0-5460] (5461 slots) master
M: 5b14756df11dc0fabf6217deafe5c7aba6bdf0f4 127.0.0.1:6390
slots:[5461-10922] (5462 slots) master
M: 3ec07bfed0db3c506366032b2d6b3206567a3992 127.0.0.1:6391
slots:[10923-16383] (5461 slots) master
Can I set the above configuration? (type 'yes' to accept): >>> Nodes configuration updated
>>> Assign a different config epoch to each node
7074:M 21 Jun 2022 02:17:43.484 # configEpoch set to 1 via CLUSTER SET-CONFIG-EPOCH
7084:M 21 Jun 2022 02:17:43.485 # configEpoch set to 2 via CLUSTER SET-CONFIG-EPOCH
7083:M 21 Jun 2022 02:17:43.485 # configEpoch set to 3 via CLUSTER SET-CONFIG-EPOCH
>>> Sending CLUSTER MEET messages to join the cluster
7074:M 21 Jun 2022 02:17:43.498 # IP address for this node updated to 127.0.0.1
7083:M 21 Jun 2022 02:17:43.599 # IP address for this node updated to 127.0.0.1
7084:M 21 Jun 2022 02:17:43.599 # IP address for this node updated to 127.0.0.1
Waiting for the cluster to join
.
>>> Performing Cluster Check (using node 127.0.0.1:6389)
M: dd2bd909a02802b97d1cac3f1c80d42343cbe8fa 127.0.0.1:6389
slots:[0-5460] (5461 slots) master
M: 3ec07bfed0db3c506366032b2d6b3206567a3992 127.0.0.1:6391
slots:[10923-16383] (5461 slots) master
M: 5b14756df11dc0fabf6217deafe5c7aba6bdf0f4 127.0.0.1:6390
slots:[5461-10922] (5462 slots) master
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
redis-cli --cluster check -a password123 127.0.0.1:6386
Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe.
127.0.0.1:6386 (6885a107...) -> 0 keys | 5461 slots | 0 slaves.
127.0.0.1:6387 (716d7e27...) -> 0 keys | 5462 slots | 0 slaves.
127.0.0.1:6388 (9702f727...) -> 0 keys | 5461 slots | 0 slaves.
[OK] 0 keys in 3 masters.
0.00 keys per slot on average.
>>> Performing Cluster Check (using node 127.0.0.1:6386)
M: 6885a10725d55686fd561f7ebd24e74585aa53ff 127.0.0.1:6386
slots:[0-5460] (5461 slots) master
M: 716d7e2774d78f5c0a4be0fc81e1c3c07ff34776 127.0.0.1:6387
slots:[5461-10922] (5462 slots) master
M: 9702f727458439f67814d40ec0ff67c91e69920b 127.0.0.1:6388
slots:[10923-16383] (5461 slots) master
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
redis-cli --cluster check -a password123 127.0.0.1:6389
Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe.
127.0.0.1:6389 (dd2bd909...) -> 0 keys | 5461 slots | 0 slaves.
127.0.0.1:6391 (3ec07bfe...) -> 0 keys | 5461 slots | 0 slaves.
127.0.0.1:6390 (5b14756d...) -> 0 keys | 5462 slots | 0 slaves.
[OK] 0 keys in 3 masters.
0.00 keys per slot on average.
>>> Performing Cluster Check (using node 127.0.0.1:6389)
M: dd2bd909a02802b97d1cac3f1c80d42343cbe8fa 127.0.0.1:6389
slots:[0-5460] (5461 slots) master
M: 3ec07bfed0db3c506366032b2d6b3206567a3992 127.0.0.1:6391
slots:[10923-16383] (5461 slots) master
M: 5b14756df11dc0fabf6217deafe5c7aba6bdf0f4 127.0.0.1:6390
slots:[5461-10922] (5462 slots) master
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
go test -race -tags=integration github.com/envoyproxy/ratelimit/...
? github.com/envoyproxy/ratelimit/src/assert [no test files]
? github.com/envoyproxy/ratelimit/src/client_cmd [no test files]
? github.com/envoyproxy/ratelimit/src/config [no test files]
? github.com/envoyproxy/ratelimit/src/config_check_cmd [no test files]
? github.com/envoyproxy/ratelimit/src/limiter [no test files]
ok github.com/envoyproxy/ratelimit/src/memcached (cached)
? github.com/envoyproxy/ratelimit/src/metrics [no test files]
? github.com/envoyproxy/ratelimit/src/redis [no test files]
? github.com/envoyproxy/ratelimit/src/server [no test files]
? github.com/envoyproxy/ratelimit/src/service [no test files]
? github.com/envoyproxy/ratelimit/src/service_cmd [no test files]
? github.com/envoyproxy/ratelimit/src/service_cmd/runner [no test files]
ok github.com/envoyproxy/ratelimit/src/settings (cached)
ok github.com/envoyproxy/ratelimit/src/srv (cached)
? github.com/envoyproxy/ratelimit/src/stats [no test files]
? github.com/envoyproxy/ratelimit/src/trace [no test files]
? github.com/envoyproxy/ratelimit/src/utils [no test files]
? github.com/envoyproxy/ratelimit/test/common [no test files]
ok github.com/envoyproxy/ratelimit/test/config (cached)
7084:M 21 Jun 2022 02:17:48.427 # Cluster state changed: ok
7083:M 21 Jun 2022 02:17:48.427 # Cluster state changed: ok
7074:M 21 Jun 2022 02:17:48.427 # Cluster state changed: ok
stunnel: LOG5[0]: Service [redis] accepted connection from 127.0.0.1:37456
stunnel: LOG5[0]: s_connect: connected 127.0.0.1:6381
stunnel: LOG5[0]: Service [redis] connected remote server from 127.0.0.1:56620
stunnel: LOG5[1]: Service [redis] accepted connection from 127.0.0.1:37462
stunnel: LOG5[1]: s_connect: connected 127.0.0.1:6381
stunnel: LOG5[1]: Service [redis] connected remote server from 127.0.0.1:56624
stunnel: LOG5[2]: Service [redis] accepted connection from 127.0.0.1:37466
stunnel: LOG5[2]: s_connect: connected 127.0.0.1:6381
stunnel: LOG5[2]: Service [redis] connected remote server from 127.0.0.1:56628
stunnel: LOG5[3]: Service [redis] accepted connection from 127.0.0.1:37472
stunnel: LOG5[3]: s_connect: connected 127.0.0.1:6381
stunnel: LOG5[3]: Service [redis] connected remote server from 127.0.0.1:56634
stunnel: LOG5[4]: Service [redis] accepted connection from 127.0.0.1:37476
stunnel: LOG5[4]: s_connect: connected 127.0.0.1:6381
stunnel: LOG5[4]: Service [redis] connected remote server from 127.0.0.1:56642
stunnel: LOG5[5]: Service [redis] accepted connection from 127.0.0.1:37484
stunnel: LOG5[5]: s_connect: connected 127.0.0.1:6381
stunnel: LOG5[5]: Service [redis] connected remote server from 127.0.0.1:56646
stunnel: LOG5[6]: Service [redis] accepted connection from 127.0.0.1:37488
stunnel: LOG5[6]: s_connect: connected 127.0.0.1:6381
stunnel: LOG5[6]: Service [redis] connected remote server from 127.0.0.1:56650
stunnel: LOG5[7]: Service [redis] accepted connection from 127.0.0.1:37492
stunnel: LOG5[7]: s_connect: connected 127.0.0.1:6381
stunnel: LOG5[7]: Service [redis] connected remote server from 127.0.0.1:56654
stunnel: LOG5[8]: Service [redis] accepted connection from 127.0.0.1:37496
stunnel: LOG5[8]: s_connect: connected 127.0.0.1:6381
stunnel: LOG5[8]: Service [redis] connected remote server from 127.0.0.1:56658
stunnel: LOG5[9]: Service [redis] accepted connection from 127.0.0.1:37500
stunnel: LOG5[9]: s_connect: connected 127.0.0.1:6381
stunnel: LOG5[9]: Service [redis] connected remote server from 127.0.0.1:56662
stunnel: LOG5[0]: Service [redis] accepted connection from 127.0.0.1:51972
stunnel: LOG5[0]: s_connect: connected 127.0.0.1:6382
stunnel: LOG5[0]: Service [redis] connected remote server from 127.0.0.1:47962
stunnel: LOG5[1]: Service [redis] accepted connection from 127.0.0.1:51976
stunnel: LOG5[10]: Service [redis] accepted connection from 127.0.0.1:37544
stunnel: LOG5[10]: s_connect: connected 127.0.0.1:6381
stunnel: LOG5[10]: Service [redis] connected remote server from 127.0.0.1:56706
stunnel: LOG5[11]: Service [redis] accepted connection from 127.0.0.1:37548
stunnel: LOG5[1]: s_connect: connected 127.0.0.1:6382
stunnel: LOG5[1]: Service [redis] connected remote server from 127.0.0.1:47972
stunnel: LOG5[2]: Service [redis] accepted connection from 127.0.0.1:51988
stunnel: LOG5[11]: s_connect: connected 127.0.0.1:6381
stunnel: LOG5[11]: Service [redis] connected remote server from 127.0.0.1:56718
stunnel: LOG5[12]: Service [redis] accepted connection from 127.0.0.1:37560
stunnel: LOG5[2]: s_connect: connected 127.0.0.1:6382
stunnel: LOG5[2]: Service [redis] connected remote server from 127.0.0.1:47984
stunnel: LOG5[3]: Service [redis] accepted connection from 127.0.0.1:51998
stunnel: LOG5[12]: s_connect: connected 127.0.0.1:6381
stunnel: LOG5[12]: Service [redis] connected remote server from 127.0.0.1:56726
stunnel: LOG5[13]: Service [redis] accepted connection from 127.0.0.1:37568
stunnel: LOG5[3]: s_connect: connected 127.0.0.1:6382
stunnel: LOG5[3]: Service [redis] connected remote server from 127.0.0.1:47992
stunnel: LOG5[4]: Service [redis] accepted connection from 127.0.0.1:52006
stunnel: LOG5[13]: s_connect: connected 127.0.0.1:6381
stunnel: LOG5[13]: Service [redis] connected remote server from 127.0.0.1:56734
stunnel: LOG5[14]: Service [redis] accepted connection from 127.0.0.1:37576
stunnel: LOG5[4]: s_connect: connected 127.0.0.1:6382
stunnel: LOG5[4]: Service [redis] connected remote server from 127.0.0.1:48000
stunnel: LOG5[5]: Service [redis] accepted connection from 127.0.0.1:52014
stunnel: LOG5[14]: s_connect: connected 127.0.0.1:6381
stunnel: LOG5[14]: Service [redis] connected remote server from 127.0.0.1:56742
stunnel: LOG5[15]: Service [redis] accepted connection from 127.0.0.1:37584
stunnel: LOG5[5]: s_connect: connected 127.0.0.1:6382
stunnel: LOG5[5]: Service [redis] connected remote server from 127.0.0.1:48008
stunnel: LOG5[6]: Service [redis] accepted connection from 127.0.0.1:52024
stunnel: LOG5[15]: s_connect: connected 127.0.0.1:6381
stunnel: LOG5[15]: Service [redis] connected remote server from 127.0.0.1:56754
stunnel: LOG5[16]: Service [redis] accepted connection from 127.0.0.1:37596
stunnel: LOG5[6]: s_connect: connected 127.0.0.1:6382
stunnel: LOG5[6]: Service [redis] connected remote server from 127.0.0.1:48020
stunnel: LOG5[7]: Service [redis] accepted connection from 127.0.0.1:52034
stunnel: LOG5[16]: s_connect: connected 127.0.0.1:6381
stunnel: LOG5[16]: Service [redis] connected remote server from 127.0.0.1:56762
stunnel: LOG5[17]: Service [redis] accepted connection from 127.0.0.1:37604
stunnel: LOG5[7]: s_connect: connected 127.0.0.1:6382
stunnel: LOG5[7]: Service [redis] connected remote server from 127.0.0.1:48028
stunnel: LOG5[8]: Service [redis] accepted connection from 127.0.0.1:52042
stunnel: LOG5[8]: s_connect: connected 127.0.0.1:6382
stunnel: LOG5[8]: Service [redis] connected remote server from 127.0.0.1:48032
stunnel: LOG5[17]: s_connect: connected 127.0.0.1:6381
stunnel: LOG5[17]: Service [redis] connected remote server from 127.0.0.1:56772
stunnel: LOG5[9]: Service [redis] accepted connection from 127.0.0.1:52048
stunnel: LOG5[18]: Service [redis] accepted connection from 127.0.0.1:37616
stunnel: LOG5[9]: s_connect: connected 127.0.0.1:6382
stunnel: LOG5[9]: Service [redis] connected remote server from 127.0.0.1:48040
stunnel: LOG5[18]: s_connect: connected 127.0.0.1:6381
stunnel: LOG5[18]: Service [redis] connected remote server from 127.0.0.1:56780
stunnel: LOG5[19]: Service [redis] accepted connection from 127.0.0.1:37622
stunnel: LOG5[19]: s_connect: connected 127.0.0.1:6381
stunnel: LOG5[19]: Service [redis] connected remote server from 127.0.0.1:56784
stunnel: LOG5[20]: Service [redis] accepted connection from 127.0.0.1:37660
stunnel: LOG5[20]: s_connect: connected 127.0.0.1:6381
stunnel: LOG5[20]: Service [redis] connected remote server from 127.0.0.1:56822
stunnel: LOG5[21]: Service [redis] accepted connection from 127.0.0.1:37664
stunnel: LOG5[21]: s_connect: connected 127.0.0.1:6381
stunnel: LOG5[21]: Service [redis] connected remote server from 127.0.0.1:56828
stunnel: LOG5[22]: Service [redis] accepted connection from 127.0.0.1:37670
stunnel: LOG5[22]: s_connect: connected 127.0.0.1:6381
stunnel: LOG5[22]: Service [redis] connected remote server from 127.0.0.1:56832
stunnel: LOG5[23]: Service [redis] accepted connection from 127.0.0.1:37674
stunnel: LOG5[23]: s_connect: connected 127.0.0.1:6381
stunnel: LOG5[23]: Service [redis] connected remote server from 127.0.0.1:56836
stunnel: LOG5[24]: Service [redis] accepted connection from 127.0.0.1:37678
stunnel: LOG5[24]: s_connect: connected 127.0.0.1:6381
stunnel: LOG5[24]: Service [redis] connected remote server from 127.0.0.1:56840
stunnel: LOG5[25]: Service [redis] accepted connection from 127.0.0.1:37682
stunnel: LOG5[25]: s_connect: connected 127.0.0.1:6381
stunnel: LOG5[25]: Service [redis] connected remote server from 127.0.0.1:56844
stunnel: LOG5[26]: Service [redis] accepted connection from 127.0.0.1:37686
stunnel: LOG5[26]: s_connect: connected 127.0.0.1:6381
stunnel: LOG5[26]: Service [redis] connected remote server from 127.0.0.1:56852
stunnel: LOG5[27]: Service [redis] accepted connection from 127.0.0.1:37694
stunnel: LOG5[27]: s_connect: connected 127.0.0.1:6381
stunnel: LOG5[27]: Service [redis] connected remote server from 127.0.0.1:56856
stunnel: LOG5[28]: Service [redis] accepted connection from 127.0.0.1:37698
stunnel: LOG5[28]: s_connect: connected 127.0.0.1:6381
stunnel: LOG5[28]: Service [redis] connected remote server from 127.0.0.1:56860
stunnel: LOG5[29]: Service [redis] accepted connection from 127.0.0.1:37702
stunnel: LOG5[29]: s_connect: connected 127.0.0.1:6381
stunnel: LOG5[29]: Service [redis] connected remote server from 127.0.0.1:56864
stunnel: LOG5[10]: Service [redis] accepted connection from 127.0.0.1:52204
stunnel: LOG5[10]: s_connect: connected 127.0.0.1:6382
stunnel: LOG5[10]: Service [redis] connected remote server from 127.0.0.1:48194
stunnel: LOG5[11]: Service [redis] accepted connection from 127.0.0.1:52210
stunnel: LOG5[30]: Service [redis] accepted connection from 127.0.0.1:37778
stunnel: LOG5[11]: s_connect: connected 127.0.0.1:6382
stunnel: LOG5[11]: Service [redis] connected remote server from 127.0.0.1:48202
stunnel: LOG5[12]: Service [redis] accepted connection from 127.0.0.1:52216
stunnel: LOG5[30]: s_connect: connected 127.0.0.1:6381
stunnel: LOG5[30]: Service [redis] connected remote server from 127.0.0.1:56944
stunnel: LOG5[31]: Service [redis] accepted connection from 127.0.0.1:37786
stunnel: LOG5[12]: s_connect: connected 127.0.0.1:6382
stunnel: LOG5[12]: Service [redis] connected remote server from 127.0.0.1:48210
stunnel: LOG5[13]: Service [redis] accepted connection from 127.0.0.1:52224
stunnel: LOG5[31]: s_connect: connected 127.0.0.1:6381
stunnel: LOG5[31]: Service [redis] connected remote server from 127.0.0.1:56952
stunnel: LOG5[32]: Service [redis] accepted connection from 127.0.0.1:37794
stunnel: LOG5[13]: s_connect: connected 127.0.0.1:6382
stunnel: LOG5[13]: Service [redis] connected remote server from 127.0.0.1:48218
stunnel: LOG5[14]: Service [redis] accepted connection from 127.0.0.1:52232
stunnel: LOG5[32]: s_connect: connected 127.0.0.1:6381
stunnel: LOG5[32]: Service [redis] connected remote server from 127.0.0.1:56960
stunnel: LOG5[33]: Service [redis] accepted connection from 127.0.0.1:37802
stunnel: LOG5[14]: s_connect: connected 127.0.0.1:6382
stunnel: LOG5[14]: Service [redis] connected remote server from 127.0.0.1:48226
stunnel: LOG5[15]: Service [redis] accepted connection from 127.0.0.1:52240
stunnel: LOG5[33]: s_connect: connected 127.0.0.1:6381
stunnel: LOG5[33]: Service [redis] connected remote server from 127.0.0.1:56968
stunnel: LOG5[34]: Service [redis] accepted connection from 127.0.0.1:37810
stunnel: LOG5[15]: s_connect: connected 127.0.0.1:6382
stunnel: LOG5[15]: Service [redis] connected remote server from 127.0.0.1:48234
stunnel: LOG5[16]: Service [redis] accepted connection from 127.0.0.1:52248
stunnel: LOG5[34]: s_connect: connected 127.0.0.1:6381
stunnel: LOG5[34]: Service [redis] connected remote server from 127.0.0.1:56976
stunnel: LOG5[35]: Service [redis] accepted connection from 127.0.0.1:37820
stunnel: LOG5[16]: s_connect: connected 127.0.0.1:6382
stunnel: LOG5[16]: Service [redis] connected remote server from 127.0.0.1:48246
stunnel: LOG5[17]: Service [redis] accepted connection from 127.0.0.1:52260
stunnel: LOG5[35]: s_connect: connected 127.0.0.1:6381
stunnel: LOG5[35]: Service [redis] connected remote server from 127.0.0.1:56988
stunnel: LOG5[36]: Service [redis] accepted connection from 127.0.0.1:37830
stunnel: LOG5[17]: s_connect: connected 127.0.0.1:6382
stunnel: LOG5[17]: Service [redis] connected remote server from 127.0.0.1:48254
stunnel: LOG5[18]: Service [redis] accepted connection from 127.0.0.1:52268
stunnel: LOG5[36]: s_connect: connected 127.0.0.1:6381
stunnel: LOG5[36]: Service [redis] connected remote server from 127.0.0.1:56998
stunnel: LOG5[37]: Service [redis] accepted connection from 127.0.0.1:37840
stunnel: LOG5[18]: s_connect: connected 127.0.0.1:6382
stunnel: LOG5[18]: Service [redis] connected remote server from 127.0.0.1:48266
stunnel: LOG5[19]: Service [redis] accepted connection from 127.0.0.1:52280
stunnel: LOG5[19]: s_connect: connected 127.0.0.1:6382
stunnel: LOG5[19]: Service [redis] connected remote server from 127.0.0.1:48270
stunnel: LOG5[37]: s_connect: connected 127.0.0.1:6381
stunnel: LOG5[37]: Service [redis] connected remote server from 127.0.0.1:57010
stunnel: LOG5[38]: Service [redis] accepted connection from 127.0.0.1:37852
stunnel: LOG5[38]: s_connect: connected 127.0.0.1:6381
stunnel: LOG5[38]: Service [redis] connected remote server from 127.0.0.1:57014
stunnel: LOG5[39]: Service [redis] accepted connection from 127.0.0.1:37856
stunnel: LOG5[39]: s_connect: connected 127.0.0.1:6381
stunnel: LOG5[39]: Service [redis] connected remote server from 127.0.0.1:57018
stunnel: LOG5[0]: Service [redis] accepted connection from 127.0.0.1:48610
stunnel: LOG5[0]: s_connect: connected 127.0.0.1:6361
stunnel: LOG5[0]: Service [redis] connected remote server from 127.0.0.1:60396
stunnel: LOG5[1]: Service [redis] accepted connection from 127.0.0.1:48616
stunnel: LOG5[1]: s_connect: connected 127.0.0.1:6361
stunnel: LOG5[1]: Service [redis] connected remote server from 127.0.0.1:60400
stunnel: LOG5[2]: Service [redis] accepted connection from 127.0.0.1:48620
stunnel: LOG5[2]: s_connect: connected 127.0.0.1:6361
stunnel: LOG5[2]: Service [redis] connected remote server from 127.0.0.1:60404
stunnel: LOG5[3]: Service [redis] accepted connection from 127.0.0.1:48624
stunnel: LOG5[3]: s_connect: connected 127.0.0.1:6361
stunnel: LOG5[3]: Service [redis] connected remote server from 127.0.0.1:60408
stunnel: LOG5[4]: Service [redis] accepted connection from 127.0.0.1:48628
stunnel: LOG5[4]: s_connect: connected 127.0.0.1:6361
stunnel: LOG5[4]: Service [redis] connected remote server from 127.0.0.1:60412
stunnel: LOG5[5]: Service [redis] accepted connection from 127.0.0.1:48632
stunnel: LOG5[5]: s_connect: connected 127.0.0.1:6361
stunnel: LOG5[5]: Service [redis] connected remote server from 127.0.0.1:60416
stunnel: LOG5[6]: Service [redis] accepted connection from 127.0.0.1:48640
stunnel: LOG5[6]: s_connect: connected 127.0.0.1:6361
stunnel: LOG5[6]: Service [redis] connected remote server from 127.0.0.1:60424
stunnel: LOG5[7]: Service [redis] accepted connection from 127.0.0.1:48644
stunnel: LOG5[7]: s_connect: connected 127.0.0.1:6361
stunnel: LOG5[7]: Service [redis] connected remote server from 127.0.0.1:60428
stunnel: LOG5[8]: Service [redis] accepted connection from 127.0.0.1:48648
stunnel: LOG5[8]: s_connect: connected 127.0.0.1:6361
stunnel: LOG5[8]: Service [redis] connected remote server from 127.0.0.1:60432
stunnel: LOG5[9]: Service [redis] accepted connection from 127.0.0.1:48652
stunnel: LOG5[9]: s_connect: connected 127.0.0.1:6361
stunnel: LOG5[9]: Service [redis] connected remote server from 127.0.0.1:60436
stunnel: LOG5[40]: Service [redis] accepted connection from 127.0.0.1:41352
stunnel: LOG5[40]: s_connect: connected 127.0.0.1:6381
stunnel: LOG5[40]: Service [redis] connected remote server from 127.0.0.1:60514
stunnel: LOG5[41]: Service [redis] accepted connection from 127.0.0.1:41356
stunnel: LOG5[41]: s_connect: connected 127.0.0.1:6381
stunnel: LOG5[41]: Service [redis] connected remote server from 127.0.0.1:60518
stunnel: LOG5[42]: Service [redis] accepted connection from 127.0.0.1:41360
stunnel: LOG5[42]: s_connect: connected 127.0.0.1:6381
stunnel: LOG5[42]: Service [redis] connected remote server from 127.0.0.1:60524
stunnel: LOG5[43]: Service [redis] accepted connection from 127.0.0.1:41366
stunnel: LOG5[43]: s_connect: connected 127.0.0.1:6381
stunnel: LOG5[43]: Service [redis] connected remote server from 127.0.0.1:60528
stunnel: LOG5[44]: Service [redis] accepted connection from 127.0.0.1:41370
stunnel: LOG5[44]: s_connect: connected 127.0.0.1:6381
stunnel: LOG5[44]: Service [redis] connected remote server from 127.0.0.1:60532
stunnel: LOG5[45]: Service [redis] accepted connection from 127.0.0.1:41374
stunnel: LOG5[45]: s_connect: connected 127.0.0.1:6381
stunnel: LOG5[45]: Service [redis] connected remote server from 127.0.0.1:60536
stunnel: LOG5[46]: Service [redis] accepted connection from 127.0.0.1:41378
stunnel: LOG5[46]: s_connect: connected 127.0.0.1:6381
stunnel: LOG5[46]: Service [redis] connected remote server from 127.0.0.1:60546
stunnel: LOG5[47]: Service [redis] accepted connection from 127.0.0.1:41388
stunnel: LOG5[47]: s_connect: connected 127.0.0.1:6381
stunnel: LOG5[47]: Service [redis] connected remote server from 127.0.0.1:60552
stunnel: LOG5[48]: Service [redis] accepted connection from 127.0.0.1:41394
stunnel: LOG5[48]: s_connect: connected 127.0.0.1:6381
stunnel: LOG5[48]: Service [redis] connected remote server from 127.0.0.1:60556
stunnel: LOG5[49]: Service [redis] accepted connection from 127.0.0.1:41398
stunnel: LOG5[49]: s_connect: connected 127.0.0.1:6381
stunnel: LOG5[49]: Service [redis] connected remote server from 127.0.0.1:60560
stunnel: LOG5[47]: Connection closed: 5 byte(s) sent to TLS, 32 byte(s) sent to socket
stunnel: LOG5[46]: Connection closed: 5 byte(s) sent to TLS, 32 byte(s) sent to socket
stunnel: LOG5[45]: Connection closed: 5 byte(s) sent to TLS, 32 byte(s) sent to socket
stunnel: LOG5[43]: Connection closed: 5 byte(s) sent to TLS, 32 byte(s) sent to socket
stunnel: LOG5[44]: Connection closed: 5 byte(s) sent to TLS, 32 byte(s) sent to socket
stunnel: LOG5[49]: Connection closed: 5 byte(s) sent to TLS, 32 byte(s) sent to socket
stunnel: LOG5[40]: Connection closed: 19 byte(s) sent to TLS, 60 byte(s) sent to socket
stunnel: LOG5[41]: Connection closed: 12 byte(s) sent to TLS, 46 byte(s) sent to socket
stunnel: LOG5[42]: Connection closed: 5 byte(s) sent to TLS, 32 byte(s) sent to socket
stunnel: LOG5[48]: Connection closed: 5 byte(s) sent to TLS, 32 byte(s) sent to socket
stunnel: LOG5[8]: Connection closed: 109 byte(s) sent to TLS, 631 byte(s) sent to socket
stunnel: LOG5[9]: Connection closed: 103 byte(s) sent to TLS, 228 byte(s) sent to socket
stunnel: LOG5[8]: Connection closed: 114 byte(s) sent to TLS, 510 byte(s) sent to socket
stunnel: LOG5[9]: Connection closed: 98 byte(s) sent to TLS, 483 byte(s) sent to socket
stunnel: LOG5[6]: Connection closed: 139 byte(s) sent to TLS, 955 byte(s) sent to socket
stunnel: LOG5[7]: Connection closed: 125 byte(s) sent to TLS, 928 byte(s) sent to socket
stunnel: LOG5[7]: Connection closed: 119 byte(s) sent to TLS, 525 byte(s) sent to socket
stunnel: LOG5[3]: Connection closed: 139 byte(s) sent to TLS, 1087 byte(s) sent to socket
stunnel: LOG5[3]: Connection closed: 162 byte(s) sent to TLS, 1399 byte(s) sent to socket
stunnel: LOG5[6]: Connection closed: 134 byte(s) sent to TLS, 1075 byte(s) sent to socket
stunnel: LOG5[4]: Connection closed: 165 byte(s) sent to TLS, 1400 byte(s) sent to socket
stunnel: LOG5[4]: Connection closed: 143 byte(s) sent to TLS, 1336 byte(s) sent to socket
stunnel: LOG5[5]: Connection closed: 148 byte(s) sent to TLS, 1103 byte(s) sent to socket
stunnel: LOG5[19]: Connection closed: 82 byte(s) sent to TLS, 186 byte(s) sent to socket
stunnel: LOG5[39]: Connection closed: 98 byte(s) sent to TLS, 360 byte(s) sent to socket
stunnel: LOG5[17]: Connection closed: 82 byte(s) sent to TLS, 186 byte(s) sent to socket
stunnel: LOG5[36]: Connection closed: 132 byte(s) sent to TLS, 1002 byte(s) sent to socket
stunnel: LOG5[18]: Connection closed: 82 byte(s) sent to TLS, 186 byte(s) sent to socket
stunnel: LOG5[38]: Connection closed: 105 byte(s) sent to TLS, 521 byte(s) sent to socket
stunnel: LOG5[0]: Connection closed: 157 byte(s) sent to TLS, 1350 byte(s) sent to socket
stunnel: LOG5[35]: Connection closed: 131 byte(s) sent to TLS, 1000 byte(s) sent to socket
stunnel: LOG5[5]: Connection closed: 142 byte(s) sent to TLS, 1224 byte(s) sent to socket
stunnel: LOG5[34]: Connection closed: 133 byte(s) sent to TLS, 1147 byte(s) sent to socket
stunnel: LOG5[16]: Connection closed: 89 byte(s) sent to TLS, 200 byte(s) sent to socket
stunnel: LOG5[2]: Connection closed: 139 byte(s) sent to TLS, 1089 byte(s) sent to socket
stunnel: LOG5[15]: Connection closed: 89 byte(s) sent to TLS, 200 byte(s) sent to socket
stunnel: LOG5[37]: Connection closed: 124 byte(s) sent to TLS, 965 byte(s) sent to socket
stunnel: LOG5[31]: Connection closed: 139 byte(s) sent to TLS, 1160 byte(s) sent to socket
stunnel: LOG5[13]: Connection closed: 89 byte(s) sent to TLS, 200 byte(s) sent to socket
stunnel: LOG5[12]: Connection closed: 89 byte(s) sent to TLS, 200 byte(s) sent to socket
stunnel: LOG5[32]: Connection closed: 139 byte(s) sent to TLS, 1160 byte(s) sent to socket
stunnel: LOG5[18]: Connection closed: 114 byte(s) sent to TLS, 511 byte(s) sent to socket
stunnel: LOG5[19]: Connection closed: 96 byte(s) sent to TLS, 214 byte(s) sent to socket
stunnel: LOG5[1]: Connection closed: 140 byte(s) sent to TLS, 1201 byte(s) sent to socket
stunnel: LOG5[16]: Connection closed: 141 byte(s) sent to TLS, 1090 byte(s) sent to socket
stunnel: LOG5[6]: Connection closed: 89 byte(s) sent to TLS, 200 byte(s) sent to socket
stunnel: LOG5[14]: Connection closed: 154 byte(s) sent to TLS, 1251 byte(s) sent to socket
stunnel: LOG5[25]: Connection closed: 139 byte(s) sent to TLS, 1135 byte(s) sent to socket
stunnel: LOG5[30]: Connection closed: 147 byte(s) sent to TLS, 1298 byte(s) sent to socket
stunnel: LOG5[9]: Connection closed: 89 byte(s) sent to TLS, 200 byte(s) sent to socket
stunnel: LOG5[29]: Connection closed: 98 byte(s) sent to TLS, 358 byte(s) sent to socket
stunnel: LOG5[8]: Connection closed: 89 byte(s) sent to TLS, 200 byte(s) sent to socket
stunnel: LOG5[33]: Connection closed: 133 byte(s) sent to TLS, 1146 byte(s) sent to socket
stunnel: LOG5[1]: Connection closed: 174 byte(s) sent to TLS, 1659 byte(s) sent to socket
stunnel: LOG5[0]: Connection closed: 111 byte(s) sent to TLS, 339 byte(s) sent to socket
stunnel: LOG5[15]: Connection closed: 156 byte(s) sent to TLS, 1252 byte(s) sent to socket
stunnel: LOG5[0]: Connection closed: 179 byte(s) sent to TLS, 1524 byte(s) sent to socket
stunnel: LOG5[7]: Connection closed: 89 byte(s) sent to TLS, 200 byte(s) sent to socket
stunnel: LOG5[27]: Connection closed: 124 byte(s) sent to TLS, 958 byte(s) sent to socket
stunnel: LOG5[4]: Connection closed: 96 byte(s) sent to TLS, 214 byte(s) sent to socket
stunnel: LOG5[2]: Connection closed: 163 byte(s) sent to TLS, 1375 byte(s) sent to socket
stunnel: LOG5[17]: Connection closed: 121 byte(s) sent to TLS, 659 byte(s) sent to socket
stunnel: LOG5[5]: Connection closed: 96 byte(s) sent to TLS, 214 byte(s) sent to socket
stunnel: LOG5[10]: Connection closed: 97 byte(s) sent to TLS, 324 byte(s) sent to socket
stunnel: LOG5[26]: Connection closed: 132 byte(s) sent to TLS, 994 byte(s) sent to socket
stunnel: LOG5[3]: Connection closed: 96 byte(s) sent to TLS, 214 byte(s) sent to socket
stunnel: LOG5[2]: Connection closed: 96 byte(s) sent to TLS, 214 byte(s) sent to socket
stunnel: LOG5[1]: Connection closed: 96 byte(s) sent to TLS, 214 byte(s) sent to socket
stunnel: LOG5[11]: Connection closed: 89 byte(s) sent to TLS, 200 byte(s) sent to socket
stunnel: LOG5[14]: Connection closed: 89 byte(s) sent to TLS, 200 byte(s) sent to socket
stunnel: LOG5[28]: Connection closed: 105 byte(s) sent to TLS, 517 byte(s) sent to socket
stunnel: LOG5[23]: Connection closed: 139 byte(s) sent to TLS, 1155 byte(s) sent to socket
stunnel: LOG5[13]: Connection closed: 148 byte(s) sent to TLS, 1214 byte(s) sent to socket
stunnel: LOG5[24]: Connection closed: 140 byte(s) sent to TLS, 1153 byte(s) sent to socket
stunnel: LOG5[21]: Connection closed: 146 byte(s) sent to TLS, 1171 byte(s) sent to socket
stunnel: LOG5[20]: Connection closed: 153 byte(s) sent to TLS, 1149 byte(s) sent to socket
stunnel: LOG5[12]: Connection closed: 157 byte(s) sent to TLS, 1385 byte(s) sent to socket
stunnel: LOG5[22]: Connection closed: 148 byte(s) sent to TLS, 1314 byte(s) sent to socket
stunnel: LOG5[11]: Connection closed: 164 byte(s) sent to TLS, 1399 byte(s) sent to socket
stunnel: LOG5[10]: Connection closed: 172 byte(s) sent to TLS, 1522 byte(s) sent to socket
ok github.com/envoyproxy/ratelimit/test/integration 71.444s
ok github.com/envoyproxy/ratelimit/test/limiter (cached)
ok github.com/envoyproxy/ratelimit/test/memcached (cached)
ok github.com/envoyproxy/ratelimit/test/metrics (cached)
? github.com/envoyproxy/ratelimit/test/mocks [no test files]
? github.com/envoyproxy/ratelimit/test/mocks/config [no test files]
? github.com/envoyproxy/ratelimit/test/mocks/limiter [no test files]
? github.com/envoyproxy/ratelimit/test/mocks/memcached [no test files]
? github.com/envoyproxy/ratelimit/test/mocks/redis [no test files]
? github.com/envoyproxy/ratelimit/test/mocks/rls [no test files]
? github.com/envoyproxy/ratelimit/test/mocks/runtime/loader [no test files]
? github.com/envoyproxy/ratelimit/test/mocks/runtime/snapshot [no test files]
? github.com/envoyproxy/ratelimit/test/mocks/srv [no test files]
? github.com/envoyproxy/ratelimit/test/mocks/stats [no test files]
? github.com/envoyproxy/ratelimit/test/mocks/utils [no test files]
ok github.com/envoyproxy/ratelimit/test/redis (cached)
ok github.com/envoyproxy/ratelimit/test/server (cached)
ok github.com/envoyproxy/ratelimit/test/service (cached)
ok github.com/envoyproxy/ratelimit/test/srv (cached)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment