GitHub - goharbor/harbor: An open source trusted cloud native registry project that stores, signs, and scans content.
Note: The main branch may be in an unstable or even broken state during development. Please use releases instead of the main branch in order to get a stable set of binaries. Harbor is an open source trusted cloud native registry project that stores, signs, and scans content. Harbor extends the open source Docker Distribution by adding the functionalities usually required by users such as security,
The revenge of the listening sockets
Back in November we wrote a blog post about one latency spike. Today I'd like to share a continuation of that story. As it turns out, the misconfigured rmem setting wasn't the only source of added latency. It looked like Mr. Wolf hadn't finished his job. After adjusting the previously discussed rmem sysctl we continued monitoring our systems' latency. Among other things we measured ping times to o
時系列DBã£ã¦çµå±€ã©ã‚ŒãŒã„ã„ã‚“ã ã£ã‘ #TSDB - weblog of key_amb
※4/6 ãã®å¾Œèª¿ã¹ãŸæƒ…å ±ãªã©ã‚’記事末尾ã«è¿½è¨˜ å‰æã¨ãªã‚‹ãƒ‹ãƒ¼ã‚º サーãƒã®è² è·æƒ…å ±ã¨ã‹ã€ã‚¢ã‚¯ã‚»ã‚¹çŠ¶æ³ã®ã‚ˆã†ãª KPI ã‚’å–得・ä¿å˜ã—ã€å¯è¦–化(å‚ç…§ã—ã¦ã‚°ãƒ©ãƒ•åŒ–)ã—ãŸã„。 リアルタイム性ãŒè¦æ±‚ã•ã‚Œã‚‹ã€‚5分以上å‰ã®ãƒ‡ãƒ¼ã‚¿ã—ã‹è¦‹ã‚Œã¾ã›ã‚“ã¿ãŸã„ãªã®ã¯ãŠå‘¼ã³ã§ãªã„。 å¤ã„データã¯ãã‚“ãªã«ç²¾åº¦ã¯æ°—ã«ã—ãªã„ã‘ã©ã€ãƒãƒ³ã‚°ã‚¹ãƒ‘ンã§ä¿¯çž°ã—ã¦è¦‹ã‚ŒãŸã‚‰ä¾¿åˆ©ã€‚ 最近ã¯ãƒ“ッグデータ環境ã®æ™‚系列データ解æžã‚‚ビジãƒã‚¹ã§ã¯ã‘ã£ã“ã†ãƒ‹ãƒ¼ã‚ºãŒã‚ã‚Šãã†ã ã‘ã©ã€ãã£ã¡ã¯ã‚‚ã†å°‘ã—è¦æ±‚ãŒå¤šãã†ã€‚ ã“ã“ã§ã¯è€ƒãˆãªã„ã“ã¨ã«ã™ã‚‹ã€‚ é¸æŠžè‚¢ã«ãªã‚Šãã†ãªã‚‚ã® å¤ãよã RRDtool Elasticsearch + Kibana Graphite + Grafana InfluxDB + Grafana ç‰ Zabbix ä»–ã«ã€ç¾å®Ÿçš„ã«ã¯ SaaS ã«ä»»ã›ã‚‹ã¨ã„ã†æ‰‹æ®µã‚‚ã‚ã‚‹ã ã‚ã†ã‘ã©ã€ãã†è¨€ã†ã¨è©±ãŒçµ‚ã‚ã£ã¦ã—ã¾ã„ãã†ãªã®ã§ã€ã“ã“ã§ã¯è€ƒãˆãªã„ã“ã¨
ä¹…ã—ã¶ã‚Šã«ãƒ‡ãƒ–ã®è–地「喫茶Yã€ã«è¡Œã£ãŸã‚‰ç›¸å¤‰ã‚らãšå‡„ã‹ã£ãŸã€‚ - Debooï¼JAPAN
ä¹…ã—ã¶ã‚Šã«å–«èŒ¶Yã¸è¡Œã£ã¦ãã¾ã—ãŸã€‚å°‘ã—å¯åŠã—ãŸã®ã§æ™‚é–“ã¯10時åŠé ƒã ã£ãŸã§ã—ょã†ã‹ã€‚モーニングã¨ãƒ©ãƒ³ãƒã®ç‹é–“ã®æ™‚é–“ã«è¨ªå•ã—ã¾ã—ãŸã€‚ 特別è¦æˆ’実施ä¸ã¨ã®ã‚·ãƒ¼ãƒ«ã€‚è¦æˆ’ã™ã‚‹ã®ã¯ãŠåº—より客ã®æ–¹ã§ã¯ãªã„ã‹ã¨æ€ã„ãªãŒã‚‰ã‚‚入店ã—ã¾ã™ã€‚ ä¸ã«ã¯äºŒçµ„ã®å®¢ãŒã„ã¾ã—ãŸã€‚ ・1組目(ç”·3å) ãŠãらã常連ã¨æ€ã—ã彼らã¯ã™ã§ã«é£Ÿäº‹ã‚’終ãˆã€ä½™éŸ»ã«æµ¸ã£ã¦ã„ã¾ã—ãŸã€‚店主ã¨ã‚‚仲良ã•ãã†ãªé–“柄。 ・2組目(男女å„1å) 若干メタボ気味ãªç”·æ€§ã¨ã€ãƒ¢ãƒ‡ãƒ«ã®ã‚ˆã†ã«ç´°ã„女性ãŒã„ã¾ã—ãŸã€‚二人ã®é–¢ä¿‚ã¯ãŸã¶ã‚“æ‹äººã®ã‚ˆã†ã§ã™ã€‚ã“ã¡ã‚‰ã®çµ„ã¯ã¾ã 入店ã—ãŸã°ã‹ã‚Šã®ã‚ˆã†ã§ã€æ¥½ã—ãã†ã«è©±ã—ãªãŒã‚‰ãƒ¡ãƒ‹ãƒ¥ãƒ¼ã‚’見ã¦ã„ã¾ã—ãŸã€‚ãŠãらã一見ã•ã‚“。 男女より後ã«å…¥åº—ã—ã¾ã—ãŸãŒã€å‘ã“ã†ã¯ã¾ã 決ã‚ã‹ãã¦ã„るよã†ãªã®ã§åƒ•ã¯ã‚«ãƒ„サンドを注文ã—ã¾ã—ãŸã€‚店主ã‹ã‚‰ã€Œä»Šãƒˆãƒ³ã‚«ãƒ„ãŒãªã„ã‹ã‚‰ãƒã‚ンカツã§ã‚‚ã„ã„ã‹ãªï¼Ÿãˆãˆãªï¼Ÿã‚ˆã£ã—ゃã€ã¨èžã‹ã‚Œè¨€ã‚ã‚Œã¾ã—ãŸã€‚逆らãˆã¾ã›ã‚“ã€ãƒã‚ンカツサン
btrfs: fix crash/invalid memory access on fsync when using overlayfs - kernel/git/torvalds/linux.git - Linux kernel source tree
btrfs: fix crash/invalid memory access on fsync when using overlayfs If the lower or upper directory of an overlayfs mount belong to a btrfs file system and we fsync the file through the overlayfs' merged directory we ended up accessing an inode that didn't belong to btrfs as if it were a btrfs inode at btrfs_sync_file() resulting in a crash like the following: [ 7782.588845] BUG: unable to handle
Introducing Dockercast – the Docker Podcast | Docker Blog
Products Docker DesktopContainerize your applicationsDocker HubDiscover and share container imagesDocker ScoutSimplify the software supply chainDocker Build Cloud Speed up your image buildsTestcontainers Desktop Local testing with real dependenciesTestcontainers Cloud Test without limits in the cloud See our product roadmapMORE resources for developers
リリースã€éšœå®³æƒ…å ±ãªã©ã®ã‚µãƒ¼ãƒ“スã®ãŠçŸ¥ã‚‰ã›
最新ã®äººæ°—エントリーã®é…ä¿¡
j次ã®ãƒ–ックマーク
kå‰ã®ãƒ–ックマーク
lã‚ã¨ã§èªã‚€
eコメント一覧を開ã
oページを開ã
{{#tags}}- {{label}}
{{/tags}}