mirror of
https://github.com/ceph/ceph
synced 2024-12-25 21:03:31 +00:00
Ceph is a distributed object, block, and file storage platform
a576eb3204
There are two problems: 1) We choose the min last_update amoung peers with the max local-les value as an upper bound on requests which could have been reported to the client as committed. We then, for ec pools, roll back to that point to ensure that we don't inadvertently commit to an update which fewer than K replicas actually saw. If the primary sets local-les, accepts an update from a client, and there is a new interval before any of the replicas have been activated, we will end up being forced to use that update which no other replica has seen as the new last_update. This will cause the object to become unfound. We don't have this problem as long as all active replicas agree on last_update before we accept IO. 2) Even for replicated pools, we would then immediately respond to the request which created the primary-only update with a commit since it is in the log and we have no outstanding repops. If we then lose that primary before any of the replicas in the new interval record the new log, we will not only lose the object, but also the log entry recording it, which will result in a lost write. For these reasons, it seems like we need to wait for the replicas to activate before we can process new requests essentially because whatever update we select as last_update is essentially regarded as committed as soon as we accept IO. Fixes: #7649 Signed-off-by: Samuel Just <sam.just@inktank.com> |
||
|---|---|---|
| admin | ||
| ceph-object-corpus@d9870cdfd8 | ||
| debian | ||
| doc | ||
| examples/librados | ||
| fusetrace | ||
| keys | ||
| m4 | ||
| man | ||
| qa | ||
| share | ||
| src | ||
| udev | ||
| wireshark | ||
| .gitignore | ||
| .gitmodules | ||
| .mailmap | ||
| .organizationmap | ||
| AUTHORS | ||
| autogen.sh | ||
| ceph.spec.in | ||
| ChangeLog | ||
| CodingStyle | ||
| configure.ac | ||
| COPYING | ||
| COPYING-LGPL2.1 | ||
| do_autogen.sh | ||
| Doxyfile | ||
| INSTALL | ||
| Makefile.am | ||
| NEWS | ||
| PendingReleaseNotes | ||
| README | ||
| SubmittingPatches | ||
============================================
Ceph - a scalable distributed storage system
============================================
Please see http://ceph.com/ for current info.
Contributing Code
=================
Most of Ceph is licensed under the LGPL version 2.1. Some
miscellaneous code is under BSD-style license or is public domain.
The documentation is licensed under Creative Commons
Attribution-ShareAlike (CC BY-SA). There are a handful of headers
included here that are licensed under the GPL. Please see the file
COPYING for a full inventory of licenses by file.
Code contributions must include a valid "Signed-off-by" acknowledging
the license for the modified or contributed file. Please see the file
SubmittingPatches for details on what that means and on how to
generate and submit patches.
We do not require assignment of copyright to contribute code; code is
contributed under the terms of the applicable license.
Building Ceph
=============
To prepare the source tree after it has been git cloned,
$ git submodule update --init
To build the server daemons, and FUSE client, execute the following:
$ ./autogen.sh
$ ./configure
$ make
(Note that the FUSE client will only be built if libfuse is present.)
Dependencies
------------
The configure script will complain about any missing dependencies as
it goes. You can also refer to debian/control or ceph.spec.in for the
package build dependencies on those platforms. In many cases,
dependencies can be avoided with --with-foo or --without-bar switches.
For example,
$ ./configure --with-nss # use libnss instead of libcrypto++
$ ./configure --without-radosgw # do not build radosgw and avoid libfcgi-dev
$ ./configure --without-tcmalloc # avoid google-perftools dependency
Building packages
-----------------
You can build packages for Debian or Debian-derived (e.g., Ubuntu)
systems with
$ sudo apt-get install dpkg-dev
$ dpkg-checkbuilddeps # make sure we have all dependencies
$ dpkg-buildpackage
For RPM-based systems (Redhat, Suse, etc.),
$ rpmbuild
Building the Documentation
==========================
Prerequisites
-------------
To build the documentation, you must install the following:
- python-dev
- python-pip
- python-virtualenv
- doxygen
- ditaa
- libxml2-dev
- libxslt-dev
- dot
- graphviz
For example:
sudo apt-get install python-dev python-pip python-virtualenv doxygen ditaa libxml2-dev libxslt-dev dot graphviz
Building the Documentation
--------------------------
To build the documentation, ensure that you are in the top-level `/ceph directory, and execute the build script. For example:
$ admin/build-doc
Build Prerequisites
===================
debian-based
------------
To build the source code, you must install the following:
- automake
- autoconf
- pkg-config
- gcc
- g++
- make
- libboost-dev
- libedit-dev
- libssl-dev
- libtool
- libfcgi
- libfcgi-dev
- xfslibs-dev
- libfuse-dev
- linux-kernel-headers
- libcrypto++-dev
- libaio-dev
- libgoogle-perftools-dev
- libkeyutils-dev
- uuid-dev
- libblkid-dev
- libatomic-ops-dev
- libboost-program-options-dev
- libboost-thread-dev
- libexpat1-dev
- libleveldb-dev
- libsnappy-dev
- libcurl4-gnutls-dev
- python-argparse
- python-flask
For example:
$ apt-get install automake autoconf pkg-config gcc g++ make libboost-dev libedit-dev libssl-dev libtool libfcgi libfcgi-dev xfslibs-dev libfuse-dev linux-kernel-headers libcrypto++-dev libaio-dev libgoogle-perftools-dev libkeyutils-dev uuid-dev libblkid-dev libatomic-ops-dev libboost-program-options-dev libboost-thread-dev libexpat1-dev libleveldb-dev libsnappy-dev libcurl4-gnutls-dev python-argparse python-flask
rpm-based
---------
These are the rpm packages needed to install in an rpm-based OS:
autoconf
automake
gcc
gcc-c++
make
libtool
python-argparse
python-flask
libuuid-devel
libblkid-devel
keyutils-libs-devel
cryptopp-devel
nss-devel
fcgi-devel
expat-devel
libcurl-devel
xfsprogs-devel
fuse-devel
gperftools-devel
libedit-devel
libatomic_ops-devel
snappy-devel
leveldb-devel
libaio-devel
boost-devel
For example:
$ yum install autoconf automake gcc gcc-c++ make libtool python-argparse python-flask libuuid-devel libblkid-devel keyutils-libs-devel cryptopp-devel nss-devel fcgi-devel expat-devel libcurl-devel xfsprogs-devel fuse-devel gperftools-devel libedit-devel libatomic_ops-devel snappy-devel leveldb-devel libaio-devel boost-devel