From: Luis Henriques <lhenriques@suse.de>
To: Ilya Dryomov <idryomov@gmail.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: wip-msgr2
Date: Mon, 14 Dec 2020 17:26:18 +0000 [thread overview]
Message-ID: <87sg881epx.fsf@suse.de> (raw)
In-Reply-To: <CAOi1vP-U4Hdw=zYNFmhX_TJeuUiAAXMwvAUJLmG++F8mN+z5HQ@mail.gmail.com> (Ilya Dryomov's message of "Mon, 14 Dec 2020 17:59:43 +0100")
Ilya Dryomov <idryomov@gmail.com> writes:
> On Mon, Dec 14, 2020 at 4:55 PM Luis Henriques <lhenriques@suse.de> wrote:
>>
>> Ilya Dryomov <idryomov@gmail.com> writes:
>>
>> > Hello,
>> >
>> > I've pushed wip-msgr2 and opened a dummy PR in ceph-client:
>> >
>> > https://github.com/ceph/ceph-client/pull/22
>> >
>> > This set has been through a over a dozen krbd test suite runs with no
>> > issues other than those with the test suite itself. The diffstat is
>> > rather big, so I didn't want to spam the list. If someone wants it
>> > posted, let me know. Any comments are welcome!
>>
>> That's *awesome*! Thanks for sharing, Ilya. Obviously this will need a
>> lot of time to digest but a quick attempt to do a mount using a v2 monitor
>> is just showing me a bunch of:
>>
>> libceph: mon0 (1)192.168.155.1:40898 socket closed (con state V1_BANNER)
>>
>> Note that this was just me giving it a try with a dummy vstart cluster
>> (octopus IIRC), so nothing that could be considered testing. I'll try to
>> find out what I'm doing wrong in the next couple of days or, worst case,
>> after EOY vacations.
>
> Hi Luis,
>
> This is because the kernel continues to default to msgr1. The socket
> gets closed by the mon right after it sees msgr1 banner and you should
> see "peer ... is using msgr V1 protocol" error in the log.
>
> For msgr2, you need to select a connection mode using the new ms_mode
> option:
>
> ms_mode=legacy - msgr1 (default)
> ms_mode=crc - crc mode, if denied fail
> ms_mode=secure - secure mode, if denied fail
> ms_mode=prefer-crc - crc mode, if denied agree to secure mode
> ms_mode=prefer-secure - secure mode, if denied agree to crc mode
Ah, right. I should have took a quick look at the patches first to check
for any new parameters. Thanks for pointing me at that, I'll retry my
test using ms_mode.
Cheers,
--
Luis
next prev parent reply other threads:[~2020-12-14 17:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 13:43 wip-msgr2 Ilya Dryomov
2020-12-14 15:55 ` wip-msgr2 Luis Henriques
2020-12-14 16:59 ` wip-msgr2 Ilya Dryomov
2020-12-14 17:26 ` Luis Henriques [this message]
2020-12-15 13:14 ` wip-msgr2 Luis Henriques
2020-12-15 15:30 ` wip-msgr2 Ilya Dryomov
2020-12-15 16:14 ` wip-msgr2 Luis Henriques
2020-12-17 16:46 ` wip-msgr2 Luis Henriques
2020-12-17 17:25 ` wip-msgr2 Ilya Dryomov
2020-12-18 16:45 ` wip-msgr2 Luis Henriques
2020-12-16 15:31 ` wip-msgr2 Jeff Layton
2020-12-16 17:18 ` wip-msgr2 Ilya Dryomov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sg881epx.fsf@suse.de \
--to=lhenriques@suse.de \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox