Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Kea
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
415
Issues
415
List
Boards
Labels
Service Desk
Milestones
Merge Requests
65
Merge Requests
65
Operations
Operations
Incidents
Packages & Registries
Packages & Registries
Container Registry
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
ISC Open Source Projects
Kea
Commits
56838694
Commit
56838694
authored
Dec 12, 2018
by
Marcin Siodelski
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
[#344,
!171
] Removed the section about server terminating when db conn lost.
parent
ace760ba
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
0 additions
and
30 deletions
+0
-30
doc/guide/admin.xml
doc/guide/admin.xml
+0
-30
No files found.
doc/guide/admin.xml
View file @
56838694
...
...
@@ -746,36 +746,6 @@ $ <userinput>kea-admin lease-upgrade cql -n <replaceable>database-name</replacea
</para>
</section>
<section>
<title>
Server Terminates when Database Connection is Lost
</title>
<para>
If Kea is configured to use an external database it opens a connection
to the database and requires that this connection is not interrupted.
When the database connection breaks, e.g. as a result of SQL server
restart, DHCP servers will terminate indicating a fatal error. In such
a case, the system administrator is required to start the database and
then "manually" start Kea to resume the service.
</para>
<para>
Although the engineering team is planning to implement some form of
reconnect mechanism in the future, this will mostly be applicable in
cases when the database service is restarted and the connection
down time is relatively short. The DHCP server can't provide its
service as long as the database is down, because it can't store
leases being assigned to the clients. The server will have to
reject any DHCP messages as long as the connection is down and
terminate if the reconnection attempt fails multiple times.
</para>
<para>
Because the database connection is critical for the operation of the
DHCP service, the current behavior is to terminate when that
connection is unavailable to indicate that server is in inconsistent
state and can't serve clients.
</para>
</section>
</section>
</section>
<!-- End of Database sections -->
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment