Hi Giacomo, My understanding is that there are no external resources involved here. The MSSQL cluster is used for the Syncope internal storage. So the users are created directly in Syncope itself via the REST API. Does this kind of deadlock issue ring any bells for any issue fixed subsequent to 1.2.5? If not we will try to reproduce the issue locally to try to narrow the problem down.
Thanks, Colm. On Thu, Mar 17, 2016 at 1:27 PM, Giacomo Lamonaco < giacomo.lamon...@tirasa.net> wrote: > Il giorno mer, 16/03/2016 alle 15.27 +0000, Aniket Band ha scritto: > > Hello All, > > > > One of our customers uses Syncope (1.2.5) and got some performance > > issues. They want to upload 100.000 users via REST interface. They > > created 3-5 routes in parallel to call the rest interface. > > Unfortunately it requires 2 day to insert 100.000 users. As far as I > > know it should not take 2 days. The Log claims some deadlocks in the > > database. > > > > Any idea about it? In the mailing list and in JIRA I could not find > > any similar issue. > > > > Database is a MSSQL in a cluster. Thanks in advance for your inputs. > > > Hi Aniket, > > Do you have some external resources connected to Syncope? (Connected means > that every time you create an user in Syncope, that user is automatically > propagated to the external resource). > > Do you have the possibility to create users just on one MSSQL instance > (switching off the cluster)? > > It's not always a good idea to perform large 'import' using the REST > interface. You could try to perform this kind of import at a lower level, > maybe creating a dump containing those users. > > Best Regards, > > -- > Giacomo Lamonaco > > Tirasa - Open Source Excellence > http://www.tirasa.net/ > > Syncope committer > http://people.apache.org/~giacomolm > > > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
