Re: How do ceph clients determine a monitor's address (and esp. port) for initial connection?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, May 12, 2016 at 12:42 PM, Christian Sarrasin
<c.nntp@xxxxxxxxxxxxxxxxxx> wrote:
> Thanks Greg!
>
> If I understood correctly, your suggesting this:
>
> cd /etc/ceph
> grep -v 'mon host' testcluster.conf > testcluster_client.conf
> diff testcluster.conf testcluster_client.conf
> 4d3
> < mon host = mona
> ceph -c ./testcluster_client.conf --cluster testcluster status
> no monitors specified to connect to.
> Error connecting to cluster: ObjectNotFound
>
> So this doesn't seem to work.  Any other suggestion is most welcome.

Hmm, I'm clearly not remembering how the parsing works for these, and
it's a bit messy. You may be stuck using the full IP:port instead of
host names for the "mon host" config, if it's not working without
that. :/
-Greg

>
> Cheers,
> Christian
>
>
> On 12/05/16 21:06, Gregory Farnum wrote:
>>
>> On Thu, May 12, 2016 at 6:45 AM, Christian Sarrasin
>> <c.nntp@xxxxxxxxxxxxxxxxxx> wrote:
>>>
>>> I'm trying to run monitors on a non-standard port and having trouble
>>> connecting to them.  The below shows the ceph client attempting to
>>> connect
>>> to default port 6789 rather than 6788:
>>>
>>> ceph --cluster testcluster status
>>> 2016-05-12 13:31:12.246246 7f710478c700  0 -- :/2044977896 >>
>>> 192.168.10.201:6789/0 pipe(0x7f7100067550 sd=3 :0 s=1 pgs=0 cs=0 l=1
>>> c=0x7f710005add0).fault
>>> 2016-05-12 13:31:15.247057 7f710468b700  0 -- :/2044977896 >>
>>> 192.168.10.201:6789/0 pipe(0x7f70f4000c00 sd=3 :0 s=1 pgs=0 cs=0 l=1
>>> c=0x7f70f4004ef0).fault
>>> ... etc ...
>>> ^CError connecting to cluster: InterruptedOrTimeoutError
>>>
>>> This is my embryonic config file:
>>>
>>> cat /etc/ceph/testcluster.conf
>>> [global]
>>> fsid = fef4370d-6d97-43d2-b156-57c2a0357ee2
>>> mon initial members = mona
>>> mon host = mona
>>> mon addr = 192.168.10.201:6788
>>
>>
>> This is *supposed* to work, but since it's not I bet the "mon host"
>> bit there is being used instead of the "mon addr" entry. Try clearing
>> that out from the client side.
>> -Greg
>>
>>> auth cluster required = cephx
>>> auth service required = cephx
>>> auth client required = cephx
>>> public network = 192.168.10.0/24
>>> cluster network = 192.168.10.0/24
>>> osd journal size = 100
>>>
>>> netstat shows the monitor listening on 6788 as expected.  If I regenerate
>>> the env, changing 6788 to 6789 in the above, everything works as
>>> expected.
>>>
>>> I _thought_ ceph would use the IP:port from "mon addr" but clearly I'm
>>> missing smth...
>>>
>>> This is ceph version 9.2.1 (752b6a3020c3de74e07d2a8b4c5e48dab5a6b6fd)
>>>
>>> Background: I want to run monitors for two separate clusters on the same
>>> h/w
>>> (OSDs on separate h/w).  Both clusters will run different version of ceph
>>> so
>>> I'm thinking of running mons for the 2nd cluster using docker (with
>>> --net=host to minimize overhead, hence the need to change the port).  I
>>> have
>>> used a slightly modified version of ceph-docker to deploy the above.
>>>
>>> Many thanks!
>>> Christian
>>>
>>> _______________________________________________
>>> ceph-users mailing list
>>> ceph-users@xxxxxxxxxxxxxx
>>> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
>
>
>
> _______________________________________________
> ceph-users mailing list
> ceph-users@xxxxxxxxxxxxxx
> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com



[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux