summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* testing: still working on the terasort testwip-buck-add-terasortJoe Buck2013-05-021-8/+8
| | | | Signed-off-by: Joe Buck <jbbuck@gmail.com>
* testing: still tweakingJoe Buck2013-05-021-12/+7
| | | | Signed-off-by: Joe Buck <jbbuck@gmail.com>
* testing: furhter work on terasort testJoe Buck2013-05-021-3/+7
| | | | Signed-off-by: Joe Buck <jbbuck@gmail.com>
* testing: tweaking the terasort testJoe Buck2013-05-021-1/+1
| | | | Signed-off-by: Joe Buck <jbbuck@gmail.com>
* testing: adding a Terasort test for HadoopJoe Buck2013-05-021-0/+40
|
* doc/install/upgrading...: note that argonaut->bobtail->cuttlefish must be ↵Sage Weil2013-05-021-12/+13
| | | | | | | | v0.56.5 Which will be released shortly. Signed-off-by: Sage Weil <sage@inktank.com>
* Merge pull request #251 from bkerensa/patch-1Sage Weil2013-05-021-3/+3
|\ | | | | | | | | Improve verbiage Signed-off-by: Benjamin Kerensa <bkerensa@ubuntu.com>
| * Update debian.rstBenjamin Kerensa2013-05-021-3/+3
| | | | | | "complete list of distributions" should be complete list of releases since we already know what distributions are supported and the list specifies releases. (Wheezy, Precise etc.)
* | doc/install/upgrading...: note about transitioning to ceph-deploySage Weil2013-05-021-0/+13
| | | | | | | | Signed-off-by: Sage Weil <sage@inktank.com>
* | doc/release-notes: note about ceph-deploySage Weil2013-05-021-0/+14
|/ | | | Signed-off-by: Sage Weil <sage@inktank.com>
* Merge branch 'next'Sage Weil2013-05-0110-107/+433
|\
| * Merge remote-tracking branch 'gh/wip-doc-cuttlefish' into nextSage Weil2013-05-011-92/+202
| |\
| | * doc: Incorporating Tamil's feedback.John Wilkins2013-04-301-6/+15
| | | | | | | | | | | | Signed-off-by: John Wilkins <john.wilkins@inktank.com>
| | * doc: Reordered header levels for visual clarity.John Wilkins2013-04-301-15/+11
| | | | | | | | | | | | Signed-off-by: John Wilkins <john.wilkins@inktank.com>
| | * doc: Fixed a few typos.John Wilkins2013-04-301-2/+2
| | | | | | | | | | | | Signed-off-by: John Wilkins <john.wilkins@inktank.com>
| | * doc: Updated the upgrade guide for Aronaut and Bobtail to Cuttlefish.John Wilkins2013-04-301-92/+197
| | | | | | | | | | | | | | | | | | fixes: #4874 Signed-off-by: John Wilkins <john.wilkins@inktank.com>
| * | Merge remote-tracking branch 'upstream/wip_4884' into nextSamuel Just2013-05-012-5/+32
| |\ \ | | | | | | | | | | | | | | | | Fixes: #4884 Reviewed-by: Greg Farnum <greg@inktank.com>
| | * | OSD: load_pgs() should fill in start_split honestlySamuel Just2013-05-011-5/+25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In load_pgs(), we previously called assigned children starting at the loaded pg created between its stored epoch and the current osdmap to have that pg as their parent. This is not correct, some of the children may have been split in subsequent epochs from children split in earlier epochs. Instead, do each map individually. Signed-off-by: Samuel Just <sam.just@inktank.com>
| | * | OSD: cancel_pending_splits needs to cancel all descendantsSamuel Just2013-05-012-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | expand_pg_num() and load_pgs() may result in a pg with children in pending_splits which also have children in pending_splits (etc). Signed-off-by: Samuel Just <sam.just@inktank.com>
| * | | Makefile,gitignore: ceph-monstore-tool, not ceph_monstore_toolSamuel Just2013-05-012-2/+2
| | | | | | | | | | | | | | | | Signed-off-by: Samuel Just <sam.just@inktank.com>
| * | | Makefile: put ceph_monstore_tool in bin_DEBUGPROGRAMSSamuel Just2013-05-011-1/+1
| | | | | | | | | | | | | | | | Signed-off-by: Samuel Just <sam.just@inktank.com>
| * | | tools: ceph-osdomap-tool.ccSamuel Just2013-05-015-0/+179
| |/ / | | | | | | | | | | | | | | | Add tool for dumping info from osd omap. Signed-off-by: Samuel Just <sam.just@inktank.com>
| * | dumper: fix Objecter lockingGreg Farnum2013-05-012-8/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Locking expectations changed at some point, and the Dumper wasn't updated to comply: 1) We need to take the lock for Objecter, as it doesn't do so on its own any more. 2) We need to drop the lock in several places so that Objecter can take delivery of messages Signed-off-by: Greg Farnum <greg@inktank.com> Reviewed-by: Sage Weil <sage@inktank.com>
* | | Merge remote-tracking branch 'gh/next'Sage Weil2013-05-0119-153/+357
|\ \ \ | |/ /
| * | Revert "PaxosService: use get and put for version_t"Sage Weil2013-05-011-2/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This reverts commit e725c3e210b244e090d70c77d937c94f4f63a2be. These inadvertantely got rid of the prefix portion of the key, which lead to overwriting the wrong keys. Fixes: #4872 Signed-off-by: Sage Weil <sage@inktank.com> Reviewed-by: Samuel Just <sam.just@inktank.com>
| * | mon/Paxos: update first_committed when we trimSage Weil2013-05-011-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The Paxos::trim() -> ::trim_to() path trims old states but does not update first_committed. This misinforms later paxos rounds such that peers think they can participate and end up with COMMIT messages following the COLLECT/LAST exchange that are for future commits they can't do anything with and then crash out when they get the BEGIN: mon/Paxos.cc: 557: FAILED assert(begin->last_committed == last_committed) Fixes: #4879 Signed-off-by: Sage Weil <sage@inktank.com> Reviewed-by: Greg Farnum <greg@inktank.com>
| * | mon/Paxos: don't ignore peer first_committedSage Weil2013-05-012-4/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We go to the effort of keeping a map of the peer's first/last committed so that we can send the right commits during the first phase of paxos, but we forgot to record the first value. This appears to simply be an oversight. It is mostly harmless; it just means we send extra states that the peer already has. Signed-off-by: Sage Weil <sage@inktank.com> Reviewed-by: Greg Farnum <greg@inktank.com>
| * | OSD: clean up in progress split state on pg removalSamuel Just2013-05-012-21/+95
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | There are two cases: 1) The parent pg has not yet initiated the split 2) The parent pg has initiated the split. Previously in case 1), _remove_pg left the entry for its children in the in_progress_splits map blocking subsequent peering attempts. In case 1), we need to unblock requests on the child pgs for the parent on parent removal. We don't need to bother waking requests since any requests received prior to the remove_pg request are necessarily obsolete. In case 2), we don't need to do anything: the child will complete the split on its own anyway. Thus, we now track pending_splits vs in_progress_splits. Children in pending_splits are in state 1), in_progress_splits in state 2). split_pgs bumps pgs from pending_splits to in_progress_splits atomically with respect to _remove_pg since the parent pg lock is held in both places. Fixes: #4813 Signed-off-by: Samuel Just <sam.just@inktank.com> Reviewed-by: Greg Farnum <greg@inktank.com>
| * | mon: communicate the quorum_features properly when declaring victory.Greg Farnum2013-04-301-0/+1
| |/ | | | | | | | | | | | | Fixes #4747. Signed-off-by: Greg Farnum <greg@inktank.com> Reviewed-by: Sage Weil <sage@inktank.com>
| * Merge branch 'wip-4837-election-syncing' into nextGreg Farnum2013-04-304-58/+43
| |\ | | | | | | | | | Reviewed-by: Sage Weil <sage@inktank.com>
| | * mon: Monitor: disregard paxos_max_join_drift when deciding whether to syncJoao Eduardo Luis2013-04-301-4/+3
| | | | | | | | | | | | | | | | | | | | | We should only rely on whether our paxos version is overlap with whatever they have -- we'll catch up later with them. Signed-off-by: Joao Eduardo Luis <joao.luis@inktank.com>
| | * mon: if we get our own sync_start back, drop it on the floor.Greg Farnum2013-04-301-7/+14
| | | | | | | | | | | | | | | | | | | | | | | | We have timeouts that will clean everything up, and this can happen in some cases that we've decided are legitimate. Hopefully we'll be able to do something else later. Signed-off-by: Greg Farnum <greg@inktank.com>
| | * Revert "mon: update assert for looser requirements"Greg Farnum2013-04-301-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | We reverted the gating by paxos sequences, so now we don't need to look at them at all. This reverts commit 1e6f02b337767012aeb387da9582cd7ad5a03084. Signed-off-by: Greg Farnum <greg@inktank.com>
| | * Revert "mon: when electing, be sure acked leaders have new enough stores to ↵Greg Farnum2013-04-303-46/+25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | lead" This was somehow broken -- out-of-date leaders were being elected -- and we've decided smaller band-aids are more appropriate. We don't completely revert the MMonElection changes, though -- there have been user clusters running the code which includes these messages so we can't pretend it never happened. We can make them clearly unused in the code, though. This reverts commit fcaabf1a22723c571c10d402464071c6405607c0. Signed-off-by: Greg Farnum <greg@inktank.com>
| * | ceph-disk: tolerate /sbin/service or /usr/sbin/serviceSage Weil2013-04-301-1/+5
| | | | | | | | | | | | | | | | | | | | | CentOS/RH has it in /sbin, others in /usr/sbin. Backport: bobtail Signed-off-by: Sage Weil <sage@inktank.com>
| * | ObjectCacher: wait for all reads when stopping flusherJosh Durgin2013-04-302-2/+23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Stopping the flusher is essentially the shutdown step for the ObjectCacher - the next thing is actually destroying it. If we leave any reads outstanding, when they complete they will attempt to use the now-destroyed ObjectCacher. This is particularly a problem with rbd images, since an -ENOENT can instantly complete many readers, so the upper layers don't wait for the other rados-level reads of that object to finish before trying to shutdown the cache. Signed-off-by: Josh Durgin <josh.durgin@inktank.com> Reviewed-by: Sage Weil <sage@inktank.com>
| * | Merge branch 'wip-mon-compact' into nextSage Weil2013-04-307-3/+76
| |\ \ | | |/ | |/| | | | Reviewed-by: Samuel Just <sam.just@inktank.com>
| | * mon: enable 'mon compact on trim' by default; trim in larger incrementsSage Weil2013-04-291-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This resolves the leveldb growth-without-bound problem observed by mikedawson, and all the badness that stems from it. Enable this by default until we figure out why leveldb is not behaving better. While we are at it, trim more states at a time. This will make compaction less frequent, which should help given that there is some overhead unrelated to the amount of deleted data. Fixes: #4815 Signed-off-by: Sage Weil <sage@inktank.com>
| | * mon/Paxos: compact on trimSage Weil2013-04-291-0/+4
| | | | | | | | | | | | | | | | | | Compact the paxos keys when we trim old paxos states. Signed-off-by: Sage Weil <sage@inktank.com>
| | * mon: compact PaxosService prefix on trimSage Weil2013-04-292-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Each time we trim a PaxosService, have leveldb compact so that the space from removed states is reclaimed. This is probably not optimal if leveldb's heuristics are doing the right thing, but it currently appears as if they are not. Signed-off-by: Sage Weil <sage@inktank.com>
| | * mon: add compact_prefix transaction operationSage Weil2013-04-291-1/+27
| | | | | | | | | | | | | | | | | | | | | Add a prefix compaction opteration to the transaction that will be performed after the transaction applies. Signed-off-by: Sage Weil <sage@inktank.com>
| | * leveldb: add compact_prefix methodSage Weil2013-04-291-0/+11
| | | | | | | | | | | | Signed-off-by: Sage Weil <sage@inktank.com>
| | * mon: compact leveldb on bootstrapSage Weil2013-04-291-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is an opportunistic time to optimize our local data since we are out of quorum. It serves as a safety net for cases where leveldb's automatic compaction doesn't work quite right and lets things get out of hand. Anecdotally we have seen stores in excess of 30GB compact down to a few hundred KB. And a 9GB store compact down to 900MB in only 1 minute. Signed-off-by: Sage Weil <sage@inktank.com>
| | * mon: compact leveldb on bootstrapSage Weil2013-04-292-0/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is an opportunistic time to optimize our local data since we are out of quorum. It serves as a safety net for cases where leveldb's automatic compaction doesn't work quite right and lets things get out of hand. Anecdotally we have seen stores in excess of 30GB compact down to a few hundred KB. And a 9GB store compact down to 900MB in only 1 minute. Signed-off-by: Sage Weil <sage@inktank.com>
| | * mon: --compact argument, config option to compact the store on startSage Weil2013-04-292-0/+10
| | | | | | | | | | | | Signed-off-by: Sage Weil <sage@inktank.com>
| | * leveldb: add compact() methodSage Weil2013-04-292-0/+9
| | | | | | | | | | | | | | | | | | This will compact the entire store; it will be slow! Signed-off-by: Sage Weil <sage@inktank.com>
| * | elector: trigger a mon reset whenever we bump the epochGreg Farnum2013-04-301-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We need to call reset during every election cycle; luckily we can call it more than once. bump_epoch is (by definition!) only called once per cycle, and it's called at the beginning, so we put it there. Fixes #4858. Signed-off-by: Greg Farnum <greg@inktank.com> Reviewed-by: Sage Weil <sage@inktank.com>
| * | Merge branch 'wip-2209' into nextDavid Zafman2013-04-304-61/+95
| |\ \ | | | | | | | | | | | | Reviewed-by: Samuel Just <sam.just@inktank.com>
| | * | Set num_rd, num_wr_kb and num_wr in various places that needed itDavid Zafman2013-04-291-2/+27
| | | | | | | | | | | | | | | | Signed-off-by: David Zafman <david.zafman@inktank.com>
| | * | osd: read kb stats not tracked?David Zafman2013-04-293-0/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In read cases track stats in PG::unstable_stats Include unstable_stats in write_info() and publish_stats_to_osd() For now this information may not get persisted fixes: #2209 Signed-off-by: David Zafman <david.zafman@inktank.com>
View Lorry Controller Status