hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Masatake Iwasaki <iwasak...@oss.nttdata.co.jp>
Subject Re: HTrace
Date Thu, 06 Aug 2015 01:43:23 GMT
Hi Priyanka,

 > If both client process and server use the same file to log htraces, 
then is
 > there a possibility of corruption while writing to the span log file?

The client and server are running on the same host?
You should use different output file for each process.
It is not safe to write to the same file from multiple processes
though it is not problem to write spans from multiple threads in single 
process.

Masatake


On 8/6/15 01:56, Priyanka Bhalerao-Deshpande wrote:
 > Hi Masatake,
 >
 > I was not able to get the client traces but I can find a workaround to
 > generate those spans myself and get a graph. I had one more question
 > related to htrace.
 >
 > If both client process and server use the same file to log htraces, 
then is
 > there a possibility of corruption while writing to the span log file? 
Since
 > there will be 2 JVMs writing to the same file. In addition, our client is
 > multithreaded too. I can use synchronize on the client side and make sure
 > multiple threads write the client spans in exclusion, however there 
can be
 > a problem if a server span is being written at the same time. Let me know
 > what you recommend. Thank you.
 >
 > Best Regards,
 > Priyanka
 >
 > On Mon, Jul 27, 2015 at 10:51 AM, Masatake Iwasaki [via Apache HBase] <
 > ml-node+s679495n4073518h44@n3.nabble.com> wrote:
 >
 >>  > Thank you for getting back to me. Yes I see the Client_htrace.out
 >> getting
 >>  > created on the client node. However it is empty. We are using
 >> htrace-2.04
 >>  > version. I believe that writes the span asynchronously. Also the
 >> client node
 >>  > is running tomcat for serving requests. Would this be a problem?
 >>
 >> Hmm... Do you have multiple processes on the client?
 >> SpanReceiverHost must be initialized in each process.
 >> If you call SpanReceiverHost#getInstance in one process and
 >> call Trace#startSpan in another process,
 >> the client span is not written to file.
 >>
 >> I think running Tomcat is not related to the issue.
 >>
 >>
 >>  > Is there any need to call closeReceivers in the client side code ? I
 >> tried
 >>  > it but that did not seem to work.
 >>
 >> SpanReceiverHost#closeReceivers should be called on just before process
 >> exit
 >> but spans will be written to file immediately without that.
 >>
 >>
 >>
 >> On 7/28/15 01:47, Priyanka B wrote:
 >>  > Hi Masatake,
 >>  >
 >>  > Thank you for getting back to me. Yes I see the Client_htrace.out
 >> getting
 >>  > created on the client node. However it is empty. We are using
 >> htrace-2.04
 >>  > version. I believe that writes the span asynchronously. Also the
 >> client node
 >>  > is running tomcat for serving requests. Would this be a problem?
 >>  >
 >>  > Is there any need to call closeReceivers in the client side code ? I
 >> tried
 >>  > it but that did not seem to work.
 >>  >
 >>  >
 >>  > Thanks,
 >>  > Priyanka
 >>  >
 >>  >
 >>  >
 >>  > --
 >>  > View this message in context:
 >> http://apache-hbase.679495.n3.nabble.com/HTrace-tp4056705p4073515.html
 >>  > Sent from the HBase Developer mailing list archive at Nabble.com.
 >>
 >>
 >>
 >>
 >> ------------------------------
 >> If you reply to this email, your message will be added to the discussion
 >> below:
 >> http://apache-hbase.679495.n3.nabble.com/HTrace-tp4056705p4073518.html
 >> To unsubscribe from HTrace, click here
 >> 
<http://apache-hbase.679495.n3.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4056705&code=cHJpeWFua2EuYmhhbGVyYW9AZ21haWwuY29tfDQwNTY3MDV8LTEwODc3MjQ5NTQ=>
 >> .
 >> NAML
 >> 
<http://apache-hbase.679495.n3.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
 >>

Mime
View raw message