PLEASE click to Vsync.codeplex.com to upgrade to Vsync. We no longer recommend the use of Isis2, and are instead supporting Vsync, which is the same system, but with a global edit mapping from Isis2 to Vsync.We've preserved this final Isis2 version is for archival purposes, but it is no longer the must solid version of the system. Important changes have been made since November of 2015, and you will want the improved system, not this. To switch over, just replace any use of Isis2 or Isis with Vsync, and of ISIS with VSYNC, using three global replaces. No other changes are required.
V2.2.2013 was our most current stable release of the system until we applied a single bug patch, which updated the version numbering to V2.2.2020 in November 205, just before switching to The new VSYNC system name. Please do not report issues you have on the issues or use the discussions tab. Isis2 is no longer supported.
Even V2.2.2013 was mostly a bug-fix release and is otherwise very similar to V2.2.1962. Basically, the system has been very stable for a while now with just minor bug patches from time to time, and that includes V2.2.2020.
V2.2.2013 includes a minor patch to V2.2.2003 to correct an issue in the DHT. V2.2.2003 was uploaded in mid July and V2.2.2013 a few days later.
Use of the OOB code in V2.2.2013 involves understanding some parameter settings. By default, it runs over UDP multicast If you specify ISISUNICASTONLY=true you'll get pure point to point, but in two possible modes Mode 1: ISIS
OOBVIATCP=true (this is the default). A TCP connection will be used for each OOB file transfer. This is a bit faster than the Isis UDP option (not hugely so) Mode 2: ISIS_OOBVIATCP=false (needs to be explicitly set, e.g. using export in bash). Uses Isis UDP unicast connections to transfer your files.
INFINIBAND=true (you need to set these; defaults are false, false): If you are on an Infiniband interconnect, and have the ib.dll file built and in a place where it can be found, does OOB transfers as big RDMA copies, DMA from memory-to-memory. You may need to email Ken (email@example.com) or Jonathan for help setting this up -- it isn't hard but it isn't properly documented yet.
Note: You'll ONLY need ib.dll (or ib.h and ib.c, from which one builds ib.dll) if you plan to use Infiniband or the new Fast Ethernet via ROE or ROCE (RDMA on Ethernet or RDMA on Converged Ethernet) feature, and obviously that only works if Isis is configured to use the Infiniband or Fast Ethernet ROE/ROCE network interface. So there is an easy but not automatic setup needed. Ken will be happy to help you get past that step. For this version of Isis2, there should be no real difference between ROE and ROCE, by the way.
For people who don't plan to play with these OOB file transfer features ib.dll won't even be loaded by Isis2, so you don't need to download the file or put it anywhere. Everything will work just fine. On the other hand, you won't get the blazingly fast OOB file transfers that we talk about so much lately.
All of this really pays off in terms of performance. Isis2 is WAY faster when using OOB in smart ways. Of course you'll need to learn how that works. But Weijia Song will soon make OOB nearly invisible: he's building a file system that does it for you, and a "command line" way of initiating OOB transfers too.
Note: In March 2015 I also modified the "research prototype" comment to tone down the warnings. By now the system seems very robust and if people are prepared to do the needed quality assurance for the applications they build, I think it can safely be used in any setting where it is safe to use computer technologies of other kinds.