Project

General

Profile

Bug #15319

A period commit fails on a secondary zone fails

Added by Shilpa MJ almost 8 years ago. Updated over 7 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
% Done:

0%

Source:
other
Tags:
Backport:
Regression:
No
Severity:
2 - major
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

The master zone is configured correctly. On a second zone, while trying to commit the local configuration, I hit this error:

$radosgw-admin period commit
0 Cannot find zone id= (name=), switching to local zonegroup configuration
20 zonegroup us
-1 Cannot find zone id= (name=)
couldn't init storage provider

Secondary zone, us-2 create command o/p:

{
"id": "c4d2d82e-fa38-4841-a639-add2bd108b01", -----> id created
"name": "us-2",

"Default info" field should have shown zone id.

zone list command o/p:

{
"default_info": "", -------> zone id seems to be missing?
"zones": [
"us-2",
"default"
]
}

History

#1 Updated by Shilpa MJ almost 8 years ago

Before doing a commit, here are the steps followed on rgw2.

$ radosgw-admin realm pull --url=http://rgw1:7480 --access-key=access --secret=secret
2016-03-30 08:03:35.753527 7f5ec7266900 0 error read_lastest_epoch .rgw.root:periods.cd891ca3-1d89-4e15-879c-22ae5800a0e3.latest_epoch {
"id": "ff8a0514-bffb-4e85-8d91-117ca13d81f3",
"name": "earth",
"current_period": "cd891ca3-1d89-4e15-879c-22ae5800a0e3",
"epoch": 2
}

$radosgw-admin realm default --rgw-realm=earth
$ radosgw-admin realm list {
"default_info": "ff8a0514-bffb-4e85-8d91-117ca13d81f3",
"realms": [
"earth"
]
}

$ radosgw-admin zonegroup default --rgw-zonegroup=us
ubuntu@magna062:~$ radosgw-admin zonegroup list
read_default_id : 0 {
"default_info": "8853adc8-a564-4692-a33a-a256f1fa9f47",
"zonegroups": [
"us",
"default"
]
}

$ radosgw-admin zone create --rgw-zonegroup=us --rgw-zone=us-2 --access-key=access --secret=secret --endpoints=http://rgw2:7480
2016-03-30 08:06:23.015265 7f1e6e267900 0 failed reading obj info from .rgw.root:zone_info.ccbd6a28-8d34-47a6-88ca-3ad89a77122f: (2) No such file or directory
2016-03-30 08:06:23.015291 7f1e6e267900 0 WARNING: could not read zone params for zone id=ccbd6a28-8d34-47a6-88ca-3ad89a77122f name=us-1 {
"id": "e390350c-4be2-415a-998a-736cb1b6e7b7",
"name": "us-2",
"domain_root": "us-2.rgw.data.root",
"control_pool": "us-2.rgw.control",
"gc_pool": "us-2.rgw.gc",
"log_pool": "us-2.rgw.log",
"intent_log_pool": "us-2.rgw.intent-log",
"usage_log_pool": "us-2.rgw.usage",
"user_keys_pool": "us-2.rgw.users.keys",
"user_email_pool": "us-2.rgw.users.email",
"user_swift_pool": "us-2.rgw.users.swift",
"user_uid_pool": "us-2.rgw.users.uid",
"system_key": {
"access_key": "access",
"secret_key": "secret"
},
"placement_pools": [ {
"key": "default-placement",
"val": {
"index_pool": "us-2.rgw.buckets.index",
"data_pool": "us-2.rgw.buckets.data",
"data_extra_pool": "us-2.rgw.buckets.non-ec",
"index_type": 0
}
}
],
"metadata_heap": "us-2.rgw.meta",
"realm_id": "ff8a0514-bffb-4e85-8d91-117ca13d81f3"
}

$ radosgw-admin zone list{
"default_info": "",
"zones": [
"us-2",
"default"
]
}

$ radosgw-admin period update
2016-03-30 08:07:18.377414 7f3da4c9f900 0 error read_lastest_epoch .rgw.root:periods.ff8a0514-bffb-4e85-8d91-117ca13d81f3:staging.latest_epoch {
"id": "ff8a0514-bffb-4e85-8d91-117ca13d81f3:staging",
"epoch": 1,
"predecessor_uuid": "cd891ca3-1d89-4e15-879c-22ae5800a0e3",
"sync_status": [
"",
"",
"",
],
"period_map": {
"id": "cd891ca3-1d89-4e15-879c-22ae5800a0e3",
"zonegroups": [ {
"id": "8853adc8-a564-4692-a33a-a256f1fa9f47",
"name": "us",
"api_name": "us",
"is_master": "true",
"endpoints": [
"http:\/\/rgw1:7480"
],
"hostnames": [],
"hostnames_s3website": [],
"master_zone": "ccbd6a28-8d34-47a6-88ca-3ad89a77122f",
"zones": [ {
"id": "ccbd6a28-8d34-47a6-88ca-3ad89a77122f",
"name": "us-1",
"endpoints": [
"http:\/\/rgw1:7480"
],
"log_meta": "true",
"log_data": "true",
"bucket_index_max_shards": 0,
"read_only": "false"
}, {
"id": "e390350c-4be2-415a-998a-736cb1b6e7b7",
"name": "us-2",
"endpoints": [
"http:\/\/rgw2:7480"
],
"log_meta": "false",
"log_data": "true",
"bucket_index_max_shards": 0,
"read_only": "false"
}
],
"placement_targets": [ {
"name": "default-placement",
"tags": []
}
],
"default_placement": "default-placement",
"realm_id": "ff8a0514-bffb-4e85-8d91-117ca13d81f3"
}
],
"short_zone_ids": [ {
"key": "ccbd6a28-8d34-47a6-88ca-3ad89a77122f",
"val": 246245092
}, {
"key": "e390350c-4be2-415a-998a-736cb1b6e7b7",
"val": 2445626586
}
]
},
"master_zonegroup": "8853adc8-a564-4692-a33a-a256f1fa9f47",
"master_zone": "ccbd6a28-8d34-47a6-88ca-3ad89a77122f",
"period_config": {
"bucket_quota": {
"enabled": false,
"max_size_kb": -1,
"max_objects": -1
},
"user_quota": {
"enabled": false,
"max_size_kb": -1,
"max_objects": -1
}
},
"realm_id": "ff8a0514-bffb-4e85-8d91-117ca13d81f3",
"realm_name": "earth",
"realm_epoch": 3
}

$ radosgw-admin period commit
2016-03-30 08:07:37.259490 7ff2e3642900 0 Cannot find zone id= (name=), switching to local zonegroup configuration
2016-03-30 08:07:37.261548 7ff2e3642900 -1 Cannot find zone id= (name=)
couldn't init storage provider

#2 Updated by Casey Bodley almost 8 years ago

Thanks for the extra info. I was able to reproduce this today, and confirmed that it was due to the lack of a default zone. Adding a --default argument to the 'zone create' command resolved the issue.

That said, I think there's more we can do to make this easier on admins. On zone creation, we can try setting the new zone as default, if a default does not yet exist.

#3 Updated by Abhishek Lekshmanan almost 8 years ago

Casey Bodley wrote:

Thanks for the extra info. I was able to reproduce this today, and confirmed that it was due to the lack of a default zone. Adding a --default argument to the 'zone create' command resolved the issue.

That said, I think there's more we can do to make this easier on admins. On zone creation, we can try setting the new zone as default, if a default does not yet exist.

Yeah this would be nice to have, since forgetting setting a default isn't that uncommon :)

#4 Updated by Shilpa MJ almost 8 years ago

Casey Bodley wrote:

Thanks for the extra info. I was able to reproduce this today, and confirmed that it was due to the lack of a default zone. Adding a --default argument to the 'zone create' command resolved the issue.

Great thanks! That works. I can see the sync happening now. Though, it requires a radosgw restart on the zone rgw2 as well after the period commit. It would be nice to add a message in the o/p asking users to restart.

That said, I think there's more we can do to make this easier on admins. On zone creation, we can try setting the new zone as default, if a default does not yet exist.

#5 Updated by Russell Islam almost 8 years ago

What about this error?
radosgw-admin realm pull --url=http://rgw1:7480 --access-key=access --secret=secret
2016-03-30 08:03:35.753527 7f5ec7266900 0 error read_lastest_epoch .rgw.root:periods.cd891ca3-1d89-4e15-879c-22ae5800a0e3.latest_epoch {
"id": "ff8a0514-bffb-4e85-8d91-117ca13d81f3",
"name": "earth",
"current_period": "cd891ca3-1d89-4e15-879c-22ae5800a0e3",
"epoch": 2
}

error read_lastest_epoch .rgw.root:periods.cd891ca3-1d89-4e15-879c-22ae5800a0e3.latest_epoch?

#6 Updated by Casey Bodley almost 8 years ago

Muminul Islam wrote:

What about this error?
...
error read_lastest_epoch .rgw.root:periods.cd891ca3-1d89-4e15-879c-22ae5800a0e3.latest_epoch?

That doesn't appear to be an actual failure, just an intermediate check that we should probably be hiding from the user.

#7 Updated by Russell Islam almost 8 years ago

Other errors/warning:
[root@ceph-us-west ceph-config]# radosgw-admin realm default --rgw-realm=gold
[root@ceph-us-west ceph-config]# radosgw-admin zonegroup default --rgw-zonegroup=us
[root@ceph-us-west ceph-config]# radosgw-admin zone create --rgw-zonegroup=us --rgw-zone=ceph-us-west --default --access-key=$SYSTEM_ACCESS_KEY --secret=$SYSTEM_SECRET_KEY --endpoints=http://ceph-us-west.us.oracle.com:80
2016-05-17 15:51:44.589775 7fa178770a40 0 failed reading obj info from .rgw.root:zone_info.2c33a216-4dda-4fbe-9ba4-da07daa8a63e: (2) No such file or directory
2016-05-17 15:51:44.589785 7fa178770a40 0 WARNING: could not read zone params for zone id=2c33a216-4dda-4fbe-9ba4-da07daa8a63e name=ceph-us-east-1
2016-05-17 15:51:44.590728 7fa178770a40 0 failed reading obj info from .rgw.root:zone_info.8f200dde-5d0f-4b8c-bd9b-fca1e6a63d79: (2) No such file or directory
2016-05-17 15:51:44.590734 7fa178770a40 0 WARNING: could not read zone params for zone id=8f200dde-5d0f-4b8c-bd9b-fca1e6a63d79 name=ceph-us-east-2
2016-05-17 15:51:44.591145 7fa178770a40 0 failed reading obj info from .rgw.root:zone_info.c4417b7b-35ab-4ad7-8190-17a01bc0d536: (2) No such file or directory
2016-05-17 15:51:44.591151 7fa178770a40 0 WARNING: could not read zone params for zone id=c4417b7b-35ab-4ad7-8190-17a01bc0d536 name=ceph-us-west

Is it normal behavior?

#8 Updated by Russell Islam over 7 years ago

Can we just get rid of this warning/error messages? This is annoying.

Also available in: Atom PDF