From: Georgy Kirichenko <georgy@tarantool.org> To: tarantool-patches@freelists.org Cc: Konstantin Belyavskiy <k.belyavskiy@tarantool.org> Subject: [tarantool-patches] Re: [PATCH] replication: force gc to clean xdir on ENOSPC err Date: Thu, 07 Jun 2018 07:24:47 +0300 [thread overview] Message-ID: <8690646.X4a4VE2vVn@home.lan> (raw) In-Reply-To: <20180606092752.96792-1-k.belyavskiy@tarantool.org> [-- Attachment #1: Type: text/plain, Size: 1007 bytes --] On Wednesday, June 6, 2018 12:27:52 PM MSK Konstantin Belyavskiy wrote: > Garbage collector do not delete xlog unless replica do not notify > master with newer vclock. This can lead to running out of disk > space error and this is not right behaviour since it will stop the > master. > > @@ -180,8 +180,13 @@ process_rw(struct request *request, struct space > *space, struct tuple **result) * when WAL is written in autocommit mode. > */ > TupleRefNil ref(tuple); > - if (txn_commit_stmt(txn, request) != 0) > + if (txn_commit_stmt(txn, request) != 0) { 1. Here you will mark as dead as many replicas as many in-flight commiting requests you have. 2. I think you should send some message from wal thread to advance gc. In that case you will be able to use fallocate without any tx thread changes. > + struct error *e = diag_last_error(diag_get()); > + if (e != NULL && e->type == &type_ClientError && > + box_error_code(e) == ER_NO_DISK_SPACE) > + gc_leftmost_mark_dead(); > return -1; [-- Attachment #2: This is a digitally signed message part. --] [-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2018-06-07 4:24 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-06-06 9:27 [tarantool-patches] " Konstantin Belyavskiy 2018-06-07 4:24 ` Georgy Kirichenko [this message]
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=8690646.X4a4VE2vVn@home.lan \ --to=georgy@tarantool.org \ --cc=k.belyavskiy@tarantool.org \ --cc=tarantool-patches@freelists.org \ --subject='[tarantool-patches] Re: [PATCH] replication: force gc to clean xdir on ENOSPC err' \ /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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox