Since many deployments may start out with 3 nodes and so little is known about how to grow a cluster from 3 memebrs to 5 members without losing the existing Quorum, here is an example of how this might be achieved.
In this example, all 5 nodes will be running on the same Vagrant host for the purpose of illustration, running on distinct configurations (ports and data directories) without the actual load of clients.
YMMV. Caveat usufructuarius.
| SELECT id,state,command,time,left(replace(info,'\n','<lf>'),120) | |
| FROM information_schema.processlist | |
| WHERE command <> 'Sleep' | |
| AND info NOT LIKE '%PROCESSLIST%' | |
| ORDER BY time DESC LIMIT 50; |
Previous versions used homebrew to install the various versions. As suggested in the comments, it's better to use pyenv instead. If you are looking for the previous version of this document, see the revision history.
$ brew update
$ brew install pyenv
$ pyenv install 3.5.0
$ pyenv install 3.4.3
$ pyenv install 3.3.6
$ pyenv install 3.2.6
$ pyenv install 2.7.10
$ pyenv install 2.6.9
| // a list of useful queries for profiler analysis. Starting with the most basic. | |
| // 2.4 compatible | |
| // | |
| // output explained: | |
| // | |
| { | |
| "ts" : ISODate("2012-09-14T16:34:00.010Z"), // date it occurred | |
| "op" : "query", // the operation type | |
| "ns" : "game.players", // the db and collection |
| # knife cheat | |
| ## Search Examples | |
| knife search "name:ip*" | |
| knife search "platform:ubuntu*" | |
| knife search "platform:*" -a macaddress | |
| knife search "platform:ubuntu*" -a uptime | |
| knife search "platform:ubuntu*" -a virtualization.system | |
| knife search "platform:ubuntu*" -a network.default_gateway |
| filter { | |
| if [type] == 'postgres_csv' { | |
| csv { | |
| columns => [ | |
| "pg_timestamp", | |
| "user_name", | |
| "database_name", | |
| "process_id", | |
| "connection_from", | |
| "session_id", |
With NLTK version 3.1 and Stanford NER tool 2015-12-09, it is possible to hack the StanfordNERTagger._stanford_jar to include other .jar files that are necessary for the new tagger.
First set up the environment variables as per instructed at https://github.com/nltk/nltk/wiki/Installing-Third-Party-Software
| 1.Producer | |
| 1.request.required.acks=[0,1,all/-1] 0 no acknowledgement but ver fast, 1 acknowledged after leader commits, all acknowledged after replicated | |
| 2.use Async producer - use callback for the acknowledgement, using property producer.type=1 | |
| 3.Batching data - send multiple messages together. | |
| batch.num.messages | |
| queue.buffer.max.ms | |
| 4.Compression for Large files - gzip, snappy supported | |
| very large files can be stored in shared location and just the file path can be logged by the kafka producer. | |