
Before, a really lagged cluster might not get its final report for a deleted container database sent to its corresponding account database. In such a case, the container database file would be permanently deleted while still leaving the container listed in the account database, never to be updated since the actual container database file was gone. The only way to fix such the situation before was to recreate and redelete the container. Now, the container database file will not be permanently deleted until it has sent its final report successfully to its corresponding account database. Change-Id: I1f42202455e7ecb0533b84ce7f45fcc7b98aeaa3
32 lines
1.1 KiB
Python
32 lines
1.1 KiB
Python
# Copyright (c) 2010-2012 OpenStack, LLC.
|
|
#
|
|
# Licensed under the Apache License, Version 2.0 (the "License");
|
|
# you may not use this file except in compliance with the License.
|
|
# You may obtain a copy of the License at
|
|
#
|
|
# http://www.apache.org/licenses/LICENSE-2.0
|
|
#
|
|
# Unless required by applicable law or agreed to in writing, software
|
|
# distributed under the License is distributed on an "AS IS" BASIS,
|
|
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
# implied.
|
|
# See the License for the specific language governing permissions and
|
|
# limitations under the License.
|
|
|
|
from swift.container import server as container_server
|
|
from swift.common import db, db_replicator
|
|
|
|
|
|
class ContainerReplicator(db_replicator.Replicator):
|
|
server_type = 'container'
|
|
brokerclass = db.ContainerBroker
|
|
datadir = container_server.DATADIR
|
|
default_port = 6001
|
|
|
|
def report_up_to_date(self, full_info):
|
|
for key in ('put_timestamp', 'delete_timestamp', 'object_count',
|
|
'bytes_used'):
|
|
if full_info['reported_' + key] != full_info[key]:
|
|
return False
|
|
return True
|