mirror of
https://github.com/featurebasedb/featurebase.git
synced 2026-09-06 08:35:55 +00:00
6740bc250e
MarshalLogMessage serializes the log message and prepends additional encoding information to each message. Currently, we prepend three bytes to each log message: byte[0]: encodeVersion - this is currently a constant within the code. If we modify structs such that they encode differently, we'll have to change the constant and keep previous versions of structs for deserialization. byte[1]: encodeType (e.g. "json", etc.) byte[2]: logMessageType If we get into a situation where we want more flexibility in these message header bytes—for example, if we want to use more than three bytes—we could do something with the first bit of the encodeVersion: if it's 1, that could indicate that there are additional header bytes, and the following seven bits could indicate how many.
88 lines
2.4 KiB
Makefile
88 lines
2.4 KiB
Makefile
.PHONY: test testv test-integration testv-integration
|
|
|
|
MCLOUD_ENV ?= sandbox
|
|
MCLOUD_ENV_FILE=.env.$(MCLOUD_ENV)
|
|
-include $(MCLOUD_ENV_FILE)
|
|
|
|
|
|
GO=go
|
|
|
|
test:
|
|
$(GO) test ./... -short
|
|
|
|
testv:
|
|
$(GO) test -v ./... -short
|
|
|
|
test-integration:
|
|
mkdir -p ../coverage-from-docker
|
|
$(GO) test ./test/dax -count 1 -run TestDAXIntegration/$(RUN)
|
|
|
|
testv-integration:
|
|
$(GO) test -v ./test/dax -count 1 -run TestDAXIntegration/$(RUN)
|
|
|
|
|
|
############################### AWS STUFF ###############################
|
|
|
|
AWS_REGION ?=
|
|
AWS_PROFILE ?=
|
|
|
|
AWS = aws --profile=$(AWS_PROFILE) --region=$(AWS_REGION)
|
|
|
|
# After pushing new images, use "make redeploy-ecs" to redeploy all DAX services.
|
|
redeploy-ecs: redeploy-svc-mds redeploy-svc-computer redeploy-svc-queryer
|
|
|
|
redeploy-svc-%:
|
|
$(AWS) ecs update-service --cluster DAX --service $*-$(MCLOUD_ENV)-ecs-service --force-new-deployment --no-cli-pager
|
|
|
|
|
|
# Scale changes the desired count of the computer service. e.g. "make scale N=4"
|
|
scale:
|
|
$(AWS) ecs update-service --cluster DAX --service computer-$(MCLOUD_ENV)-ecs-service --desired-count=$(N) --no-cli-pager
|
|
|
|
|
|
I ?= 0
|
|
# Get a shell on a running contianer. e.g. "make mds-shell", "make datagen-shell", etc.
|
|
%-shell:
|
|
$(eval TASK_ARN := $(shell $(AWS) ecs list-tasks --cluster=DAX --family=$*-family | jq -r .taskArns[$(I)]))
|
|
$(AWS) ecs execute-command --cluster=DAX --task=$(TASK_ARN) --command=/bin/sh --interactive
|
|
|
|
datagen: task-arn-datagen
|
|
$(eval TASK_ARN := $(shell $(AWS) ecs list-tasks --cluster=DAX --family=$*-family | jq -r .taskArns[$(I)]))
|
|
$(AWS) ecs run-task --cluster=DAX --task-definition=$(TASK_ARN) --cli-input-json=file://./datagen_task_input.json --no-cli-pager --enable-execute-command
|
|
|
|
|
|
####################### docker-compose stuff ##############################3
|
|
|
|
|
|
dc-reset: dc-prereqs dc-down
|
|
rm -rf ./dax-data/{snapshotter,writelogger}/*
|
|
|
|
dc-build:
|
|
cd .. && $(MAKE) build-for-quick
|
|
docker-compose build
|
|
|
|
dc-up:
|
|
docker-compose up -d
|
|
|
|
dc-down:
|
|
docker-compose down
|
|
|
|
dc-full-reup: dc-reset dc-build dc-up
|
|
|
|
dc-logs:
|
|
docker-compose logs -f
|
|
|
|
dc-logs-%:
|
|
docker-compose logs -f $*
|
|
|
|
dc-prereqs:
|
|
mkdir -p ../.quick
|
|
|
|
# This is just an example. For it to work, you'll first need to:
|
|
# featurebase cli --host localhost --port 8080 --org-id=testorg --db-id=testdb
|
|
# create table keysidstbl2 (_id string, slice idset);
|
|
dc-datagen:
|
|
docker-compose run datagen --end-at=500 --pilosa.batch-size=500 --featurebase.table-name=keysidstbl2
|
|
|
|
dc-exec-%:
|
|
docker-compose exec $* /bin/sh
|