VirtualTam's bookmarks
322 bookmarks found
-
- https://www.elastic.co/guide/en/logstash/current/field-extraction.html
- https://www.elastic.co/guide/en/logstash/current/config-examples.html
- https://github.com/logstash-plugins/logstash-patterns-core/blob/master/patterns/grok-patterns
- https://logz.io/blog/logstash-grok/
- https://github.com/elastic/logstash/issues/2965
-
Migrating a 130TB Cluster from Elasticsearch 2 to 5 in 20 Hours with 0 Downtime and a Rollback…
2018-01-31 - https://thoughts.t37.net/how-we-reindexed-36-billions-documents-in-5-days-within-the-same-elasticsearch-cluster-cd9c054d1db8
- https://thoughts.t37.net/how-we-upgraded-a-22tb-mysql-cluster-from-5-6-to-5-7-in-9-months-cc41b391895d
- https://www.elastic.co/blog/hot-warm-architecture-in-elasticsearch-5-x
- https://www.graylog.org/post/back-to-basics-using-a-hot-warm-elasticsearch-cluster
- https://github.com/mraad/es-hot-warm
-
-
- https://dzone.com/articles/parsing-in-python-tools-and-libraries-part-1
- https://dzone.com/articles/parsing-in-python-tools-and-libraries-part-2
- https://dzone.com/articles/parsing-in-python-tools-and-libraries-part-3
- https://dzone.com/articles/parsing-in-python-tools-and-libraries-part-4
- https://dzone.com/articles/parsing-in-python-tools-and-libraries-part-5
-
Advent Calendar - Discuss the Elastic Stack
2017-12-11 "To celebrate the end of the 2017 calendar year, the Elastic Engineering team will be publishing a series of Elastic Stack tips each day, from the 1st of December through the 25th of December[0]. As we are a distributed organisation, and with community members from all corners of the globe, you'll be seeing these threads in a variety of our native languages.
For some examples of what to expect, here is a selection of upcoming topics:
- How to make an Elasticsearch Ingest Plugin (in Japanese)
- Upgrade to 6.x with reindex API and tips (in Chinese)
- ECE: From the trenches (in English)
- Kibana tips for new users (in English)"
-
Actors:
- database server / cluster
- load-balanced application servers relying on a database schema with migrations
- reverse proxy
Issue:
- managing database schema migrations
Possible sequence:
- create the database
- run a service that executes database schema migrations
- start application servers
- start the load-balancer / reverse-proxy
Resources:
- https://www.reddit.com/r/docker/comments/2t2pnf/what_are_best_strategies_to_migrate_relational/
- https://softwareengineering.stackexchange.com/questions/357929/db-migration-strategy-for-docker-containers-in-aws-ecs
- https://stackoverflow.com/questions/41592091/run-a-database-migration-command-when-deploying-a-docker-container-to-aws
- https://ltd-keeper.lsst.io/gke-migrations.html
- https://stackoverflow.com/questions/31715239/docker-compose-database-migrations-and-other-pre-post-scripts
- https://stackoverflow.com/questions/38089999/docker-compose-rails-best-practice-to-migrate
- https://stackoverflow.com/questions/37058812/how-best-to-run-one-off-migration-tasks-in-a-kubernetes-cluster