My apologies, I don't seem to be getting notifications on PRs. I'll review
this week.
Thanks,
Berant
On Mon, Mar 19, 2018 at 5:55 AM, Konstantin Shalygin wrote:
> Hi Berant
>
>
> I've created prometheus exporter that scrapes the RADOSGW Admin Ops API and
>> exports the usage information for all
ket_owner = bucket['owner']
>
> Kind regards,
>
> Ben Morrice
>
> __
> Ben Morrice | e: ben.morr...@epfl.ch | t: +41-21-693-9670
> <+41%2021%20693%2096%2070>
> EPFL / BBP
> Biotech Campus
> Chemin
Hello all,
I've created prometheus exporter that scrapes the RADOSGW Admin Ops API and
exports the usage information for all users and buckets. This is my first
prometheus exporter so if anyone has feedback I'd greatly appreciate it.
I've tested it against Hammer, and will shortly test against Jew
On Tue, May 19, 2015 at 7:13 PM, Berant Lemmenes
wrote:
> Sam,
>
> It is for a valid pool, however the up and acting sets for 2.14 both show
> OSDs 8 & 7. I'll take a look at 7 & 8 and see if they are good.
>
> If so, it seems like it being present on osd.3 could b
much for the assistance!
Berant
On Tuesday, May 19, 2015, Samuel Just wrote:
> If 2.14 is part of a non-existent pool, you should be able to rename it
> out of current/ in the osd directory to prevent the osd from seeing it on
> startup.
> -Sam
>
> - Original Message -
&
ub_stamp": "2015-05-12 22:50:16.011867",
"log_size": 3001,
"ondisk_log_size": 3001,
"stats_invalid": "0",
"stat_sum": { "num_bytes": 441982976,
&q
ues/11429. There are
> some workarounds in the bugs marked as duplicates of that bug, or you can
> wait for the next hammer point release.
> -Sam
>
> - Original Message -----
> From: "Berant Lemmenes"
> To: ceph-users@lists.ceph.com
> Sent: Monday, May 18, 20
Hello all,
I've encountered a problem when upgrading my single node home cluster from
giant to hammer, and I would greatly appreciate any insight.
I upgraded the packages like normal, then proceeded to restart the mon and
once that came back restarted the first OSD (osd.3). However it
subsequentl
Greg,
So is the consensus that the appropriate way to implement this scenario is
to have the fs created on the EC backing pool vs. the cache pool but that
the UI check needs to be tweaked to distinguish between this scenario and
just trying to use a EC pool alone?
I'm also interested in the scena
Argh, premature email sending!
On Thu, Nov 14, 2013 at 12:28 PM, Berant Lemmenes wrote:
>
> On Thu, Nov 14, 2013 at 12:11 PM, Alfredo Deza
> wrote:
>
>> This is just one of the items that caught my attention:
>>
>> 2013-10-29 15:56:03,982 [ceph11][ERRO
On Thu, Nov 14, 2013 at 12:11 PM, Alfredo Deza wrote:
>
>
> From your logs, it looks like you have a lot of errors from attempting
> to get monitors running and I can't see how/where ceph-deploy can
> be causing them. Are those errors known issues for you? Where they
> fixed or those are part of th
On Tue, Nov 12, 2013 at 7:28 PM, Joao Eduardo Luis wrote:
>
> This looks an awful lot like you started another instance of an OSD with
> the same ID while another was running. I'll walk you through the log lines
> that point me towards this conclusion. Would still be weird if the admin
> sockets
er addr is really 192.168.48.103:0/1090276439 (socket
is 192.168.48.103:41220/0)
After the 'restart ceph-osd-all' the admin sockets for all 4 OSDs on this
host are present.
Let me know if there is additional logging or assistance I can provide to
narrow it down.
Thanks,
Berant
O
I noticed the same behavior on my dumpling cluster. They wouldn't show up
after boot, but after a service restart they were there.
I haven't tested a node reboot since I upgraded to emperor today. I'll give
it a shot tomorrow.
Thanks,
Berant
On Nov 11, 2013 9:29 PM, "Peter Matulis"
wrote:
> Aft
pool than it actually does?
Thanks in advance.
Berant
On Mon, May 6, 2013 at 4:43 PM, Berant Lemmenes wrote:
> TL;DR
>
> bobtail Ceph cluster unable to finish rebalance after drive failure, usage
> increasing even with no clients connected.
>
>
> I've been running
TL;DR
bobtail Ceph cluster unable to finish rebalance after drive failure, usage
increasing even with no clients connected.
I've been running a test bobtail cluster for a couple of months and it's
been working great. Last week I had a drive die and rebalance; durring that
time another OSD cr
16 matches
Mail list logo
