You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Zhao Yongming (JIRA)" <ji...@apache.org> on 2011/08/11 09:49:27 UTC

[jira] [Created] (TS-913) logging in collation client mode will report with incorrect space warning

logging in collation client mode will report with incorrect space warning
-------------------------------------------------------------------------

                 Key: TS-913
                 URL: https://issues.apache.org/jira/browse/TS-913
             Project: Traffic Server
          Issue Type: Improvement
          Components: Logging
    Affects Versions: 3.1.0
            Reporter: Zhao Yongming


when collation mode set to 2, you can get a WARNING in traffic.out when server started:
{code}
WARNING: Access logging to local log directory suspended - configured space allocation exhausted.
{code}

this is by far not the case, it should print something like:
{code}
NOTE: Access logging to local log directory suspended - remote collation is activated
{code}

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Closed] (TS-913) logging in collation client mode will report with incorrect space warning

Posted by "Zhao Yongming (Closed) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TS-913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Zhao Yongming closed TS-913.
----------------------------

    Resolution: Fixed
    
> logging in collation client mode will report with incorrect space warning
> -------------------------------------------------------------------------
>
>                 Key: TS-913
>                 URL: https://issues.apache.org/jira/browse/TS-913
>             Project: Traffic Server
>          Issue Type: Improvement
>          Components: Documentation, Logging
>    Affects Versions: 3.1.0
>            Reporter: Zhao Yongming
>            Assignee: Zhao Yongming
>             Fix For: 3.1.1
>
>
> when collation mode set to 2, you can get a WARNING in traffic.out when server started:
> {code}
> WARNING: Access logging to local log directory suspended - configured space allocation exhausted.
> {code}
> this is by far not the case, it should print something like:
> {code}
> NOTE: Access logging to local log directory suspended - remote collation is activated
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (TS-913) logging in collation client mode will report with incorrect space warning

Posted by "Zhao Yongming (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/TS-913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13083987#comment-13083987 ] 

Zhao Yongming commented on TS-913:
----------------------------------

document it:

proxy.config.log.max_space_mb_for_logs
  when works in collation client mode, if there is no local disk logging, or max_space_mb_for_orphan_logs is set to a higher value than  max_space_mb_for_logs, TS will take proxy.config.log.max_space_mb_for_orphan_logs for maximum allowed log space.


proxy.config.log.max_space_mb_for_orphan_logs
  when max_space_mb_for_orphan_logs is take as the maximum allowedlog space in the logging system, the same rule apply to proxy.config.log.max_space_mb_for_logs also apply to proxy.config.log.max_space_mb_for_orphan_logs, ie: All files in the logging directory contribute to the space used, even if they are not log files. you may need to consider this when you enable full remote logging, and bump to the same size as proxy.config.log.max_space_mb_for_logs.

> logging in collation client mode will report with incorrect space warning
> -------------------------------------------------------------------------
>
>                 Key: TS-913
>                 URL: https://issues.apache.org/jira/browse/TS-913
>             Project: Traffic Server
>          Issue Type: Improvement
>          Components: Documentation, Logging
>    Affects Versions: 3.1.0
>            Reporter: Zhao Yongming
>            Assignee: Zhao Yongming
>
> when collation mode set to 2, you can get a WARNING in traffic.out when server started:
> {code}
> WARNING: Access logging to local log directory suspended - configured space allocation exhausted.
> {code}
> this is by far not the case, it should print something like:
> {code}
> NOTE: Access logging to local log directory suspended - remote collation is activated
> {code}

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (TS-913) logging in collation client mode will report with incorrect space warning

Posted by "Zhao Yongming (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TS-913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Zhao Yongming updated TS-913:
-----------------------------

    Component/s: Documentation
       Assignee: Zhao Yongming

> logging in collation client mode will report with incorrect space warning
> -------------------------------------------------------------------------
>
>                 Key: TS-913
>                 URL: https://issues.apache.org/jira/browse/TS-913
>             Project: Traffic Server
>          Issue Type: Improvement
>          Components: Documentation, Logging
>    Affects Versions: 3.1.0
>            Reporter: Zhao Yongming
>            Assignee: Zhao Yongming
>
> when collation mode set to 2, you can get a WARNING in traffic.out when server started:
> {code}
> WARNING: Access logging to local log directory suspended - configured space allocation exhausted.
> {code}
> this is by far not the case, it should print something like:
> {code}
> NOTE: Access logging to local log directory suspended - remote collation is activated
> {code}

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (TS-913) logging in collation client mode will report with incorrect space warning

Posted by "Leif Hedstrom (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TS-913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Leif Hedstrom updated TS-913:
-----------------------------

    Fix Version/s: 3.1.1

> logging in collation client mode will report with incorrect space warning
> -------------------------------------------------------------------------
>
>                 Key: TS-913
>                 URL: https://issues.apache.org/jira/browse/TS-913
>             Project: Traffic Server
>          Issue Type: Improvement
>          Components: Documentation, Logging
>    Affects Versions: 3.1.0
>            Reporter: Zhao Yongming
>            Assignee: Zhao Yongming
>             Fix For: 3.1.1
>
>
> when collation mode set to 2, you can get a WARNING in traffic.out when server started:
> {code}
> WARNING: Access logging to local log directory suspended - configured space allocation exhausted.
> {code}
> this is by far not the case, it should print something like:
> {code}
> NOTE: Access logging to local log directory suspended - remote collation is activated
> {code}

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (TS-913) logging in collation client mode will report with incorrect space warning

Posted by "Zhao Yongming (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/TS-913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13083983#comment-13083983 ] 

Zhao Yongming commented on TS-913:
----------------------------------

after reading the code, there is nothing that we need to fix in code, but maybe in docs.

when TS try to get the max space allowed, it may take the value from proxy.config.log.max_space_mb_for_orphan_logs, it is depend on:
{code}
  use_orphan_log_space_value =
    (num_collation_clients == 0 ? false :
     (log_object_manager.get_num_objects() == num_collation_clients ? true :
      max_space_mb_for_orphan_logs > max_space_mb_for_logs));
{code}
that is a good idea, we need to update all docs regarding to proxy.config.log.max_space_mb_for_orphan_logs and proxy.config.log.max_space_mb_for_logs, to get this clear.

> logging in collation client mode will report with incorrect space warning
> -------------------------------------------------------------------------
>
>                 Key: TS-913
>                 URL: https://issues.apache.org/jira/browse/TS-913
>             Project: Traffic Server
>          Issue Type: Improvement
>          Components: Documentation, Logging
>    Affects Versions: 3.1.0
>            Reporter: Zhao Yongming
>
> when collation mode set to 2, you can get a WARNING in traffic.out when server started:
> {code}
> WARNING: Access logging to local log directory suspended - configured space allocation exhausted.
> {code}
> this is by far not the case, it should print something like:
> {code}
> NOTE: Access logging to local log directory suspended - remote collation is activated
> {code}

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira