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

Posted to issues@kudu.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2016/09/02 00:29:21 UTC

[jira] [Resolved] (KUDU-1460) StartRemoteBootstrap trace can be many MB large

     [ https://issues.apache.org/jira/browse/KUDU-1460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Todd Lipcon resolved KUDU-1460.
-------------------------------
          Resolution: Fixed
       Fix Version/s: 0.9.0
    Target Version/s:   (was: 1.0.0)

> StartRemoteBootstrap trace can be many MB large
> -----------------------------------------------
>
>                 Key: KUDU-1460
>                 URL: https://issues.apache.org/jira/browse/KUDU-1460
>             Project: Kudu
>          Issue Type: Bug
>          Components: tserver
>    Affects Versions: 0.8.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>             Fix For: 0.9.0
>
>
> Currently, StartRemoteBootstrap runs the entire bootstrap process inside the RPC handler thread. This includes replaying all the operations from the log, which generate trace statements. The RPC trace is then many MB large, and it gets sampled for rpcz, holdnig memory and making /rpcz slow to load.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)