jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrei Dulceanu (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (OAK-6673) Improve cold standby logging
Date Fri, 15 Sep 2017 08:21:00 GMT

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

Andrei Dulceanu updated OAK-6673:
---------------------------------
    Description: 
With the new feature which allows chunking in blob transfer between server and client, there
are various places in which more meaningful log messages could be used. For example, on the
server, there's a tally of the no. of chunks sent/total no. of chunks, but this part is missing
on the client, i.e. no. of chunks received/total no. of chunks. 

Another case which would benefit from improved logging is when a big blob can't be sent fully
from the server to the client in {{readTimeoutMs}}. The current exception message is a bit
scarce in details (e.g. {{"Unable to load remote blob " + blobId + " at " + path + "#" + pName}}).
This could also mean that the remote blob doesn't exist on the server in the first place.
A better option would be to advise about increasing {{readTimeoutMs}}.

Finally, the same log level should be used everywhere, since currently {{DEBUG}} and {{INFO}}
are  interchangeably mixed.

/cc [~frm]

  was:
With the new feature which allows chunking in blob transfer between server and client, there
are various places in which more meaningful log messages could be used. For example, on the
server, there's a tally of the no. of chunks sent/total no. of chunks, but this part is missing
on the client, i.e. no. of chunks received/total no. of chunks. 

Another case which would benefit from improved logging is when a big blob can't be sent fully
from the server to the client in {{readTimeoutMs}}. The current exception message is a bit
scarce in details (e.g. {{"Unable to load remote blob " + blobId + " at " + path + "#" + pName}}).
This could also mean that the remote blob doesn't exist on the server in the first place.
A better option would be to advise about increasing {{readTimeoutMs}}.

Finally, the same log level should be used everywhere, since currently {{DEBUG}} and {{INFO}}
are  interchangeably mixed.


> Improve cold standby logging
> ----------------------------
>
>                 Key: OAK-6673
>                 URL: https://issues.apache.org/jira/browse/OAK-6673
>             Project: Jackrabbit Oak
>          Issue Type: Task
>          Components: segment-tar, tarmk-standby
>            Reporter: Andrei Dulceanu
>            Assignee: Andrei Dulceanu
>            Priority: Minor
>              Labels: cold-standby
>             Fix For: 1.7.8
>
>
> With the new feature which allows chunking in blob transfer between server and client,
there are various places in which more meaningful log messages could be used. For example,
on the server, there's a tally of the no. of chunks sent/total no. of chunks, but this part
is missing on the client, i.e. no. of chunks received/total no. of chunks. 
> Another case which would benefit from improved logging is when a big blob can't be sent
fully from the server to the client in {{readTimeoutMs}}. The current exception message is
a bit scarce in details (e.g. {{"Unable to load remote blob " + blobId + " at " + path + "#"
+ pName}}). This could also mean that the remote blob doesn't exist on the server in the first
place. A better option would be to advise about increasing {{readTimeoutMs}}.
> Finally, the same log level should be used everywhere, since currently {{DEBUG}} and
{{INFO}} are  interchangeably mixed.
> /cc [~frm]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message