[
https://issues.apache.org/jira/browse/TS-170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12833238#action_12833238
]
John Plevyak commented on TS-170:
---------------------------------
The problem is that this hostdb uses the baker half-space GC algorithm, so the
space is not actually
reclaimed and available till after GC has completed. This means that the most
effective place to
delete the entries is just before GC so that the space will be available as
soon as it get's done.
This thing really needs to be redesigned as this heap was bolted on (by me) and
the whole
thing is just too complicated for what it does.
> hostdb cores in reply_to_cont() when running out of space
> ---------------------------------------------------------
>
> Key: TS-170
> URL: https://issues.apache.org/jira/browse/TS-170
> Project: Traffic Server
> Issue Type: Bug
> Reporter: Bryan Call
> Assignee: Bryan Call
> Priority: Critical
> Fix For: 2.0.0a
>
> Attachments: hostdb_bcall_001.diff
>
>
> In HostDBContinuation::lookup_done() if we can't allocate memory in the cache
> we will free some space (delete_block())
> and then return a NULL. Also, the error message "out of room in hostdb for
> reverse DNS data" gets printed
> out.
> This NULL pointer will be dereferenced later when we call reply_to_cont().
> bz 3191464
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
