Hi Jose,
I understand what's going in this case. Unfortunately, it's how Sedna works
by design.
Very simplified explanation. To provide ACID transactions Sedna uses
snapshots (consider this as multiple copies of the database). All
transactions work with the latests one. If Sedna determines (see upd_crt in
docs) that the current snapshot has been updated enough, it starts
checkpoint procedure - make the current snapshot stable (flash all changes
to the disc) and start a new one (and make it current).
Checkpoint procedure is the problem here. When Sedna wants to start it (and
it may happen right in the middle of your big transaction with a lot of
updates) it stops to accept any new transactions. It can be considered as a
global lock.
It can't be fixed easily. Unfortunately, I don't know if it can be fixed at
all. As a workaround, you can try to avoid very long transactions which
update significant portion of the database. For example, you can run every
DROP as a transaction. You can also try to tune value of the upd_crt
(search history of this list for discussions about upd_crt).
Ivan Shcheklein,
Sedna Team
On Tue, Apr 2, 2013 at 2:44 PM, Jose Sierra <jose.sie...@integromics.com>wrote:
> Hello Ivan.
>
> I have attached the logs with the problem.
>
> In the logs you can see several delete big files documents:
>
> --- DROP document "BOOKMARK_48597973" in collection "summary"
> --- DROP document "BOOKMARK_48597973" in collection "features"
> --- DROP document "BOOKMARK_48597973" in collection "peptides"
> --- DROP document "BOOKMARK_48597973" in collection "proteins"
>
> When these deleting process are working i try to get some new queries from
> differents collections, and the queries is not returned until the deletion
> is finished.
>
> I hope these logs help you to calrify my doubt.
>
> Best regards.
> Jose Sierra
>
>
> On 07/03/2013 14:56, Ivan Shcheklein wrote:
>
> Jose, I can't reproduce your problem exactly. Can you send us event logs?
>
>
> On Wed, Mar 6, 2013 at 8:51 PM, Jose Sierra
> <jose.sie...@integromics.com>wrote:
>
>> Hello.
>>
>> I am working with sedna 3.5.161, storing the files in different
>> collections. some of the files has a big size, and when i delete them,
>> all the other queries/transactions are locked and they don´t run even if
>> i am consulting/working with other collections. Now to delete i am using
>> the drop document in collection sentence. Exists some other way more
>> efficient to delete document or locking only the collection when i am
>> deleting the resource instead all the database?
>>
>> Best regards.
>> Jose Sierra
>>
>>
>> ------------------------------------------------------------------------------
>> Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester
>> Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the
>> endpoint security space. For insight on selecting the right partner to
>> tackle endpoint security challenges, access the full report.
>> http://p.sf.net/sfu/symantec-dev2dev
>> _______________________________________________
>> Sedna-discussion mailing list
>> Sedna-discussion@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/sedna-discussion
>>
>
>
>
------------------------------------------------------------------------------
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire
the most talented Cisco Certified professionals. Visit the
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html
_______________________________________________
Sedna-discussion mailing list
Sedna-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sedna-discussion
