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
ã¯ããã« æè¿ã¯ãã£ã±ãIoTé¢é£ã®æ¡ä»¶ãæ å½ãã¦ãã¾ãã AWSã使ã£ã¦ããã®ã§ãDynamoDBã«ããã¤ã¹ããã®ãã¼ã¿ãæºãè¾¼ãã ãããã®ãã¼ã¿ãåå¾ãã¦å¯è¦åããããªã©ãããã¨ãå¤ãããã®éã«ã¯Lambdaã大活èºãã¦ãã¾ãã 主ã«Node.jsã使ã£ã¦ãããæ¡ä»¶ã«å¿ãã¦Pythonã§ãå®è£ ããã¦ãã¦ãèªåã®ä¸ã§ãã³ãã¬ã¼ãåãã¦ãããªã¼ã¨æã£ãã®ã§ã¾ã¨ãã¦ãããã£ã¨ãªã DynamoDBã«ãã¼ã¿ãPutãã 主ã«ããã¤ã¹ããåãã¨ã£ããã¼ã¿ãDynamoDBã«æ¸ãè¾¼ã¿ã¾ãã æ¬æ¥ã§ããã°ãã¼ã¿ãå å·¥ããå¿ è¦ãããã¾ãããããã¯ããã¤ã¹ã«ãã£ã¦å¤ç¨®å¤æ§ã§ãã®ã§å²æãã¾ãã ããã§éè¦ãªã®ã¯ãPartitionKeyã¨SortKeyã®æå®ã§ãã ãããééãã¦ãã¾ãã¨ã¨ã©ã¼ãåãã¦ãã¾ãã(Keyæ å ±ãééã£ã¦ããï¼çãªæã) Node.js const AWS = require("
ããããã㨠ããã¤ã³ã¹ã¿ã³ã¹ã§åãã¦ã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
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
å æ¥ 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
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.
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
ããä¸ã¶æãããããJavaScriptãæ³¨ç®ããã¦ããããã ãçç±ã¯ç°¡åã§ãGoogleã®JavaScriptã¨ã³ã¸ã³ã使ã£ãã¢ããªã±ã¼ã·ã§ã³ã»ãµã¼ãã¼ã§ããnode.jsã®æ§è½ãé«ãã¨ä¸»å¼µããã¦ããããã ã å°å³ã«ãã¼ã ã«ãªãã¤ã¤ãããAjaxã®ããã«ã¦ã§ãéçºã®ç¾å ´ã«å®çããããç¥ããªãã夿°ã®ããã°ã§ç´¹ä»ãããã¦ãããç¾ç¶ã®ãã®ç¹å¾´ãæ¯ãè¿ãã¤ã¤ãnode.jsãæ®åããããèå¯ãã¦ã¿ãã 1. JavaScriptã¯ããã©ã¦ã¶çºã®äººæ°ã¹ã¯ãªããè¨èª JavaScriptã¯ãLiveScriptã¨ãã¦1995å¹´ã«Netscape Navigatorã¨ããã¦ã§ãã»ãã©ã¦ã¶ã«æè¼ãããã®ãå§ã¾ãã§ãããã«æ¿æ²»çãªçç±ã§JavaScriptã«æ¹åãããã1996å¹´ã«ã¯ããã®åºæ¬çãªææ³ãECMAScriptã¨ãã¦ãECMA-262ã¨ISO/IEC 16262ã§å®ç¾©ããã¦ãããè¨èªä»æ§ãç°¡
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
ã¡ã³ããã³ã¹
ã©ã³ãã³ã°
ãç¥ãã
ãªãªã¼ã¹ãé害æ å ±ãªã©ã®ãµã¼ãã¹ã®ãç¥ãã
ææ°ã®äººæ°ã¨ã³ããªã¼ã®é ä¿¡
å¦çãå®è¡ä¸ã§ã
j次ã®ããã¯ãã¼ã¯
kåã®ããã¯ãã¼ã¯
lãã¨ã§èªã
eã³ã¡ã³ãä¸è¦§ãéã
oãã¼ã¸ãéã
{{#tags}}- {{label}}
{{/tags}}