Building from source gives old version ?
Hi,
On Ubuntu Server 12.04, we are trying to build the very latest Couchbase from source using the instructions on those pages:
http://www.couchbase.com/wiki/display/couchbase/Building+Couchbase+from+...
http://www.couchbase.com/wiki/display/couchbase/Architecture+and+Source+...
The first page assumes there's a "couchbase{$ver}_src.tar.gz" file but we can't find any on your site.
On the second page, we manage to get the source code with repo init/sync
Using branch-2.0.xml as branch, we managed to compile the source code and run with:
./install/bin/couchbase-server
The server starts fine but going to the web interface to set the cluster up, we are displayed the following version:
2.0.0 DEV edition (build-433)
Then, after deleting the whole folder and start repo init with released/2.0.0-beta-linux.xml branch this time gives this version:
2.0.0 DEV edition (build-331)
But when installing the beta 2.0 from installer shows build 1723
After testing of build 433, we are getting serious connectivity errors where the service go away and restart.
I'm really confused. How to get the latest source code ?
We are trying to get a build # >1723, basically, more recent than 2.0 beta
The reason is that on 2.0 beta we are getting a bug where views return "badarg" for a couple of seconds after deleting multiple keys using memcache interface (using python library).
This doesn't happens if we only try to delete only one key but using delete multi or one at a time in a tight loop, the view returns "badargs" error and then suddenly fix itself after a couple of seconds.
Looking at Couchbase issues, there's some bugs involving views returning "badargs" that seemed to be fix in recent builds and we wanted to try the very latest to see if it fixed our problem as well before we actually fill a bug report.
We tried on both Windows and Ubuntu, only one server in cluster.
Any help building latest appreciated...
Hope someone else can help with the building question.
We will be pushing out a refresh with these bug fixes sometime next week. So hope that helps you out.