sequoiadb-discuss

Re: [Sequoiadb-discuss] [Sequoia] Problems with sequoia in Loadtests

[Emmanuel C. <ma...@fr...>]

Hi Toni,

The Sequoia mailing list has moved to 
seq...@li....
> We are doing LoadTests of our product which is based in Sequoia + 
> mysql with 2 BE´s.
>  
> And the thing is that some SQL comands get stuck from time to time 
> spending more that 1seg to answer, I have donr a trace in MYSQL and 
> response in MYSQL is quite quickly ( 1mseg ). So, I suspect that we 
> have some problems in sequoia.
>  
> Is there any possiblity to traduce the messages from a TCPDUMP, in 
> order to see when sequoia response the the SQL sent from hibernate ?
>  
> We are working with jboss-4.0.3SP1, sequoia-2.10.10 and mysql 4.1.20 
> in a RHEL environment !
The delays you are observing might be due to retransmissions in the 
group communication. Are you using JGroups?

To sample the request arrival time, you can activate the following in 
log4j.properties:
# To trace requests #
log4j.logger.org.continuent.sequoia.controller.virtualdatabase.request=INFO, 
Requests
# To trace distributed requests #
log4j.logger.org.continuent.sequoia.controller.distributedvirtualdatabase.request=INFO, 
DistributedRequests

This will give you the request arrival time at each controller (look for 
the results in log/request.log and log/distributed_request.log).

For the request response time, the write request response times are 
logged in the recovery log. You can also use the SQLMonitoring element 
in your virtual database configuration file (look for more info in 
sequoia.dtd) to profile request execution time.

Hope this helps,
Emmanuel

-- 
Emmanuel Cecchet
FTO @ Frog Thinker 
Open Source Development & Consulting
--
Web: http://www.frogthinker.org
email: ma...@fr...
Skype: emmanuel_cecchet

Re: [Sequoiadb-discuss] [Sequoia] Problems with sequoia in Loadtests

[Emmanuel C. <ma...@fr...>]

Toni,

> The thing is that the problem only ocurrs from time to time, and when
> high load is sent,
>
> Is there any way to tune sequoia? Or monitor sequoia when high load is sent ?
>
> -which are good jvm parameters?any way to monitor jvm ?
>   
I would recommend to use jconsole 
(http://java.sun.com/developer/technicalArticles/J2SE/jconsole.html) 
that is shipped since J2SE 5 to monitor your JVM and find out if you 
have any memory problems.
> -how request caché works?
>   
Sequoia has 3 caches as described in sequoia.dtd:
"  MetadataCache: this cache improves the ResultSet creation time by keeping
   the various field information with their metadata. It is strongly 
encouraged
   to use this cache that reduces both cpu and memory usage.
  ParsingCache: allows to parse a request only once for all its executions.
   This reduces the cpu load on the controller.
  ResultCache: this cache keeps the results associated to a given request.
   Cache entries can be invalidated according to various policies. This 
cache
   reduces the load on the database backends."

I would not recommend to use the result cache if you have memory problems.
> -for last,how many queries per second can we achice ?
>
> The thing is our application works quite bad with high load, and we
> have to improve the Database access.
>   
For reads, there is no real limit for queries per second as long as you 
have enough concurrent queries and enough resources to execute them. 
Everything depends on your system setup and your workload.

Hope this helps,
Emmanuel

-- 
Emmanuel Cecchet
FTO @ Frog Thinker 
Open Source Development & Consulting
--
Web: http://www.frogthinker.org
email: ma...@fr...
Skype: emmanuel_cecchet

Re: [Sequoiadb-discuss] [Sequoia] Problems with sequoia in Loadtests

[Toni M. L. <ton...@gm...>]

Master I manage to put the SQL Monitoring, and now my surprise is even
great...


Look this a trace in MySQL :
select user0_.ID as ID19_0_, user0_.SPROLE_FK as SPROLE2_19_0_,
user0_.IAPROLE_FK as IAPROLE3_19_0_, user0_.COROLE_FK as COROLE4_19_0_,
user0_.NAME as NAME19_0_, user0_.PASSWORD as PASSWORD19_0_, user0_.ROLETYPE
as ROLETYPE19_0_, user0_.USER_FK as USER8_19_0_, user0_.EMAIL as EMAIL19_0_,
user0_.STATUS as STATUS19_0_, user0_.TRUSTED as TRUSTED19_0_,
user0_.VALIDATIONUSERID as VALIDAT12_19_0_, user0_.CMSCO as CMSCO19_0_ from
cdpdb.user user0_ where user0_.ID=21 Jun  2, 2009 10:19:17.149134000
 Jun  2, 2009 10:19:17.149185000
select roleiap0_.ID as ID16_0_, roleiap0_.USER_FK as USER2_16_0_,
roleiap0_.NAME as NAME16_0_ from cdpdb.roleiap roleiap0_ where
roleiap0_.ID=1 Jun  2, 2009 10:19:17.149605000
select itvplat0_.ID as ID9_0_, itvplat0_.NAME as NAME9_0_,
itvplat0_.BROADCAST as BROADCAST9_0_, itvplat0_.AUTHCLASS as AUTHCLASS9_0_,
itvplat0_.PUBLISHER as PUBLISHER9_0_ from cdpdb.itvplat itvplat0_ where
itvplat0_.ID=4 Jun  2, 2009 10:19:17.149856000
 Jun  2, 2009 10:19:17.149876000
 Jun  2, 2009 10:19:17.149881000
 Jun  2, 2009 10:19:17.167730000
 Jun  2, 2009 10:19:17.187738000
 Jun  2, 2009 10:19:17.188534000
 Jun  2, 2009 10:19:17.188737000
 Jun  2, 2009 10:19:17.188743000
 Jun  2, 2009 10:19:17.189901000
 Jun  2, 2009 10:19:17.189905000
select itvplat0_.ID as ID9_0_, itvplat0_.NAME as NAME9_0_,
itvplat0_.BROADCAST as BROADCAST9_0_, itvplat0_.AUTHCLASS as AUTHCLASS9_0_,
itvplat0_.PUBLISHER as PUBLISHER9_0_ from cdpdb.itvplat itvplat0_ where
itvplat0_.ID=4 Jun  2, 2009 10:19:18.030538000
 Jun  2, 2009 10:19:18.030604000
 Jun  2, 2009 10:19:18.030620000
select itvplat0_.ID as ID9_0_, itvplat0_.NAME as NAME9_0_,
itvplat0_.BROADCAST as BROADCAST9_0_, itvplat0_.AUTHCLASS as AUTHCLASS9_0_,
itvplat0_.PUBLISHER as PUBLISHER9_0_ from cdpdb.itvplat itvplat0_ where
itvplat0_.ID=4 Jun  2, 2009 10:19:18.030825000

Which it looks that between 10:19:17.149856000 and 10:19:18.030538000 we
have a gap that no selects are executed.... ( remember that LoadTests are
beeing executed so it is impossible this), but when I try to see the results
of SQLMonitoring in Sequoia we don´t have any "Max time (ms):" bigger that
50, so...

So, it seems that we have any kind of problem related to transmission or
queue or I don´t no what....

Do you know is there is any chance to monitor traffic between hibernate (
JBOSS)  and the  input of sequoia, I think that it is  in port 25322 (
controller ? ).

Anyway, now I am going to check Jconsole !

Toni.




2009/6/2 Emmanuel Cecchet <ma...@fr...>

> Toni,
>
> The thing is that the problem only ocurrs from time to time, and when
>> high load is sent,
>>
>> Is there any way to tune sequoia? Or monitor sequoia when high load is
>> sent ?
>>
>> -which are good jvm parameters?any way to monitor jvm ?
>>
>>
> I would recommend to use jconsole (
> http://java.sun.com/developer/technicalArticles/J2SE/jconsole.html) that
> is shipped since J2SE 5 to monitor your JVM and find out if you have any
> memory problems.
>
>> -how request caché works?
>>
>>
> Sequoia has 3 caches as described in sequoia.dtd:
> "  MetadataCache: this cache improves the ResultSet creation time by
> keeping
>  the various field information with their metadata. It is strongly
> encouraged
>  to use this cache that reduces both cpu and memory usage.
>  ParsingCache: allows to parse a request only once for all its executions.
>  This reduces the cpu load on the controller.
>  ResultCache: this cache keeps the results associated to a given request.
>  Cache entries can be invalidated according to various policies. This cache
>  reduces the load on the database backends."
>
> I would not recommend to use the result cache if you have memory problems.
>
>> -for last,how many queries per second can we achice ?
>>
>> The thing is our application works quite bad with high load, and we
>> have to improve the Database access.
>>
>>
> For reads, there is no real limit for queries per second as long as you
> have enough concurrent queries and enough resources to execute them.
> Everything depends on your system setup and your workload.
>
> Hope this helps,
>
> Emmanuel
>
> --
> Emmanuel Cecchet
> FTO @ Frog Thinker Open Source Development & Consulting
> --
> Web: http://www.frogthinker.org
> email: ma...@fr...
> Skype: emmanuel_cecchet
>
>

Re: [Sequoiadb-discuss] [Sequoia] Problems with sequoia in Loadtests

[Toni M. L. <ton...@gm...>]

I configured Jconsole and it seems we don´t have any problem with Memory.

After some investigation I think that we have the problem not in sequoia, we
have it in JBOSS... I will tell you....

Thanks a lot for the help,

Toni.

2009/6/2 Toni Menendez Lopez <ton...@gm...>

> Master I manage to put the SQL Monitoring, and now my surprise is even
> great...
>
>
> Look this a trace in MySQL :
> select user0_.ID as ID19_0_, user0_.SPROLE_FK as SPROLE2_19_0_,
> user0_.IAPROLE_FK as IAPROLE3_19_0_, user0_.COROLE_FK as COROLE4_19_0_,
> user0_.NAME as NAME19_0_, user0_.PASSWORD as PASSWORD19_0_, user0_.ROLETYPE
> as ROLETYPE19_0_, user0_.USER_FK as USER8_19_0_, user0_.EMAIL as EMAIL19_0_,
> user0_.STATUS as STATUS19_0_, user0_.TRUSTED as TRUSTED19_0_,
> user0_.VALIDATIONUSERID as VALIDAT12_19_0_, user0_.CMSCO as CMSCO19_0_ from
> cdpdb.user user0_ where user0_.ID=21 Jun  2, 2009 10:19:17.149134000
>  Jun  2, 2009 10:19:17.149185000
> select roleiap0_.ID as ID16_0_, roleiap0_.USER_FK as USER2_16_0_,
> roleiap0_.NAME as NAME16_0_ from cdpdb.roleiap roleiap0_ where
> roleiap0_.ID=1 Jun  2, 2009 10:19:17.149605000
> select itvplat0_.ID as ID9_0_, itvplat0_.NAME as NAME9_0_,
> itvplat0_.BROADCAST as BROADCAST9_0_, itvplat0_.AUTHCLASS as AUTHCLASS9_0_,
> itvplat0_.PUBLISHER as PUBLISHER9_0_ from cdpdb.itvplat itvplat0_ where
> itvplat0_.ID=4 Jun  2, 2009 10:19:17.149856000
>  Jun  2, 2009 10:19:17.149876000
>  Jun  2, 2009 10:19:17.149881000
>  Jun  2, 2009 10:19:17.167730000
>  Jun  2, 2009 10:19:17.187738000
>  Jun  2, 2009 10:19:17.188534000
>  Jun  2, 2009 10:19:17.188737000
>  Jun  2, 2009 10:19:17.188743000
>  Jun  2, 2009 10:19:17.189901000
>  Jun  2, 2009 10:19:17.189905000
> select itvplat0_.ID as ID9_0_, itvplat0_.NAME as NAME9_0_,
> itvplat0_.BROADCAST as BROADCAST9_0_, itvplat0_.AUTHCLASS as AUTHCLASS9_0_,
> itvplat0_.PUBLISHER as PUBLISHER9_0_ from cdpdb.itvplat itvplat0_ where
> itvplat0_.ID=4 Jun  2, 2009 10:19:18.030538000
>  Jun  2, 2009 10:19:18.030604000
>  Jun  2, 2009 10:19:18.030620000
> select itvplat0_.ID as ID9_0_, itvplat0_.NAME as NAME9_0_,
> itvplat0_.BROADCAST as BROADCAST9_0_, itvplat0_.AUTHCLASS as AUTHCLASS9_0_,
> itvplat0_.PUBLISHER as PUBLISHER9_0_ from cdpdb.itvplat itvplat0_ where
> itvplat0_.ID=4 Jun  2, 2009 10:19:18.030825000
>
> Which it looks that between 10:19:17.149856000 and 10:19:18.030538000 we
> have a gap that no selects are executed.... ( remember that LoadTests are
> beeing executed so it is impossible this), but when I try to see the results
> of SQLMonitoring in Sequoia we don´t have any "Max time (ms):" bigger that
> 50, so...
>
> So, it seems that we have any kind of problem related to transmission or
> queue or I don´t no what....
>
> Do you know is there is any chance to monitor traffic between hibernate (
> JBOSS)  and the  input of sequoia, I think that it is  in port 25322 (
> controller ? ).
>
> Anyway, now I am going to check Jconsole !
>
> Toni.
>
>
>
>
> 2009/6/2 Emmanuel Cecchet <ma...@fr...>
>
> Toni,
>>
>> The thing is that the problem only ocurrs from time to time, and when
>>> high load is sent,
>>>
>>> Is there any way to tune sequoia? Or monitor sequoia when high load is
>>> sent ?
>>>
>>> -which are good jvm parameters?any way to monitor jvm ?
>>>
>>>
>> I would recommend to use jconsole (
>> http://java.sun.com/developer/technicalArticles/J2SE/jconsole.html) that
>> is shipped since J2SE 5 to monitor your JVM and find out if you have any
>> memory problems.
>>
>>> -how request caché works?
>>>
>>>
>> Sequoia has 3 caches as described in sequoia.dtd:
>> "  MetadataCache: this cache improves the ResultSet creation time by
>> keeping
>>  the various field information with their metadata. It is strongly
>> encouraged
>>  to use this cache that reduces both cpu and memory usage.
>>  ParsingCache: allows to parse a request only once for all its executions.
>>  This reduces the cpu load on the controller.
>>  ResultCache: this cache keeps the results associated to a given request.
>>  Cache entries can be invalidated according to various policies. This
>> cache
>>  reduces the load on the database backends."
>>
>> I would not recommend to use the result cache if you have memory problems.
>>
>>
>>> -for last,how many queries per second can we achice ?
>>>
>>> The thing is our application works quite bad with high load, and we
>>> have to improve the Database access.
>>>
>>>
>> For reads, there is no real limit for queries per second as long as you
>> have enough concurrent queries and enough resources to execute them.
>> Everything depends on your system setup and your workload.
>>
>> Hope this helps,
>>
>> Emmanuel
>>
>> --
>> Emmanuel Cecchet
>> FTO @ Frog Thinker Open Source Development & Consulting
>> --
>> Web: http://www.frogthinker.org
>> email: ma...@fr...
>> Skype: emmanuel_cecchet
>>
>>
>

Re: [Sequoiadb-discuss] [Sequoia] Problems with sequoia in Loadtests

[Emmanuel C. <ma...@fr...>]

> Master
Hello young padawan :-)
> I manage to put the SQL Monitoring, and now my surprise is even great...
  The delays you see at MySQL can come from Sequoia or your application.  
> Look this a trace in MySQL :
> select user0_.ID as ID19_0_, user0_.SPROLE_FK as SPROLE2_19_0_, 
> user0_.IAPROLE_FK as IAPROLE3_19_0_, user0_.COROLE_FK as 
> COROLE4_19_0_, user0_.NAME as NAME19_0_, user0_.PASSWORD as 
> PASSWORD19_0_, user0_.ROLETYPE as ROLETYPE19_0_, user0_.USER_FK as 
> USER8_19_0_, user0_.EMAIL as EMAIL19_0_, user0_.STATUS as STATUS19_0_, 
> user0_.TRUSTED as TRUSTED19_0_, user0_.VALIDATIONUSERID as 
> VALIDAT12_19_0_, user0_.CMSCO as CMSCO19_0_ from cdpdb.user user0_ 
> where user0_.ID=21 Jun  2, 2009 10:19:17.149134000
>  Jun  2, 2009 10:19:17.149185000
> select roleiap0_.ID as ID16_0_, roleiap0_.USER_FK as USER2_16_0_, 
> roleiap0_.NAME as NAME16_0_ from cdpdb.roleiap roleiap0_ where 
> roleiap0_.ID=1 Jun  2, 2009 10:19:17.149605000
> select itvplat0_.ID as ID9_0_, itvplat0_.NAME as NAME9_0_, 
> itvplat0_.BROADCAST as BROADCAST9_0_, itvplat0_.AUTHCLASS as 
> AUTHCLASS9_0_, itvplat0_.PUBLISHER as PUBLISHER9_0_ from cdpdb.itvplat 
> itvplat0_ where itvplat0_.ID=4 Jun  2, 2009 10:19:17.149856000
>  Jun  2, 2009 10:19:17.149876000
>  Jun  2, 2009 10:19:17.149881000
>  Jun  2, 2009 10:19:17.167730000
>  Jun  2, 2009 10:19:17.187738000
>  Jun  2, 2009 10:19:17.188534000
>  Jun  2, 2009 10:19:17.188737000
>  Jun  2, 2009 10:19:17.188743000
>  Jun  2, 2009 10:19:17.189901000
>  Jun  2, 2009 10:19:17.189905000
> select itvplat0_.ID as ID9_0_, itvplat0_.NAME as NAME9_0_, 
> itvplat0_.BROADCAST as BROADCAST9_0_, itvplat0_.AUTHCLASS as 
> AUTHCLASS9_0_, itvplat0_.PUBLISHER as PUBLISHER9_0_ from cdpdb.itvplat 
> itvplat0_ where itvplat0_.ID=4 Jun  2, 2009 10:19:18.030538000
>  Jun  2, 2009 10:19:18.030604000
>  Jun  2, 2009 10:19:18.030620000
> select itvplat0_.ID as ID9_0_, itvplat0_.NAME as NAME9_0_, 
> itvplat0_.BROADCAST as BROADCAST9_0_, itvplat0_.AUTHCLASS as 
> AUTHCLASS9_0_, itvplat0_.PUBLISHER as PUBLISHER9_0_ from cdpdb.itvplat 
> itvplat0_ where itvplat0_.ID=4 Jun  2, 2009 10:19:18.030825000
>  
> Which it looks that between 10:19:17.149856000 and 10:19:18.030538000 
> we have a gap that no selects are executed.... ( remember that 
> LoadTests are beeing executed so it is impossible this), but when I 
> try to see the results of SQLMonitoring in Sequoia we don´t have any 
> "Max time (ms):" bigger that 50, so...
It might well be that the problem comes from the application.
Can you try to add some monitoring code in your application to output 
the query execution time you see in the application?
Something like:
start = System.currentTimeInMillis(); s.execute(...); end = 
System.currentTimeInMillis(); print(end-start);  
> So, it seems that we have any kind of problem related to transmission 
> or queue or I don´t no what....
>  
> Do you know is there is any chance to monitor traffic between 
> hibernate ( JBOSS)  and the  input of sequoia, I think that it is  in 
> port 25322 ( controller ? ).
You can turn the Sequoia driver in DEBUG mode if you append the option 
debugLevel=debug to the JDBC URL you give to the Sequoia driver.
You can also set the VirtualDatabaseWorkerThread logger to DEBUG in 
log4j.properties to log all the commands issued by the driver with their 
timestamp.
> Anyway, now I am going to check Jconsole !
Ok, keep me posted with your progress.

Emmanuel

-- 
Emmanuel Cecchet
FTO @ Frog Thinker 
Open Source Development & Consulting
--
Web: http://www.frogthinker.org
email: ma...@fr...
Skype: emmanuel_cecchet

Re: [Sequoiadb-discuss] [Sequoia] Problems with sequoia in Loadtests

[Toni M. L. <ton...@gm...>]

Emmanuel,

I am not able to get the recovery logs, I have done this in the
log4j.properties :

log4j.logger.org.continuent.sequoia.controller.recoverylog=INFO,
Console,Filetrace
log4j.additivity.org.continuent.sequoia.controller.recoverylog=true

Where :

# Filetrace is used for Sequoia log files, this appender is removed from the
log4j system
# if the parameter setFileLogging is set to false in the controller xml
configuration file.
log4j.appender.Filetrace=org.apache.log4j.RollingFileAppender
log4j.appender.Filetrace.File=${sequoia.log}/full_cluster.log
log4j.appender.Filetrace.MaxFileSize=10MB
log4j.appender.Filetrace.MaxBackupIndex=5
log4j.appender.Filetrace.layout=org.apache.log4j.PatternLayout
log4j.appender.Filetrace.layout.ConversionPattern=%d %-5p %c{3} %m\n
log4j.appender.Filetrace.immediateFlush=true

But I am not able to get any info related to recovery log.

Is it needed any special config ?



2009/5/29, Emmanuel Cecchet <ma...@fr...>:
>
> Hi Toni,
>
> The Sequoia mailing list has moved to
> seq...@li....
> > We are doing LoadTests of our product which is based in Sequoia +
> > mysql with 2 BE´s.
> >
> > And the thing is that some SQL comands get stuck from time to time
> > spending more that 1seg to answer, I have donr a trace in MYSQL and
> > response in MYSQL is quite quickly ( 1mseg ). So, I suspect that we
> > have some problems in sequoia.
> >
> > Is there any possiblity to traduce the messages from a TCPDUMP, in
> > order to see when sequoia response the the SQL sent from hibernate ?
> >
> > We are working with jboss-4.0.3SP1, sequoia-2.10.10 and mysql 4.1.20
> > in a RHEL environment !
> The delays you are observing might be due to retransmissions in the
> group communication. Are you using JGroups?
>
> To sample the request arrival time, you can activate the following in
> log4j.properties:
> # To trace requests #
>
> log4j.logger.org.continuent.sequoia.controller.virtualdatabase.request=INFO,
> Requests
> # To trace distributed requests #
>
> log4j.logger.org.continuent.sequoia.controller.distributedvirtualdatabase.request=INFO,
> DistributedRequests
>
> This will give you the request arrival time at each controller (look for
> the results in log/request.log and log/distributed_request.log).
>
> For the request response time, the write request response times are
> logged in the recovery log. You can also use the SQLMonitoring element
> in your virtual database configuration file (look for more info in
> sequoia.dtd) to profile request execution time.
>
> Hope this helps,
> Emmanuel
>
> --
> Emmanuel Cecchet
> FTO @ Frog Thinker
> Open Source Development & Consulting
> --
> Web: http://www.frogthinker.org
> email: ma...@fr...
> Skype: emmanuel_cecchet
>
> _______________________________________________
> Sequoia mailing list
> Se...@li...
> http://forge.continuent.org/mailman/listinfo/sequoia
>

Re: [Sequoiadb-discuss] [Sequoia] Problems with sequoia in Loadtests

[Emmanuel C. <ma...@fr...>]

Toni,
> I am not able to get the recovery logs, I have done this in the 
> log4j.properties :
The recovery log is stored in a database that you configure in your 
virtual database configuration file. You can directly look at the 
content of the table by connecting to the database or use the Sequoia 
admin console using the 'dump recoverylog' command (note that you have 
to set the debug mode to on first).

Hope this helps,
Emmanuel

-- 
Emmanuel Cecchet
FTO @ Frog Thinker 
Open Source Development & Consulting
--
Web: http://www.frogthinker.org
email: ma...@fr...
Skype: emmanuel_cecchet

Re: [Sequoiadb-discuss] [Sequoia] Problems with sequoia in Loadtests

[Toni M. L. <ton...@gm...>]

Emmanuel,

Where I have to setup the DEBUG ?

Now I have the table empty :

mysql> select * from cdpdb_logtable;
Empty set (0.00 sec)


2009/5/29, Emmanuel Cecchet <ma...@fr...>:
>
> Toni,
> > I am not able to get the recovery logs, I have done this in the
> > log4j.properties :
> The recovery log is stored in a database that you configure in your
> virtual database configuration file. You can directly look at the
> content of the table by connecting to the database or use the Sequoia
> admin console using the 'dump recoverylog' command (note that you have
> to set the debug mode to on first).
>
> Hope this helps,
> Emmanuel
>
> --
> Emmanuel Cecchet
> FTO @ Frog Thinker
> Open Source Development & Consulting
> --
> Web: http://www.frogthinker.org
> email: ma...@fr...
> Skype: emmanuel_cecchet
>
> _______________________________________________
> Sequoia mailing list
> Se...@li...
> http://forge.continuent.org/mailman/listinfo/sequoia
>

Re: [Sequoiadb-discuss] [Sequoia] Problems with sequoia in Loadtests

[Emmanuel C. <ma...@fr...>]

Toni,

When you start the Sequoia admin console, use 'admin myvdb' with your 
login and password and then use 'debug on'. You will be able to use the 
'dump recoverylog' command of the console.

Let me know if you can't get it working.
Emmanuel

>  
> Where I have to setup the DEBUG ?
>  
> Now I have the table empty :
>  
> mysql> select * from cdpdb_logtable;
> Empty set (0.00 sec)
>
>  
> 2009/5/29, Emmanuel Cecchet <ma...@fr... 
> <mailto:ma...@fr...>>:
>
>     Toni,
>     > I am not able to get the recovery logs, I have done this in the
>     > log4j.properties :
>     The recovery log is stored in a database that you configure in your
>     virtual database configuration file. You can directly look at the
>     content of the table by connecting to the database or use the Sequoia
>     admin console using the 'dump recoverylog' command (note that you have
>     to set the debug mode to on first).
>
>     Hope this helps,
>     Emmanuel
>


-- 
Emmanuel Cecchet
FTO @ Frog Thinker 
Open Source Development & Consulting
--
Web: http://www.frogthinker.org
email: ma...@fr...
Skype: emmanuel_cecchet

Re: [Sequoiadb-discuss] [Sequoia] Problems with sequoia in Loadtests

[Toni M. L. <ton...@gm...>]

No way master,

localhost:1090 > admin cdpdb
Virtual database Administrator Login > admin
Virtual database Administrator Password >
Ready to administrate virtual database cdpdb
cdpdb(admin) > debug on
Debug mode on

Now I execute some commands !!!!

cdpdb(admin) > dump recoverylog
Recovery Log is empty


2009/5/29, Emmanuel Cecchet <ma...@fr...>:
>
> Toni,
>
> When you start the Sequoia admin console, use 'admin myvdb' with your
> login and password and then use 'debug on'. You will be able to use the
> 'dump recoverylog' command of the console.
>
> Let me know if you can't get it working.
> Emmanuel
>
> >
> > Where I have to setup the DEBUG ?
> >
> > Now I have the table empty :
> >
> > mysql> select * from cdpdb_logtable;
> > Empty set (0.00 sec)
> >
> >
> > 2009/5/29, Emmanuel Cecchet <ma...@fr...
> > <mailto:ma...@fr...>>:
> >
> >     Toni,
> >     > I am not able to get the recovery logs, I have done this in the
> >     > log4j.properties :
> >     The recovery log is stored in a database that you configure in your
> >     virtual database configuration file. You can directly look at the
> >     content of the table by connecting to the database or use the Sequoia
> >     admin console using the 'dump recoverylog' command (note that you
> have
> >     to set the debug mode to on first).
> >
> >     Hope this helps,
> >     Emmanuel
> >
>
>
> --
> Emmanuel Cecchet
> FTO @ Frog Thinker
> Open Source Development & Consulting
> --
> Web: http://www.frogthinker.org
> email: ma...@fr...
> Skype: emmanuel_cecchet
>
> _______________________________________________
> Sequoia mailing list
> Se...@li...
> http://forge.continuent.org/mailman/listinfo/sequoia
>

Re: [Sequoiadb-discuss] [Sequoia] Problems with sequoia in Loadtests

[Toni M. L. <ton...@gm...>]

Emmanuel,

I get what has happenned...

The thing is that I am doing only SELECT commands, nor transactional
comands, and SELECT commands are not saved in recovery log.

Do you know how can I know the time spent in this SELECT commands...

It seems that some commands get stuck a take more that 2 segs to answer,
when we are doing LoadTests....

Toni.


2009/5/29, Toni Menendez Lopez <ton...@gm...>:
>
> No way master,
>
> localhost:1090 > admin cdpdb
> Virtual database Administrator Login > admin
> Virtual database Administrator Password >
> Ready to administrate virtual database cdpdb
> cdpdb(admin) > debug on
> Debug mode on
>
> Now I execute some commands !!!!
>
> cdpdb(admin) > dump recoverylog
> Recovery Log is empty
>
>
> 2009/5/29, Emmanuel Cecchet <ma...@fr...>:
>>
>> Toni,
>>
>> When you start the Sequoia admin console, use 'admin myvdb' with your
>> login and password and then use 'debug on'. You will be able to use the
>> 'dump recoverylog' command of the console.
>>
>> Let me know if you can't get it working.
>> Emmanuel
>>
>> >
>> > Where I have to setup the DEBUG ?
>> >
>> > Now I have the table empty :
>> >
>> > mysql> select * from cdpdb_logtable;
>> > Empty set (0.00 sec)
>> >
>> >
>> > 2009/5/29, Emmanuel Cecchet <ma...@fr...
>> > <mailto:ma...@fr...>>:
>> >
>> >     Toni,
>> >     > I am not able to get the recovery logs, I have done this in the
>> >     > log4j.properties :
>> >     The recovery log is stored in a database that you configure in your
>> >     virtual database configuration file. You can directly look at the
>> >     content of the table by connecting to the database or use the
>> Sequoia
>> >     admin console using the 'dump recoverylog' command (note that you
>> have
>> >     to set the debug mode to on first).
>> >
>> >     Hope this helps,
>> >     Emmanuel
>> >
>>
>>
>> --
>> Emmanuel Cecchet
>> FTO @ Frog Thinker
>> Open Source Development & Consulting
>> --
>> Web: http://www.frogthinker.org
>> email: ma...@fr...
>> Skype: emmanuel_cecchet
>>
>> _______________________________________________
>> Sequoia mailing list
>> Se...@li...
>> http://forge.continuent.org/mailman/listinfo/sequoia
>>
>
>

Re: [Sequoiadb-discuss] [Sequoia] Problems with sequoia in Loadtests

[Emmanuel C. <ma...@fr...>]

Toni,
> I get what has happenned...
>  
> The thing is that I am doing only SELECT commands, nor transactional 
> comands, and SELECT commands are not saved in recovery log.
>  
> Do you know how can I know the time spent in this SELECT commands...
>  
> It seems that some commands get stuck a take more that 2 segs to 
> answer, when we are doing LoadTests....
You can profile SELECT statement execution time using the SQLMonitoring 
option in your virtual database config file (see sequoia.dtd for 
details). You can dump query execution time from the Sequoia console.
Some possible causes for slow SELECTs are:
- large tuples and inappropriate JVM memory settings requiring a lot of 
garbage collecting,
- SELECT statement broadcast if the SQL has side effects that must be 
performed on every backend,
- inappropriate request cache configuration,
- missing metadata cache,
- backend failure during select,
- request invoking a stored procedure that forces a schema refresh.

Keep us posted with your findings,
Emmanuel

-- 
Emmanuel Cecchet
FTO @ Frog Thinker 
Open Source Development & Consulting
--
Web: http://www.frogthinker.org
email: ma...@fr...
Skype: emmanuel_cecchet

Re: [Sequoiadb-discuss] [Sequoia] Problems with sequoia in Loadtests

[Toni M. L. <ton...@gm...>]

Emmanuel,
The thing is that the problem only ocurrs from time to time, and when
high load is sent,

Is there any way to tune sequoia? Or monitor sequoia when high load is sent ?

-which are good jvm parameters?any way to monitor jvm ?

-how request caché works?

-for last,how many queries per second can we achice ?

The thing is our application works quite bad with high load, and we
have to improve the Database access.

Thanks again one more time..

Toni


2009/5/30, Emmanuel Cecchet <ma...@fr...>:
> Toni,
>> I get what has happenned...
>>
>> The thing is that I am doing only SELECT commands, nor transactional
>> comands, and SELECT commands are not saved in recovery log.
>>
>> Do you know how can I know the time spent in this SELECT commands...
>>
>> It seems that some commands get stuck a take more that 2 segs to
>> answer, when we are doing LoadTests....
> You can profile SELECT statement execution time using the SQLMonitoring
> option in your virtual database config file (see sequoia.dtd for
> details). You can dump query execution time from the Sequoia console.
> Some possible causes for slow SELECTs are:
> - large tuples and inappropriate JVM memory settings requiring a lot of
> garbage collecting,
> - SELECT statement broadcast if the SQL has side effects that must be
> performed on every backend,
> - inappropriate request cache configuration,
> - missing metadata cache,
> - backend failure during select,
> - request invoking a stored procedure that forces a schema refresh.
>
> Keep us posted with your findings,
> Emmanuel
>
> --
> Emmanuel Cecchet
> FTO @ Frog Thinker
> Open Source Development & Consulting
> --
> Web: http://www.frogthinker.org
> email: ma...@fr...
> Skype: emmanuel_cecchet
>
> _______________________________________________
> Sequoia mailing list
> Se...@li...
> http://forge.continuent.org/mailman/listinfo/sequoia
>