$ ssh remote-host "epmd -names"
epmd: up and running on port 4369 with data:
name some_node at port 58769
Note the running on port for epmd itself and the port of the node you're interested in debugging. Reconnect to the remote host with these ports forwarded:
$ ssh -L 4369:localhost:4369 -L 58769:localhost:58769 remote-host
| { | |
| "servers" : [ | |
| { | |
| "queries" : [ | |
| { | |
| "resultAlias" : "jvmMemory", | |
| "obj" : "java.lang:type=Memory", | |
| "attr" : [ | |
| "HeapMemoryUsage", | |
| "NonHeapMemoryUsage" |
| defmodule Check do | |
| def is_utf8?(""), do: true | |
| def is_utf8?(<< char :: size(8), rest :: binary >>) when char <= 0x7f, do: is_utf8?(rest) | |
| def is_utf8?(<< f :: size(8), s :: size(8), rest :: binary >>) | |
| when f >= 0xc0 and f <= 0xdf and # 110* **** | |
| s >= 0x80 and s <= 0xbf do # 10** **** | |
| is_utf8?(rest) | |
| end |
The following are examples of the four types rate limiters discussed in the accompanying blog post. In the examples below I've used pseudocode-like Ruby, so if you're unfamiliar with Ruby you should be able to easily translate this approach to other languages. Complete examples in Ruby are also provided later in this gist.
In most cases you'll want all these examples to be classes, but I've used simple functions here to keep the code samples brief.
This uses a basic token bucket algorithm and relies on the fact that Redis scripts execute atomically. No other operations can run between fetching the count and writing the new count.
| #!/bin/sh | |
| ## package install | |
| cd /tmp | |
| wget -c https://s3-us-west-2.amazonaws.com/grafana-releases/release/grafana-4.4.1.linux-x64.tar.gz | |
| tar zxvf grafana-4.4.1.linux-x64.tar.gz -C /usr/local && mv /usr/local/grafana{-4.4.1,} | |
| wget -c https://dl.influxdata.com/influxdb/releases/influxdb-1.2.4_linux_amd64.tar.gz | |
| tar xvfz influxdb-1.2.4_linux_amd64.tar.gz -C /usr/local && mv /usr/local/influxdb{-1.2.4-1,} | |
| wget -c https://dl.influxdata.com/telegraf/releases/telegraf-1.3.4_linux_amd64.tar.gz | |
| tar xvfz telegraf-1.3.4_linux_amd64.tar.gz -C /usr/local && mv /usr/local/telegraf{-1.3.4,} |
| { | |
| "__inputs": [ | |
| { | |
| "name": "DS_INFLUXDB", | |
| "label": "influxdb", | |
| "description": "", | |
| "type": "datasource", | |
| "pluginId": "influxdb", | |
| "pluginName": "InfluxDB" | |
| } |
| package main | |
| import ( | |
| "bufio" | |
| "flag" | |
| "fmt" | |
| "io" | |
| "io/ioutil" | |
| "log" | |
| "net/http" |
| #!/bin/bash | |
| # Author: Delweng Zheng <[email protected]> | |
| if $(lsmod | grep -q "ip_vs"); then | |
| exit 0 | |
| fi | |
| if [ -f /etc/redhat-release ]; then | |
| RELEASE="centos" | |
| elif cat /etc/issue | grep -Eqi "debian"; then |
So yeah... no documentation for the HBase REST API in regards to what should a filter look like...
So I installed Eclipse, got the library, and took some time to find some of the (seemingly) most useful filters you could use. I'm very green at anything regarding HBase, and I hope this will help anyone trying to get started with it.
What I discovered is that basically, attributes of the filter object follow the same naming than in the documentation. For this reason, I have made the link clickable and direct them to the HBase Class documentation attached to it; check for the instantiation argument names, and you will have your attribute list (more or less).
| # coding=utf-8 | |
| import math | |
| import os | |
| import random | |
| import tensorflow as tf | |
| import dataset_utils | |
| import argparse | |
| # 定义一些全局常量 |