You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@accumulo.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2014/01/03 16:13:52 UTC

[jira] [Commented] (ACCUMULO-1743) Seeing unexpected trace output

    [ https://issues.apache.org/jira/browse/ACCUMULO-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861581#comment-13861581 ] 

ASF subversion and git services commented on ACCUMULO-1743:
-----------------------------------------------------------

Commit 51f84de0ec2435e70c37846c7f363bfce3ebca00 in branch refs/heads/1.6.0-SNAPSHOT from [~ecn]
[ https://git-wip-us.apache.org/repos/asf?p=accumulo.git;h=51f84de ]

ACCUMULO-1743 added trace check of conditional writes


> Seeing unexpected trace output
> ------------------------------
>
>                 Key: ACCUMULO-1743
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1743
>             Project: Accumulo
>          Issue Type: Bug
>          Components: trace
>            Reporter: Keith Turner
>             Fix For: 1.6.0
>
>
> While testing ACCUMULO-1608 I was seeing unexpected trace output on the monitor page.  For example I would see two prep or two wal events when I only expected to see one.  I added debug stmts on the tserver to verify that wal was only being written to once.   
> Once we figure out what is going on, need to write a trace test for conditional writer.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)