-This guess at the memleak was incorrect and extraneous. It did introduce a bug, so revert it (if DB worker memory usage does not start leaking, no further thought required
git-svn-id: https://svn.code.sf.net/p/xcat/code/xcat-core/trunk@4128 8638fb3e-16cb-4fca-ae20-7b5d299a9bcd
This commit is contained in:
parent
7925af8fa8
commit
8d7d768230
@ -1433,12 +1433,6 @@ sub _clear_cache { #PRIVATE FUNCTION TO EXPIRE CACHED DATA EXPLICITLY
|
||||
}
|
||||
#it shouldn't have been zero, but whether it was 0 or 1, ensure that the cache is gone
|
||||
$self->{_use_cache}=0; # Signal slow operation to any in-flight operations that may fail with empty cache
|
||||
if (ref $self->{_tablecache}) {
|
||||
undef %{$self->{_tablecache}};
|
||||
}
|
||||
if (ref $self->{_nodecache}) {
|
||||
undef %{$self->{_nodecache}};
|
||||
}
|
||||
undef $self->{_tablecache};
|
||||
undef $self->{_nodecache};
|
||||
}
|
||||
|
Loading…
Reference in New Issue
Block a user