Read, Write, Repeat
- The principle of reader-is-also-publisher is the basis for Cullect.
- From what I’ve seen, it take 20 years to build a successful company. I think it’d be fantastic if Cullect could have 2 decades behind it.
Cullect is 3/4 Back
Under the assumption that databases are like kidneys – I’ve turned parts of Cullect back on.
URL shortening: ON
Short URL redirects: ON (as I mentioned, some urls from last week might be broken)
Reading Lists: ON
Feed Updating: OFF until the 2nd DB comes back online later today.
Back after the Massive Database Re-import
If you’ve been following along, my 2 databases got out of sync last week.
After looking for ways to re-sync them without doing a massive re-import, I’m biting the bullet – and re-importing everything into the most-out-of-sync database.
This means, in an effort to minimize missing anything else, I’ll be down for the night again.
(including url shortening/redirecting).
I’m expecting a day or two to confirm everything is as it should be, so once I’m back, please send in bug reports – either email or @cullect on Twitter – if something’s not as it should be (recommendations not showing up, short links not redirecting where they should, etc).
I know you will.
Oh, Those Wacky DBs
Yesterday, I was getting reports of some odd behavior within Cullect. Looking into it further, it seems the two databases running Cullect are out of sync.
While URL shortening will continue to work, I won’t be updating feeds until the databases are friendly again.
Down For Maintenance Feb 11, 8pm CT
For the past couple weeks, Cullect has been far less stable, and far less snappy, than any of us would like it to be.
I diagnosed part of the problem yesterday.
Tonight, at 8pm, I’ll be taking the whole system down to push an update containing some additional diagnostic tools.
As always, thank you for your support.
Update 11:55PM
Cullect is back. Enjoy.
Cullect is Getting a Tune-up
I spent all day today reworking Cullect’s database – and as I write this – it’s being pushed to production. Like the database replication I set up a couple weeks back, this push needs to touch each of the 14 million+ records. So, it will take a bit.
Once we’re back, I’m anticipating some fairly significant performance boosts from this update.