You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@mesos.apache.org by Marc Roos <M....@f1-outsourcing.eu> on 2017/12/23 00:09:40 UTC
Cannot enable the isolator volume/host_path
Dec 23 01:04:33 m01 mesos-slave[10344]: E1223 01:04:33.213044 10344
main.cpp:489] EXIT with status 1: Failed to create a containerizer:
Could not create MesosContainerizer: Failed to create isolator
'volume/host_path': Unknown or unsupported isolator
/etc/mesos-slave/isolation
filesystem/linux,docker/runtime,volume/image
http://mesos.apache.org/documentation/latest/container-volume/
Re: Persistent volume with ceph
Posted by Guang Ya Liu <gy...@gmail.com>.
My bad, I did not notice it is requesting for a Mesos solution.
Can you help check following docs to see if they can help?
1.
https://github.com/apache/mesos/blob/master/docs/isolators/docker-volume.md
2. https://github.com/codedellemc/dvdcli
3. https://github.com/thecodeteam/rexray#storage-provider-support
On Thu, Dec 28, 2017 at 11:45 AM, Guang Ya Liu <gy...@gmail.com> wrote:
> For your reference
>
> 1. https://github.com/kubernetes-incubator/external-
> storage/tree/master/ceph/rbd
> 2. https://crondev.com/kubernetes-persistent-storage-ceph/
>
> Hope this helps.
>
> On Sat, Dec 23, 2017 at 8:22 PM, Marc Roos <M....@f1-outsourcing.eu>
> wrote:
>
>>
>> Is there a recommended procedure, or has anyone experience with using
>> ceph storage as persistent volumes with a database?
>>
>> Eg. A mysql/mariadb/influxdb writing to a rbd image from a rbd ceph
>> pool?
>>
>>
>>
>>
>>
>
Re: Persistent volume with ceph
Posted by Guang Ya Liu <gy...@gmail.com>.
For your reference
1.
https://github.com/kubernetes-incubator/external-storage/tree/master/ceph/rbd
2. https://crondev.com/kubernetes-persistent-storage-ceph/
Hope this helps.
On Sat, Dec 23, 2017 at 8:22 PM, Marc Roos <M....@f1-outsourcing.eu> wrote:
>
> Is there a recommended procedure, or has anyone experience with using
> ceph storage as persistent volumes with a database?
>
> Eg. A mysql/mariadb/influxdb writing to a rbd image from a rbd ceph
> pool?
>
>
>
>
>
Local volume not getting any data
Posted by Marc Roos <M....@f1-outsourcing.eu>.
I am not getting what I am doing wrong here.
Influx is writing the data at the correct location
[marc@m02 mesos]# ls -lart
/var/lib/mesos/provisioner/containers/d481a7ad-e404-4d6e-baea-9c06a6f9f2
28/backends/copy/rootfses/fef9b89e-4be6-45df-be8f-fa367ea55648/influxdbd
ata/
total 0
drwxr-xr-x 22 root root 289 Dec 23 14:44 ..
drwxr-xr-x 4 root root 30 Dec 23 14:44 .
drwxr-xr-x 2 root root 21 Dec 23 14:44 meta
drwxr-xr-x 3 root root 23 Dec 23 14:44 data
But is should end up here not?
[marc@m02 mesos]# ls -lart
/var/lib/mesos/volumes/roles/foo/influxdb#influxdbdata#5435256f-e7e7-11e
7-88f3-0a58c0a80001/
total 0
drwxr-xr-x 3 root root 72 Dec 23 14:43 ..
drwxr-xr-x 2 root root 6 Dec 23 14:43 .
{
"id": "influxdb",
"cmd": null,
"cpus": 0.5,
"mem": 128,
"instances": 1,
"acceptedResourceRoles": ["*"],
"container": {
"type": "MESOS",
"docker": {
"image": "influxdb",
"credential": null,
"forcePullImage": false
},
"volumes": [
{
"containerPath": "influxdbdata",
"persistent": {
"type": "root",
"size": 100
},
"mode": "RW"
}
]
},
"env": {
"INFLUXDB_META_DIR": "/influxdbdata/meta",
"INFLUXDB_DATA_DIR": "/influxdbdata/data",
"INFLUXDB_REPORTING_DISABLED": "true",
"INFLUXDB_HTTP_AUTH_ENABLED": "true",
"INFLUXDB_ADMIN_ENABLED": "true",
"INFLUXDB_ADMIN_USER": "admin",
"INFLUXDB_ADMIN_PASSWORD": "xxxxx"
},
"healthChecks": [
{
"gracePeriodSeconds": 240,
"intervalSeconds": 10,
"timeoutSeconds": 10,
"maxConsecutiveFailures": 10,
"port": 8086,
"path": "/ping",
"protocol": "HTTP",
"ignoreHttp1xx": false
}
]
}
Persistent volume with ceph
Posted by Marc Roos <M....@f1-outsourcing.eu>.
Is there a recommended procedure, or has anyone experience with using
ceph storage as persistent volumes with a database?
Eg. A mysql/mariadb/influxdb writing to a rbd image from a rbd ceph
pool?
RE: Cannot enable the isolator volume/host_path
Posted by Marc Roos <M....@f1-outsourcing.eu>.
mesos-1.4.1-2.0.1.x86_64
marathon-1.4.9-1.0.668.el7.x86_64
-----Original Message-----
From: Jie Yu [mailto:yujie.jay@gmail.com]
Sent: zaterdag 23 december 2017 1:12
To: user
Subject: Re: Cannot enable the isolator volume/host_path
What's your Mesos version?
On Fri, Dec 22, 2017 at 4:09 PM, Marc Roos <M....@f1-outsourcing.eu>
wrote:
Dec 23 01:04:33 m01 mesos-slave[10344]: E1223 01:04:33.213044 10344
main.cpp:489] EXIT with status 1: Failed to create a containerizer:
Could not create MesosContainerizer: Failed to create isolator
'volume/host_path': Unknown or unsupported isolator
/etc/mesos-slave/isolation
filesystem/linux,docker/runtime,volume/image
http://mesos.apache.org/documentation/latest/container-volume/
<http://mesos.apache.org/documentation/latest/container-volume/>
Re: Cannot enable the isolator volume/host_path
Posted by Jie Yu <yu...@gmail.com>.
What's your Mesos version?
On Fri, Dec 22, 2017 at 4:09 PM, Marc Roos <M....@f1-outsourcing.eu> wrote:
>
>
> Dec 23 01:04:33 m01 mesos-slave[10344]: E1223 01:04:33.213044 10344
> main.cpp:489] EXIT with status 1: Failed to create a containerizer:
> Could not create MesosContainerizer: Failed to create isolator
> 'volume/host_path': Unknown or unsupported isolator
>
> /etc/mesos-slave/isolation
> filesystem/linux,docker/runtime,volume/image
>
> http://mesos.apache.org/documentation/latest/container-volume/
>