首页 文章 精选 留言 我的

精选列表

搜索[es],共4398篇文章
优秀的个人博客,低调大师

5 月数据库排行榜:ES 排名下跌、Oracle 分数浅增

DB-Engines 数据库流行度排行榜发布了 5 月份的更新。 与上个月的数据相比,各数据库的分数波动不大。Oracle 是本月分数增加最多的数据库,但也只是比上月多了 8 分,而且与去年同期相比,下降了 7.12 分。紧跟其后的 MySQL 和 SQL Server 跟去年同期相比,分数可谓是暴跌,分别下降了 34.28 和 51.46 分。 PostgreSQL 和 Redis 的分数较去年也上涨了不少,分别增加了 56.04 和 16.85 分。此外,Redis 的排名也从去年同期的第 7 名上升到了现在的第 6 名。 和去年同期相比,分数显著上涨的数据库还有 Microsoft Access、MariaDB 和 Snowflake。Snowflake 去年曾获得“2021 年度数据库”称号。 继续看看主流的数据库的分数趋势变化: 最后看看各类型数据库的排名情况。 关系数据库前 10 名 Key-Value 数据库前 10 名 文档数据库前 10 名 时序数据库前 10 名 图数据库前 10 名 DB-Engines 根据流行度对数据库管理系统进行排名,排名每月更新一次。排名的数据依据 5 个不同的指标: Google 以及 Bing 搜索引擎的关键字搜索数量 Google Trends 的搜索数量 Indeed 网站中的职位搜索量 LinkedIn 中提到关键字的个人资料数 Stackoverflow 上相关的问题和关注者数量 这份榜单分析旨在为数据库相关从业人员提供一个技术方向的参考,其中涉及到的排名情况并非基于产品的技术先进程度或市场占有率等因素。无论排名先后,选择适合与企业业务需求相比配的技术才是最重要的。

优秀的个人博客,低调大师

ES不设置副本是非常脆弱的,整个文章告诉了你为什么

Delaying Shard Allocation As discussed way back inScale Horizontally, Elasticsearch will automatically balance shards between your available nodes, both when new nodes are added and when existing nodes leave. Theoretically, this is the best thing to do. We want to recover missing primaries by promoting replicas as soon as possible. We also want to make sure resources are balanced evenly across the cluster to prevent hotspots. In practice, however, immediately re-balancing can cause more problems than it solves. For example, consider this situation: Node 19 loses connectivity to your network (someone tripped on the power cable) Immediately, the master notices the node departure. It determines what primary shards were on Node 19 and promotes the corresponding replicas around the cluster After replicas have been promoted to primary, the master begins issuing recovery commands to rebuild the now-missing replicas. Nodes around the cluster fire up their NICs and start pumping shard data to each other in an attempt to get back to green health status This process will likely trigger a small cascade of shard movement, since the cluster is now unbalanced. Unrelated shards will be moved between hosts to accomplish better balancing Meanwhile, the hapless admin who kicked out the power cable plugs it back in.Node 19 reboots and rejoins the cluster. Unfortunately, the node is informed that its existing data is now useless; the data being re-allocated elsewhere. So Node 19 deletes its local data and begins recovering a different set of shards from the cluster (which then causes a new minor re-balancing dance). If this all sounds needless and expensive, you’re right. It is, butonly when you know the node will be back soon. If Node 19 was truly gone, the above procedure is exactly what we want to happen. To help address these transient outages, Elasticsearch has the ability to delay shard allocation. This gives your cluster time to see if nodes will rejoin before starting the re-balancing dance. Changing the default delay By default, the cluster will wait one minute to see if the node will rejoin. If the node rejoins before the timer expires, the rejoining node will use its existing shards and no shard allocation occurs. This default time can be changed either globally, or on a per-index basis, by configuring thedelayed_timeoutsetting: PUT /_all/_settings { "settings": { "index.unassigned.node_left.delayed_timeout": "5m" } } By using the_allindex name, we can apply this setting to all indices in the cluster The default time is changed to 5 minutes The setting is dynamic and can be changed at runtime. If you would like shards to allocate immediately instead of waiting, you can setdelayed_timeout: 0. Delayed allocation won’t prevent replicas from being promoted to primaries. The cluster will still perform promotions as necessary to get the cluster back toyellowstatus. The allocation of the now-missing replicas will be the only process that is delayed Auto-cancellation of shard relocation What happens if the node comes backafterthe timeout expires, but before the cluster has finished moving shards around? In this case, Elasticsearch will check to see if the on-disk data matches the current "live" data in the primary shard. If the two shards are identical — meaning there have been no new documents, updates or deletes — the master will cancel the on-going rebalancing and restore the on-disk data. This is done since recovery of on-disk data will always be faster than transferring over the network, and since we can guarantee the shards are identical, the process is a win-win. If the shards have diverged (e.g. new documents have been indexed since the node went down), the recovery process will continue as normal. The rejoining node will delete it’s local, out-dated shards and obtain a new set. 本文转自张昺华-sky博客园博客,原文链接:http://www.cnblogs.com/bonelee/p/7444495.html,如需转载请自行联系原作者

资源下载

更多资源
优质分享App

优质分享App

近一个月的开发和优化,本站点的第一个app全新上线。该app采用极致压缩,本体才4.36MB。系统里面做了大量数据访问、缓存优化。方便用户在手机上查看文章。后续会推出HarmonyOS的适配版本。

Mario

Mario

马里奥是站在游戏界顶峰的超人气多面角色。马里奥靠吃蘑菇成长,特征是大鼻子、头戴帽子、身穿背带裤,还留着胡子。与他的双胞胎兄弟路易基一起,长年担任任天堂的招牌角色。

Nacos

Nacos

Nacos /nɑ:kəʊs/ 是 Dynamic Naming and Configuration Service 的首字母简称,一个易于构建 AI Agent 应用的动态服务发现、配置管理和AI智能体管理平台。Nacos 致力于帮助您发现、配置和管理微服务及AI智能体应用。Nacos 提供了一组简单易用的特性集,帮助您快速实现动态服务发现、服务配置、服务元数据、流量管理。Nacos 帮助您更敏捷和容易地构建、交付和管理微服务平台。

Rocky Linux

Rocky Linux

Rocky Linux(中文名:洛基)是由Gregory Kurtzer于2020年12月发起的企业级Linux发行版,作为CentOS稳定版停止维护后与RHEL(Red Hat Enterprise Linux)完全兼容的开源替代方案,由社区拥有并管理,支持x86_64、aarch64等架构。其通过重新编译RHEL源代码提供长期稳定性,采用模块化包装和SELinux安全架构,默认包含GNOME桌面环境及XFS文件系统,支持十年生命周期更新。

用户登录
用户注册