From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from [87.239.111.99] (localhost [127.0.0.1]) by dev.tarantool.org (Postfix) with ESMTP id AFBC16EC5B; Sat, 10 Apr 2021 00:32:48 +0300 (MSK) DKIM-Filter: OpenDKIM Filter v2.11.0 dev.tarantool.org AFBC16EC5B DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=tarantool.org; s=dev; t=1618003968; bh=xjHEteXOiko4aXqMMUAXmJupPAWRn0E26S78imNhdjc=; h=To:Cc:References:Date:In-Reply-To:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From:Reply-To:From; b=E4KKm8rzMiDs+hEC7ac/mBFjPpigLGpfOdw/Y7RSaCx/JYZnFtrnCTSnPKTNSSc+L L8qY3ci542ZULqumSsqgBhMcb80WnhhXDIppJLt3MMGgCskmhLch5qwWMIg4wQ4a6T 6N+DCZnOB4x0rf5BLjiJqt9I2riil4XJCUrvXXKM= Received: from smtpng3.m.smailru.net (smtpng3.m.smailru.net [94.100.177.149]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dev.tarantool.org (Postfix) with ESMTPS id 84B7E6EC5B for ; Sat, 10 Apr 2021 00:32:47 +0300 (MSK) DKIM-Filter: OpenDKIM Filter v2.11.0 dev.tarantool.org 84B7E6EC5B Received: by smtpng3.m.smailru.net with esmtpa (envelope-from ) id 1lUykA-00023A-Gz; Sat, 10 Apr 2021 00:32:46 +0300 To: Serge Petrenko , Cyrill Gorcunov Cc: tarantool-patches@dev.tarantool.org References: <00c39bc5e3090383a5f0e732b5a1f32130191cf1.1617835503.git.v.shpilevoy@tarantool.org> <71ee3907-a8fd-d916-fc6a-3205e66f2d29@tarantool.org> <72609da5-e79f-dd29-c69e-77090ea06df2@tarantool.org> Message-ID: <045a7eae-595a-10c4-779e-c80272eef611@tarantool.org> Date: Fri, 9 Apr 2021 23:32:45 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.9.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-7564579A: 78E4E2B564C1792B X-77F55803: 4F1203BC0FB41BD92FFCB8E6708E748094FADAEB10E66ADA4C48BE3C291E66DA182A05F538085040887F82F396607FB3D83EECFA689767D08B57BAE7C45C40EDEB41E8CB57574BC7 X-7FA49CB5: FF5795518A3D127A4AD6D5ED66289B5278DA827A17800CE7C4A7E4C0BFE8628DEA1F7E6F0F101C67BD4B6F7A4D31EC0BCC500DACC3FED6E28638F802B75D45FF8AA50765F7900637AF78C68CB7D402738638F802B75D45FF914D58D5BE9E6BC1A93B80C6DEB9DEE97C6FB206A91F05B21B8A9C58144002125222D2007DF852C051ACFDFAE348AC99D2E47CDBA5A96583C09775C1D3CA48CFE478A468B35FE767117882F4460429724CE54428C33FAD30A8DF7F3B2552694AC26CFBAC0749D213D2E47CDBA5A9658378DA827A17800CE7D38CA8945C5827839FA2833FD35BB23DF004C906525384302BEBFE083D3B9BA73A03B725D353964B0B7D0EA88DDEDAC722CA9DD8327EE4930A3850AC1BE2E7356C9A9530EBF72002C4224003CC83647689D4C264860C145E X-C1DE0DAB: 0D63561A33F958A546BE5BD68619259125AC743790E4998501260211B541C0DAD59269BC5F550898D99A6476B3ADF6B47008B74DF8BB9EF7333BD3B22AA88B938A852937E12ACA7502E6951B79FF9A3F410CA545F18667F91A7EA1CDA0B5A7A0 X-C8649E89: 4E36BF7865823D7055A7F0CF078B5EC49A30900B95165D345DE7771146E56B08F86C034C8751A582B41AFD91791FA876910125E6ED85C498F050C8722D4B4A0C1D7E09C32AA3244CFE3E6BF06C5E6E88551003AEE9FE41B58580396430872480FACE5A9C96DEB163 X-D57D3AED: 3ZO7eAau8CL7WIMRKs4sN3D3tLDjz0dLbV79QFUyzQ2Ujvy7cMT6pYYqY16iZVKkSc3dCLJ7zSJH7+u4VD18S7Vl4ZUrpaVfd2+vE6kuoey4m4VkSEu530nj6fImhcD4MUrOEAnl0W826KZ9Q+tr5ycPtXkTV4k65bRjmOUUP8cvGozZ33TWg5HZplvhhXbhDGzqmQDTd6OAevLeAnq3Ra9uf7zvY2zzsIhlcp/Y7m53TZgf2aB4JOg4gkr2biojqcJA+pXcDunbFKhVJdtNTw== X-Mailru-Sender: 689FA8AB762F73936BC43F508A063822A59FF96B5061CB59C8696D668F32AC243841015FED1DE5223CC9A89AB576DD93FB559BB5D741EB963CF37A108A312F5C27E8A8C3839CE0E267EA787935ED9F1B X-Mras: Ok Subject: Re: [Tarantool-patches] [PATCH 1/1] applier: process synchro rows after WAL write X-BeenThere: tarantool-patches@dev.tarantool.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Tarantool development patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Vladislav Shpilevoy via Tarantool-patches Reply-To: Vladislav Shpilevoy Errors-To: tarantool-patches-bounces@dev.tarantool.org Sender: "Tarantool-patches" >> I didn't try to reproduce this craziness though. However I have an idea how >> we could fix it "for good". Introduce a fiber read-write lock. All the >> transactions take read-lock on the limbo. All CONFIRM/ROLLBACK/PROMOTE take >> a write-lock on the limbo. Then all the limbo owner transitions would be >> fixed. > > Sounds good. Isn't it enough to only have a write lock though? Perhaps. I didn't give it much thought yet. Maybe after this patch is pushed, and after you introduce PROMOTE.