Node.js heap out of memory
Today I ran my script for filesystem indexing to refresh RAID files index and after 4h it crashed with following error: [md5:] 241613/241627 97.5% [md5:] 241614/241627 97.5% [md5:] 241625/241627 98.1% Creating missing list... (79570 files missing) Creating new files list... (241627 new files) <--- Last few GCs ---> 11629672 ms: Mark-sweep 1174.6 (1426.5) -> 1172.4 (1418.3) MB, 659.9 / 0 ms [alloca
Lambdaã§DynamoDBã®ãƒ‡ãƒ¼ã‚¿ã‚’æ“作ã™ã‚‹(Node&Python) - Qiita
ã¯ã˜ã‚㫠最近ã¯ã‚‚ã£ã±ã‚‰IoT関連ã®æ¡ˆä»¶ã‚’担当ã—ã¦ã„ã¾ã™ã€‚ AWSを使ã£ã¦ã„ã‚‹ã®ã§ã€DynamoDBã«ãƒ‡ãƒã‚¤ã‚¹ã‹ã‚‰ã®ãƒ‡ãƒ¼ã‚¿ã‚’溜ã‚込んã ã‚Šã€ãã®ãƒ‡ãƒ¼ã‚¿ã‚’å–å¾—ã—ã¦å¯è¦–化ã—ãŸã‚Šãªã©ã™ã‚‹ã“ã¨ãŒå¤šãã€ãã®éš›ã«ã¯LambdaãŒå¤§æ´»èºã—ã¦ã„ã¾ã™ã€‚ 主ã«Node.jsを使ã£ã¦ãŠã‚Šã€æ¡ˆä»¶ã«å¿œã˜ã¦Pythonã§ã‚‚実装をã—ã¦ã„ã¦ã€è‡ªåˆ†ã®ä¸ã§ãƒ†ãƒ³ãƒ—レート化ã—ã¦ããŸãªãƒ¼ã¨æ€ã£ãŸã®ã§ã¾ã¨ã‚ã¦ãŠã“ã†ã£ã¨ãªã€‚ DynamoDBã«ãƒ‡ãƒ¼ã‚¿ã‚’Putã™ã‚‹ 主ã«ãƒ‡ãƒã‚¤ã‚¹ã‹ã‚‰å—ã‘ã¨ã£ãŸãƒ‡ãƒ¼ã‚¿ã‚’DynamoDBã«æ›¸ãè¾¼ã¿ã¾ã™ã€‚ 本æ¥ã§ã‚ã‚Œã°ãƒ‡ãƒ¼ã‚¿ã‚’åŠ å·¥ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ãŒã€ãã“ã¯ãƒ‡ãƒã‚¤ã‚¹ã«ã‚ˆã£ã¦å¤šç¨®å¤šæ§˜ã§ã™ã®ã§å‰²æ„›ã—ã¾ã™ã€‚ ã“ã“ã§é‡è¦ãªã®ã¯ã€PartitionKeyã¨SortKeyã®æŒ‡å®šã§ã™ã€‚ ã“ã“ã‚’é–“é•ãˆã¦ã—ã¾ã†ã¨ã‚¨ãƒ©ãƒ¼ã‚’åã„ã¦ãã¾ã™ã€‚(Keyæƒ…å ±ãŒé–“é•ã£ã¦ã‚‹ãœï¼çš„ãªæ„Ÿã˜) Node.js const AWS = require("
Elasticsearchã®ãƒ‡ãƒ¼ã‚¿ã‚’dumpã—ã¦ã‚³ãƒ”ーã—ãŸã„ - DRYãªå‚™å¿˜éŒ²
ã‚„ã‚ŠãŸã„ã“㨠ã‚るインスタンスã§å‹•ã„ã¦ã‚‹Elasticsearchサーãƒã®ã‚¤ãƒ³ãƒ‡ãƒƒã‚¯ã‚¹ãƒ‡ãƒ¼ã‚¿ã®dumpã‚’ã€ãŸã¨ãˆã°è‡ªåˆ†ã®ãƒãƒ¼ã‚«ãƒ«ã«ã‚³ãƒ”ーã—ãŸã„ ã“ã‚“ãªã®ãŒã‚ã‚‹ elasticdump ã“れ便利ã ã£ãŸ 最低é™ã®ä½¿ã„方（書ã„ã¦ã‚ã‚‹ã‚“ã§ã™ã‘ã©â†‘） % npm install -g elasticdump % elasticdump --input=http:/my.elasticsearch.server.com:9200/my_index --output=http://localhost:9200/my_index ã‚ã‚‹ã„ã¯ã€ % elasticdump --input=http://my.elasticsearch.server.com:9200/my_index --output=$ | gzip > my_index.json.gz è§£å‡ % gzip -dc my_index.jso
Node.js throws "btoa is not defined" error
In my node.js application I did an npm install btoa-atob so that I could use the btoa() and atob() functions which are native in client-side javascript but for some reason weren't included in node. The new directory showed up in my node_modules folder, which itself is in root alongside app.js. Then I made sure to add btoa-atob as a dependency in my package.json file which is in root. However, for
Kibana-4.5 ã®ãƒ¡ãƒ¢ãƒªä½¿ç”¨é‡ãŒå¢—ãˆç¶šã‘る件ã¸ã®å¯¾å‡¦æ–¹æ³•ã¨çµæžœ
先日 Elasticsearch ã‚’ 1.7.5 ã‹ã‚‰ 2.3.3 ã«ã€Kibana ã‚’ 4.1.2 ã‹ã‚‰ 4.5.1 ã«ã‚¢ãƒƒãƒ—デートã—ã¾ã—ãŸã€‚ アップデート自体ã¯ãã‚Œãªã‚Šã«ãƒãƒžã£ãŸã‚‚ã®ã®ã€ãªã‚“ã¨ã‹å¯¾å‡¦ã§ãã¾ã—ãŸã€‚ ãŸã ã€Kibana ã®ãƒ¡ãƒ¢ãƒªä½¿ç”¨é‡ãŒå¢—ãˆç¶šã‘ã€ã•ãªãŒã‚‰ãƒ¡ãƒ¢ãƒªãƒªãƒ¼ã‚¯ã®ã‚ˆã† ã§ã—ãŸã€‚ ã“ã¡ã‚‰ã®è¨˜äº‹ã®æ–¹æ³•ã§è§£æ±ºã§ããŸã®ã§ã€çµæžœã¨ã¨ã‚‚ã«è¨˜éŒ²ã—ã¾ã™ã€‚ ver4.2以é™ã®kibanaãŒçªç„¶æ»ã™ã‚‹å•é¡Œã«ã¤ã„㦠- mnatsu31’s blog 環境# OS: Ubuntu-14.04 LTS Memory: 2GB Elasticsearch: 2.3.3 Kibana: 4.5.1 ※ Elasticsearch 㨠Kibana ã¯ã¨ã‚‚ã«å…¬å¼ãƒ‘ッケージを使用。 Repositories｜Elasticsearch Reference [2.3]｜Elastic Getting K
io.js - JavaScript I/O
Run JavaScript EverywhereNode.js® is a free, open-source, cross-platform JavaScript runtime environment that lets developers create servers, web apps, command line tools and scripts.
Node.js vs Play Framework
Video: https://www.youtube.com/watch?v=b6yLwvNSDck Here's the showdown you've been waiting for: Node.js vs Play Framework. Both are popular open source web frameworks that are built for developer productivity, asynchronous I/O, and the real time web. But which one is easier to learn, test, deploy, debug, and scale? Should you pick Javascript or Scala? The Google v8 engine or the JVM? NPM or Ivy? G
node.jsã¯æ™®åŠã—ãã†ã«ç„¡ã„
ã“ã“一ヶ月ãらã„ã‹ã‚‰JavaScriptãŒæ³¨ç›®ã•ã‚Œã¦ã„るよã†ã 。ç†ç”±ã¯ç°¡å˜ã§ã€Googleã®JavaScriptエンジンを使ã£ãŸã‚¢ãƒ—リケーション・サーãƒãƒ¼ã§ã‚ã‚‹node.jsã®æ€§èƒ½ãŒé«˜ã„ã¨ä¸»å¼µã•ã‚Œã¦ã„ã‚‹ã‹ã‚‰ã 。 地味ã«ãƒ–ームã«ãªã‚Šã¤ã¤ã‚ã‚Šã€Ajaxã®ã‚ˆã†ã«ã‚¦ã‚§ãƒ–開発ã®ç¾å ´ã«å®šç€ã™ã‚‹ã‹ã‚‚知れãªã„。多数ã®ãƒ–ãƒã‚°ã§ç´¹ä»‹ãŒã•ã‚Œã¦ã„る。ç¾çŠ¶ã®ãã®ç‰¹å¾´ã‚’振り返りã¤ã¤ã€node.jsãŒæ™®åŠã™ã‚‹ã‹ã‚’考察ã—ã¦ã¿ãŸã€‚ 1. JavaScriptã¯ã€ãƒ–ラウザ発ã®äººæ°—スクリプト言語 JavaScriptã¯ã€LiveScriptã¨ã—ã¦1995å¹´ã«Netscape Navigatorã¨ã„ã†ã‚¦ã‚§ãƒ–・ブラウザã«æ載ã•ã‚ŒãŸã®ãŒå§‹ã¾ã‚Šã§ã€ã™ãã«æ”¿æ²»çš„ãªç†ç”±ã§JavaScriptã«æ”¹åã•ã‚ŒãŸã€‚1996å¹´ã«ã¯ã€ãã®åŸºæœ¬çš„ãªæ–‡æ³•ãŒECMAScriptã¨ã—ã¦ã€ECMA-262ã¨ISO/IEC 16262ã§å®šç¾©ã•ã‚Œã¦ã„る。言語仕様ãŒç°¡
node.js
V8 JavaScript を用ã„ãŸã‚¤ãƒ™ãƒ³ãƒˆé§†å‹•I/Oã®å®Ÿç¾ å…¨ã¦ã®ãƒªã‚¯ã‚¨ã‚¹ãƒˆã«å¯¾ã—ã¦"Hello World"ã¨è¿”ç”ã™ã‚‹Nodeã§æ›¸ã‹ã‚ŒãŸWEBサーãƒã®ä¾‹ã§ã™ã€‚ var http = require('http'); http.createServer(function (req, res) { res.writeHead(200, {'Content-Type': 'text/plain'}); res.end('Hello World\n'); }).listen(8124, "127.0.0.1"); console.log('Server running at http://127.0.0.1:8124/'); ã“ã®ã‚µãƒ¼ãƒã‚’走らã›ã‚‹ã«ã¯ã€ã‚³ãƒ¼ãƒ‰ã‚’ example.jsã¨ã„ã†ãƒ•ã‚¡ã‚¤ãƒ«åã§ä¿å˜ã—ã€ä¸‹è¨˜ã®ã‚ˆã†ã« nodeコマンドを実行ã—ã¦ãã ã•ã„。 % node example.js
1
メンテナンス
ランã‚ング
ãŠçŸ¥ã‚‰ã›
リリースã€éšœå®³æƒ…å ±ãªã©ã®ã‚µãƒ¼ãƒ“スã®ãŠçŸ¥ã‚‰ã›
最新ã®äººæ°—エントリーã®é…ä¿¡
j次ã®ãƒ–ックマーク
kå‰ã®ãƒ–ックマーク
lã‚ã¨ã§èªã‚€
eコメント一覧を開ã
oページを開ã
get error 'CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory' · Issue #10536 · nodejs/node · GitHub
Ubuntu ã« node.js インストールã—ãŸã®ã« command not found: node ã¨è¨€ã‚ã‚Œã¦å›°ã£ãŸã¨ãã®å¯¾å¿œæ–¹æ³• ヽ(ﾟｰﾟ*ヽ)(ﾉ*ﾟｰﾟ)ﾉã‚ãã„ - Qiita
{{#tags}}- {{label}}
{{/tags}}