Commit 3531ee9e authored by Julien Muchembled's avatar Julien Muchembled

doc: only 1 log file per process

parent ee6e413e
...@@ -175,6 +175,15 @@ Note also that you can't mix non-SSL nodes and SSL nodes, even between a ...@@ -175,6 +175,15 @@ Note also that you can't mix non-SSL nodes and SSL nodes, even between a
upstream cluster and a backup one. In doing so, connections can get stuck, upstream cluster and a backup one. In doing so, connections can get stuck,
or fail with malformed packets or SSL handshake errors. or fail with malformed packets or SSL handshake errors.
Only 1 log file per process
---------------------------
Having multiple log file per process is not implemented yet. This limitation is
mainly visible because client configuration offers an option to specify a log
file whereas NEO events are logged in the one that's specificied last.
This is not considered an issue so far because each event in the log contains
the id & cluster of the node that emitted it.
Deployment Deployment
========== ==========
......
...@@ -34,6 +34,7 @@ ...@@ -34,6 +34,7 @@
<key name="logfile" datatype="existing-dirpath"> <key name="logfile" datatype="existing-dirpath">
<description> <description>
Log debugging information to specified SQLite DB. Log debugging information to specified SQLite DB.
Limitation: there can be only 1 log per process.
</description> </description>
</key> </key>
<key name="cache-size" datatype="byte-size" default="20MB"> <key name="cache-size" datatype="byte-size" default="20MB">
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment