Hi Shekar,
I do not have much experience in setting up the HA. So if I were you, I may
check 1) when you take the RM down, does the backup RM runs successfully?
2) if the backup RM runs successfully, can you see the Samza Application
run in the Yarn UI (such as, localhost:8088?) 3) if can not see
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/34206/#review83938
---
Ship it!
I am +1 for the overall API design. Lets push this to
On May 15, 2015, 4:27 p.m., Milinda Pathirage wrote:
samza-sql-core/src/main/java/org/apache/samza/sql/api/data/Table.java, line
36
https://reviews.apache.org/r/34206/diff/2/?file=960924#file960924line36
How about supporting multi column primary keys? We can add it to the
API
Hi, Shekar.
The failed happens when:
*sprdargas403t/10.180.195.33 to sprdargas403:8031*
I suggest that you verify:
1)* $nmap -sT sprdargas * to check whether the port 8031 is open;
2) Use *traceroute* to check if the name of machine is being resolved
correctly;
3) Check your /etc/hosts
I think I figured it out.
stop-yarn.sh and start-yarn.sh restarts resourcemanager on the same node
but not on all other nodes.
The workaround is to go to all rm nodes and start rm individually.
I see that these scripts invoke another command yarn-daemon.sh which takes
a argument --hosts. I tried
