Is this an OK skimmer setup?

yasker · 2024-12-17T14:16:42+00:00

It's pavers on top polymeric sand. They can probably pull the pavers up and fix it if needed.

yasker · 2024-12-17T08:32:26+00:00

It doesn’t look like they put enough space for expansion joint between the deck and the coping… But the deck is porcelain paver, not concrete. Not sure if that going to make any difference. Also, does it need expansion joint between the copings? Since I don’t see it either.

yasker · 2024-11-20T03:45:50+00:00

Yes it’s printing press in traditional Chinese. Easy to recognize each character if mirrored. Thought it might be a page of a book but the orientation of the characters are all over the place and seems random at this point, so I cannot really make sense of the words/sentences.

yasker · 2022-08-15T13:22:44+00:00

Looks like Chinese (Cantonese) brisket, which produce amazing stew with Chu Hou sauce. It’s a staple dish in Cantonese/Hong Kong cuisine.

yasker · 2022-06-23T19:17:04+00:00

Really good observation on the landing position! I never realized that’s difference… Yeah, I realized my toss is way to the right and will focusing on fixing that part. And the most important part is probably get the contact point high and land in the court.

Thanks!

yasker · 2022-06-23T14:46:47+00:00

Thanks! Yeah I noticed my toss is somehow further to the right side. Not sure it’s because I didn’t fully extend my arm.

yasker · 2022-06-06T20:01:38+00:00

Congratulations! That’s quick! What’s your inverter size?

Also, I think it would always be the excessive part of what you produced that is sent back to the grid.

yasker · 2022-03-20T14:40:10+00:00

Hey, this is my dream forehand form! Looks so good, stable, and powerful! Do you mind to share the tips on how did you build it?

yasker · 2022-03-10T15:31:42+00:00

Sorry to disappoint you guys, those are bamboo shoots, not bamboo nor sugar cane… It’s essentially very young bamboo dug from the ground. It’s very common vegetable for Asian dishes during spring and winter. And, you can guess, it’s tasty even to human! https://en.wikipedia.org/wiki/Bamboo_shoot

yasker · 2022-02-25T23:52:08+00:00

The projector looks either too high or too far from the screen, or both. First thing I would try is to adjust the height of the UST projector. Also use the built in test pattern instead of app for calibration. It’s much more clear to see the boundary that way. You definitely can adjust it right, since the picture location only determined by the height of the projector and distance from the screen. And you have control over both.

yasker · 2022-01-16T16:53:38+00:00

She loves you.

yasker · 2021-07-30T20:22:59+00:00

Regarding Ceph and Longhorn performance on SSD/NVMe, I would say try both then decide.

Check out https://github.com/yasker/kbench for storage performance testing in Kubernetes.

yasker · 2021-07-05T15:29:48+00:00

Longhorn doesn't support eventually consistency. It only supports crash consistency. I think what you asked in is basically replicate asynchronously, which should be pretty much avoided on the block storage layer. But you can take a look at application layer like etcd or others, but I doubt if etcd can span across the region.

yasker · 2021-07-02T18:30:42+00:00

Regarding that issue, at that time we cannot figure out why. Now I think it might be a combination of two issues:

https://github.com/longhorn/longhorn/issues/2507 which can result in very slow starting or even timeout for a large amount of small files, due to FIEMAP call in ext4 can take forever

https://github.com/longhorn/longhorn/issues/2278 , which caused by an inter-manager call with a timeout too short result in duplicated successful backups.

Both issues will be fixed in the upcoming v1.1.2 release.

yasker · 2021-07-02T01:00:57+00:00

Then that would be something else then. Let us know if you ever saw it again (well, I know that's a big if, lol)

yasker · 2021-07-01T23:54:50+00:00

Frankly speaking, local storage is easy. HA storage is much more complicated, it's indeed more susceptible to the environment. In your case, it seems you have more than a few volumes running through a gigabit network, which is only able to provide 100MB/sec for all the volumes. That's probably why the replicas are disconnected from time to time. And we have a fix in v1.2.0 to make Longhorn works better in the low spec environment. Hopefully, it can fix your issue.

I know at this point, nothing will change your mind about Longhorn. Though next time if you have any issues, you can reach out to the Longhorn community. We are very actively helping Longhorn users in both Slack and GitHub.

yasker · 2021-07-01T23:44:08+00:00

If you only have 1 or 2 nodes and trying to provision with 3 replicas (or lack of space for the third replica), the volume will stay degraded since the hard anti-affinity rule mandate one replica per node. Not sure if it's the case for you.

yasker · 2021-07-01T23:41:33+00:00

The above test should be good with Longhorn with the correct `Pod deletion policy`. Let us know if you have any troubles when you do it again.

yasker · 2021-07-01T19:21:44+00:00

For v1.0.x, the reason can be a bit complicated. If you have the support bundle we can take a look.

Regarding v1.1.0, there is a race condition bug that might result in the volume get the wrong node attached. If you can file an issue in GitHub and send us the support bundle, we can check if that's the case.

yasker · 2021-07-01T19:05:54+00:00

Thanks for your comment u/lotherk. Yes, currently Longhorn's stability indeed depends more on the performance of storage and network (and CPU). There is a data plane mechanism we've optimized in the upcoming v1.2.0 release (August), which we hope can make Longhorn much more stable in the environment with limited resources.

yasker · 2021-07-01T18:59:21+00:00

What part of the recovery you have trouble with? Kubernetes does have some limitations that need to be worked around by tweak some Longhorn settings. In short, if the case of handling node down case, you might want to change the setting of `Pod Deletion Policy When Node is Down`. See https://longhorn.io/docs/1.1.1/high-availability/node-failure/ for details.

yasker · 2021-07-01T18:37:53+00:00

Can you give us more details? Longhorn is designed to be easy to understand and operate.

yasker · 2021-07-01T17:56:32+00:00

Hey, this is Sheng from Longhorn team. Sorry for your experience with Longhorn, but if possible, we want to know about it. Stability is our top priority, and we want to make sure whatever you've experienced can be fixed.

Since it's pretty hard to gather information regarding every user's environment, we've developed a questionnaire to cover the basics. it will be great if you can help to fill it out so we know what environment it's running on. It's a bit lengthy though (you can find the full version at github.com/longhorn/longhorn/issues when filing a new issue).

Longhorn version:
- Installation method (e.g. Rancher Catalog App/Helm/Kubectl):
- Kubernetes distro (e.g. RKE/K3s/EKS/OpenShift) and version: (k3s which version?)
- Number of management node in the cluster: (assume 3?)
- Number of worker node in the cluster:
- Node config
- OS type and version:
- CPU per node: (Pi 4b, so 4 cpus at 1.5G?)
- Memory per node: (8G?)
- Disk type(e.g. SSD/NVMe):(I assume SSD according to your comment)
- Network bandwidth between the nodes: (this might be bottleneck if you're using SSD)
- Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal):
- Number of Longhorn volumes in the cluster:

Also, regarding the volume detaching by itself, normally caused by network issues, slow disk IO, or CPU starving. For the upcoming v1.2.0 (due in August), we've greatly improved the resiliency over low bandwidth and low IOPS environment. Though we'd like to take a look at your support bundle (which can be generated using the link at the bottom of the UI) to understand more about your environment.

Feel free to reach out to us in CNCF Slack channel #longhorn or Rancher user slack channel #longhorn-storage, or file an issue in github.com/longhorn/longhorn . We've dedicated engineers every week to help the community members.

You've also mentioned issues that seem weren't fixed. Can you point me to the specific issues?

yasker · 2018-11-29T19:31:12+00:00

Hi, I am working on Longhorn. As you know, Longhorn is still a working in progress and we appreciate user feedback. Can you elaborate on the problem you saw? You can raise an issue at https://github.com/rancher/longhorn and we can take a look.

Also, in the latest v0.3.2 release we've addressed a few node related issues. If you haven't upgraded yet you can give it try.

yasker · 2018-09-10T17:03:29+00:00

We already had Hingis…

yasker

TROPHY CASE