Lynn Gallinat created GEODE-9445:
------------------------------------
Summary: Disk Store IDs are logged in two different formats
Key: GEODE-9445
URL: https://issues.apache.org/jira/browse/GEODE-9445
Project: Geode
Issue Type: Bug
Components: persistence
Affects Versions: 1.15.0
Reporter: Lynn Gallinat
Logging disk store IDs in two different formats might confuse users. They
should be logged consistently.
Here the disk store ID is logged with four "-" characters. This is from the
toString method in util.UUID
{noformat}
[info 2021/06/23 14:59:31.002 GMT gemfirecluster-sample-locator-0 <main>
tid=0x1] Region /_ConfigurationRegion has potentially stale data. It is waiting
for another member to recover the latest data.
My persistent id:
DiskStore ID: 0bfd6f3f-8244-4eae-8c1f-108feff87273
Name: gemfirecluster-sample-locator-0
Location: /10.208.0.26:/data/ConfigDiskDir_gemfirecluster-sample-locator-0
Members with potentially new data:
[
DiskStore ID: 4b08042e-61b7-42a8-8549-2ef0a7152284
Name: gemfirecluster-sample-locator-1
Location: /10.208.2.25:/data/ConfigDiskDir_gemfirecluster-sample-locator-1
]
{noformat}
Here the disk store Id is logged with one "-" character. This comes from the
toString method in org.apache.geode.internal.cache.DiskStoreImpl
{noformat}
[info 2021/06/23 15:00:07.251 GMT gemfirecluster-sample-locator-1 <main>
tid=0x1] Recovered disk store cluster_config with unique id
4b08042e61b742a8-85492ef0a7152284{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
