Summary

After being notified that a long standing community member (that has been with the platform since around June 2016) can not view content that has been posed to their own channel before May (2019), I checked my own channel and it seems like I also can not access content prior to June 5th 2018. However I am aware and checked on July 2nd (due to wanting to pin an old post that refers to a blog article), and at the time all of my posts where being displayed within the channel (note that the oldest posts within my own channel should refer to around June 2017).

Therefore I am presuming that there has been some form of database corruption (or some other issue) that has occurred within the last 10 days.

I have also spoken with a number of other community members and they have all confirmed that older post are not being displayed within their own channels.

Steps to reproduce

View Channel Content

Platform information

End User Platform Neutral

What is the current bug behavior?

See Above

What is the expected correct behavior?

Old channel content should be accessible.

Relevant logs and/or screenshots

Refer to my own channel (@medworthy) to confirm the above dates and situation

Also refer to the following Help & Support enquiry

Reference:

• H&S Enquiry
  https://www.minds.com/newsfeed/996785732627431424

• My Own Channel
  https://www.minds.com/medworthy

Possible fixes

changed the description

changed the description

I am still experiencing this issue too. All my posts before May 2016 are gone and have been that way since the summer.

Just assigned

added scoped labels

assigned to @benhayward.ben

added scoped label and automatically removed label

added 1 deleted label

added 1 deleted label

unassigned @benhayward.ben

added scoped label and automatically removed label

added 1 deleted label and removed 1 deleted label

added 1 deleted label and removed 1 deleted label

added scoped label and automatically removed label

removed label

removed 1 deleted label

added scoped label

removed label

@benhayward.ben @xander-miller let's triage this please! if you need access to an old channel please message me.

added scoped label

removed label

I don't think it possible to triage further. It's likely the result of the ElasticSearch switch and misindexed, or unindexed content.

I'd very much expect the data is there, and our app just looking for it in the correct place.

added scoped labels and automatically removed label

Moving this out of triage as I don't believe we will be able to get replication steps without digging down far enough to solve the issue. Very tricky one and may require READ access to production Cassandra.