HyperDex 1.7: Improved Coordinator

[Robert Escriva]

We are proud to announce HyperDex 1.7, the next generation NoSQL data
store that provides ACID transactions, schema-less documents, per-object
authorization fault-tolerance, and high-performance.

This release brings the following changes and improvements:

- Coordinator improvements: A new coordinator provides the same fault
tolerance guarantees as before, and achieves better stability, reduced
resource usage, and improved recovery time.

- cond_put_or_create: A new atomic API call.

- Internal performance improvements and bug fixes.

Some key features of HyperDex are:

- High Performance: HyperDex is fast. It outperforms MongoDB and
Cassandra on industry-standard benchmarks by a factor of 2X or more.

- Advanced Functionality: With the Warp add-on, HyperDex offers
multi-key transactions that span multiple objects with ACID
guarantees.

- Strong Consistency: HyperDex ensures that every GET returns the
result of the latest PUT.

- Fault Tolerance: HyperDex automatically replicates data to tolerate a
configurable number of failures.

- Scalable: HyperDex automatically redistributes data to make use of
new resources as you add more nodes to your cluster.

HyperDex runs on 64-bit Linux (Ubuntu, Debian, Fedora, Centos) and OS X.
Binary packages for Debian 7, Ubuntu 12.04,14.04, Fedora 20, and CentOS
6,7 are available [1], as well as source tarballs for other Linux
platforms.

This release provides bindings for C, C++, Python, Node.js, Java, Ruby,
and Go.

An evaluation version of Warp, and Warp bindings for Python, Java, and
Ruby are available in the HyperDex repository. Install the
"hyperdex-warp" package in your package manager to switch from HyperDex
to Warp and test out the evaluation version.

Happy Hacking,
The HyperDex Team

[1] http://hyperdex.org/download

[Robert Escriva]

Hi Puneet,

Can you try installing "replicant-tools", or running "apt-get update &&
apt-get upgrade"? The former is a work-around, while the latter will
update to packages we just published to fix the issue.

-Robert

On Wed, May 27, 2015 at 03:59:54PM -0700, Puneet Jain wrote:
>
> Is this only me or anyone else is also facing this problem. I installed
> hyerpdex 1.7 today on ubuntu 14.04
>
>
> I started coordinator like this:
>
> synrg@synrg:hyperdex-admin$ hyperdex coordinator -f -l a.b.c.d -p 1982
>
> I0527 17:38:13.139991 16859 daemon.cc:325] running in the foreground
>
> I0527 17:38:13.140103 16859 daemon.cc:326] no log will be generated; instead,
> the log messages will print to the terminal
>
> I0527 17:38:13.140122 16859 daemon.cc:327] provide "--daemon" on the
> command-line if you want to run in the background
>
> I0527 17:38:13.140233 16859 daemon.cc:359] started cluster
> (13553916486075948557)
>
> I0527 17:38:13.269907 16859 daemon.cc:1455] starting scout for ballot(2, server
> (5522063474190744419))
>
> I0527 17:38:13.284836 16859 daemon.cc:982] phase 1a: taking up ballot(2,
> server(5522063474190744419))
>
> I0527 17:38:13.474941 16859 daemon.cc:1026] phase 1b: server
> (5522063474190744419) has taken up ballot(2, server(5522063474190744419))
>
> I0527 17:38:13.474967 16859 daemon.cc:1042] phase 1 complete: transitioning to
> phase 2 on ballot(2, server(5522063474190744419))
>
> I0527 17:38:13.560874 16859 replica.cc:1337] creating object "hyperdex"
>
> E0527 17:38:13.610273 16859 replica.cc:1767] could not spawn library for
> hyperdex: No such file or directory [2]
>
> I0527 17:38:51.956310 16859 daemon.cc:870] introducing 130.126.139.84:40114 to
> the cluster
>
> I0527 17:41:15.909327 16859 daemon.cc:870] introducing 130.126.139.84:40119 to
> the cluster
>
> I0527 17:42:40.756572 16859 daemon.cc:870] introducing 130.126.139.84:40124 to
> the cluster
>
> Daemon like this:
>
> synrg@synrg:hyperdex-daemon$ hyperdex daemon -f --listen=127.0.0.1
> --listen-port=2012 --coordinator=a.b.c.d --coordinator-port=1982 --data=/home/
> synrg/Downloads/hyperdex-data/
>
> I0527 17:38:51.767685 16867 daemon.cc:284] running in the foreground
>
> I0527 17:38:51.767761 16867 daemon.cc:285] no log will be generated; instead,
> the log messages will print to the terminal
>
> I0527 17:38:51.767767 16867 daemon.cc:286] provide "--daemon" on the
> command-line if you want to run in the background
>
> I0527 17:38:51.767771 16867 daemon.cc:293] initializing local storage
>
> I0527 17:38:51.887771 16870 background_thread.cc:150] checkpointer thread
> started
>
> I0527 17:38:51.887785 16871 background_thread.cc:150] indexing thread started
>
> I0527 17:38:51.887801 16872 background_thread.cc:150] wiping thread started
>
> I0527 17:38:51.887805 16867 daemon.cc:324] changing coordinator address from
> 127.0.0.1:1982 to a.b.c.d:1982
>
> But when I try to create a space using python or directly, the command never
> returns. It neither prints error.
>
> I am using standard tutorial: http://hyperdex.org/doc/latest/QuickStart/
>
> I am also facing similar problems on Macbook.
>
> Thanks
> -Puneet

> --
> You received this message because you are subscribed to the Google Groups
> "hyperdex-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an email
> to hyperdex-discu...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.