{"id":576,"date":"2011-03-28T12:15:24","date_gmt":"2011-03-28T16:15:24","guid":{"rendered":"http:\/\/hstore.cs.brown.edu\/"},"modified":"2012-07-26T11:08:32","modified_gmt":"2012-07-26T15:08:32","slug":"debug-frontend","status":"publish","type":"page","link":"https:\/\/hstore.cs.brown.edu\/documentation\/debugging\/debug-frontend\/","title":{"rendered":"Debugging Java Frontend"},"content":{"rendered":"<p id=\"top\" \/><div class=\"prevpage\"><B>\u00ab<\/B> <a href=\"https:\/\/hstore.cs.brown.edu\/documentation\/debugging\/\" title=\"Debugging\">Debugging<\/a><\/div> <div class=\"nextpage\"><a href=\"https:\/\/hstore.cs.brown.edu\/documentation\/debugging\/debug-engine\/\" title=\"Debugging C++ Execution Engine\">Debugging C++ Execution Engine<\/a> <B>\u00bb<\/B><\/div><div style=\"clear:both;\"><\/div><\/p>\n<h2>Debugging H-Store in Eclipse<\/h2>\n<p>The following instructions will allow you to execute a single node H-Store cluster from Eclipse. Note that you must build the EE libraries first from the command-line before you can execute these commands. In this example, we will use the TPC-C benchmark that comes with H-Store.<\/p>\n<ol>\n<li>After starting Eclipse, right click on <a href=\"https:\/\/github.com\/apavlo\/h-store\/blob\/master\/src\/frontend\/edu\/brown\/hstore\/HStore.java\">HStore.java<\/a> and select <i>Debug As \u2192 Java Application<\/i>. Create a new debug configuration for <tt>HStore<\/tt> with the following parameters:\n<ul>\n<li> <b>Program Arguments:<\/b>\n<pre>catalog.jar=tpcc.jar\r\nsite.id=0\r\nconf=properties\/default.properties\r\n<\/pre>\n<\/li>\n<li> <b>VM Arguments:<\/b>\n<pre>-ea\r\n-server\r\n-Xmx2048m\r\n-Xcheck:jni\r\n-Djava.library.path=obj\/release\/nativelibs<\/pre>\n<\/li>\n<li> <b>Working Directory:<\/b> <i>File System \u2192<\/i>\n<pre>\/path\/to\/h-store<\/pre>\n<\/li>\n<\/ul>\n<\/li>\n<li>Build H-Store and create the TPC-C project catalog:\n<pre>ant <tt class=\"ant-target\">hstore-prepare<\/tt> -Dproject=tpcc -Dhosts=localhost:0:0-1<\/pre>\n<\/li>\n<\/ul>\n<li>Execute the <tt>HStore<\/tt> profile target in Eclipse. Once it prints the message &#8220;<tt>Site is ready for action<\/tt>&#8220;, it is ready for new incoming connections. You can test that the database is online by executing the following command:\n<pre>ant <tt class=\"ant-target\">hstore-invoke<\/tt> -Dproject=tpcc -Dproc=\"@NoOp\"<\/pre>\n<\/li>\n<li>You can now use H-Store&#8217;s <tt>BenchmarkController<\/tt> to load data into the database. The following command will connect to the cluster running in Eclipse, load data for the target benchmark, and then immediately exit.\n<pre>ant <tt class=\"ant-target\">hstore-benchmark<\/tt> -Dproject=tpcc -Dnosites=true -Dnoexecute=true <\/pre>\n<\/ol>\n<h3>Multi-Node Clusters:<\/h3>\n<p>You can also debug a multi-node cluster in Eclipse. In this example, we will create a two site cluster on the same machine and then launch one of the sites in Eclipse and one of the sites from the command-line. Note that the two sites do not need to be on the same machine, but for simplicity we will assume that they are.<\/p>\n<ol>\n<li>Create a two-node \/ two-site \/ two-partition cluster project jar:\n<pre>ant <tt class=\"ant-target\">hstore-prepare<\/tt> -Dproject=tpcc -Dhosts=\"localhost:0:0;localhost:1:1\"<\/pre>\n<\/li>\n<li>Start the first <tt>HStoreSite<\/tt> in Eclipse using the instructions above.<\/li>\n<li>Immediately start the second <tt>HStoreSite<\/tt> from the command-line using the following command. The <tt class=\"ant-option\">nostart<\/tt> option is a comma-separated list of the sites that should not be started by the <tt>BenchmarkController<\/tt>. This must be executed right after the first <tt>HStoreSite<\/tt> is started in Eclipse so that the two sites can find each other on the network.\n<pre>ant <tt class=\"ant-target\">hstore-benchmark<\/tt> -Dproject=tpcc -Dnoloader=true -Dnoshutdown=true -Dnostart=0<\/pre>\n<\/li>\n<li>Once the first site prints the message &#8220;<tt>Site is ready for action<\/tt>&#8221; in the Eclipse console, you can then test that the database is online by executing the following command:\n<pre>ant <tt class=\"ant-target\">hstore-invoke<\/tt> -Dproject=tpcc -Dproc=\"@NoOp\"<\/pre>\n<\/li>\n<\/ol>\n<h2>H-Store Status Thread<\/h2>\n<p>In order to better understand what each <tt>HStoreSite<\/tt> is doing at run time, you can use the <a href=\"https:\/\/github.com\/apavlo\/h-store\/blob\/master\/src\/frontend\/edu\/brown\/hstore\/HStoreSiteStatus.java\">HStoreSiteStatus<\/a> feature to print non-blocking debug information about the current status of the system. <\/p>\n<p>The functionality of <a href=\"https:\/\/github.com\/apavlo\/h-store\/blob\/master\/src\/frontend\/edu\/brown\/hstore\/HStoreSiteStatus.java\">HStoreSiteStatus<\/a> can be controlled with the following H-Store configuration parameters. The <a href=\"\/documentation\/configuration\/properties-file\/site#status_show_txn_info\" class=\"property\">site.status_show_txn_info<\/a>, <a href=\"\/documentation\/configuration\/properties-file\/site#status_show_executor_info\" class=\"property\">site.status_show_executor_info<\/a>, and <a href=\"\/documentation\/configuration\/properties-file\/site#status_show_thread_info\" class=\"property\">site.status_show_thread_info<\/a> options can be used to control the amount of information printed in each status update. Note that although this additional information does not cause the system to block, there is increased overhead for adding this throttling information.<\/p>\n<table>\n<tr>\n<td><a href=\"\/documentation\/configuration\/properties-file\/site#status_enable\" class=\"property\">site.status_enable<\/a><\/td>\n<td>If set to true, then this will enable the <a href=\"https:\/\/github.com\/apavlo\/h-store\/blob\/master\/src\/frontend\/edu\/brown\/hstore\/HStoreSiteStatus.java\">HStoreSiteStatus<\/a> thread.<\/td>\n<\/tr>\n<tr>\n<td><a href=\"\/documentation\/configuration\/properties-file\/site#status_interval\" class=\"property\">site.status_interval<\/a><\/td>\n<td>How often (in milliseconds) will the <a href=\"https:\/\/github.com\/apavlo\/h-store\/blob\/master\/src\/frontend\/edu\/brown\/hstore\/HStoreSiteStatus.java\">HStoreSiteStatus<\/a> print an update.<\/td>\n<\/tr>\n<tr>\n<td><a href=\"\/documentation\/configuration\/properties-file\/site#status_kill_if_hung\" class=\"property\">site.status_kill_if_hung<\/a><\/td>\n<td>Allow the HStoreSiteStatus thread to kill the cluster if the local HStoreSite appears to be hung.<\/td>\n<\/tr>\n<tr>\n<td><a href=\"\/documentation\/configuration\/properties-file\/site#status_show_txn_info\" class=\"property\">site.status_show_txn_info<\/a><\/td>\n<td>Print a summarization table of how transactions were executed. This includes information such as the number of transactions that were single-partitioned, multi-partitioned, speculatively executed, and committed\/aborted.<\/td>\n<\/tr>\n<tr>\n<td><a href=\"\/documentation\/configuration\/properties-file\/site#status_show_executor_info\" class=\"property\">site.status_show_executor_info<\/a><\/td>\n<td>Print information about each PartitionExecutor. This includes information such as the amount of time that the execution thread was blocked waiting for work, the average time it took to execute transactions.<\/td>\n<\/tr>\n<tr>\n<td><a href=\"\/documentation\/configuration\/properties-file\/site#status_show_thread_info\" class=\"property\">site.status_show_thread_info<\/a><\/td>\n<td>Print abbreviated stack traces for all of the threads running at a site.<\/td>\n<\/tr>\n<tr>\n<td><a href=\"\/documentation\/configuration\/properties-file\/site#status_check_for_zombies\" class=\"property\">site.status_check_for_zombies<\/a><\/td>\n<td>Allow the HStoreSiteStatus thread to check whether there any zombie transactions. This can occur if the transaction has already sent back the ClientResponse, but its internal state has not been cleaned up.<\/td>\n<\/tr>\n<\/table>\n<p>For example, the following command will execute the TM1 benchmark and have each HStoreSite in the cluster print out a summary table about transactions every 10 seconds. The table will appear in the site&#8217;s log files (<a href=\"\/documentation\/configuration\/properties-file\/site#log_dir\" class=\"property\">site.log_dir<\/a>)<\/p>\n<pre>ant <tt class=\"ant-target\">hstore-benchmark<\/tt> -Dproject=tm1 \\\r\n   -Dsite.status_enable=true \\\r\n   -Dsite.status_interval=10000 \\\r\n   -Dsite.status_show_txn_info=true<\/pre>\n<p>And example of this table is show below:<\/p>\n<pre style=\"font-size: 60%\">\r\n****************************************************************************************************************************************************************\r\n* HStoreSite Status:        H01                                                                                                                                *\r\n* Number of Partitions:     1                                                                                                                                  *\r\n* ------------------------------------------------------------------------------------------------------------------------------------------------------------ *\r\n* Completed Txns:           229955                                                                                                                             *\r\n* # of Connections:         12                                                                                                                                 *\r\n* Client Interface Queue:   190 txns [limit=1500, release=1200, bytes=13198]                                                                                   *\r\n* InFlight Txns:            53188 total \/ 270 dtxn \/ 0 finished [totalMin=0, totalMax=53188]                                                                   *\r\n* ------------------------------------------------------------------------------------------------------------------------------------------------------------ *\r\n*                           RECEIVED  REJECTED  REDIRECTED  EXECUTED | SINGLE-P  MULTI-P | COMPLETED  ABORTED  RESTARTED  MISPREDICTED | SPECULATIVE  NO-UNDO  *\r\n* @GarbageCollection:              1         -           -         2 |        -        - |         1        -          -             - |           -        -  *\r\n* @LoadMultipartitionTable:       83         -           -       166 |        -        - |        83        -          -             - |           -        -  *\r\n* @ResetProfiling:                 1         -           -         2 |        -        - |         1        -          -             - |           -        -  *\r\n* DeleteCallForwarding:        13557      9210        4248     12722 |        -       21 |        21        -        915         11733 |         915        -  *\r\n* GetAccessData:              108922      9039           -     99994 |    99916        - |     99916        -         78             - |        7507    99994  *\r\n* GetNewDestination:           30813      2586           -     28267 |    28239        - |     28239        -         28             - |        2074    28267  *\r\n* GetSubscriberData:          108661      9112           -     99641 |    99569        - |     99569        -         72             - |        7595    99641  *\r\n* InsertCallForwarding:         8947      6107        2789      8367 |        -       29 |        29        -        549          7784 |         549        -  *\r\n* UpdateLocation:              63567     43059       20115     59821 |        -      311 |       311        -       4189         55321 |        4189        -  *\r\n* UpdateSubscriberData:         3109       282           -      2830 |     2827        - |      1785     1042          3             - |         232        -  *\r\n*                           -----------------------------------------------------------------------------------------------------------------------------------*\r\n* TOTAL:                      337661     79395       27152    311812 |   230551      361 |    229955     1042       5834         74838 |       23061   227902  *\r\n*                                        0.235       0.080     0.923 |    0.998    0.002 |              0.003      0.019         0.240 |       0.100    0.731  *\r\n****************************************************************************************************************************************************************<\/pre>\n<p><div class=\"prevpage\"><B>\u00ab<\/B> <a href=\"https:\/\/hstore.cs.brown.edu\/documentation\/debugging\/\" title=\"Debugging\">Debugging<\/a><\/div> <div class=\"nextpage\"><a href=\"https:\/\/hstore.cs.brown.edu\/documentation\/debugging\/debug-engine\/\" title=\"Debugging C++ Execution Engine\">Debugging C++ Execution Engine<\/a> <B>\u00bb<\/B><\/div><div style=\"clear:both;\"><\/div><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Debugging H-Store in Eclipse The following instructions will allow you to execute a single node H-Store cluster from Eclipse. Note that you must build the EE libraries first from the command-line before you can execute these commands. In this example, we will use the TPC-C benchmark that comes with H-Store. After starting Eclipse, right click [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"parent":1725,"menu_order":1,"comment_status":"closed","ping_status":"closed","template":"","meta":[],"_links":{"self":[{"href":"https:\/\/hstore.cs.brown.edu\/wp-json\/wp\/v2\/pages\/576"}],"collection":[{"href":"https:\/\/hstore.cs.brown.edu\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/hstore.cs.brown.edu\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/hstore.cs.brown.edu\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/hstore.cs.brown.edu\/wp-json\/wp\/v2\/comments?post=576"}],"version-history":[{"count":47,"href":"https:\/\/hstore.cs.brown.edu\/wp-json\/wp\/v2\/pages\/576\/revisions"}],"predecessor-version":[{"id":1785,"href":"https:\/\/hstore.cs.brown.edu\/wp-json\/wp\/v2\/pages\/576\/revisions\/1785"}],"up":[{"embeddable":true,"href":"https:\/\/hstore.cs.brown.edu\/wp-json\/wp\/v2\/pages\/1725"}],"wp:attachment":[{"href":"https:\/\/hstore.cs.brown.edu\/wp-json\/wp\/v2\/media?parent=576"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}