diff --git a/README.md b/README.md index 1c7f47f2a..a74a32498 100644 --- a/README.md +++ b/README.md @@ -1,33 +1,19 @@ --- layout: page -title: About +title: About Me permalink: /about/ --- -## Theme Monos -> Simple and lightweight theme for Jekyll +## In a nutshell +* Position: Data Engineer +* E-mail: seolgi911@gmail.com +* Linked In: [링크드인 주소 바로가기](https://www.linkedin.com/in/%EC%8A%AC%EA%B8%B0-%EA%B0%95-991769187/) -### Features -- Responsive. -- Syntax Highlight -- Most optimized theme for tech blog. -- Lightweight with minimum stylesheet. -- Easy to customize. -- Offers category menu. - -### _config.yml -> Code block will look like this. -```yml -highlighter-theme: monokai //you can change your syntax color scheme. -date_format: "%Y-%M-%D" //and date format. -``` - -### Screenshots -#### Page -![alt text](/public/img/screenshot-1.png) -#### Articles -![alt text](/public/img/screenshot-2.png) -#### Page - Mobile -![alt text](/public/img/screenshot-m1.png) -#### Page - Articles -![alt text](/public/img/screenshot-m2.png) +### Skills +* Java +* Elastic Stack +* Kafka +* JavaScript +* Scala +* Spark +* ![update_icon](/public/img/update_icon.png) 업데이트중 diff --git a/_config.yml b/_config.yml index 529bf07b5..bc2b007bd 100644 --- a/_config.yml +++ b/_config.yml @@ -18,13 +18,13 @@ # You can create any custom variable you would like, and they will be accessible # in the templates via {{ site.myvariable }}. -title: Monos -email: ejjoo7994@gmail.com +title: Arisong +email: seolgi911@gmail.com description: >- # this means to ignore newlines until "baseurl:" - Themed by ejjoo + Data Engineer # baseurl: "/" # the subpath of your site, e.g. /blog -# url: "http://ejjoo.github.io" # the base hostname & protocol for your site, e.g. http://example.com -github_username: ejjoo +url: "https://arisong-kang.github.io/" # the base hostname & protocol for your site, e.g. http://example.com +github_username: arisong-Kang highlighter: rouge svg: optimize: true @@ -56,3 +56,5 @@ tag_dir: tag/ # - vendor/cache/ # - vendor/gems/ # - vendor/ruby/ + +disqus_shortname: arisong-kang.github.io \ No newline at end of file diff --git a/_includes/home.html b/_includes/home.html index c86502d60..c46da902f 100644 --- a/_includes/home.html +++ b/_includes/home.html @@ -1,6 +1,6 @@
-
Articles
+
Posts
diff --git a/_includes/page.html b/_includes/page.html index 9b5e7e15d..82cc33e70 100644 --- a/_includes/page.html +++ b/_includes/page.html @@ -1,6 +1,6 @@
-
+
{{ page.title | escape }}
diff --git a/_includes/post.html b/_includes/post.html index 0a6ea3c2b..4f4145ee8 100644 --- a/_includes/post.html +++ b/_includes/post.html @@ -12,4 +12,26 @@
{{ content }}
+ +
>
+ +
\ No newline at end of file diff --git a/_includes/sidebar.html b/_includes/sidebar.html index 0f1e4b94d..de0d5a769 100644 --- a/_includes/sidebar.html +++ b/_includes/sidebar.html @@ -15,7 +15,7 @@
-

Powered by Jekyll

+

Powered by skkang

\ No newline at end of file diff --git a/_layouts/page.html b/_layouts/page.html index 5594215f8..3a1e5bbf4 100644 --- a/_layouts/page.html +++ b/_layouts/page.html @@ -1,4 +1,6 @@ --- layout: default + +comments: true --- {% include page.html %} \ No newline at end of file diff --git a/_posts/2020-01-02-post1.markdown b/_posts/2020-01-02-post1.markdown deleted file mode 100644 index 0ab0ff599..000000000 --- a/_posts/2020-01-02-post1.markdown +++ /dev/null @@ -1,13 +0,0 @@ ---- -layout: post -title: post-sample -date: 2020-01-02 19:20:23 +0900 -category: sample ---- -# post-sample -> Hello! - -This is code -```ruby -print 'hello world' -``` \ No newline at end of file diff --git a/_posts/2020-01-02-welcome-to-jekyll.markdown b/_posts/2020-01-02-welcome-to-jekyll.markdown deleted file mode 100644 index c94ca9a76..000000000 --- a/_posts/2020-01-02-welcome-to-jekyll.markdown +++ /dev/null @@ -1,29 +0,0 @@ ---- -layout: post -title: "Welcome to Jekyll!" -date: 2020-01-02 19:31:29 +0900 -categories: jekyll update ---- -You’ll find this post in your `_posts` directory. Go ahead and edit it and re-build the site to see your changes. You can rebuild the site in many different ways, but the most common way is to run `jekyll serve`, which launches a web server and auto-regenerates your site when a file is updated. - -Jekyll requires blog post files to be named according to the following format: - -`YEAR-MONTH-DAY-title.MARKUP` - -Where `YEAR` is a four-digit number, `MONTH` and `DAY` are both two-digit numbers, and `MARKUP` is the file extension representing the format used in the file. After that, include the necessary front matter. Take a look at the source for this post to get an idea about how it works. - -Jekyll also offers powerful support for code snippets: - -{% highlight ruby %} -def print_hi(name) - puts "Hi, #{name}" -end -print_hi('Tom') -#=> prints 'Hi, Tom' to STDOUT. -{% endhighlight %} - -Check out the [Jekyll docs][jekyll-docs] for more info on how to get the most out of Jekyll. File all bugs/feature requests at [Jekyll’s GitHub repo][jekyll-gh]. If you have questions, you can ask them on [Jekyll Talk][jekyll-talk]. - -[jekyll-docs]: https://jekyllrb.com/docs/home -[jekyll-gh]: https://github.com/jekyll/jekyll -[jekyll-talk]: https://talk.jekyllrb.com/ diff --git a/_posts/2021-03-23-Elasticsearch Review.markdown b/_posts/2021-03-23-Elasticsearch Review.markdown new file mode 100644 index 000000000..7e619f944 --- /dev/null +++ b/_posts/2021-03-23-Elasticsearch Review.markdown @@ -0,0 +1,108 @@ +--- + +layout: post + +title: "Elasticsearch Review" + +date: 2021-03-23 10:00:00 +0900 + +categories: elasticsearch + +comments: true + +--- + + + +```markdown +* Elasticsearch 를 스터디 및 운영하면서 정리한 내용 모음집 +``` + + + + + + +# 인덱스당 적정한 샤드와 레플리카 수 + +* 클러스터내 노드 사이에 이동하는 가장 작은 단위의 파일 +* 샤드의 개수는 인덱스가 아닌 노드와 밀접한 관련 +* (김종민 elastic avangelist)경험상 1개 노드에 700개 이상의 샤드가 쌓이지 않게 하는 것이 중요 +* 그 이상이 되는 경우 Disk I/O, Network I/O로 인한 병목 현상 심각 + + + +# 인덱스당 적절한 사이즈 + +* 위와 같은 이유로 인덱스당 사이즈가 아닌 샤드당 사이즈가 중요 +* 샤드의 1개 사이즈는 20~30GB 권고 +* 검색 위주의 클러스터면 20GB에 가까울수록 좋고, 단순 로깅 목적이라면 50GB 까지도 고려가능 + + + + + +# 오래된 인덱스를 관리할 방법? + +* Timeseries data라면 rollover index 를 사용이 편리 +* 조금 더 깊은 레벨로 관리하고 싶다면 Curator(인덱스 관리 도구) 사용 검토필요 + * 기능 리스트 : [https://www.elastic.co/guide/en/elasticsearch/client/curator/5.4/about.html](https://www.elastic.co/guide/en/elasticsearch/client/curator/5.4/about.html) + * 깃허브 링크 : [https://github.com/elastic/curator](https://github.com/elastic/curator) +* Rollup API + * 오래된 인덱스의 필요한 통계치만 저장하여 저장 공간을 쉽게 줄여주는 데이터 관리 방법중 하나 + * 데이터를 미리 aggregation 하여 통계 데이터만 보는 방법 + * query&aggregaion을 미리 등록해두고 scedule을 설정하는 것으로 사용 가능 + * 참고 페이지 : [https://www.elastic.co/guide/en/elasticsearch/reference/master/rollup-job-config.html](https://www.elastic.co/guide/en/elasticsearch/reference/master/rollup-job-config.html) + + + + + +# 검색 속도 튜닝 + +* 참고페이지: [https://www.elastic.co/guide/en/elasticsearch/reference/master/tune-for-search-speed.html](https://www.elastic.co/guide/en/elasticsearch/reference/master/tune-for-search-speed.html) +* 파일 시스템 캐시에 메모리 부여 +* SSD, 빠른 CPU 사용 +* Document Modeling + * 가능한 가벼운 검색이 될수있도록 모델링 + * nested, parent-child 구조는 검색이 느려지게 함 +* 가능한 한 적은 수의 필드 검색 + * 'query_string' or 'multi_match' 쿼리에서 대상 필드가 많을 경우 느려짐 + * 'copy_to' 를 활용하면 쿼리 대상 필드를 줄여서 쿼리할 수 있음 +* 숫자 필드의 경우 keyword 보다는 integer 또는 long 으로 매핑 +* [Adaptive Replica Selection](https://www.elastic.co/guide/en/elasticsearch/reference/current/tune-for-search-speed.html#_turn_on_adaptive_replica_selection) + + + + + +# 인덱싱 성능 고려사항 + +* 참고페이지: [https://www.elastic.co/blog/performance-considerations-elasticsearch-indexing](https://www.elastic.co/blog/performance-considerations-elasticsearch-indexing) + + + + + +# index를 close 할 때의 이점 + +* 참고페이지: https://www.elastic.co/guide/en/elasticsearch/reference/6.3/indices-open-close.html +* close는 말 그대로 메모리에 안 띄워두고 파일을 닫아둠 +* 저장공간 빼곤 일체의 리소스를 차지 안함 +* ES 샤드 형태로 오래도록 저장해두고, 검색이 필요없는 경우 close 적합 +* 인덱스가 필요해지면 open해서 사용가능 +* elasticsearch 6.6부터 frozen indices 기능 추가 + * 기본적으로 close indices와 같음 + * 검색요청이 들어오면 open 하여 검색하고 자동으로 다시 close 시킴 + + + + + + + + + + + +--- diff --git a/public/css/style.css b/public/css/style.css index fd2620934..30e25e976 100644 --- a/public/css/style.css +++ b/public/css/style.css @@ -98,7 +98,7 @@ code { flex: 0 0 220px; padding: 15px; z-index: 1; - background-color: #222; + background-color: #00004d; color: #fff; } diff --git a/public/css/syntax/README.md b/public/css/syntax/README.md deleted file mode 100644 index c3d5775ee..000000000 --- a/public/css/syntax/README.md +++ /dev/null @@ -1,22 +0,0 @@ -# pygments-css - - -[Pygments](http://pygments.org), a Python-based code highlighting tool, comes with a set of builtin styles (not css files) for code highlighting. You have to generate a CSS file using the command line. - -You can generate these yourself, but this git repository has already generated them for you. - - -build ------ - -These css files were generated using pygmentize on the command line like so:: - - pygmentize -S default -f html -a .highlight > default.css - -You can remove or change the top-level class by removing or modifying `-a .highlight` in the `makefile`. - -To regenerate them all with whichever ``pygments`` version you are using, run - - git clone - cd pygments-css - make cssfiles diff --git a/public/css/syntax/package.json b/public/css/syntax/package.json index 195fa734c..46e9bc6e0 100644 --- a/public/css/syntax/package.json +++ b/public/css/syntax/package.json @@ -10,6 +10,5 @@ "license": "UNLICENSE", "bugs": { "url": "https://github.com/richleland/pygments-css/issues" - }, - "homepage": "https://github.com/richleland/pygments-css#readme" + } } diff --git a/public/img/cat.JPG b/public/img/cat.JPG new file mode 100644 index 000000000..ab9adc414 Binary files /dev/null and b/public/img/cat.JPG differ diff --git a/public/img/update_icon.png b/public/img/update_icon.png new file mode 100644 index 000000000..063882fed Binary files /dev/null and b/public/img/update_icon.png differ