Today was my last day at Basho, just 3 weeks shy of 4 years.
Looking back, I'm thrilled how much we've accomplished, both with Riak itself but also the impact Basho has had on the greater distributed systems community.
I'm proud that my work on improving Riak's clustering system in Riak 1.0 ended up inspiring how Akka Clustering was built.
I'm forever grateful for being given the opportunity to build
Today was my last day at Basho, just 3 weeks shy of 4 years.
Looking back, I'm thrilled how much we've accomplished, both with Riak itself but also the impact Basho has had on the greater distributed systems community.
I'm proud that my work on improving Riak's clustering system in Riak 1.0 ended up inspiring how Akka Clustering was built.
I'm forever grateful for being given the opportunity to build
I was at Amazon for about six and a half years, and now I've been at Google for that long. One thing that struck me immediately about the two companies -- an impression that has been reinforced almost daily -- is that Amazon does everything wrong, and Google does everything right. Sure, it's a sweeping generalization, but a surprisingly accurate one. It's pretty crazy. There are probably a hundred or even two hundred different ways you can compare the two companies, and Google is superior in all but three of them, if I recall correctly. I actually did a spreadsheet at one point but Legal wouldn't let me show it to anyone, even though recruiting loved it.
I mean, just to give you a very brief taste: Amazon's recruiting process is fundamentally flawed by having teams hire for themselves, so their hiring bar is incredibly inconsistent across teams, despite various efforts they've made to level it out. And their operations are a mess; they don't real
| :: Running Test Package 'delete_test'... | |
| :: Updating schema for 'test'... | |
| :: Done. | |
| :: Indexing documents... | |
| :: Running Solr document(s) '../_files/sample100/solr_add.xml'... | |
| Starting... |
| {ok, Ring} = riak_core_ring_manager:get_my_ring(). | |
| rp(riak_core_ring:all_owners(Ring)). |
| Given that 1.0 prerelease packages are now available, I wanted to briefly mention some changes to Riak's clustering capabilities in 1.0. In particular, there are some subtle semantic differences in the riak-admin commands. More complete docs will be updated in the near future, but I hope a quick email suffices for now. | |
| [nodeB/riak-admin join nodeA] is now strictly one-way. It joins nodeB to the cluster that nodeA is a member of. This is semantically different than pre-1.0 Riak in which join essentially joined clusters together rather than joined a node to a cluster. As part of this change, the joining node (nodeB in this case) must be a singleton (1-node) cluster. | |
| In pre-1.0, leave and remove were essentially the same operation, with leave just being an alias for 'remove this-node'. This has changed. Leave and remove are now very different operations. | |
| [nodeB/riak-admin leave] is the only safe way to have a node leave the cluster, and it must be executed by the node that you want to remove. In this case, no |
| Assuming there are 2 nodes called riak@host1 and riak@host2. | |
| Attach to riak console for riak@host1. Either 'riak-admin console' if the node is down, or 'riak-admin attach' if the node is already up and running. | |
| Update the first line below with the right "other node" name, then copy/paste: | |
| Other = 'riak@host2'. | |
| net_adm:ping(Other). | |
| riak_kv_console:join([atom_to_list(Other)]). | |
| riak:join(Other). |
| Vagrant::Config.run do |config| | |
| config.vm.box = "lucid64" | |
| config.vm.provision :shell, :inline => "rm -f /etc/init.d/sudo /etc/init.d/rsync" | |
| config.vm.provision :chef_solo do |chef| | |
| chef.add_recipe("jdb-basho-expect") | |
| end | |
| config.vm.define :box1 do |box_config| | |
| box_config.vm.network("192.168.60.10") | |
| box_config.vm.host_name = "box1" |
| require 'fog' | |
| def start_server | |
| Fog::Compute[:aws].servers.bootstrap( | |
| :provider => "AWS", | |
| # EBS-backed | |
| # :image_id => "ami-63be790a" | |
| # Ephermal | |
| :image_id => "ami-fbbf7892", | |
| :availability_zone => "us-east-1b", |
| %% Claim dry-run / simulation code | |
| %% | |
| %% If running outside attached Riak shell, must have Riak libs in codepath and | |
| %% proper cookie / long-form node name. Eg: | |
| %% erl -pa RIAK/deps/*/ebin -setcookie riak -name claim@127.0.0.1 | |
| %% | |
| %% Run node/2 passing in cluster claimaint and number of new nodes to test: | |
| %% Add 1 node: claim_dryrun:node('dev1@127.0.0.1', 1) | |
| %% Add 2 nodes: claim_dryrun:node('dev1@127.0.0.1', 2) | |
| %% ... |