On Sat, 4 Nov 2017, Kevin Hrpcek wrote:
> Hey Sage,
>
> Thanks for getting back to me this late on a weekend.
>
> Do you now why the OSDs were going down? Are there any crash dumps in the
> osd logs, or is the OOM killer getting them?
>
> That's a part I can't nail down yet. OSDs didn't
Hey Sage,
Thanks for getting back to me this late on a weekend.
Do you now why the OSDs were going down? Are there any crash dumps in the
osd logs, or is the OOM killer getting them?
That's a part I can't nail down yet. OSDs didn't crash, after the
reweight-by-utilization OSDs on some of our
Hi Kevin,
On Sat, 4 Nov 2017, Kevin Hrpcek wrote:
> Hello,
>
> I've run into an issue and would appreciate any assistance anyone can provide
> as I haven't been able to solve this problem yet
> and am running out of ideas. I ran a reweight-by-utilization on my cluster
> using conservative
Hello,
I've run into an issue and would appreciate any assistance anyone can
provide as I haven't been able to solve this problem yet and am running
out of ideas. I ran a reweight-by-utilization on my cluster using
conservative values so that it wouldn't cause a large rebalancing. The
On Sat, 2017-11-04 at 20:35 +, Bryan Henderson wrote:
> Hi. Can anyone give me a rough idea of what the monitor database is
> for?
The monitor k/v store is where we'll keep maps and other relevant data.
These maps keep the cluster state over time, and are critical for the
system to properly
OK zstd.h needs:
#define ZSTD_STATIC_LINKING_ONLY
to export that one.
Stefan
Am 04.11.2017 um 21:23 schrieb Stefan Priebe - Profihost AG:
> Thanks - not a C++ guy what's wrong with it?
>
> /build/ceph/src/compressor/zstd/ZstdCompressor.h: In member function
> 'virtual int
Hi. Can anyone give me a rough idea of what the monitor database is for? I'm
curious about how it is behaving in an experimental system I set up.
I have a single monitor and a single client that just connects once a second
and does a "status" command. There is one OSD and one MDS in there too.
Thanks - not a C++ guy what's wrong with it?
/build/ceph/src/compressor/zstd/ZstdCompressor.h: In member function
'virtual int ZstdCompressor::compress(const bufferlist&,
ceph::bufferlist&)':
/build/ceph/src/compressor/zstd/ZstdCompressor.h:48:28: error:
'ZSTD_resetCStream' was not declared in
On Sat, 4 Nov 2017, Stefan Priebe - Profihost AG wrote:
> Hi Sage,
>
> Am 26.10.2017 um 13:58 schrieb Sage Weil:
> > On Thu, 26 Oct 2017, Stefan Priebe - Profihost AG wrote:
> >> Hi Sage,
> >>
> >> Am 25.10.2017 um 21:54 schrieb Sage Weil:
> >>> On Wed, 25 Oct 2017, Stefan Priebe - Profihost AG
Hi Sage,
Am 26.10.2017 um 13:58 schrieb Sage Weil:
> On Thu, 26 Oct 2017, Stefan Priebe - Profihost AG wrote:
>> Hi Sage,
>>
>> Am 25.10.2017 um 21:54 schrieb Sage Weil:
>>> On Wed, 25 Oct 2017, Stefan Priebe - Profihost AG wrote:
Hello,
in the lumious release notes is stated that
Jon Light wrote:
I followed the instructions in the Github repo for cloning and setting
up the build environment, checked out the 12.2.0 tag, modified OSD.cc
with the fix, and then tried to build with dpkg-buildpackage. I got
the following error:
"ceph/src/kv/RocksDBStore.cc:593:22: error:
What is the new syntax for "ceph osd status" for luminous?
-Original Message-
From: I Gede Iswara Darmawan [mailto:iswaradr...@gmail.com]
Sent: donderdag 2 november 2017 6:19
To: ceph-users@lists.ceph.com
Subject: [ceph-users] No ops on some OSD
Hello,
I want to ask about my
12 matches
Mail list logo