Conflicts: lib/nanite/cluster.rb lib/nanite/job.rb lib/nanite/mapper.rb
…d RS nanite
The version of Nanite is updated to reflect the significance of the recent changes: - support for Redis - addition of tags - nanite-agent stop - nanite-mapper stop - writing pid file
…ilable Signed-off-by: ezmobius <firstname.lastname@example.org>
+ Its preferable to install amqp gem from RubyForge + Minor update to README.rdoc related to --token Signed-off-by: ezmobius <email@example.com>
note that it requires that dtach is installed. Signed-off-by: ezmobius <firstname.lastname@example.org>
- crew and rabbitconf should not be general binaries installed with the gem - the async rack example belongs in the examples dir - modified the Rakefile to no longer install crew and rabbitconf in the bin dir - modified README.rdoc to reference new location for rabbitconf - added some example related TODO's
…ently the README is broken in gem server and needs some love.
…n' from anywhere.
exchange and have a nanite on each server in your cluster that subscribes to the named file broadcast 'channel' This allows for multi server depoyments with no clustered filesystem to try and maintain a replicated set of files. When an upload happens on one slice, it publishes the file to the exchange and all the subscribers write it out on their own filesystems in their Nanite.file_root
…-strong names and they only share the hasehs queue names with the mapper. Any other agents in the system will only ever know their user name they used to log into rabbitmq but will not know the name of the queue to send them ops on. Also when an agent makes a request for an op, he creates a temporary queue with a strong hashed name for the return results to come to. This way the worker agents still don't know the requestors true queue name. The return address queue is only temporary and is only used once and then remopved when all results for said op are collected. This system gives us better security then we had in XMPP since the mapper is the only thing that knows an agents true address Temporary queues only take 4bytes of ram in rabbitmq and are auto deleted after they are no longer in use.
and reducing in the requesting client. can push 3000 ops to 30 agents in 12 seconds