Hi Kota,
I was installing these on fresh 14.04 VMs, so I don't know how I could have
had stale apt-cache info re Stanchion, but still had up to date riak-cs
package info.
Oh well, if you couldn't reproduce it, never mind. Thanks for trying.
Cheers
Toby
On Mon, 8 Jun 2015 at 11:54 Kota Uenishi wr
Hi Matt,
This page contains the incorrect URLs:
http://docs.basho.com/riakcs/latest/cookbooks/installing/Installing-Riak-CS/
If you search on that page for this text, you'll find it right
underneath. "The resulting file should hold contents like the following"
Cheers,
Toby
On Thu, 4 Jun 2015 at
Congrats on the configure running. I will ask around concerning best practices
and get back to you tomorrow.
Is your /mnt/slow a remote mount? If so, what details can you share?
Sent from my iPhone
> On Jun 8, 2015, at 2:58 PM, Joe Olson wrote:
>
> Matthew - I got it to work. Setting the fi
Odd.
The tree builds fine, including the lock file, once the config was good:
/mnt
├── fast
│ └── leveldb
│ ├── 0
│ │ ├── CURRENT
│ │ ├── LOCK
│ │ ├── LOG
│ │ ├── MANIFEST-02
│ │ ├── sst_0
│ │ ├── sst_1
│ │ ├── sst_2
│ │
Does it require remove yz_anti_entropy directory on all nodes at same time?
Does it require to restart nodes?
On Mon, Jun 8, 2015 at 4:01 PM, Zeeshan Lakhani wrote:
> Hello Alexander,
>
> Can you send us the logs? I’d like to see the errors that occurred after
> the time of the node name chang
Joe,
I have built up your config and confirmed two bugs:
- you need the fourth config line:
leveldb.tiered = 4
leveldb.tiered.path.fast = /mnt/fast
leveldb.tiered.path.slow = /mnt/slow
leveldb.data_root = ./leveldb
- you must manually create the /mnt/fast/leveldb and /mnt/slow/leveldb
director
Matt - thanks for the support.
Adding
leveldb.data_root=“./leveldb”
results in
"IO error:
/mnt/fast/./leveldb/91343852333181432387730302044767688728495783936/LOCK: No
such file or directory"
Changing it to
leveldb.data_root=“leveldb”
results in
"IO error:
/mnt/fast/leveldb/9134385233
Joe,
Long story short, I am slowly rebuilding my debug setup. Taking longer than I
thought. I suspect, but have not yet verified, that if you add one more line:
leveldb.data_root=“./leveldb”
… your troubles will go away. If you test that before I do, let me know your
results. I will get th
Hello Alexander,
Can you send us the logs? I’d like to see the errors that occurred after the
time of the node name change.
In terms of getting your data back into the indexes, I’d recommend letting AAE
handle the situation by removing the `yz_anti_entropy` directory and letting
the keys re-in
I was perform all nodes upgrade in x6 nodes cluster
and at same time 4 of them was prooceed with node name changed by steps:
http://docs.basho.com/riak/latest/ops/running/recovery/failed-node/#Node-Name-Changed
after that search indexes becomes completely broken - many data missed,
returns diff
10 matches
Mail list logo
